monster/PROCITY
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fable (integrator): R27 wave-2 status — F's three load-bearing inputs (pick-then-omit, make-fixture for gone[], the lifecycle switch)

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
m3ultra 2026-07-17 14:13:39 +10:00
parent bee7563a76
commit 70743db47e
1 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
docs/LANES/ROUND27_INSTRUCTIONS.md
View File

@ -71,6 +71,34 @@ fences (`sku_`/`mint_`, plan-id/godverse-id) · no golden moves expected this ro
touches no plan, no cache, no atlas bytes) · the offline law is THE gate this round, not a
footnote.
## WAVE-2 STATUS + F'S THREE LOAD-BEARING INPUTS (Fable, post-wave review)
*A/B/C/E/G are ALL IN. The beta tagged. What remains is F's close (#2 reader → #3 gate → #4
sandbox → #5 tour → #7 tag). The waves handed F three inputs that change the brief's letter —
build to THESE, not to my original wording:*
1. **C's seam ruling (§8): direct wire, no hook — but PICK-THEN-OMIT is law.** The naive wiring
(filter `pack.items`) RESHUFFLES the crate — C measured one sale changing 21 other records.
The reader draws from the stable full list and omits `gone` after: a crate with 3 sold shows
13, not a different 16. **Assert zero collateral in the gate** (sell one fixture record, the
other 119 identities unchanged). "Selling one record must remove one record, not re-stock
the shop."
2. **G's finding: `gone[]` has no subject in production.** The real POS has recorded no sale
since 2026-07-01 — 0 of crate 550's 120 records have ever sold, so a sold-means-gone assert
on live data passes vacuously forever. G built the remedy: **`make-fixture`** gives the gate
a subject. The gate MUST use it (vacuous-gate law — G flagged it before the gate could be
born blind).
3. **G's lifecycle is the kill switch:** `godverse_server.py start|stop|status` — the
kill-the-server gate drives it directly. The three fences are machine-enforced (read-only
credential measured permission-denied; `/reserve`+`/buy` → 501; metadata only, mint shops
404) — assert on them as fences, not re-derive them.
*Also for the record: E's freeze caught redhill_godverse missing from the towns roster for
three rounds (on disk, pinned, bootable by key — invisible only in B's selector; the one
consumer nobody gated). E owned it, fixed it, and wrote the gate-shape lesson. B verified the
R26 handshake against G's real manifest. A judged the risk list line-by-line and correctly
CARRIED risk #1 — "nothing retires this line except that gate going green."*
## THE EXACT RUN ORDER
0. **WAVE 0: F re-runs and tags `v5.0-beta`.** Hard stop until it lands.