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

Ground peer-site backing selector field owner

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 18:41:20 -07:00
commit a4976ed7ae
2 changed files with 21 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/rehost-queue.md
View file

@ -62,18 +62,25 @@ Working rule:
`0x4a9d/0x4a3a/0x4a3b` side-buffer owner only persists route-entry lists, three byte arrays,
five proximity buckets, and the sampled-cell list
- the winning linked company id comes from `[region+0x2a4]`
- direct disassembly now shows the generic base constructor `0x0052edf0` clearing base state
through `0x0052ecd0` and then writing `[this+0x04]` from caller arg `1`
- `0x00455c62` is one concrete placed-structure specialization caller of `0x0052edf0`
- `0x00485819` is one typed placed-structure caller of `0x0052edf0` through the generic
three-arg wrapper `0x00530640`
So the next owner question is no longer “what does the acquisition branch do?” or “which post-
load owner replays linked-site refresh?” but “which remaining owner reseeds the live backing-
record selector `[site+0x04]` once the existing bring-up replay finishes?”
load owner replays linked-site refresh?” but “which placed-structure load or bring-up caller
supplies the `0x0052edf0` arg-1 selector that becomes the live backing-record selector
`[site+0x04]` once the existing bring-up replay finishes?”
- Make the next static/rehost slice the peer-site rebuild seam above persistence, not another save
scan:
- treat `0x00444690 -> 0x004133b0 -> 0x0040e450 / 0x0040ee10 -> 0x0040edf6 -> 0x00480710` as
the checked-in bring-up replay path for existing saves
- treat `0x004160aa -> 0x0040ee10` as the checked-in recurring runtime maintenance entry into the
same linked-peer refresh strip
- find the remaining owner that reseeds `[site+0x04]` before
`0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50` consume it, if that owner is distinct
from the bring-up replay path
- treat `0x0052edf0` as the checked-in field owner for `[site+0x04]`
- map the concrete placed-structure load or bring-up caller that feeds caller arg `1` into
`0x0052edf0` before `0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50` consume the
resulting selector, if that caller is distinct from the bring-up replay path
- 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>`,