From 558a2d6c3c6b9993ea077c22c6cca94cd6da4a41 Mon Sep 17 00:00:00 2001 From: Jan Petykiewicz Date: Sun, 19 Apr 2026 11:53:47 -0700 Subject: [PATCH] Tighten tier2 kind-8 minimal recipe cluster --- ...ffect-kind8-tier2-recipe-signature-note.md | 74 +++++++++++++++++++ docs/rehost-queue.md | 10 +++ 2 files changed, 84 insertions(+) diff --git a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md index 3e73ad6..0573379 100644 --- a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md +++ b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md @@ -144,3 +144,77 @@ So the current checked downstream split is sharper than a generic “same mode-s That makes `Louisiana.gmp` the first checked member of that mode-shape family whose distinct exact token-bearing `book00` signature also lines up with the add-building runtime path. + +## Compact-family split inside the checked peers + +The current runtime-facing split is not just “dispatch rows present versus absent.” The checked +peer maps also diverge inside the broader `nondirect-ge1e-h0001-0007` compact family: + +- `Louisiana.gmp` reaches the checked add-building strip on + - `nondirect-ge1e-h0001-0007-0000-5200-0200-p0000-0000-0000-ffff :: [7:0]` + - with decoded label `Add Building Warehouse05` +- `Britain.gmp` keeps `nondirect-ge1e-h0001-0007-0000-4a00-0200-p0000-0000-0000-ffff` + but no add-building dispatch-strip rows +- `South East USA.gmp` keeps several other `0007` mids + - `...-3100-...` + - `...-3500-...` + - `...-3800-...` + - `...-3b00-...` + - `...-4200-...` + and again no add-building dispatch-strip rows + +So the current checked peer split is now: + +- same coarse mode-shape family +- different exact token-bearing `book00` signature +- different `h0001-0007` mid-word family at runtime +- only `Louisiana.gmp` currently reaches the `5200 :: [7:0]` add-building strip + +## Minimal imported-cluster split + +The next corpus pass sharpens that again. + +`Louisiana.gmp` is not the only map that reuses pieces of the apparent `lC / 0x00080000 / +0x00004080` cluster: + +- `Ireland.gmp` carries + - `book02.line01 = demanded 0x6c430000` + - `book02.line02 = mode 0x00080000, supplied 0x00004080` + - plus additional active rows in `book00`, `book01`, and `book03` +- `Eastern China.gmp` carries + - `book02.line00 = demanded 0x00010000` + - `book02.line01 = demanded 0x6c430000` + - `book02.line02 = mode 0x00080000, supplied 0x00004080` + - plus additional active rows in `book00` and `book01` + +But the exact three-row cluster as the *entire* nonzero imported recipe surface is unique to +`Louisiana.gmp` in the 41-map corpus: + +- `book00.line00 = demanded 0x00010000` +- `book00.line01 = demanded 0x6c430000` +- `book00.line02 = mode 0x00080000, supplied 0x00004080` + +No other bundled map keeps exactly that three-line imported set and nothing else. + +That matters on the runtime side too: + +- `Ireland.gmp` still has no add-building dispatch-strip rows at all + - `add_building_dispatch_strip_records_missing_trigger_kind = 0` + - checked `0007` family stays on `...-6300-...` +- `Eastern China.gmp` also has no add-building dispatch-strip rows at all + - `add_building_dispatch_strip_records_missing_trigger_kind = 0` + - checked `0007` mids stay on other families such as `...-a100-...`, `...-a600-...`, + `...-b100-...`, `...-b700-...`, `...-cf00-...`, and `...-d100-...` + +So the stronger current read is no longer just “the `0x00080000 / 0x00004080` triplet exists +somewhere.” It is: + +- `Louisiana.gmp` is the only bundled map whose whole imported nonzero recipe surface collapses to + that exact three-row cluster +- maps that merely reuse pieces of the cluster do not currently reach the same add-building strip + +That makes the next Tier 2 question smaller again: + +- whether the `5200 :: [7:0]` add-building strip is tied to that minimal imported-cluster shape + specifically, rather than to the presence of any one of its component token rows in a broader + recipe profile diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md index 5911cee..2648001 100644 --- a/docs/rehost-queue.md +++ b/docs/rehost-queue.md @@ -633,6 +633,16 @@ Working rule: but neither has any add-building dispatch-strip trigger rows at all. So `Louisiana.gmp` is now the first checked member of that `book00.line02` mode-shape family whose exact token-bearing signature also lines up with the shipped add-building runtime path. + - the next corpus split is tighter now too: + the apparent `0x00010000 / 0x6c430000 / 0x00080000+0x00004080` three-row cluster is no longer + just a local `Louisiana.gmp` curiosity; `Ireland.gmp` and `Eastern China.gmp` both reuse parts + of it, but only inside broader multi-book imported profiles, and neither currently reaches any + add-building dispatch-strip rows. `Louisiana.gmp` is the only bundled map whose *entire* + nonzero imported recipe surface collapses to that exact three-row cluster. So the current + queue head is now narrower again: + test whether the shipped `5200 :: [7:0]` `Add Building Warehouse05` strip is tied to that + minimal imported-cluster shape specifically, rather than to the mere presence of one reused + `0x00080000 / 0x00004080` triplet inside a broader recipe profile. 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: