Wednesday Steam Store Metadata Diff Ritual - Fifteen Minutes Before Fest Branch Promotion

You promoted nextfest-oct-2026-rc4 at lunch. The store still says last week's demo scope, the FAQ still promises co-op, and the About section still names last month's LLM vendor. Players install the new build and blame you for lying—not Steam, not the algorithm.

Process & Workflow for micro-studios is often binary: heroic upload nights or nothing. This article defines a Wednesday fifteen-minute metadata diff ritual that runs before any fest branch promotion—so store text, depot reality, and BUILD_RECEIPT ids stay aligned through October 2026 Next Fest and Q3 2026 partner windows.

Pair with Friday Block 5 (evidence hygiene) and FAQ LLM pipeline (copy governance).

Who this is for and what you get

Time: 15 minutes weekly (Wednesday default); +5 minutes when build_id changes demo scope.
Prerequisites: Exported store copy in git or release-evidence/store-metadata/, live Steamworks access, current fest branch name documented.

Why this matters now (May 2026)

1. Branch promotion ≠ store update — Steamworks separates build promotion from page copy; teams forget the second step.
2. FAQ and AI annex drift — Human diff gates fail if Wednesday never catches live-page drift.
3. Fest cap discipline — Marketing spend assumes honest pages; paid traffic on stale metadata burns runway.
4. Six-week lock — Timeline assumes metadata freezes; Wednesday is how you earn the freeze.
5. Partner parity — Mock audit dimension 7 compares FAQ, About, and demo.

Direct answer: Log wednesday-metadata-diff-YYYY-WW.md with pass/fail per field group; no fest branch promotion that week if RED rows remain.

What counts as store metadata (field groups)

Export live page to store-metadata/live-YYYY-MM-DD.txt each Wednesday (copy-paste or script)—diff against store-metadata/approved/ in git.

Building store-metadata/approved/ for the first time

When demo scope changes, create new approved baseline—do not edit history silently.

G4 media diff detail

Screenshots and trailer links fail in predictable ways:

Keep store-art/screenshots/ folder dated alongside screenshot safe zones exports.

G5 commercial diff detail

Price and DLC metadata drift hurts conversion:

• Base price matches regional second pass documented rows
• DLC linked on store page exists in Steamworks
• No fest-week surprise discount without cap worksheet update
• DLC anchor worksheet bullets reflected if cosmetics marketed

G6 demo linkage detail

Internal doc (not always public) must list:

• Fest branch name
• Demo depot id(s)
• Last cold install date
• Password rotation date if playtest
• Link to demo depot audit

G6 RED when engineer promotes branch but audit file still references previous rc.

The fifteen-minute ritual (minute-by-minute)

Set calendar invite: "Wednesday metadata diff — promotion gate."

RED / YELLOW / GREEN rules

YELLOW is not "ship anyway"—it means finish FAQ Gate D before promotion.

Log template

# Wednesday metadata diff — 2026-W21
build_id: nextfest-oct-2026-rc4
branch: nextfest-oct-2026-rc4
reviewer: (name)

| group | status | notes |
|-------|--------|-------|
| G1 | GREEN | |
| G2 | YELLOW | About AI vendor sentence pending FAQ sync |
| G3 | RED | FAQ Q05 still says co-op |
| G4 | GREEN | |
| G5 | GREEN | |
| G6 | GREEN | demo depot id matches audit |

Promotion this week: BLOCKED (G3 RED)

Save under release-evidence/05-operations/store-metadata/.

Promotion gate integration

The gate exists because teams routinely treat green CI as green launch. CI proves the binary; Wednesday proves the story. Partners and players judge the story first.

Add to your promotion checklist (beside validate-packet):

[ ] Wednesday metadata diff log exists for this ISO week
[ ] No RED rows
[ ] BUILD_RECEIPT build_id matches branch string
[ ] Cold install rehearsed since last metadata change (if G3 touched)

Engineers script gate as pre-promote hook if desired—humans still own G3 judgment.

Worked example (composite micro-studio week)

Context: Duo shipping nextfest-oct-2026-rc4 Thursday; Wednesday ritual runs first.

Outcome: Thursday promotion slipped one day—cheaper than fest-week reputation damage.

Field-by-field diff prompts (G1–G3)

Use these questions when reading live vs approved text:

G1 short description

• Does the first sentence match demo first-hour experience?
• Are platforms listed correctly?
• Any feature words not in source bullets?

G2 long / About

• AI disclosure sentences match ai-disclosure/ annex?
• Roadmap language qualified ("planned," "in development")?
• Credits and engine version current?

G3 FAQ

• Each answer traceable to approved faq-approved/ file?
• Demo scope questions negated where needed?
• No [NEEDS_HUMAN] placeholders live on store

Tools that help (free / common)

No single vendor required—repeatability beats stack.

Distributed team handoff

When Asia-EU handoff promotes overnight:

• EU morning: run Wednesday diff before announcing branch to marketing
• Asia evening: export live-*.txt after any emergency copy fix
• Never "quick fix" FAQ in Steam without updating git approved files

Add handoff_metadata_diff: pending|done to BUILD_RECEIPT optional fields if you use JSON receipts.

Intake compression and partner packets

Q3 intake compression means yellow flags arrive fast. Attach last four Wednesday logs to partner ZIP—shows sustained discipline, not one heroic audit.

Pair with partner ZIP naming 05_ops/ store-metadata folder.

Calendar integration (May–October 2026)

Escalation when RED persists

If RED spans two weeks, run truth audit—weekly ritual is not enough.

Snippet-friendly answers

What is a store metadata diff?
A weekly compare of live Steam store text and media against approved copy in git (or exported baseline), logged before fest build promotion.

How long does the ritual take?
15 minutes when exports exist; first runs may take 30 minutes while you create store-metadata/approved/ baselines.

Can engineers skip if "only binary changed"?
Only if G6 confirms demo depot unchanged and G3 FAQ unchanged—rare; default is run full ritual.

Operating review hook

Four-Friday operating reviews Block 2 add:

• Wednesdays GREEN count last month
• Longest-open RED row
• Correlation with wishlist grumble threads (qualitative)

Relationship to Friday Block 5

Same person can run both; logs stay separate so fest post-mortems show which layer failed.

Month-one adoption ladder

By week four the ritual should feel faster than explaining a store lie on Discord.

Roles on a three-person team

Solo dev: run all groups but still write log—future partner diligence needs paper trail.

When Wednesday conflicts with promotion day

If promotion must happen Wednesday:

1. Run ritual first in morning.
2. Promote only after GREEN.
3. Re-export live-*.txt post-promotion same day.
4. Note in log: "post-promotion export pending Thursday mini-diff."

Never promote at 11pm without log because "players are waiting."

Vertical slice and final-week fest

7-day vertical slice challenge Day 4 store parity assumes metadata truth. Wednesday ritual in the week before Day 4 prevents starting the challenge with live-page lies.

Hash mismatch recovery pattern

If partner flags store/demo mismatch, Wednesday logs prove whether copy or binary drifted first—recovery pattern similar to hash case study discipline (evidence timeline, not same failure class).

Pairing with truth and disclosure sprints

• 7-day truth audit is a deep pass; Wednesday is weekly regression.
• 7-day AI disclosure challenge seeds G2/G3 content; Wednesday catches drift after.
• Prompt registry freeze does not replace G2—runtime ≠ marketing.

Pre-promotion tabletop (10 minutes, optional)

When promotion is high-stakes (fest launch week):

1. Producer reads G3 FAQ aloud from live page.
2. Engineer confirms on installed build_id.
3. Marketer confirms UTM landing matches G1 promise.
4. Sign Wednesday log together.

Ten minutes prevents hour-long social media damage control.

Metrics without fake benchmarks

Track internally:

Improve the ritual; do not publish metrics as marketing claims.

CI and release automation hooks

Optional pre-promote script pseudologic:

if ! test -f release-evidence/.../wednesday-metadata-diff-${ISO_WEEK}.md; then exit 2
if grep -q '| G3 | RED' that_file; then exit 3
if grep build_id receipt != branch; then exit 4
exit 0

Align exit code legend with validate-packet documentation style.

Cold-hash and metadata same week

Teams on cold-hash challenge should run Wednesday diff before Friday hash on demo zip—binary integrity without copy integrity still fails partners.

Beginner path (first Wednesday ever)

1. Copy live short description into store-metadata/live-2026-05-18.txt.
2. Copy same text to approved-baseline.txt after human read once.
3. Next week: diff the two files.
4. Any unexpected line → investigate.
5. Celebrate boring empty diffs.

Success: you know where live copy lives and what "approved" means for your team.

Second-week expansion

Add FAQ export to the ritual even if FAQ is empty—empty FAQ is a valid baseline. Add one screenshot filename list. When week-two diff shows a new FAQ answer you did not approve, you have proof the ritual caught drift before a fest branch promotion.

Third-week expansion

Wire the promotion gate: tell your team "no Steam branch promotion without Wednesday log file path in Slack." Social enforcement beats hoping everyone remembers.

Incident response when live page lied during fest

Wednesday ritual reduces incidents; it does not eliminate human error. Treat the log file path as part of your definition of done for fest promotion—the same way you treat green CI.

Fest marketing and icon gates

• Fest spend cap: no spend increase while G3 RED.
• 32px icon: capsule text still appears in G1 scans.

Common mistakes (seven)

1. Diff after promotion — Players see the lie first.
2. Only checking build notes in Steamworks — Players read store page.
3. Skipping weeks without releases — Drift accumulates quietly.
4. One-person team skips log — Future partner questions have no answer.
5. Fixing FAQ in Steam without git — Next diff breaks.
6. Ignoring screenshot group — Visual demo scope lies.
7. Wednesday green, Thursday manual edit — Re-run diff or block Friday promotion.

Pro tips (six)

1. Screenshot store page when GREEN—attach to log.
2. Tie to UTM week — note campaign id in log header.
3. Automate text export with Playwright or manual copy—consistency beats tooling brand.
4. Align with evidence cycles — metadata week alternates heavy engineering weeks.
5. Block fest marketing on RED — same stop rules.
6. Index logs by ISO week — 2026-W21 sorts correctly.

Key takeaways

• Branch promotion and store metadata are separate events—Wednesday closes the gap.
• Fifteen minutes weekly beats fest-week copy firefights.
• Six field groups: short, long, FAQ, media, commercial, demo.
• RED blocks promotion that week—non-negotiable.
• Log in release-evidence/05-operations/store-metadata/.
• Complements Friday Block 5, FAQ pipeline, demo depot audit, truth audit.
• October 2026 Next Fest traffic punishes stale FAQs more than stale trailers.
• Partners ask what was live when—logs answer.
• Approved baselines version with demo scope—never silent edits.
• G4 screenshots are metadata—diff them weekly in fest prep months.
• RED promotion blocks are feature, not bureaucracy.
• Solo teams still write logs for future diligence.
• Combine with validate-packet and BUILD_RECEIPT for full upload-week story.
• ISO-week log filenames keep four months of fest prep searchable in one glance.

Export script sketch (optional)

Teams comfortable with Python can scrape Steam store page text into grouped files—human review still required:

# Pseudocode — adapt to your store URL and compliance rules
groups = {"g1_short": "#short", "g2_about": "#about", "g3_faq": ".faq"}
for name, selector in groups.items():
    text = fetch(store_url, selector)  # your implementation
    write(f"store-metadata/live-{date}-{name}.txt", text)

Log script version in Wednesday header. Script does not replace human RED/YELLOW judgment on G3.

Post-October retrospective

Within seven days after fest:

1. Count RED weeks during prep.
2. List promotion delays caused by metadata.
3. Note whether fest marketing cap stop rules fired on RED.
4. Archive logs to fest-2026-retro/ for next cycle.

FAQ

We promote daily during crunch—still Wednesday?
Run a mini diff (G3 + G6 only) on promotion days; full ritual weekly.

No git for store copy?
Start exporting live-*.txt every Wednesday—git comes later.

What if only trailer changed?
G4 only; still log row—proves ritual ran.

Does this replace 32px icon gates?
No—art gates are separate; Wednesday may note capsule text in G1.

How does this interact with diligence packets?
Attach four recent Wednesday logs to show store discipline—not a substitute for demo quality.

We use LLM for all copy—skip ritual?
No—LLMs increase drift risk; ritual is more important, paired with FAQ pipeline.

Conclusion

Promoting a fest branch without a metadata diff is shipping two products: the binary players get and the story the store tells.

Book fifteen minutes every Wednesday. Block promotion on RED. Let October players meet the game you actually built.

The ritual is small. The trust it protects is not.

Set the recurring calendar event before your next fest branch promotion—not after the first angry review mentions co-op that does not exist.

Fifteen minutes on Wednesday is cheaper than fifteen hours of community management explaining why the store page lied.

If your team already runs strong evidence cycles, slot Wednesday in the light week between validator and binary promotion work—metadata discipline is part of the cycle, not an interruption. The calendar invite title should include the word gate so nobody confuses this with optional paperwork.