Narrow tier2 kind-8 setup gate role
This commit is contained in:
parent
cfeb3e893c
commit
d583020b5b
2 changed files with 17 additions and 1 deletions
|
|
@ -592,7 +592,12 @@ Working rule:
|
|||
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.
|
||||
as the stronger remaining differentiator. The same note now also sharpens the `+0x20` bridge
|
||||
itself: current grounded downstream consumers of mirrored `[world+0x66de]` are mostly the
|
||||
editor metadata checkbox and campaign-gated branches inside `0x00442c30`, not the core
|
||||
Tier 2 helpers directly. So the likely Tier 2 relevance of `+0x20` is the branch gate inside
|
||||
`0x00436d10 / 0x00443a50` before the rebuild family runs, not a later direct
|
||||
`[world+0x66de] -> 0x00435630/0x00412bd0/0x00412c10` data path.
|
||||
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