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

Reduce acquisition lanes to payload owners

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 19:18:38 -07:00
commit 6aeb580065
2 changed files with 11 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/rehost-queue.md
View file

@ -145,13 +145,16 @@ Working rule:
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;
`[region+0x310/+0x338/+0x360]` has an exact raw delta reader at `0x0040cac0` and likewise no
direct region-class runtime writer in the current binary scan, so it now also looks
payload/restore-owned;
`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
which later save payload or restore owner rehydrates the remaining region-side `0x004014b0`
inputs `[region+0x2a4]` and `[region+0x310/+0x338/+0x360]` once the peer/company inputs are
treated as grounded and `[region+0x276]` is treated as a producer-known ordinary-save restore
gap
- Use the higher-layer probes as the standard entry point for the current blocked frontier instead
of generic save scans:
`runtime inspect-periodic-company-service-trace <save.gms>`,