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

Narrow tier2 runtime split to template bank state

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 12:00:40 -07:00
commit 03fdcdf998
2 changed files with 115 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/rehost-queue.md
View file

@ -660,6 +660,30 @@ Working rule:
recover the later runtime-record / named-availability consequence under
`0x00412d70 / 0x00412fb0 / 0x00412c10` that makes the minimal cluster land on
`5200 :: [7:0]` only in `Louisiana.gmp`.
- the direct named-availability table is still not that consequence:
the nearest single-import peer `South East USA.gmp` keeps `Warehouse05 = 1` and `Port01 = 1`
just like `Louisiana.gmp`, matching the earlier `Dutchlantis.gmp` read. So the next later
Tier 2 question is now even narrower:
recover the runtime-record bank/template consequences under `0x00412d70`
(plus dependent `0x00411ce0 / 0x00411ee0`) before `0x00412c10` mirrors anything into
`[candidate+0x7ac]`.
- the `0x00412d70` runtime-record roots are grounded now too:
direct `objdump` over `RT3.exe` shows `0x005c93d8 = "Warehouse%02d"` and
`0x005c93e8 = "Port%02d"`, with the rebuild choosing the `Port%02d` root only when
`[candidate+0xba] != 0` and the `Warehouse%02d` root otherwise. That turns the next queue head
into a concrete port-versus-warehouse runtime-record question:
recover how the bank/template pass and live availability bytes `[candidate+0xba/+0xbb]`
make `Louisiana.gmp` land on the `Warehouse%02d` side that later lines up with
`5200 :: [7:0]`.
- the writer-side split is narrower now too:
direct disassembly of `0x004120b0` shows that the per-record stream-load helper clears
`[candidate+0x79c/+0x7a0/+0x78c/+0x790/+0x794/+0x7b0]`, restores the fixed fields through
`[candidate+0x33]`, and streams the packed `0xbc` descriptor array into `[candidate+0x37]`,
but does **not** write `[candidate+0xba/+0xbb]` in the checked body. So the next concrete
recovery target is now the bank-qualified template source in `0x00412d70`, not the lower
tagged-record reader:
recover how preserved `[candidate+0xba/+0xbb]` bank/template state feeds the
`Warehouse%02d` runtime side before `0x00411ee0 / 0x00411ce0 / 0x00412c10` run.
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: