January 2027 Indies Rush February Next Fest Signups - What Changed for Micro-Studios Trend Playbook

January 8: the team clicks Participate on Steam Next Fest February 2027. January 9: someone asks whether January re-entry smoke is GREEN. January 10: marketing schedules creator keys while build_label still points at December baseline and December defer rows list twelve DEFER items nobody resumed.

January 2027 concentrates a different pressure than October 2026 signup season: teams return from holiday freeze with compressed RC weeks, shorter internal approval chains, and less slack before February fest branch lock. The signup button is not the start of fest prep—it is a commitment gate that assumes November close-out, December defer, January re-entry, and unfreeze audit already filed.

This Trend-Jacking / News Commentary playbook is the January signup economics layer—not the February prep calendar (date milestones), not the 7-day RC smoke challenge (daily ritual ladder), not October depot rules (May branch audit). It answers what must be GREEN before you click Participate and how to file february_fest_signup_receipt_v1.json with December defer crosswalk.

Non-repetition note: February prep calendar owns when to lock scope. December defer owns freeze vs ship lanes. October timeline owns six-week October anchors. This URL owns January 2027 signup rush discipline + participate gate receipt.

Pair BUILD_RECEIPT beginner, blog cluster #1–#5, and forward #7 February capsule safe-zone art pass.

Why this matters now (January 2027 signup window)

1. Compressed signup-to-RC timeline — February fest teams get fewer working days between "participate" and first fest-demo-2027-02-rc* upload than October 2026 cohorts reported in partner threads.
2. Holiday defer backlog — December defer receipt DEFER rows need explicit resume dates—not automatic unfreeze on signup.
3. Receipt sprawl — January cluster expects re-entry, unfreeze audit, and optional 7-day RC challenge—signup without crosswalk invites hero scope.
4. Store page vs binary truth — Teams update fest copy in January while demo still shows December build_label—signup amplifies mismatch threads.
5. Micro-studio cash rhythm — January marketing spend cap sets weekly spend dates after signup evidence is filed.

Direct answer: Before clicking Participate, run gates G1–G6, crosswalk December defer, file february_fest_signup_receipt_v1.json, set BUILD_RECEIPT february_fest_signup_ok: true—then schedule February RC label evening.

Who should read this

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

Format ladder (January cluster)

Order: January cluster #1–#3 GREEN → this signup playbook → participate → #4 seven-day challenge → RC label evening.

What changed vs October 2026 signup season (qualitative)

Patterns from January 2027 partner-facing threads and February prep post-mortems—no invented signup statistics:

Micro-studios that treated signup as marketing confirmation repeated January scramble. Studios that filed signup receipt with defer crosswalk entered RC week with one build_label story.

Beginner path — pre-participate checklist

Copy into release-evidence/ops/february-fest-signup-checklist-2027.md:

# February 2027 Next Fest — before Participate
target_fest: Steam Next Fest February 2027
signup_owner: producer
participate_clicked_utc: (blank until G1–G6 GREEN)

[ ] G1 — January re-entry smoke GREEN (january_reentry_smoke_ok)
[ ] G2 — January unfreeze audit GREEN (january_unfreeze_audit_ok)
[ ] G3 — December defer crosswalk: no orphan DEFER rows past resume date
[ ] G4 — Demo scope one paragraph matches store FAQ (no hero features)
[ ] G5 — fest branch name + depot id documented in runbook
[ ] G6 — february_fest_signup_receipt_v1.json filed
[ ] BUILD_RECEIPT february_fest_signup_ok == true
[ ] Producer sign-off — then click Participate

Beginner mistake: Updating store page fest banner before G4 scope lock—creates public promise before binary truth.

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.

December defer crosswalk (G3 detail)

Load December defer receipt december_defer_receipt_v1.json and verify:

jq -e '
  [.defer_rows[] | select(.lane == "DEFER" and (.resume_date > $today))] | length == 0
' --arg today "2027-01-08" december_defer_receipt_v1.json

If DEFER rows remain past resume date without SHIP exception:

Rule: Signup does not auto-resume DEFER work—it only authorizes fest ops calendar.

G4 demo scope lock (one paragraph, hashable)

Create release-evidence/ops/february-demo-scope-2027.md:

# February 2027 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 (see LFS audit).

Hash for receipt:

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

Store hash in february_fest_signup_receipt_v1.json as demo_scope_sha256. If store FAQ promises features outside this doc, G4 RED until copy or scope aligns—signup amplifies public mismatch.

G5 steamworks_map.json (export template)

{
  "app_id": "1234560",
  "demo_depot_id": "1234561",
  "main_depot_id": "1234562",
  "fest_branch": "nextfest-feb-2027",
  "playtest_branch": "playtest-invite",
  "last_cold_install_utc": "2027-01-07T14:00:00Z",
  "steam_input_vdf_path": "controller_config/demo_deck.vdf",
  "notes": "January catch-up audit—cousin to May 2026 depot rules playbook"
}

Cross-check against October depot rules cold-install row—February teams often skip May audit and discover wrong depot at signup.

february_fest_signup_receipt_v1.json (schema)

{
  "schema": "february_fest_signup_receipt_v1",
  "iso_week": "2027-W02",
  "fest_name": "Steam Next Fest February 2027",
  "participate_clicked_utc": "2027-01-08T16:00:00Z",
  "gates": {
    "G1": "GREEN",
    "G2": "GREEN",
    "G3": "GREEN",
    "G4": "GREEN",
    "G5": "GREEN",
    "G6": "GREEN"
  },
  "evidence": {
    "january_reentry_receipt": "release-evidence/03-builds/january-reentry/2027-W01/january_reentry_smoke_receipt_v1.json",
    "january_unfreeze_audit": "release-evidence/audit/january_unfreeze_audit_receipt_v1.json",
    "december_defer_receipt": "release-evidence/ops/december_defer_receipt_v1.json",
    "demo_scope_doc": "release-evidence/ops/february-demo-scope-2027.md",
    "steamworks_map": "release-evidence/steam/february-fest/steamworks_map_v1.json"
  },
  "steamworks": {
    "app_id": "1234560",
    "demo_depot_id": "1234561",
    "fest_branch": "nextfest-feb-2027",
    "build_label_baseline": "fest-demo-2026-12-rc3"
  },
  "defer_crosswalk": {
    "open_defer_count": 0,
    "ship_exceptions_since_freeze": 1,
    "notes": "OTLP proxy SHIP exception 2026-12-19 documented"
  },
  "february_fest_signup_ok": true,
  "next_milestone": "7-day RC smoke challenge Day 1"
}

BUILD_RECEIPT root rows (same commit)

{
  "build_label": "fest-demo-2026-12-rc3",
  "january_reentry_smoke_ok": true,
  "january_unfreeze_audit_ok": true,
  "holiday_defer_ok": true,
  "february_fest_signup_ok": true,
  "february_fest_signup_receipt": "release-evidence/ops/february_fest_signup_receipt_v1.json",
  "february_rc_challenge_ok": false
}

Set february_rc_challenge_ok after 7-day challenge C7—not at signup.

jq gate sketch (working dev)

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

Merge BUILD_RECEIPT:

jq -e --slurpfile su february_fest_signup_receipt_v1.json '
  .february_fest_signup_ok == $su[0].february_fest_signup_ok
  and .january_reentry_smoke_ok == true
' BUILD_RECEIPT.json

October vs February signup comparison table

Proof table

Scenarios A–G

Producer participate workflow (60 minutes)

Schedule 7-day RC challenge start same week.

Partner / creator email row (post-signup)

Subject: <Game> — February 2027 Next Fest participation note

Body:

We filed february_fest_signup_receipt_v1.json Jan 8 with baseline fest-demo-2026-12-rc3. RC week starts 7-day challenge; creator keys after Day 3 smoke GREEN. Defer items resume per December receipt—no hero scope during RC week.

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

Micro-studio time budget

Cheaper than announcing fest participation while build_label still disagrees with store FAQ—common January thread pattern.

Common mistakes

Counterarguments (honest limits)

"Valve does not require JSON receipts."
Correct—this is team ops discipline, not platform policy. Partners and creators ask for proof anyway.

"We signed up last year without this."
February 2027 post-holiday timeline differs from October 2026—defer crosswalk is the new failure mode.

"Same as February prep calendar."
Calendar owns dates; this playbook owns participate gate evidence.

Outbound references

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

Related GamineAI reads

• February 2027 prep calendar
• December defer playbook
• January re-entry smoke
• January unfreeze audit
• 7-day RC smoke challenge
• February RC label receipt
• October depot rules
• Git LFS pointer drift case study
• BUILD_RECEIPT beginner pipeline
• Wednesday demo smoke

Key takeaways

1. January 2027 signup is a commitment gate—not the start of fest prep.
2. Gates G1–G3 tie re-entry, unfreeze audit, and December defer crosswalk together.
3. february_fest_signup_receipt_v1.json records evidence before Participate.
4. february_fest_signup_ok on BUILD_RECEIPT latches signup discipline.
5. February timeline compresses vs October 2026—receipts beat hero scope.
6. Pair February prep calendar for dates after signup.
7. Post-signup: 7-day RC challenge Day 1 baseline.
8. G5 steamworks_map catches depot drift October alumni skip.
9. Signup does not auto-resume DEFER rows—explicit resume or SHIP exception.
10. Forward #7 February capsule safe-zone pass when store art swaps winter HDR masters—Z1–Z6 after RC crop.
11. No invented signup metrics—qualitative pattern read only.
12. Creator keys wait until smoke discipline starts—not signup click.
13. January marketing spend cap gates paid social until G1–G3 and smoke receipts align.

FAQ

Can we participate before re-entry smoke?

Not recommended—G1 RED blocks receipt; run re-entry evening first.

What if we have no December defer receipt?

Document defer_crosswalk.not_applicable in signup receipt—G3 waived with producer note.

Is this the same as the February prep calendar?

No. Calendar = when to lock milestones. This playbook = what must be GREEN before Participate.

Does signup require the 7-day RC challenge?

Not before participate—but schedule challenge same week after signup for RC discipline.

How does this relate to October 2026 fest?

October timeline and depot rules are cousins—February teams need January catch-up in G5.

Can marketing announce signup before receipt?

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

What happens the week after signup?

Do not schedule creator mail blasts until Day 3 smoke GREEN unless keys are explicitly labeled pre-RC.

RED / YELLOW / GREEN routing (G gates)

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

Closing

January 2027 signup rush rewards teams that already proved holiday baseline—not teams that treat Participate as permission to reopen hero scope. File defer crosswalk, latch re-entry and unfreeze booleans, document depot map, then click the button.

Signup is the receipt moment. RC week is the work.

Next: February capsule safe-zone pass — Z1–Z6 after RC crop; backlog #8 jq capstone pointer forward.