From cfeb3e893c09df655514bf5552a2ee6b04400de8 Mon Sep 17 00:00:00 2001 From: Jan Petykiewicz Date: Sun, 19 Apr 2026 11:39:54 -0700 Subject: [PATCH] Test tier2 kind-8 bridge peer against recipes --- ...untime-effect-kind8-tier2-setup-core-note.md | 17 +++++++++++++++++ docs/rehost-queue.md | 7 ++++++- 2 files changed, 23 insertions(+), 1 deletion(-) diff --git a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md index dc9aedc..3eb6659 100644 --- a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md +++ b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md @@ -167,6 +167,23 @@ evidence still only grounds the direct Tier 2 bridge through setup payload `+0x1 `[profile+0x77/+0xc5]`, then through `0x00436d10 / 0x00443a50`. But it does make the upstream picture less likely to collapse to one trivial peer class before that bridge. +## Bridge-peer recipe check + +The only wider-corpus peer on the selected-year side of the bridge is `Mexico.gmp`, which shares +`payload_word_0x14 = 1870` but not the unique `payload_byte_0x20 = 0x3a`. + +`compare-recipe-book-lines Louisiana.gmp Mexico.gmp` keeps the recipe/runtime split sharp: + +- `Louisiana.gmp` keeps a nonzero `book00` profile + - `book00.line02 mode = 0x00080000` + - `book00.line02 supplied token = 0x00004080` + - `book00.line00/line01` demanded tokens nonzero +- `Mexico.gmp` stays zero across the whole checked recipe-book surface + +So the only current `+0x14` bridge peer does **not** reproduce the sparse `Louisiana` recipe +profile. That keeps the recipe/runtime side as the stronger remaining differentiator even after the +setup bridge was narrowed to `+0x14/+0x20`. + ## Current implication The upstream side of the Tier 2 strip is now bounded more tightly: diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md index 03f15de..e2f987d 100644 --- a/docs/rehost-queue.md +++ b/docs/rehost-queue.md @@ -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: