Adopted 11 September 2026 (advice item 6). The mark ritual works before the ledger exists; when practice.mark receipts land (Library #88), the line below becomes the receipt’s human-readable form.

Next Thursday

Thursday 17 September 2026 · 09:00 Pacific (16:00 UTC) · Ken hosts · join from the community events page — the link is posted there the morning of. Bring a receipt, or come to watch one. (A host updates this line each week.)

Run-of-show (60 minutes, Ken hosts until a 400 does)

Minute What happens Who
0–5 Receipts. Every 100 shows a bundle hash and says the rule they wrote. No slides. the 100s
5–15 One 200 shows a diff: what one policy change did to a real run. a 200
15–25 One 300 says a coverage number — or “cannot count yet” — and who could reproduce it. a 300
25–35 One 400 reads a verification statement of someone else’s bundle, offline. a 400
35–50 The case of the week (FailFest) — the gate that would have caught it, in plain words, then as code. the host
50–58 Marks. The host reads each mark aloud (the line below). the host
58–60 Who hosts next; who is pairing with whom; the Tuesday Letter line. the host

The second-hour Thursday (for people who cannot make 09:00) is proposed, not yet on the calendar; ask Wren.

The mark line — the receipt until the receipt exists

One line per mark, written by the host into the Thursday recap (the recap becomes next week’s story):

MARK · <level> · <first name or "a member", with permission> · <bundle or artifact hash, first 12> · host <host's name> · <date>

Example: MARK · 100 · Bob · 7f3a9c1e02bd · host Ken · 2026-09-17

Rules: a mark names a level, never a system; the hash is the artifact’s, never its content; “with permission” means the person said yes on the call; a mark can be corrected by the same host in the next recap. When practice.mark receipts exist, the host’s line is generated from the receipt, not typed.

What the host brings