jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Trace tier2 kind-8 recipe sequencing

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 11:27:09 -07:00
commit ed53d9220c
5 changed files with 682 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

38
docs/rehost-queue.md
View file

@ -495,6 +495,44 @@ Working rule:
“which broader candidate-state rebuild or latch sequencing difference above
`0x00437737 / 0x00412c10 / 0x00412bd0 / 0x00412d70 / 0x00412fb0` leads to the shipped
`Add Building Warehouse05` row in `Louisiana.gmp`?”
The broader `compare-candidate-table` surface now reinforces the same point too:
`Louisiana.gmp` versus `Dutchlantis.gmp` stays on the same
`scenario-named-candidate-availability-table` semantic family, still keeps `Warehouse05 = 1/1`,
and moves the actual `difference_count = 43` into the wider industry mix and zero-trailer-name
set rather than a unique `Warehouse05` gate.
- that sequencing question is checked in directly now too:
`artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-sequencing-note.md`
extracts the current late order around the explicit `0x197` checkpoint:
the earlier `0x00443ebc` recipe-runtime rebuild still sits before
`0x00412c10 / 0x00412bd0 / 0x00434130 / 0x00436af0`, while the later `0x00444ac1`
checkpoint runs after `0x004354a0 / 0x00487de0` and then falls through into
`0x00437737 -> 0x00434f20 -> 0x00412c10`, with the separate recipe-runtime side re-entering
`0x00435630 -> 0x00412d70`. That keeps the next recovery pass focused on Tier 2 sequencing
interactions instead of title strings or direct `Warehouse05` availability bits.
- the strongest title-overlap pair now has a recipe-book note too:
`artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-book-note.md`
shows `Louisiana.gmp` and `Dutchlantis.gmp` diverge heavily on the recipe-book surface even
though `Warehouse05` stays `1 / 1` in the named-availability table. `Louisiana.gmp` is sparse
there (currently only `book00.line02` stays nonzero), while `Dutchlantis.gmp` keeps multiple
later mixed lines and mode words. That shifts the current Tier 2 bias further toward the
`0x00435630 -> 0x00412d70` rebuild side rather than the direct `0x00437737 -> 0x00412c10`
availability side.
The same note now also boxes in the same-condition-family counterexample:
`Louisiana.gmp` and `Texas Tea.gmp` both sit on `[7:0]`, but `Louisiana.gmp` keeps the one-row
`Warehouse05` cluster with only `book00.line02 = 0x00080000`, while `Texas Tea.gmp` keeps the
one-row `Port01` cluster with a broader four-book nonzero mode strip. So the current evidence
no longer supports “shared `[7:0]` family implies one shared Tier 2 recipe/runtime shape.”
- the bundled add-building carrier set now has a checked recipe-book corpus too:
`artifacts/exports/rt3-1.05/add-building-carriers-recipe-book-scan.json`
shows the six carrier maps split into two recipe families:
`Alternate USA.gmp` stands alone with the richer five-book nonzero mode strip, while the other
five carrier maps fall into one broader family but still diverge sharply inside it.
Among that five-map family, `Louisiana.gmp` is currently the sparsest nonzero profile
(only `book00.line02 = 0x00080000` plus the paired `book00` token lanes), while
`Chicago to New York.gmp`, `Rhodes Unfinished.gmp`, and `Texas Tea.gmp` each keep broader
multi-book nonzero mode strips and `Pacific Coastal.gmp` keeps supplied-token-only activity.
That makes `Louisiana.gmp` look less like a generic carrier-map recipe pattern and more like a
genuinely narrow Tier 2 recipe/runtime-record case.
kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes
`[event+0x7ef]` itself or a still-later owner does.
- two explicit trigger-kind materializations are now grounded inside that retagger: