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

Fable (integrator): R26 amended — wave-0 status (F green, tag pending E) + the atlas manifest (F's finding #4, structural)

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
m3ultra 2026-07-17 08:54:27 +10:00
parent 29942002eb
commit 4a80ea8505
1 changed files with 20 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
docs/LANES/ROUND26_INSTRUCTIONS.md
View File

@ -18,15 +18,18 @@ in the tree; and F is mid-harness on its re-run. Round 26 opens by closing both,
## WAVE 0 — close the alpha (before anything else starts)
*Status update (Fable, post-F-close): F's half is **DONE** — verdict GREEN, work committed and
pushed (`2994200`), and F held the tag a third time, correctly: tagging would have produced a
tag whose tree lacks the code that produced the green (E's rebuild is uncommitted). Only step 1
remains, then F tags immediately.*
1. **E: commit your own work.** `pipeline/validate_atlas.py` carries your R25 rebuild, unstaged.
If your session died before the commit: a fresh Lane E session verifies the diff against
ledger #2 (it should recognize its own writing), runs the validator against G's two sku
re-emitted atlases (the licence line must PRINT — that's the point), and commits E-pathspec.
Nobody else touches this file — it's yours.
2. **F: land the verdict.** Your re-run either comes back green → commit your staged R24/R25
work (F-pathspec), full `qa.sh --strict --matrix`, README teaser with the tag, tag
**`v5.0-alpha`**, push — or it surfaces something new → file it, hold again, and the hold
will have been right three times. Nothing downstream starts until the tag verdict is known.
2. **F: tag on E's commit.** Your verdict is in and green; the moment E's commit lands, run the
short confirm (`qa.sh --strict`), tag **`v5.0-alpha`**, push, README teaser with it.
## Then: v5.0-beta — EVERY CRATE DIFFERENT (the honest version)
@ -64,9 +67,20 @@ hold, on three rungs:
list as promised, weighted toward the beta: shopfront signage/window treatment for stocked
godverse shops (a crate-diggers' shop should read as one from the footpath), or the awning
ripple, or the tram-stop tri diet — your choice, one item, measured as ever.
6. **The beta gate (F).** Per-shop distinctness (no two keyed crates identical — assert on
6. **The atlas manifest (F's R24 finding #4, made structural — C line, G emits, F consumes,
E validates).** Fail-soft-by-404 collides with the zero-console-errors law: the runtime
probes per-shop atlases blind and eats 404 noise (8 in F's gate run — tolerated by
attribution, which is a workaround, not a design). Fix at the root: G emits
`web/assets/stock_godverse/index.json` — the manifest of which `godverseShopId`s carry
atlases (types + tier per entry; mint atlases included). C: the §7 contract line. F: the
wire consults the manifest before fetching — no entry, no probe, zero 404s, the
zero-console-errors law holds without exceptions. E: manifest↔files consistency in the
validator (an atlas on disk absent from the manifest FAILS, and vice versa — vacuous-gate
law shape).
7. **The beta gate (F).** Per-shop distinctness (no two keyed crates identical — assert on
title sets, the R24 pattern), tier provenance visible in gate output (a mint crate never
reports as real), the ladder re-proof, `qa.sh --strict --matrix`, tag **`v5.0-beta`**, push.
reports as real), zero console errors WITHOUT 404-attribution exceptions (the manifest makes
this honest), the ladder re-proof, `qa.sh --strict --matrix`, tag **`v5.0-beta`**, push.
7. **A / D — on-call.** A: nothing pending (your R25 close was clean). D: nothing — unless F's
distinctness gate wants a crowd check at a stocked shop (patronage at Monster Robot on a
Saturday feels like a D flourish, not a requirement).