Lesson 217: H1 Player Trust and Observability Capstone Receipt (2026)

Direct answer: H1 2026 player trust closes when h1_player_trust_capstone_v1.json links five child receipts from Lessons 212–216, proves build_label alignment across saves, telemetry, crashes, refunds, and AI dialogue patches, and points to the prior Q4 capstone (211) so fest promotion is not “trust GREEN, scope RED.”

Why this matters now (H2 traffic on H1 receipts)

July–August 2026 studios promote fest_public while H2 playtests spike. Partners and players ask one question: “Can you prove this build respects saves, privacy, crashes, refunds, and generative dialogue?” Scattered JSON in release-evidence/ without a capstone row forces four Slack threads during Thursday BUILD_RECEIPT review.

This lesson is the single promotion gate for the 212–216 arc—same pattern as Lesson 211 Q4 capstone but for trust & observability, not Fab URLs. Pairs GameMaker GX upload preflight (channel build_label discipline) and 12-free playtest isolation runbooks.

Beginner path (45-minute capstone audit)

Time: ~45 minutes when child lessons done; 75 minutes first audit across surfaces.

Developer path (gates H1–H8)

Child receipt crosswalk (do not re-author)

Copy paths only from lesson outputs—capstone does not duplicate gate logic.

H5 n/a rule: If the promotion train ships zero generative dialogue changes, set ai_dialogue_patch_receipt: "n/a" with reason combat_only_train—still require H6 build_label bump.

build_label alignment matrix (H6)

Surface column: Child receipts that include surface must agree with Lesson 206 facilitator map (playtest_invite vs fest_public).

h1_player_trust_capstone_v1.json

{
  "schema": "h1_player_trust_capstone_v1",
  "build_label": "fest-demo-2026-10-rc4",
  "arc_lessons": ["212", "213", "214", "215", "216", "217"],
  "receipts": {
    "212": "save_slot_label_receipt_v1.json",
    "213": "telemetry_session_receipt_v1.json",
    "214": "crash_symbolicate_receipt_v1.json",
    "215": "refund_dashboard_receipt_v1.json",
    "216": "ai_dialogue_patch_receipt_v1.json"
  },
  "receipt_paths": {
    "212": "release-evidence/saves/SAVE_SLOT_LABEL_RECEIPT.json",
    "213": "release-evidence/telemetry/TELEMETRY_SESSION_RECEIPT.json",
    "214": "release-evidence/crash/CRASH_SYMBOLICATE_RECEIPT.json",
    "215": "release-evidence/refunds/REFUND_DASHBOARD_RECEIPT.json",
    "216": "release-evidence/ai-dialogue/AI_DIALOGUE_PATCH_RECEIPT.json"
  },
  "prior_arc_pointer": {
    "lesson": "211",
    "schema": "q4_post_shipping_capstone_v1",
    "path": "release-evidence/capstone/Q4_POST_SHIPPING_CAPSTONE.json",
    "required_for_fest_promotion": true
  },
  "gates": {
    "H1_save_slots": "pass",
    "H2_telemetry_no_pii": "pass",
    "H3_crash_symbolicate": "pass",
    "H4_refund_dashboard": "pass",
    "H5_ai_dialogue": "pass",
    "H6_build_label_crosswalk": "pass",
    "H7_q4_capstone_linked": "pass",
    "H8_capstone": "pass"
  },
  "fest_promotion_allowed": true
}

Pin under release-evidence/capstone/H1_PLAYER_TRUST_CAPSTONE.json. Folder taxonomy: release-evidence spine.

BUILD_RECEIPT capstone row

Thursday row review — add H1 Capstone section listing 212–216 pass/fail/n/a. BUILD_RECEIPT beginner pipeline explains column naming if the sheet is new.

Proof table (H1 promotion week)

Key takeaways

1. Capstone = wiring, not re-teaching PostHog or Steam Cloud steps.
2. build_label is the join key across trust receipts—same discipline as Lesson 201 triple-channel.
3. Lesson 213 blocks promotion if prompts leak into telemetry.
4. Lesson 216 is required for any generative dialogue in the train.
5. Lesson 211 Q4 capstone still required—trust without playtest URL isolation fails fest week.
6. Refund dashboard (215) explains player pain; capstone proves you correlated it to builds.
7. Crash symbolicate (214) without build_label makes refunds and crashes incomparable.
8. H2 fest hardening continues in Lessons 218–223—wire 217 before filing 223 so trust + perf promote together.
9. Course-Planner refill follows—H1 arc 212–217 is complete after this lesson; H2 arc 218–223 closes with Lesson 223.

Prerequisites

• Lesson 212 — save slot labels
• Lesson 213 — telemetry without PII
• Lesson 214 — crash symbolicate
• Lesson 215 — refund dashboard
• Lesson 216 — AI dialogue patch
• Lesson 211 — Q4 capstone
• Save-slot recovery case study
• PostHog privacy-safe pipeline

Common mistakes

• Filing capstone while Lesson 214 still shows symbolicate_pass: false.
• Different build_label on telemetry vs crash receipts “because backends differ.”
• Skipping Q4 capstone link because “we already did playtest isolation last month.”
• Treating combat-only train as dialogue-patch pass without explicit n/a.
• Promoting fest_public while playtest_invite row still shares Cloud save filenames (Lesson 212).

Troubleshooting

Mini exercise (70 minutes)

1. Intentionally mismatch telemetry build_label—confirm H6 fails.
2. Fix crosswalk; verify all five paths resolve.
3. Set 216 to n/a on a combat-only dry run—confirm H5 allows with note.
4. Link Q4 capstone path from Lesson 211 output.
5. File h1_player_trust_capstone_v1.json; run Thursday review row.

Continuity — H1 arc close (212–217)

Prior arc: Lessons 206–211 (Q4 post-shipping). H1 212–217 arc complete.

Next: Lesson 218 — Godot Deck static menu receipt (opens H2 218–223 fest hardening arc).

FAQ

Skip capstone if only one receipt changed?
Re-run H6–H8 minimum; full capstone JSON still updates capstone_version semver.

Web-only HTML5, no Steam Cloud?
H1 save receipt may be n/a with local_save_label_map documented—H2–H5 still required for fest builds with telemetry.

Partner packet vs this capstone?
Lesson 180 governance is partner-facing; this is ops promotion proof.

Does capstone replace Wednesday smoke?
No—Wednesday smoke ritual runs before child receipts; capstone aggregates results.

One BUILD_RECEIPT row for player trust—H2 traffic meets receipts, not promises.