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

Favor tier2 kind-8 recipe profile over header peers

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 11:42:05 -07:00
commit 15751b1d5f
2 changed files with 18 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/rehost-queue.md
View file

@ -604,7 +604,12 @@ Working rule:
numeric Tier 2 input; on the current evidence it collapses to the ordinary nonzero campaign or
setup branch before `0x00436d10 / 0x00443a50` run. That shifts even more weight back onto the
sparse recipe/runtime family, with `+0x14` the only currently grounded preserved setup-side
scalar still crossing the bridge.
scalar still crossing the bridge. The same note now also adds a same-header-class recipe check:
`compare-recipe-book-lines Louisiana.gmp "Argentina Opens Up.gmp"` shows that even another
`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
predictor of the Tier 2 runtime shape either; the recipe/runtime family remains the dominant
differentiator.
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: