Steam Community Hub Announcements and Store Metadata Parity - Next Fest 2026 Checklist for Micro-Studios

Your Steam Events headline is green. Your FAQ says solo demo. Yesterday's community hub announcement still promises co-op weekend tests and a full-game roadmap screenshot. Wishlisters get the hub notification first—they install before they re-open the store page. Partners screenshot hub posts beside build_id under intake compression the same way they capture store-demo mismatch FAQ rows.

This Process & Workflow checklist treats community hub announcements as store-adjacent marketing tied to Next Fest demo hour-one proof—not a separate social channel with different truth rules. It expands wishlist truth audit Day 6 into a standing audit. Pair with event post parity (Events tool) and metadata sprint. Anchor publishing to Steamworks community announcements. No invented studios or metrics.

Time to read: ~36 minutes. Time to run first hub audit: ~2 hours including export and proof table.

Why this matters now (May–October 2026)

1. Hub notifications bypass store scroll — Players act on push text before FAQ.
2. Fest week post volume spikes — Teams publish daily updates; scope creep accumulates.
3. Events ≠ hub posts — Green event checklist does not govern informal hub updates.
4. LLM draft risk — FAQ LLM pipeline tone spreads to hub paste without Gate D.
5. May is the habit month — Install Wednesday diff row for hub before October freeze.

Direct answer: Export live hub posts to git, build hub-post-proof.md (one row per published announcement), mark pass/fail against fest demo hour-one and green store surfaces, rewrite or unpublish failures, and gate new posts behind engineer sign-off until BUILD_RECEIPT hub_surfaces_locked is true.

Who this is for

Prerequisites

Hub post proof table (core artifact)

release-evidence/03-store/hub/hub-post-proof.md:

Pass rule: Every gameplay claim in the post is observable in fest demo hour one, or explicitly prefixed FULL GAME / NOT IN DEMO with matching store copy.

Fail rule: Edit live post, unpublish, or publish correction post that cites corrected build_id—do not leave fail posts up during paid traffic per fest marketing cap.

Hub vs Events vs patch notes (do not conflate)

Publishing the same scope lie on all three still fails—each needs its proof row or a shared canonical post linked from others.

High-risk hub post categories

Feature and mode announcements

Co-op weekends, PvP tests, mod tools, level editors. Cross-check tags and content descriptors.

Roadmap and timeline posts

Quarterly roadmaps belong in FULL GAME labeled sections—never imply modes are playable in fest zip.

Media posts

GIFs and screenshots must pass screenshot gates and trailer frame table—hub is not a loophole for cut content.

Discount and commercial posts

Regional pricing and DLC anchors must not promise demo content tied to purchases.

AI and generative updates

Match AI disclosure challenge and storefront disclosure rows.

Pre-publish gate (five steps)

Never skip step 3 because "it's just a small hub update."

BUILD_RECEIPT extension

"hub_surfaces_locked": false,
"hub_proof_path": "release-evidence/03-store/hub/hub-post-proof.md",
"hub_last_export_sha256": "",
"hub_post_count_live": 0

Lock when all live rows pass and validate-packet hub dimension exits 0.

Wednesday ritual row

After FAQ export in Wednesday ritual:

1. Export hub posts list or archive visible posts
2. Diff vs hub-approved/
3. New posts since last Wednesday → proof rows before promotion continues

Five to ten minutes prevents fest-week debt.

Evidence folder

release-evidence/03-store/hub/
  README.md
  hub-post-proof.md
  hub-approved/
  live-hub-export-YYYY-MM-DD.html
  engineer-signoff.txt
  producer-signoff.txt

Link from release-evidence taxonomy.

Triangle diff (hub leg)

Red-team questions

1. "Hub said co-op—where is invite?"
2. "Is this screenshot from the demo or full game?"
3. "Post says major update—why is zip unchanged?"
4. "Announcement promises AI voices—where is disclosure?"
5. "Fest post links old build_id—which is live?"

Common mistakes (eleven)

1. Treating hub as "social" not binding.
2. Copy-pasting Discord hype.
3. Skipping proof on "small" posts.
4. Events green so hub ignored.
5. Roadmap images without FULL GAME label.
6. No export after publish.
7. Mods pinning outdated posts.
8. LLM drafts without human diff.
9. October daily posts without re-proof.
10. Hub promises features vertical slice opinion bar does not meet.
11. Two-storefront itch post contradicts Steam hub.

Worked example (anonymous)

Before: three live hub posts; one promised co-op playtest.
Audit: co-op fail hour one.
Fix: Unpublished fail post; correction post with DEMO boundary; FAQ row 3 updated same day.
Result: Mock audit dimension on marketing surfaces green.

Writer ~3h; engineer ~2h; producer ~1h.

Integration with metadata sprint

Add optional Day 6b in 7-day metadata sprint: audit last 30 days hub posts + schedule Wednesday hub row.

Publisher diligence

Hub announcement audit <date> — hub-post-proof.md green; exports archived; live posts match build_id <id>.

Supports publisher diligence and partner ZIP.

Post-fest maintenance

Friday Block 5 hub row; re-proof after demo patch notes; tag drift sprint if scope tags changed.

Ninety-minute hub backlog audit (first time)

Start with pinned and fest-week posts—highest refund risk.

Sample proof rows

Row — Playtest invite:

Row — Demo launch:

Moderator and community macro policy

Mods answer questions with linked FAQ rows, not improvised features. Template:

For demo scope see FAQ #1: <url> — current build_id <id>.

Ban macros that say "full game soon" without FULL GAME label. Asia–EU handoff must not approve hub posts while EU sleeps without proof table update.

validate-packet hub dimension

Optional script checks:

• hub-post-proof.md exists
• No Fail rows for posts dated within 90 days
• hub_last_export_sha256 matches committed export
• Pinned post IDs listed in README

Fail blocks partner ZIP assembly.

Team RACI

Comparison to reactive recovery

Hub posts appear in refund tickets as screenshots—fix before UTM experiments send traffic to fest posts.

Ads and fest marketing coupling

Fest marketing cap: no boosted posts pointing at hub URLs until proof table green for all posts in the last 30 days. Paid social copy must match hub claims verbatim—no "multiplayer weekend" ads on solo demo.

Mock audit tabletop hook

Seven-dimension mock audit: facilitator reads newest hub headline aloud; engineer states hour-one proof without opening Steamworks. Fail if hesitation.

LLM draft guardrails

If using FAQ LLM pipeline patterns for hub:

• Gate A: frozen bullets from green About
• Gate D: human diff vs hub-approved/
• Gate E: hub-post-proof before publish

Never pipe model output directly to Steam client.

Specs and performance hub posts

Posts claiming "runs on Steam Deck at 60fps" need spec honesty and Deck tools captures—same bar as FAQ performance answers.

When to re-audit hub only

Beginner path

1. Read event post checklist for Events tool.
2. Clone hub-approved/ template from FAQ approved files.
3. Run ninety-minute backlog audit.
4. Install Wednesday hub export.
5. Lock hub_surfaces_locked after green table.

Operating review

Four Friday five-block review Block 4 (community): count posts published vs posts proofed—ratio must stay 1:1.

Intake compression talking points

Partners ask "what did you tell the community?" Open hub-post-proof.md + latest export—answer without scheduling a call.

Localization

Translated hub posts need localization QA—do not auto-translate roadmap hype into stronger claims than English store copy.

Hash and promotion coupling

After cold-hash week, publish hub post only after receipt shows new build_id—posts citing old ids recreate mismatch timelines.

Snippet-friendly answers

Do community hub posts affect refunds?
Yes. Players treat them as official scope promises, especially when Steam sends notification emails.

How is this different from Steam Events?
Events use the Events tool and event parity checklist; hub announcements use community posts—both need proof tables.

How often should we audit?
Backlog once in May; Wednesday diff weekly; full re-scan after any demo scope change.

Glossary

Schedule hub backlog audit the week your fest demo branch first promotes—most fest-week lies are old posts you forgot to unpin.

Correction post template (when you already failed)

When a fail post went live:

## Correction — demo scope (build_id <id>)

Our <date> hub post overstated online features. The **Next Fest demo** is **solo only** through Act 1.  
FAQ: <store url>  
We unpinned the prior post. Sorry for the confusion.

Publish within 24 hours of discovery—partners treat fast correction better than silent edits. Log correction ID in hub-post-proof.md.

Pinned post policy

External social mirroring

Discord announcements and X threads should copy hub-approved markdown—not invent stronger claims. If social exceeds hub truth, social is wrong. Link hub correction posts from social within one hour.

Evidence cycles opinion

Per evidence cycles, batch non-critical hub typos weekly—but never batch scope claims. Scope posts publish only after same-day proof.

Depot and branch naming in hub copy

Posts saying "download the latest beta" must cite branch naming string matching library label—avoid default shorthand players cannot find.

Press and influencer kits

Influencer briefs should link hub-approved/ canonical post—not a custom Google Doc with extra modes. Press kits attach hub-post-proof.md summary table for diligence.

Additional common mistakes (five)

12. Editing hub HTML in Steam client without git export.
13. Scheduling posts while engineer offline.
14. Cross-posting Events headline stronger than hub without shared proof.
15. Ignoring non-English hub posts.
16. Assuming pinned "Known Issues" exempt from proof.

October freeze

September: no new scope claims in hub—only build_id maintenance and typo fixes. October fest week: pre-written pass-row templates only; no improvised feature announcements during traffic spikes.

Hub post calendar for fest week (template)

Pre-write pass-row drafts in git before October—publish by copy-paste, not improvisation.

Wishlist truth audit coupling

7-day wishlist truth audit Day 6 community hub becomes mandatory when this checklist exists—run backlog audit that day, then maintain Wednesday exports. Skipping Day 6 while running sprint Day 7 leaves notifications lying.

Crash-log and support escalation

When crash-log challenge surfaces instability, hub posts must not claim "stable on Deck" until captures exist—same rule as spec honesty. Link log upload instructions instead of performance superlatives.

Partner question script

When partners ask "what did you communicate to players?":

1. Open hub-post-proof.md.
2. Attach last export + BUILD_RECEIPT build_id.
3. List pinned post IDs with pass status.

Under two minutes—fits 72-hour intake windows.

Metrics you should not invent

Do not claim "10,000 co-op sessions" or "viral hub engagement" in official posts unless telemetry exists in release-evidence/04-telemetry/ with methodology footnote. Fest marketing needs honest scope, not vanity counters—operating review Block 4 should track posts proofed / posts published, not impressions alone.

Handoff to community contractors

If contractors draft hub posts, contract language must require: git markdown delivery, engineer sign-off field, and export within 24h of publish. Contractors without Steam login still produce claims—you review proof table, not tone.

Key takeaways

• Community hub posts are store-adjacent—audit like FAQ.
• hub-post-proof.md per live announcement.
• Pre-publish five-step gate with engineer hour-one sign-off.
• Events checklist does not replace hub checklist.
• Wednesday export diff prevents fest-week drift.
• FULL GAME vs DEMO labels in posts.
• Triangle-diff hub against store surfaces.
• BUILD_RECEIPT hub_surfaces_locked when green.
• Unpublish or correct fails before ads restart.
• Cheaper than 48-hour mismatch recovery.
• Correction posts within 24h when fails shipped.
• Pin policy limits stale scope amplification.
• Social mirrors hub-approved markdown only.
• Metadata sprint Day 7 should include hub as eighth surface.
• Track posts proofed vs posts published in operating review.
• Contractor drafts require engineer sign-off fields.
• Unpin outdated posts before running paid fest traffic.

FAQ

Do pinned hub posts need re-audit?
Yes—pins amplify old lies; unpin or update.

Can mods write posts?
Only with same proof gate; producer approves.

What about comments?
Macros and pinned comments follow FAQ truth—separate moderation doc.

October policy?
Typos only unless build_id changes—then re-proof affected posts.

How relate to 5-day metadata freeze?
Assign hub to marketing freeze day.

Should we delete old fail posts?
Unpublish or edit with visible correction—silent deletes still appear in player screenshots partners receive.

Can hub posts link to itch demos?
Only if two-storefront rule scope labels match—separate proof rows per storefront.

Conclusion

Hub announcements feel informal—they perform like push notifications with legal weight. A co-op weekend post on a solo fest demo destroys the same trust as a lying FAQ row, faster, because wishlisters never scroll back to your store page first. The hub channel is where scope lies compound during fest week because teams post faster than they proof.

Export hub history. Proof every claim. Unpublish what hour one cannot show. When October traffic spikes, you will publish daily updates on a rail that already proved truthful in May.

Audit your last three hub posts tonight. One correction post beats a fest-week refund spiral.

When metadata sprint Day 7 goes green, add hub as the eighth surface—store truth is not complete if notifications still lie. Treat every hub notification as a contract sentence: if you would not put it in FAQ row one, do not broadcast it to wishlisters. Proof the backlog before you schedule the next announcement. Unpin before you promote. Export after every publish. Diff against git every time.