jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Test tier2 kind-8 bridge peer against recipes

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 11:39:54 -07:00
commit cfeb3e893c
2 changed files with 23 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

17
artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md
View file

@ -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: