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

Check tier2 kind-8 recipe peers against runtime path

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 11:48:57 -07:00
commit ac227ac48a
2 changed files with 29 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

24
artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md
View file

@ -120,3 +120,27 @@ So the current corpus split is:
- `book00.line02`-only mode shape is a three-map family - `book00.line02`-only mode shape is a three-map family
- but `Louisiana.gmp` still has a distinct exact token-bearing signature even inside that family - but `Louisiana.gmp` still has a distinct exact token-bearing signature even inside that family
## Checked downstream split
One immediate runtime-facing comparison is now grounded too:
- `runtime inspect-smp Britain.gmp`
- `runtime inspect-smp "South East USA.gmp"`
Both mode-shape peers still expose in-file candidate names such as `Port01` and `Warehouse05`, but
neither currently exposes any add-building dispatch-strip trigger rows:
- `add_building_dispatch_strip_records_with_trigger_kind = 0`
- `trigger_kinds_present = []`
So the current checked downstream split is sharper than a generic “same mode-shape family” read:
- `Britain.gmp` and `South East USA.gmp` share the coarse `book00.line02` mode footprint with
`Louisiana.gmp`
- both also still carry the relevant candidate names in-file
- but neither currently reaches the shipped add-building dispatch-strip family that
`Louisiana.gmp` does
That makes `Louisiana.gmp` the first checked member of that mode-shape family whose distinct exact
token-bearing `book00` signature also lines up with the add-building runtime path.

5
docs/rehost-queue.md
View file

@ -628,6 +628,11 @@ Working rule:
differs on the exact `book00.line01` demanded token and `book00.line02` mode/supplied-token differs on the exact `book00.line01` demanded token and `book00.line02` mode/supplied-token
pair. So the current queue head is no longer “find a peer”; it is “find the downstream pair. So the current queue head is no longer “find a peer”; it is “find the downstream
runtime-facing consequence of Louisiana’s distinct exact `book00` token-bearing signature.” runtime-facing consequence of Louisiana’s distinct exact `book00` token-bearing signature.”
That downstream split is now partially grounded too: direct `inspect-smp` checks show both
`Britain.gmp` and `South East USA.gmp` still carry `Port01` and `Warehouse05` names in-file
but neither has any add-building dispatch-strip trigger rows at all. So `Louisiana.gmp` is now
the first checked member of that `book00.line02` mode-shape family whose exact token-bearing
signature also lines up with the shipped add-building runtime path.
kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes
`[event+0x7ef]` itself or a still-later owner does. `[event+0x7ef]` itself or a still-later owner does.
- two explicit trigger-kind materializations are now grounded inside that retagger: - two explicit trigger-kind materializations are now grounded inside that retagger: