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

Prioritize tier2 kind-8 imported recipe set

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 11:44:46 -07:00
commit 6459e7a714
2 changed files with 29 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -71,6 +71,29 @@ One upstream pairwise check now supports that same read:
So the current evidence no longer stops at the recipe-book lines themselves; there are already So the current evidence no longer stops at the recipe-book lines themselves; there are already
setup-payload-core differences upstream of the coupled Tier 2 rebuild strip. setup-payload-core differences upstream of the coupled Tier 2 rebuild strip.
The setup-side read is narrower now too:
- the currently grounded `+0x20 -> [profile+0xc5]` bridge weakens to a nonzero gate, not a unique
preserved numeric input
- the only `+0x14` peer (`Mexico.gmp`) stays zero across the checked recipe-book surface
- one same-header peer (`Argentina Opens Up.gmp`) keeps a broader mixed `book01/book02` profile
So the stronger current differentiator is the imported recipe-runtime set itself, not the coarse
setup-header class and not the raw `+0x20` byte value.
The importer-side branch map now supports that more concrete read:
- `0x00435630` only materializes nonzero-mode rows into runtime descriptors
- `Louisiana.gmp` currently imports a minimal nonzero set centered on `book00.line02`
- `Mexico.gmp` imports none of that checked book content
- `Argentina Opens Up.gmp` keeps additional nonzero `book01/book02` content
That makes the current Tier 2 question smaller and more specific:
- which maps share the same minimal imported nonzero recipe-runtime set as `Louisiana.gmp`
- and whether that minimal imported set, more than the setup-side bridge fields, predicts the
shipped `Add Building Warehouse05` runtime shape
So the next recovery pass should target the internal sequencing and data handoff across: So the next recovery pass should target the internal sequencing and data handoff across:
- `0x00435630` - `0x00435630`

7
docs/rehost-queue.md
View file

@ -609,7 +609,12 @@ Working rule:
`0xcdcdcdcd / 0xcdcdcdcd` peer keeps a broader mixed `book01/book02` profile while `0xcdcdcdcd / 0xcdcdcdcd` peer keeps a broader mixed `book01/book02` profile while
`Louisiana.gmp` stays sparse. So the coarse setup-header class is no longer a plausible `Louisiana.gmp` stays sparse. So the coarse setup-header class is no longer a plausible
predictor of the Tier 2 runtime shape either; the recipe/runtime family remains the dominant predictor of the Tier 2 runtime shape either; the recipe/runtime family remains the dominant
differentiator. differentiator. The checked Tier 2 recipe-runtime note now carries the stronger current read:
`0x00435630` only materializes nonzero-mode rows, `Mexico.gmp` is the only `+0x14` peer and
still stays zero across the checked recipe-book surface, and the same-header peer
`Argentina Opens Up.gmp` keeps additional nonzero `book01/book02` content. So the next pass
should bias toward finding other maps that share Louisiana's minimal imported nonzero
recipe-runtime set, rather than reopening broader setup-core or header-class hypotheses.
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: