Classify tier2 kind-8 recipe signatures
This commit is contained in:
parent
6459e7a714
commit
529bdcc0e6
2 changed files with 101 additions and 1 deletions
|
|
@ -614,7 +614,15 @@ Working rule:
|
|||
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.
|
||||
recipe-runtime set, rather than reopening broader setup-core or header-class hypotheses. That
|
||||
scan is now checked in at
|
||||
`artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md`:
|
||||
across all 41 bundled `rt3_105` maps there are 23 nonzero-mode path signatures, and
|
||||
`Louisiana.gmp` sits in a small three-map `book00.line02`-only mode family with
|
||||
`Britain.gmp` and `South East USA.gmp`. But `Louisiana.gmp` becomes unique again once the
|
||||
supplied and demanded token lanes are included. That makes the next concrete Tier 2 recipe pass
|
||||
smaller: compare `Louisiana.gmp` directly against `Britain.gmp` and `South East USA.gmp` on
|
||||
the token-bearing minimal imported set and then on any downstream runtime-facing differences.
|
||||
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