Lesson 221: Multi-Channel Facilitator Amendment Receipt on BUILD_RECEIPT (2026)

Direct answer: When VERSION, channel_label_match, or authorized surfaces change after Lesson 206 sign-off, stop facilitator sessions, file facilitator_amendment_receipt_v1.json with version_pin_ok: true on the new pin, and update BUILD_RECEIPT facilitator_amendment_pass before paying invoices or running Lesson 220 batch Whisper on stale clips.

Why this matters now (October 2026 mid-week hotfix)

October 2026 playtest week ships fest-demo-2026-10-01-rc1 Monday and fest-demo-2026-10-03-hotfix1 Wednesday. Facilitators already ran two GX sessions on rc1; Steam HTML5 logs show hotfix1 while the signed SOW still pins rc1. Finance approves the invoice; ops discovers itch_public URLs in the playtest Discord thread—scope bleed, not malice. Q3 2027 cousin: pair scope amendments with Lesson 239 feedback tag taxonomy so triage labels stay aligned after pin bumps.

Lesson 201 channel_label_match catches label drift on uploads; GameMaker VERSION pin preflight catches sign-time pins—this lesson is the BUILD_RECEIPT amendment milestone when contracts and receipts must move together mid-week.

Planned blog #11 (facilitator contract template) ships the SOW; community playtest resource #12 refreshes README blocks—this lesson owns facilitator_amendment_receipt_v1.json.

Beginner path (amendment in one sitting)

Time: ~25 min documentation + ~20 min facilitator re-sign—65 minutes first hotfix week.

Developer path (gates M1–M6)

Channel scope amendment block

Append to SOW as Amendment §A (initialed):

Rule: any new surface key requires playtest isolation map update before M6.

facilitator_amendment_receipt_v1.json

{
  "schema": "facilitator_amendment_receipt_v1",
  "facilitator_id": "fac-oct-2026-01",
  "amendment_id": "amd-2026-10-03-hotfix1",
  "version_pin_before": "fest-demo-2026-10-01-rc1",
  "version_pin_after": "fest-demo-2026-10-03-hotfix1",
  "version_pin_ok": true,
  "channel_label_match_after": true,
  "scope_amendment": {
    "surfaces_added": [],
    "surfaces_removed": [],
    "surfaces_visibility_changed": ["gx_public"]
  },
  "prior_contract_receipt": "release-evidence/ops/FACILITATOR_CONTRACT_RECEIPT.json",
  "amendment_pdf_sha256": "sha256:REPLACE",
  "vod_sessions_invalidated": ["fac-02-2026-10-02-eve"],
  "gates": {
    "M1_prior_archived": "pass",
    "M2_pin_changed": "pass",
    "M3_triple_channel": "pass",
    "M4_scope_block": "pass",
    "M5_vod_invalidation": "pass",
    "M6_build_receipt": "pass"
  }
}

Pin under release-evidence/ops/FACILITATOR_AMENDMENT_RECEIPT.json. BUILD_RECEIPT columns: facilitator_amendment_pass, version_pin_ok, version_pin (current).

Lineage table (audit)

BUILD_RECEIPT row (post-amendment)

Run Thursday row review after Wednesday smoke on hotfix1.

Key takeaways

1. Amendment ≠ optional email—file JSON or invoices lie.
2. version_pin_before/after must differ or you are not amending—you are hiding drift.
3. Re-run Lesson 201 compare on the new pin before M6.
4. Invalidate VOD batch rows tied to old pin (Lesson 220).
5. GameMaker VERSION pin is sign-time; Phaser amendment surface map is engine boot + wrapper parity; this lesson is mid-week change control.
6. itch custom domain deferrals stay on Lesson 208 hosting decision—do not sneak CORP work into amendment without 222.
7. Facilitator Discord README must show current pin only.
8. GX internal→public promote is a visibility amendment, not a free scope expansion.
9. Archive prior contract receipt—never delete lineage (M1).
10. H2 capstone 223 will require facilitator_amendment_pass or explicit n/a with reason.

Common mistakes

• Paying facilitator before M6 while clips reference rc1.
• Amendment PDF signed but channel_label_match still false on hotfix1 logs.
• Adding fest_public to scope without producer approval.
• Skipping GX re-upload after pin change—receipts disagree.
• Treating amendment as substitute for initial Lesson 206 contract.

Troubleshooting

Mini exercise (55 minutes)

1. Archive contract receipt for rc1.
2. Bump VERSION to hotfix1; fail M2 if pins match.
3. Re-run triple-channel compare; file amendment JSON.
4. Mark one VOD session invalidated in batch receipt.
5. Update BUILD_RECEIPT; run Thursday review row.

Continuity — H2 2026 arc (218–223)

Previous: Lesson 220 — facilitator VOD concat batch
Next: Lesson 222 — Construct CORP/COEP fest HTML5 receipt.

FAQ

Same as Lesson 206?
206 is initial contract; 221 is mid-week change with version_pin_before/after and VOD invalidation.

Same as Lesson 201?
201 proves labels match on a build; 221 governs legal/ops when that build changes under an active facilitator.

Can we amend without facilitator signature?
No—M4 requires initialed scope block; unpaid work stays paused.

October only?
Hook is October 2026 hotfix week; use whenever VERSION moves during contracted playtests.

A hotfix without facilitator_amendment_receipt_v1.json is not “same facilitator, new build”—it is unapproved scope drift billed as playtesting.