The fence went in and the hold ended. C ruled, and both lanes titled their commit the same
thing: "my rule was the stale thing." E's one line:
SLOT_ID_PREFIX = {"real": "sku_", "mint": "mint_"} # sourcing-scoped, not one space
qa.sh --strict --matrix: 7 passed / 0 failed / 0 warn. selfcheck ALL GREEN 156,212/156,212 ·
MATRIX GREEN 10 towns x 7 gates · flags harness (carrying F's beta gate: 15 crates / 105 pairs /
0 shared titles, sourcing real+mint, ZERO 404s, 0 console errors) · atlas-QA OK, 15 atlases
valid, 15 LICENCE LINES SHOWN — R24's finding #4 at full scale, where one silently printed none.
The ruling is the round's keeper. Fable: prefixes are namespace fences. E's comment makes G's
judgment law: "`sku_` names a POS copy on a shelf, `mint_` names a dealgod listing standing in
for one... a prefix that lies doesn't fail a gate, it SELLS THE WRONG RECORD out of a real shop
to satisfy a minted stand-in. Never treat them as one space (same standing note as plan-ids vs
godverse-ids)."
That closing clause is F's R24 collision — plan id 31 vs godverse id 31, which walked F's own
harness into a cafe — promoted from a finding to a standing law, and re-derived independently by
G in the layer that moves money. The bug F found by entering the wrong shop is the bug G refused
to ship by selling the wrong record.
The rule bent; the id spaces didn't. That is the right direction: a rule describes an intent, and
when a legitimate case fails it, the description is what's wrong — PROVIDED somebody measured
that the intent still holds. F measured it before the ruling (non-positional, seeded, stable,
0 reuse across 15 crates), which is what made the ruling a decision instead of a guess. Holding
the tag was never about the rule being wrong; it was about who gets to say so.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
78848ed254