August 2026 Soft-Launch Windows Before October Next Fest - What Changed for Micro-Studios Trend Playbook

August 12: marketing schedules a “soft launch” closed beta with itch play-now and Steam keys. August 13: Weblate is still writable, dual-SKU labels disagree, and the age-rating packet is a Slack screenshot. August 20: soft traffic spikes—wishlists stall on Steam while itch absorbs plays. September 5: October Next Fest upload week inherits the mess October signup receipts never covered.

August 2026 is when soft-launch calendars collide with October Next Fest prep. Micro-studios treat soft launch as optional marketing theater. Partners and players treat it as a preview of fest truths: languages claimed, storefront hierarchy, age markers, and which build_label is “real.” Teams that skip the three operational gates—string freeze, dual-SKU dress rehearsal / split hygiene, age-rating packet—waste September–October upload week rebuilding evidence they could have locked in August.

This Trend-Jacking / News Commentary playbook is the August soft-launch transfer map—not July signup compression (Participate before vacation), not June aftermath (keep/archive June lessons), not T-90 creator outreach (press calendar). It answers what must be GREEN before you open a soft-launch window that can still feed October fest success.

Non-repetition note: July signup owns Participate + vacation handoff. June aftermath owns post-fest transfer before October. T-90 owns creator/press runway. Cluster tutorials own freeze L1–L6, dual-SKU D1–D6, age A1–A6, freeze challenge F1–F5, wishlist recovery R1–R6. This URL owns soft-launch window policy + soft_launch_window_receipt_v1.json G1–G6 + three-gate model.

Pair localization freeze evening, 5-day #LocFreeze2026 challenge, dual-depot dress rehearsal, wishlist-split recovery, IARC age-rating packet tools.

Why this matters now (August 2026)

1. Soft launch is no longer free marketing. Unscoped itch + Steam dual CTAs can dilute October wishlist conversion before fest (wishlist-split recovery).
2. Localization reopenings kill upload week. Verbal freezes reopen after soft feedback—“one more string” becomes October depot debt (freeze evening + challenge).
3. Age packets arrive earlier. Q3–Q4 partners ask for questionnaire evidence during soft windows, not only at submit (IARC tools).
4. July signup is not soft-launch permission. october_fest_signup_ok proves Participate hygiene—not soft traffic readiness.
5. September has no spare days. Soft-launch fallout that could have been gated in August becomes SteamPipe queue drama.

Direct answer: Before opening an August soft-launch window, run gates G1–G6, require the three-gate model (string freeze + dual-SKU + age packet), file soft_launch_window_receipt_v1.json, set BUILD_RECEIPT soft_launch_window_ok: true—then allow Steam-first CTAs and dated soft windows with stop rules.

Who should read this

Time: ~40 minutes read; ~2 hours first soft-launch receipt sprint if cousins incomplete.

Beginner path — three-gate soft-launch model

Think of soft launch as a preview of October, not a separate toy SKU.

If any gate is RED, do not buy soft-launch ads. Soft keys for friends-and-family without public CTAs are fine under documented scope.

Format ladder

Order: June map → July signup → August soft-launch (this) → September T-90 / upload rehearsal → October fest.

What changed vs prior soft-launch habits (qualitative)

No invented download charts—partner-facing pattern contrasts:

Gates G1–G6

Transfer map vs July signup and T-90

June aftermath (keep/archive)
    ↓
July signup receipt (Participate + vacation map)
    ↓
August soft-launch receipt (three gates + window calendar)  ← THIS ARTICLE
    ↓
T-90 outreach / press kit (creators see consistent languages, CTAs, ratings)
    ↓
October upload / Next Fest live week

soft_launch_window_receipt_v1.json

{
  "schema": "soft_launch_window_receipt_v1",
  "created_utc": "2026-08-10T17:00:00Z",
  "window_start_utc": "2026-08-18T00:00:00Z",
  "window_end_utc": "2026-08-31T23:59:59Z",
  "july_signup_receipt": "release-evidence/october-fest/july-signup/october_fest_signup_receipt_v1.json",
  "three_gates": {
    "localization_freeze_ok": true,
    "localization_freeze_challenge_ok": true,
    "dual_sku_rehearsal_ok": true,
    "dual_sku_wishlist_recovery_ok": true,
    "age_rating_packet_ok": true
  },
  "cta_hierarchy": "P1_steam_first",
  "build_label": "fest_2026-08-18_soft_a1b2",
  "gates": {
    "G1": "PASS",
    "G2": "PASS",
    "G3": "PASS",
    "G4": "PASS",
    "G5": "PASS",
    "G6": "PASS"
  },
  "soft_launch_window_ok": true,
  "stop_rules": ["no_itch_first_socials", "no_language_claims_beyond_manifest", "pause_if_split_R2_red"],
  "notes": "Friends-and-family keys OK before window_start; paid ads only after G6."
}

BUILD_RECEIPT crosswalk:

{
  "soft_launch_window_ok": true,
  "soft_launch_window_receipt": "release-evidence/soft-launch/2026-08/soft_launch_window_receipt_v1.json"
}

verify_soft_launch_window.sh

#!/usr/bin/env bash
set -euo pipefail
R="${1:-release-evidence/soft-launch/latest/soft_launch_window_receipt_v1.json}"
test "$(jq -r .soft_launch_window_ok "$R")" = "true"
for g in G1 G2 G3 G4 G5 G6; do
  test "$(jq -r ".gates.$g" "$R")" = "PASS"
done
test "$(jq -r .three_gates.localization_freeze_ok "$R")" = "true"
test "$(jq -r .three_gates.dual_sku_rehearsal_ok "$R")" = "true"
test "$(jq -r .three_gates.age_rating_packet_ok "$R")" = "true"
echo "soft_launch_window_ok"

Producer dashboard (print beside the calendar)

Spend five minutes each soft-launch morning on this board. It prevents “we soft-launched last week—why is October messy?” meetings.

Paid soft-ad preflight (after G6 only)

1. Confirm soft_launch_window_ok: true on BUILD_RECEIPT within 24 hours.
2. Landing URL is Steam store / wishlist, not itch alone.
3. Creative copy does not promise languages outside locale_manifest.
4. Age-facing claims match packet (no “E for everyone” improvisation).
5. UTM or notes column ready for funnel CSV.
6. Kill-switch owner named in G5 calendar.
7. Budget cap written (pair future money worksheet when #9 ships)—do not unlimited-boost soft week.

If any item fails, spend on capsule or trailer craft instead of soft traffic.

Deep dive — how G2–G4 map to cluster receipts

G2 string freeze. Point at freeze evening localization_freeze_receipt_v1.json. If soft launch is public enough that translators feel pressure, also require challenge localization_freeze_challenge_ok. Soft feedback that invents new UI strings must open an exception ticket and a new freeze—never rewrite L2 hash in place.

G3 dual-SKU. Point at dress rehearsal receipt. If itch is off, document single_channel: steam. If itch is on, require no open wishlist-split incident; if split fired mid-soft, attach recovery receipt before restoring ads.

G4 age packet. Point at age_rating_packet_receipt_v1.json and hashed questionnaire. Soft keys that land with strangers (creators, Discord outside core team) count as public enough to need G4. Friends-and-family only may defer only with an explicit note and a max key count—document it, do not hide it.

Soft-window calendar template (G5)

August week plan (working Micro-studio)

Scenarios A–G

A - Soft launch scheduled before July signup filed

Fail G1 or document “signup deferred / not participating”—do not invent Participate history.

B - Freeze GREEN but challenge abandoned mid-week

If marketing claimed #LocFreeze2026, require challenge OK or stop claiming social freeze. Evening latch alone may suffice for private keys—state which.

C - Soft ads itch-first, rehearsal GREEN

Expect wishlist split. Open recovery; keep G3 RED until closed.

D - Age packet missing, Steam store shows rating

Fail G4. Screenshot store without hashed questionnaire is not a packet.

E - Soft window overlaps vacation handoff gap

Fail G1/G5. Align with July vacation map—no uncovered soft traffic.

F - Creator wants English-only soft build while store claims JP

Fail G2. Store claim ⊆ soft Preferences.

G - Soft success tempts “one more language”

New freeze evening + challenge restart—do not reopen Weblate casually mid-window.

Common mistakes

• Treating soft launch as July signup’s free sequel without new gates.
• Equal dual links during soft week.
• Skipping age packet because “Steam will ask later.”
• Soft building from unlabeled main.
• Closing soft week without checking three-gate still GREEN.
• Buying ads before G6.
• Letting soft feedback silently reopen string freeze.
• Confusing this with October T-6 timeline milestones.

Proof table

Troubleshooting

“We only soft-launch on Steam.” Still require freeze + age packet; dual-SKU gate can be N/A with documented single-channel note in G3.

“Closed beta keys only—no ads.” You may run a pre-window private key phase under friends-and-family rules, but still file freeze/age honesty if keys go to strangers or creators.

“July signup was RED—can we soft-launch anyway?” Not as “Next Fest soft launch.” Rebrand as private playtest without fest claims until G1 clear.

“T-90 starts mid soft window.” Freeze press kit URLs to Steam-first; do not ship equal dual links to creators.

Pairing with forward Money / Process / AI rows

Outbound: follow current Steamworks and Next Fest partner posts for exact participate/upload dates—this playbook owns evidence gates, not Valve’s calendar text.

Also pair BUILD_RECEIPT beginner if latches are new, and itch browser scope opinion when itch remains in the soft mix.

Key takeaways

1. August 2026 soft-launch windows collide with October fest prep—gate them.
2. Use the three-gate model: string freeze, dual-SKU hygiene, age packet.
3. July signup GREEN ≠ soft-launch permission (G1).
4. File soft_launch_window_receipt_v1.json with G1–G6.
5. Steam-first CTA hierarchy by default; itch secondary or closed.
6. Monitor funnel during soft; reopen wishlist-split recovery when needed.
7. Do not reopen string freeze for soft feedback without a new evening receipt.
8. Transfer map: June → July → August soft → T-90 → October.
9. Private keys without ads still need honesty if strangers receive them.
10. Latch soft_launch_window_ok before paid soft spend.
11. Forward money/process/AI rows inherit soft-window stop rules.
12. This is trend policy—execute details via cluster #1–#5 recipes.

Keep soft-launch policy short enough that marketing can recite it: no paid soft ads without three gates and a dated window. Everything else in this article exists to make that sentence enforceable with JSON paths, not vibes—print the gate card and tape it near the ad budget sheet today itself.

FAQ

What is a soft-launch window in this playbook?

A dated August period when limited public or semi-public demo traffic runs before October Next Fest, under Steam-first hierarchy and three operational gates.

Can we soft-launch without dual SKU?

Yes—document Steam-only in G3. Dual-SKU gate fails only when itch (or GX) is live without rehearsal/recovery honesty.

Do we need #LocFreeze2026 or only evening freeze?

Evening localization_freeze_ok is required (G2). Challenge OK is required if you publicly claimed the five-day ritual.

How does this differ from July signup?

July decides Participate readiness. August decides whether soft traffic may begin without poisoning October.

What if soft launch discovers critical bugs?

Ship hotfixes that do not reopen freezes lightly. String changes require new freeze receipts. Dual-SKU label changes require re-rehearsal.

Should T-90 wait until soft window ends?

Prefer starting T-90 with Steam-first kits after G6. Soft can overlap if stop rules and funnel monitoring continue.

Is this legal advice for age ratings?

No—operational timing. Use IARC packet tools for packet hygiene.

When is the soft window “done”?

Calendar end UTC plus three-gate still GREEN, no open split incident, and BUILD_RECEIPT still shows soft_launch_window_ok or a closed amendment note.

What counts as “soft launch” vs “private playtest”?

Private playtest: named invitees, no public CTA, no paid ads, keys counted.
Soft launch (this playbook): any semi-public discovery window—Discord open invites, itch public play, Steam wishlist ads, creator send with public page links. If strangers can find the build without a personal DM, treat it as soft launch and require G1–G6.

Can we reopen soft after ending the window?

Yes—with a new receipt revision, new window dates, and re-check of three gates. Do not silently extend window_end_utc after ads restart.

How do June aftermath keep-rows interact?

If June aftermath archived a messaging claim as rewrite-only, soft launch must not resurrect it. Attach the keep/archive table path in soft receipt notes when soft copy references prior fest claims.

Printable soft-launch gate card

August Soft-Launch Gate Card — Before Paid Traffic

[ ] G1 July signup path or documented N/A
[ ] G2 localization_freeze_ok (+ challenge if claimed)
[ ] G3 dual_sku_rehearsal_ok / single-channel note / recovery if needed
[ ] G4 age_rating_packet_ok + questionnaire hash
[ ] G5 window calendar + Steam-first CTA + kill-switch owner
[ ] G6 soft_launch_window_receipt filed; soft_launch_window_ok = true

Window: ________ → ________   Owner: ________
Landing URL: ________
Do NOT buy soft ads until all boxes checked.

Related reads

• July 2026 October Next Fest Signup Window Compression
• June 2026 Next Fest Aftermath Before October Prep
• 14 Free Creator Outreach Press Kit Tools October T-90
• Localization String Freeze Receipt Before October PO Import
• 5-Day Localization Freeze Gate Challenge
• itch + Steam Dual-Depot Dress Rehearsal
• Dual-SKU Wishlist-Split Recovery Case Study
• 14 Free IARC PEGI ESRB Age-Rating Packet Tools
• Multilingual Capsule Typography Safe-Zone Pass JP KR Before October — Z6 before JP/KR soft creatives if store claims those locales

Closing

August soft launch is either an October dress rehearsal with receipts or a September debt factory. Run the three gates, file the soft-window receipt, keep Steam first, and refuse paid soft traffic until G1–G6 are honest green.

July proved you can Participate. August proves you can preview without poisoning the fest. October rewards the studios that treated soft launch like evidence—not like a vibes campaign with an itch button.

If you only ship one artifact this August, make it soft_launch_window_receipt_v1.json with three-gate paths filled. Everything else—trailers, keys, Discord hype—can attach to that latch. Without it, October upload week becomes archaeology: excavating which soft build players actually saw.