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

Bound tier2 kind-8 setup profile bridge

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

14
docs/rehost-queue.md
View file

@ -565,7 +565,19 @@ Working rule:
(`payload_word_0x14 = 1870`, `payload_byte_0x20 = 0x3a`, `payload_word_0x3b2 = 2`,
`candidate_header = 0xcdcdcdcd / 0xcdcdcdcd`) is still unique across the 41-map corpus even
after the coarse header class is demoted, so the next pass should compare that tighter tuple to
the sparse recipe/runtime family rather than reopening the broad header-pair question.
the sparse recipe/runtime family rather than reopening the broad header-pair question. The same
note now also carries the grounded owner bridge for those compared setup-core fields. The early
copy path is still `0x00442400 -> 0x00502220 -> 0x0047be50`, but the later reset or
reactivation owners are now bounded too:
`0x00436d10` and `0x00443a50` both reimport the staged subset
`[profile+0x77/+0xc5]` before rerunning the same rebuild family that includes
`0x00435603`, `0x00435630`, `0x0041e970`, `0x00412bd0`, `0x00434130`, and `0x00436af0`.
That narrows the open question again:
`+0x14/+0x20` now have one real bridge into the Tier 2 strip through
`[profile+0x77/+0xc5]`, while `+0x3b2/+0x3ba` still stop on the setup-panel threshold or
scroll path. The next pass should therefore test whether the unique `Louisiana.gmp`
`+0x14/+0x20` pair is enough to explain its Tier 2 runtime shape through that grounded bridge,
or whether the sparse recipe/runtime side is still the more plausible 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: