5-Day Store Metadata Freeze Challenge - One Field Group Per Day Before October 2026 Next Fest

You run Wednesday diffs when you remember. Fest month you forget. Players install a new build and read last month's FAQ.

This Challenges & Sprints piece is a five-day weekday sprint that freezes Steam store metadata one field group per day (G1–G6 from the Wednesday ritual)—with signed daily logs and a promotion freeze until Friday's gate passes. It is the habit installer before October 2026 Next Fest branch traffic.

Pair with 14 metadata tools and FAQ LLM pipeline.

Who this is for

• 1–4 person teams with live Steamworks access
• Studios that promoted fest branches without updating FAQs
• Anyone who failed truth audit once and wants a shorter re-run focused on metadata groups

Time: ~45–60 minutes per weekday (~4–5 hours total).

Why this matters now (May 2026)

1. Metadata drift velocity — May–September fest prep promotes builds weekly; copy lags.
2. Tooling without habit — Free diff tools do not run themselves.
3. Partner dimension 7 — Mock audit scores FAQ vs demo.
4. Marketing cap stops — Fest spend worksheet blocks ads on RED metadata.
5. Six-week lock — Timeline assumes frozen store truth.

Direct answer: Mon–Fri, one field group each day; export live → diff approved → fix → sign metadata-freeze-dayN.md; no fest branch promotion until Day 5 GREEN.

Field groups (same as Wednesday ritual)

Sample metadata-freeze-day3 log (pattern)

# Metadata freeze — Day 3 (G3 FAQ)
date: 2026-05-20
build_id: nextfest-oct-2026-rc4
reviewer: (writer), sign-off: (producer)

| question | diff result | action |
|----------|-------------|--------|
| Q03_ai | match | GREEN |
| Q05_multi | live says co-op | RED → removed |
| Q08_deck | match | GREEN |

status: GREEN after Q05 fix
promotion: still blocked until Day 5 complete

Copy structure for days 1–2 and 4–5; keep tables short.

Energy and scope management

Skipping challenge because "we are busy" is when lies ship busiest.

Before you start

• [ ] store-metadata/approved-baseline/ exists in git
• [ ] BUILD_RECEIPT build_id for fest branch documented
• [ ] Owner per group assigned (can be one person wearing hats)
• [ ] Team agrees: promotion blocked until Day 5 sign-off
• [ ] Folder release-evidence/05-operations/metadata-freeze-challenge-2026/

May–September scheduling guide

Do not run full challenge every month—Wednesday maintenance between runs.

Comparison to other five-day challenges

Run crash-log week after metadata freeze if both needed—players read store before they crash.

Challenge rules

1. One group per weekday — no skipping ahead.
2. Export live before diff — Tool 8 discipline from tools listicle.
3. RED blocks promotion that week—even if binary is urgent.
4. No price changes during challenge week unless Day 5 explicitly includes regional worksheet pass.
5. Sign daily log — producer name, not "team."

How this differs from Wednesday-only discipline

Run challenge when onboarding new marketing contractor, after major demo scope change, or first time adopting metadata exports.

Day 1 (Monday) — G1 short copy freeze

Goal: First sentences match demo first hour.

Steps (45–60 min):

1. Export G1 live to live-day1-g1.txt.
2. Diff vs approved/g1-short.txt.
3. Remove co-op, "full game," unverified features.
4. Add one honest scope line ("Demo ends after chapter 1").
5. Paste to Steamworks; screenshot live page.
6. Write metadata-freeze-day1.md — status GREEN or RED.

Pass: Three non-team readers paraphrase genre from short description alone.

Fail pattern: "Survival MMO" when demo is arena mode—fix before Tuesday.

Snippet answer for Day 1: The short description must describe what a player experiences in the first hour of the fest demo, not the full release roadmap.

Tooling: git diff (Tool 1) + Steamworks paste (Tool 8) from metadata tools listicle.

Day 2 (Tuesday) — G2 long copy + AI lines freeze

Goal: About section matches ai-disclosure/ annex and build.

Steps:

1. Export G2 live.
2. Cross-check AI disclosure challenge bullets.
3. Diff vs approved; run FAQ pipeline Gate D if LLM touched long copy.
4. Second human signs AI sentences.
5. Log Day 2.

Pass: Every AI claim names model class or "no AI in demo" honestly.

Cross-links to check in G2:

• Steam About vs mobile form if you ship mobile SKU
• Press kit one-pager if it exists
• Prompt registry hash referenced when runtime AI exists

Fail pattern: About says "AI-generated voices" but demo uses only text barks—narrow the claim.

Day 3 (Wednesday) — G3 FAQ freeze

Goal: Each FAQ answer traceable to approved files.

Steps:

1. Export all FAQ Q&A to live-day3-faq/.
2. Per-question diff vs faq-approved/.
3. Fix RED questions; update promotion log in FAQ pipeline folder.
4. Run markdownlint on pasted content before Steam save.
5. Log Day 3—this is the highest-risk day; budget 60 minutes.

Pass: Zero [NEEDS_HUMAN] or stale co-op answers live.

Pair: This day replaces your normal Wednesday ritual week—same discipline, challenge framing.

FAQ question IDs to prioritize:

Fix high-risk IDs before low-risk cosmetic FAQ.

Two-human rule: AI and multiplayer rows require second signature per FAQ pipeline.

Day 4 (Thursday) — G4 media freeze

Goal: Trailer and screenshots match demo visuals.

Steps:

1. List live screenshot filenames + trailer URL.
2. Compare to store-art/ dated exports and screenshot safe zones.
3. Replace mismatched stills; note trailer timestamp fixes.
4. Screenshot gallery in Steamworks.
5. Log Day 4.

Pass: First screenshot scene exists in current build_id.

Not in scope: Re-shooting trailer—only fix store links and stills or add honest "prototype footage" note in G2 if trailer stale (Tuesday file update).

Icon check: Verify 32px icon still matches screenshot #1 mood—note in Day 4 log if mismatch, fix in art pass not by lying in G1.

Tooling: Screenshot capture listicle for replacements.

Day 5 (Friday) — G5 commercial + G6 demo linkage freeze

Goal: Price story coherent; depot ids match demo audit.

Steps:

1. Confirm base price rows match regional worksheet (read-only check unless worksheet scheduled).
2. Export G6: branch name, demo depot id, last cold install date.
3. Diff vs fest-demo-depot-audit-2026.md.
4. Producer signs challenge complete row.
5. Promotion unblocked after GREEN.

Pass: build_id in log matches BUILD_RECEIPT and branch string.

G5 note: If regional pricing worksheet scheduled next week, only verify live price matches documented worksheet rows—do not launch full second pass during challenge week unless producer escalates.

G6 note: Cold install test optional on Day 5 if time allows—15 minutes that prevent October surprises. Log pass/fail beside depot ids.

CHALLENGE-COMPLETE.txt one line:

metadata-freeze-challenge-2026: COMPLETE
build_id: nextfest-oct-2026-rc4
signed: ProducerName 2026-05-22
promotion: UNBLOCKED

Weekend — optional reinforcement

No required tasks. Optional:

• Re-read live page incognito.
• Run vertical slice Day 4 if fest month imminent.
• Archive five daily logs to partner evidence ZIP.

Saturday sanity check (15 minutes): Open Steam store on phone and desktop; read short description and first FAQ answer cold. If you cringe, open metadata-freeze-day3.md and verify fixes actually published—Steamworks save failures happen.

Sunday planning (10 minutes): Schedule Wednesday recurring ritual; note next challenge rerun date if demo scope changes in July or August.

Daily time budget table

Total envelope 4–6 hours per person-week depending on RED count—not free, but bounded.

When to abort the challenge mid-week

Abort only for:

• Studio emergency (layoffs, platform outage) — resume next week same day number
• Discovered demo scope cut >50% — restart from Day 1 after new baseline

Do not abort because promotion pressure—promotion waits; that is the point.

Evidence folder layout

release-evidence/05-operations/metadata-freeze-challenge-2026/
  metadata-freeze-day1.md … day5.md
  live-day1-g1.txt
  live-day3-faq/
  screenshots-day4/
  CHALLENGE-COMPLETE.txt

Day-by-day artifact checklist

Missing artifact = log stays YELLOW, promotion stays blocked.

Worked week (composite duo, illustrative)

Total: under five hours engineer+writer time; one delayed promotion beats fest-week Discord fire.

Pairing with cert and evidence lanes

Do not stack three seven-day challenges same calendar week—alternate weeks in May–August.

Promotion gate script (read aloud)

Before any fest branch promote:

"Show me metadata-freeze-day5 GREEN, Wednesday log for this ISO week, and BUILD_RECEIPT build_id match."

If anyone cannot produce files, meeting ends.

Metrics to track (internal only)

No public benchmarks—improve your process.

Handoff to Wednesday ritual

After challenge week:

Challenge installs habit; Wednesday maintains it.

Distributed teams

Asia-EU handoff rules:

• EU completes Day N log before US promotes overnight.
• US does not edit Steam FAQ without updating faq-approved/ git.
• BUILD_RECEIPT notes metadata_freeze_day: N.

Intake compression recovery

Q3 intake compression yellow on store mismatch:

1. Pull five challenge logs if exist.
2. Export live; diff; fix fastest lie.
3. Attach recovery diff to evidence—pattern from hash case study timeline discipline.

Snippet-friendly answers

What is the 5-day store metadata freeze challenge?
A weekday sprint where micro-studios freeze Steam store field groups G1–G6 one per day with signed logs, blocking fest branch promotion until Day 5 passes.

How long per day?
45–60 minutes most days; up to 60 on FAQ day.

Can I run it without git?
Use diff tools with exported text files per 14 tools listicle—git recommended.

