Prioritize tier2 kind-8 imported recipe set
This commit is contained in:
parent
15751b1d5f
commit
6459e7a714
2 changed files with 29 additions and 1 deletions
|
|
@ -609,7 +609,12 @@ Working rule:
|
|||
`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.
|
||||
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
|
||||
`[event+0x7ef]` itself or a still-later owner does.
|
||||
- two explicit trigger-kind materializations are now grounded inside that retagger:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue