Test tier2 kind-8 bridge peer against recipes
This commit is contained in:
parent
d3a54b82ca
commit
cfeb3e893c
2 changed files with 23 additions and 1 deletions
|
|
@ -587,7 +587,12 @@ Working rule:
|
|||
all 41 bundled `rt3_105` maps, while `payload_word_0x14 = 1870` has only one peer (`Mexico`).
|
||||
That makes the campaign/setup-byte side of the bridge the strongest remaining setup-core
|
||||
differentiator, with the year-word side a secondary companion rather than a full peer-group
|
||||
collapse.
|
||||
collapse. The same note now also carries the direct bridge-peer check:
|
||||
`compare-recipe-book-lines Louisiana.gmp Mexico.gmp` shows that the only `+0x14` peer still
|
||||
stays zero across the checked recipe-book surface while `Louisiana.gmp` keeps the sparse
|
||||
nonzero `book00` profile. So the next pass should keep the setup bridge narrowed to the
|
||||
unique `+0x20` campaign/setup-byte side while still treating the sparse recipe/runtime family
|
||||
as the stronger remaining 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:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue