Differentiate tier2 kind-8 recipe shape peers
This commit is contained in:
parent
529bdcc0e6
commit
b727d36b96
2 changed files with 35 additions and 0 deletions
|
|
@ -623,6 +623,11 @@ Working rule:
|
|||
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.
|
||||
The note now carries that first peer split too: `Britain.gmp` diverges strongly with different
|
||||
mode and extra supplied rows, while `South East USA.gmp` stays structurally closer but still
|
||||
differs on the exact `book00.line01` demanded token and `book00.line02` mode/supplied-token
|
||||
pair. So the current queue head is no longer “find a peer”; it is “find the downstream
|
||||
runtime-facing consequence of Louisiana’s distinct exact `book00` token-bearing signature.”
|
||||
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