Split acquisition region lane statuses

This commit is contained in:
Jan Petykiewicz 2026-04-18 19:17:22 -07:00
commit 23beba2a63
2 changed files with 34 additions and 5 deletions

View file

@ -140,6 +140,15 @@ Working rule:
remaining owner gaps
`[region+0x276]`, `[region+0x2a4]`, `[region+0x310/+0x338/+0x360]`, and the stable region
class/type discriminator consumed through `0x0040d360`
- use the new per-lane region status split in the same trace:
`[region+0x276]` already has a grounded runtime producer at `0x00422100` and is now only an
ordinary-save restore gap;
`[region+0x2a4]` currently has no region-class runtime writer in the binary scan and now looks
payload/restore-owned;
`[region+0x310/+0x338/+0x360]` has an exact raw delta reader at `0x0040cac0` but still lacks a
payload/restore owner;
`0x0040d360` is now exact as `[owner_vtable+0x80+0x32] == 4`, so the remaining gap there is
only the save-native projection of that byte
- make the next periodic-company slice about the smaller shellless-simulation question instead:
which later restore or rebuild owner rehydrates the remaining region-side `0x004014b0` inputs
once the peer/company inputs are treated as grounded