July 2026 October Next Fest Signup Window Compression - What Changed for Micro-Studios Trend Playbook

July 14: marketing posts "we're in October Next Fest" on Discord. July 15: engineering is on vacation and build_label still reads fest-demo-2026-06-rc4. July 22: someone clicks Participate in Steamworks while May depot audit never filed and October RC label receipt is still a verbal "we'll do it when we're back."

July 2026 is the signup compression month for October 2026 Steam Next Fest. Micro-studios that treated the participate button like a marketing checkbox discover in September that signup happened on the wrong depot story, the wrong scope promise, and the wrong vacation handoff. Studios that filed october_fest_signup_receipt_v1.json with gates G1–G6 before August PTO entered summer freeze with one build_label, one demo scope hash, and one on-call map—not a Slack thread asking "which branch did we mean?"

This Trend-Jacking / News Commentary playbook is the July signup economics layer—not the October 6-week timeline (weekly milestone locks), not the October RC label evening (label unity before Addressables freeze), not February signup rush (holiday defer crosswalk). It answers what must be GREEN before you click Participate in July and how October's shorter signup-to-RC runway differs from February 2027's post-holiday scramble.

Non-repetition note: February signup trend owns January 2027 participate gate + December defer crosswalk. October timeline owns T-6…T-0 weekly locks. October RC label evening owns L1–L6 label unity before summer freeze. This URL owns July 2026 signup window compression + vacation handoff crosswalk + october_fest_signup_receipt_v1.json.

Pair BUILD_RECEIPT beginner, March cluster #1–#5 post-fest evidence, and forward #7 summer capsule gradient readability art pass when store art swaps after signup.

Why this matters now (July 2026 signup window)

1. Signup-to-RC compression — October 2026 cohorts report fewer working days between Participate and first fest-demo-2026-10-rc* upload than February 2027 teams expect after holiday re-entry—July signup without receipts leaves August vacation as the only "prep week."
2. Summer vacation handoff — Engineers leave mid-August; signup without vacation coverage map and content-freeze manifest pins means September promotion runs on verbal Discord, not filed evidence.
3. May depot audit debt — Teams that skipped October depot rules in May discover wrong demo_depot_id at July signup—G1 catches drift before participate amplifies it.
4. Post-February evidence sprawl — March cluster expects Monday debrief, velocity exports, and evidence sprint receipts—signup without crosswalk invites hero scope on top of unfrozen post-fest branches.
5. Store page vs binary truth — July marketing updates fest banners while player footer still shows June build_label—signup compresses the public mismatch window.

Direct answer: Before clicking Participate in July, run gates G1–G6, crosswalk vacation handoff + May depot audit, file october_fest_signup_receipt_v1.json, set BUILD_RECEIPT october_fest_signup_ok: true—then declare summer content freeze on a proven label and schedule forward #7 capsule gradient pass before CTR-sensitive store swaps.

Who should read this

Time: ~45 minutes read; ~90 minutes first July signup receipt sprint.

Format ladder (October prep cluster)

Order: July this signup playbook → participate → October RC label evening (if not already GREEN) → summer content freeze → September upload/setlive.

What changed vs February 2027 signup season (qualitative)

Patterns from July 2026 partner-facing threads and October prep post-mortems—no invented signup statistics:

Micro-studios that treated July signup as marketing confirmation repeated September scramble. Studios that filed signup receipt with vacation crosswalk entered August PTO with one on-call row and one content_freeze_label.

Beginner path — three-gate participate model

Beginners do not need all six gates on day one—memorize three blockers before Participate:

If any beginner gate is RED, do not click Participate—file a receipt note and schedule the cousin evening (depot rules, RC label evening, or vacation handoff doc).

Copy the full checklist into release-evidence/ops/october-fest-signup-checklist-2026.md:

# October 2026 Next Fest — before Participate (July window)
target_fest: Steam Next Fest October 2026
signup_owner: producer
participate_clicked_utc: (blank until G1–G6 GREEN)

[ ] G1 — May depot audit GREEN (october_depot_audit_ok)
[ ] G2 — October RC label receipt GREEN OR wednesday smoke baseline (october_rc_label_ok)
[ ] G3 — Vacation handoff map filed — on-call + freeze dates
[ ] G4 — Demo scope one paragraph matches store FAQ (no hero features)
[ ] G5 — fest branch name + depot id in steamworks_map.json
[ ] G6 — october_fest_signup_receipt_v1.json filed
[ ] BUILD_RECEIPT october_fest_signup_ok == true
[ ] Producer sign-off — then click Participate

Beginner mistake: Announcing fest participation on social before G6—creates public pressure to ship September builds on June labels.

Developer path — gates G1–G6

G1–G3 are participate blockers when RED. G4–G5 YELLOW only with producer waiver when store copy intentionally lags one week—document in receipt notes.

G1 May depot audit crosswalk (July catch-up)

Load May depot rules october_depot_audit_receipt_v1.json (or run cold-install row from that playbook) and verify:

jq -e '
  .october_depot_audit_ok == true
  and (.steamworks.demo_depot_id | length > 0)
' october_depot_audit_receipt_v1.json

If May audit was skipped:

Rule: July signup does not substitute for May audit—it only authorizes fest ops calendar if depot truth is already filed or caught up same week.

G2 RC label vs smoke baseline

Prefer october_rc_label_ok: true from L1–L6 evening. If RC receipt is pending but participate window closes:

jq -e '
  .wednesday_smoke_ok == true
  and (.build_label | test("fest-demo-2026-10-rc"))
' wednesday_smoke_receipt_v1.json

Document g2_waiver: "smoke_baseline_only" in signup receipt—schedule RC label evening before content-freeze manifest pins Addressables hash.

G3 vacation handoff map (July-specific)

Create release-evidence/ops/vacation_handoff_map_v1.json:

{
  "schema": "vacation_handoff_map_v1",
  "fest_name": "Steam Next Fest October 2026",
  "freeze_start_utc": "2026-08-01T00:00:00Z",
  "freeze_end_utc": "2026-08-18T00:00:00Z",
  "on_call": {
    "primary": "[email protected]",
    "engineering_escalation": "[email protected]",
    "pager_rotation": "none"
  },
  "allowed_actions_during_freeze": [
    "HOTFIX with numbered exception only",
    "store metadata typo fix",
    "no new Addressables bundles"
  ],
  "content_freeze_label": "fest-demo-2026-10-rc1",
  "notes": "Signup filed 2026-07-14; RC label receipt path on disk"
}

Crosswalk against February signup cousin defer_crosswalk—October teams use vacation handoff instead of December DEFER rows, but the discipline is identical: no silent assumptions during offline weeks.

G4 demo scope lock (one paragraph, hashable)

Create release-evidence/ops/october-demo-scope-2026.md:

# October 2026 demo promise (signup lock)
One fantasy: survive three dungeon floors with one companion.
Cut: multiplayer, crafting, endgame boss.
Duration: ~45 minutes skilled / ~90 minutes explore.
Persistence: one save slot, local only.
Audio: FMOD desktop banks required.

Hash for receipt:

sha256sum release-evidence/ops/october-demo-scope-2026.md | awk '{print $1}'

Store hash in october_fest_signup_receipt_v1.json as demo_scope_sha256. If store FAQ promises features outside this doc, G4 RED until copy or scope aligns.

G5 steamworks_map.json (export template)

{
  "app_id": "1234560",
  "demo_depot_id": "1234561",
  "main_depot_id": "1234562",
  "fest_branch": "nextfest-oct-2026",
  "playtest_branch": "playtest-invite",
  "last_cold_install_utc": "2026-07-10T14:00:00Z",
  "steam_input_vdf_path": "controller_config/demo_deck.vdf",
  "notes": "July signup catch-up—cross-check May depot audit"
}

october_fest_signup_receipt_v1.json (schema)

{
  "schema": "october_fest_signup_receipt_v1",
  "iso_week": "2026-W28",
  "fest_name": "Steam Next Fest October 2026",
  "participate_clicked_utc": "2026-07-14T16:00:00Z",
  "gates": {
    "G1": "GREEN",
    "G2": "GREEN",
    "G3": "GREEN",
    "G4": "GREEN",
    "G5": "GREEN",
    "G6": "GREEN"
  },
  "evidence": {
    "october_depot_audit": "release-evidence/steam/october-fest/october_depot_audit_receipt_v1.json",
    "october_rc_label_receipt": "release-evidence/03-builds/october-rc/2026-W28/october_rc_branch_label_receipt_v1.json",
    "vacation_handoff_map": "release-evidence/ops/vacation_handoff_map_v1.json",
    "demo_scope_doc": "release-evidence/ops/october-demo-scope-2026.md",
    "steamworks_map": "release-evidence/steam/october-fest/steamworks_map_v1.json"
  },
  "steamworks": {
    "app_id": "1234560",
    "demo_depot_id": "1234561",
    "fest_branch": "nextfest-oct-2026",
    "build_label_baseline": "fest-demo-2026-10-rc1"
  },
  "vacation_handoff": {
    "freeze_start_utc": "2026-08-01T00:00:00Z",
    "on_call_primary": "[email protected]",
    "content_freeze_label": "fest-demo-2026-10-rc1"
  },
  "february_signup_cousin_crosswalk": {
    "compared_to": "february_fest_signup_receipt_v1",
    "october_specific": "vacation_handoff replaces december_defer_crosswalk",
    "shared_gates": ["G4 scope hash", "G5 steamworks_map", "G6 signup receipt"]
  },
  "october_fest_signup_ok": true,
  "next_milestone": "summer content freeze on rc1 label"
}

BUILD_RECEIPT root rows (same commit)

{
  "build_label": "fest-demo-2026-10-rc1",
  "october_depot_audit_ok": true,
  "october_rc_label_ok": true,
  "october_fest_signup_ok": true,
  "october_fest_signup_receipt": "release-evidence/ops/october_fest_signup_receipt_v1.json",
  "summer_content_freeze_ok": false
}

Set summer_content_freeze_ok after content-freeze manifest L5—not at signup.

verify_october_fest_signup.sh (sketch)

#!/usr/bin/env bash
set -euo pipefail
RECEIPT="${1:-october_fest_signup_receipt_v1.json}"
BUILD="${2:-BUILD_RECEIPT.json}"

jq -e '
  .october_fest_signup_ok == true
  and (.gates | .G1, .G2, .G3, .G4, .G5, .G6 | . == "GREEN")
' "$RECEIPT"

jq -e --slurpfile su "$RECEIPT" '
  .october_fest_signup_ok == $su[0].october_fest_signup_ok
  and .october_depot_audit_ok == true
' "$BUILD"

test -f "$(jq -r '.evidence.vacation_handoff_map' "$RECEIPT")"
echo "OK: october fest signup gates GREEN"

PowerShell cousin for Windows-first studios:

$r = Get-Content october_fest_signup_receipt_v1.json | ConvertFrom-Json
if (-not $r.october_fest_signup_ok) { throw "october_fest_signup_ok false" }
@("G1","G2","G3","G4","G5","G6") | ForEach-Object {
  if ($r.gates.$_ -ne "GREEN") { throw "$_ not GREEN" }
}
Write-Host "OK: october fest signup gates GREEN"

jq gate sketch (working dev)

jq -e '
  .october_fest_signup_ok == true
  and (.gates | .G1, .G2, .G3, .G4, .G5, .G6 | . == "GREEN")
' october_fest_signup_receipt_v1.json

Merge BUILD_RECEIPT:

jq -e --slurpfile su october_fest_signup_receipt_v1.json '
  .october_fest_signup_ok == $su[0].october_fest_signup_ok
  and .october_depot_audit_ok == true
' BUILD_RECEIPT.json

February cousin diff (one command):

diff <(jq -S '.gates' february_fest_signup_receipt_v1.json) \
     <(jq -S '.gates' october_fest_signup_receipt_v1.json) || true

Expect G1/G3 semantic drift—gate names match; evidence paths differ.

July vs February signup comparison table

Proof table

Scenarios A–H

Producer participate workflow (90 minutes)

Schedule October RC label evening same week if G2 not yet GREEN from L1–L6.

Partner / publisher email row (post-signup)

Subject: <Game> — October 2026 Next Fest participation note

Body:

We filed october_fest_signup_receipt_v1.json July 14 with baseline fest-demo-2026-10-rc1. Summer content freeze starts Aug 1 per vacation_handoff_map_v1.json. Creator keys after Wednesday smoke GREEN on frozen label—not signup click.

Pointer-first—attach signup receipt path, not fest hype.

Micro-studio time budget

Cheaper than September promotion panic on a June build_label—common July thread pattern.

March cluster integration (post-February teams)

Common mistakes

Counterarguments (honest limits)

"Valve does not require JSON receipts."
Correct—this is team ops discipline, not platform policy. Publishers and co-dev partners ask for proof anyway.

"We signed up last October without this."
July 2026 vacation-compressed timeline differs—handoff crosswalk is the new failure mode.

"Same as February signup playbook."
February owns December defer; October owns vacation handoff—cousin structure, different G3 evidence.

"Same as October timeline."
Timeline owns weekly locks; this playbook owns participate gate evidence in July.

Outbound references

• Steamworks documentation — festival participation workflows
• Steam Next Fest — official festival news group

Related GamineAI reads

• October 2026 timeline
• February signup trend cousin
• October RC label evening
• May depot rules
• Wednesday demo smoke
• 7-day vertical slice challenge
• BUILD_RECEIPT beginner pipeline
• March evidence sprint
• Post-fest velocity tools

Key takeaways

1. July 2026 signup is a commitment gate before summer vacation—not September marketing theater.
2. Gates G1–G3 tie May depot audit, RC label/smoke baseline, and vacation handoff together.
3. october_fest_signup_receipt_v1.json records evidence before Participate.
4. october_fest_signup_ok on BUILD_RECEIPT latches signup discipline.
5. October July window compresses vs February 2027 post-holiday—vacation handoff replaces defer crosswalk.
6. Pair October timeline for weekly locks after signup.
7. Post-signup: RC label evening + summer content freeze on proven label.
8. G5 steamworks_map catches depot drift May alumni skip.
9. Signup does not auto-pin content freeze—explicit vacation_handoff_map required.
10. Forward #7 summer capsule gradient pass when store art swaps after signup.
11. No invented signup metrics—qualitative pattern read only.
12. Creator keys wait until smoke discipline on frozen label—not signup click.
13. February signup cousin shares G4–G6 shape—diff G1/G3 evidence paths.

FAQ

Can we participate before May depot audit?

Not recommended—G1 RED blocks receipt; run May depot rules catch-up first.

What if we have no vacation?

Document G3 with on_call.primary = solo founder and explicit allowed_actions_during_freeze—still file handoff map.

Is this the same as the October timeline?

No. Timeline = when to lock milestones. This playbook = what must be GREEN before Participate in July.

Does signup require the RC label evening?

G2 prefers october_rc_label_ok—smoke baseline waiver allowed with dated producer note; RC evening before Addressables freeze.

How does this relate to February 2027 signup?

February signup trend is the cousin—same G4–G6 receipt culture, different G1/G3 crosswalk.

Can marketing announce signup before receipt?

Wait for G6—announcement without receipt recreates "which build?" threads in August.

What happens the week after July signup?

Do not schedule creator mail blasts until Wednesday smoke GREEN on frozen label.

RED / YELLOW / GREEN routing (G gates)

Document routing decision in october_fest_signup_receipt_v1.json notes when any gate was YELLOW with producer waiver.

Closing

July signup window compression is not a Valve policy headline—it is an ops calendar fact: fewer working days between Participate and summer vacation than teams plan for. File october_fest_signup_receipt_v1.json, crosswalk vacation handoff, and treat the three beginner gates as participate blockers. Working devs wire verify_october_fest_signup.sh; producers send pointer-first partner notes before the second call. Prevention beats September promotion on the wrong build_label—and forward #7 capsule art pass catches gradient banding before October CTR-sensitive store swaps.