Tabletop sign-off (Friday, 20 minutes)

1. Producer reads CHALLENGE-COMPLETE criteria.
2. Engineer confirms G6 cold install date fresh.
3. Writer confirms G3 FAQ matches approved folder.
4. Marketer confirms fest cap may increase only if all GREEN.
5. Archive ZIP for diligence.

Refusal-to-stack rule

Failed Day 3 FAQ does not get hidden by Day 4 pretty screenshots. Finish RED day before advancing—challenge order is intentional.

Team roles

Solo: same person; still five separate logs—paper trail matters.

Common mistakes (seven)

1. Batching all days Monday — Defeats habit installer.
2. Diff without approved baseline — Everything RED, no progress.
3. Skipping Day 3 — FAQ lies survive fest.
4. Promotion during RED — Destroys challenge trust.
5. Changing price mid-week — Confuses G5; defer.
6. No screenshots Day 4 — Visual lies remain.
7. Challenge complete without G6 — Branch promotes wrong depot.

Pro tips (six)

1. Calendar holds 9:00–10:00 each weekday.
2. Slack status metadata-freeze-dayN during sprint.
3. Link logs in Friday Block 5.
4. Re-run challenge when demo scope changes materially.
5. Attach logs to diligence packets.
6. After challenge, revert to Wednesday ritual maintenance.

Key takeaways

• Five weekdays freeze G1–G6 store metadata—one group per day.
• Daily export, diff, fix, sign log—promotion blocked until Day 5 GREEN.
• Day 3 FAQ is highest risk; budget full hour.
• Pairs with metadata tools listicle and Wednesday ritual long-term.
• Evidence in metadata-freeze-challenge-2026/ folder.
• October Next Fest needs frozen truth before branch promotion spikes.
• Shorter than seven-day truth audit—focused on metadata groups only.
• Solo teams still produce five signed logs.
• Day 3 FAQ is the promotion gate—never skip for "just a binary fix."
• CHALLENGE-COMPLETE file unblocks branch promotion explicitly.
• Run before raising fest ads or trailer shoots.
• Pairs with demo depot audit and icon gates for full store stack.
• Abort only for real emergencies—promotion pressure is not one.
• Saturday phone check catches Steamworks saves that never applied to the live page.

FAQ

How is this different from truth audit?
Truth audit is broader (trailer frames, capsule text, demo labels). This challenge is metadata group discipline aligned to Wednesday ritual—can run after truth audit as a focused five-day refresher before fest promotion ramps.

Can we run six days for six groups?
Yes—split Day 5 into G5 Monday week-two and G6 Tuesday if you prefer; five-day version combines commercial + depot for micro-team time budgets.

We have no approved baseline yet?
Spend Day 0 (Sunday) creating baseline from live export per tools listicle; start challenge Monday.

Does this replace FAQ LLM pipeline?
No—Day 3 uses pipeline outputs as approved source.

What if we only have a playtest page, not full store?
Run Days 1–3 on available fields; skip G5; still do G6 internal doc for branch discipline.

Can marketing run Days 1–2 while engineering runs 4–6?
Yes if handoffs include artifact checklist—producer still signs single Friday complete.

How does UTM tracking fit?
After Day 5 GREEN, start UTM experiment—do not tag campaigns while metadata RED.

Operating review integration

Four-Friday operating reviews Block 2 question:

"Did we complete metadata freeze challenge this quarter? If not, why?"

If answer is "no time," revisit fest marketing cap—ads without metadata discipline waste money.

Post-challenge failure modes (watch through October)

Challenge is not permanent immunity—Wednesdays catch drift.

Beginner success path

Week zero: create approved baseline Sunday.
Week one: five challenge days.
Week two onward: fifteen-minute Wednesday only.

Three weeks to mature process—faster than learning after public fest embarrassment.

Outbound references

• Steamworks store page documentation
• Steam Next Fest timeline article

Publisher conversation script

When a publisher asks "how do you keep store truth aligned with builds?"

Answer: "We run a five-day metadata freeze challenge with daily signed logs, weekly Wednesday diffs, and promotion gates tied to BUILD_RECEIPT ids. I can attach last month's logs to the diligence packet."

Process beats adjectives.

Conclusion

Fest branches move fast. Store metadata should move deliberately. Five days, five logs, one promotion gate at the end—that is how micro-studios earn October traffic without FAQ apologies.

Start next Monday. Block branch promotion until Friday signs GREEN. Then keep the habit on Wednesdays every week until fest traffic peaks.

Players forgive rough art. They rarely forgive store copy that promises a different game.

Schedule the challenge the week before you book trailer reshoots or raise fest marketing spend—truth first, amplification second.

The five logs you produce this week are the proof you can show a partner, a publisher, or your future self that the store page was intentional—not accidental. Keep them in release-evidence beside your demo depot audit so October week is paperwork, not panic. Then return to fifteen-minute Wednesdays until the October fest window closes.