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

Split peer-site restore and runtime inputs

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 19:07:20 -07:00
commit 1d6eed09ab
2 changed files with 29 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/rehost-queue.md
View file

@ -114,10 +114,15 @@ Working rule:
`0x0040ceab -> 0x0045c150` / `0x0040d1a1 -> 0x0045c310` /
`0x0040cd70 seeds [site+0x3cc/+0x3d0] from 0x62b2fc / 0x62b268`
- treat the peer-site selector seam itself as grounded enough for planning purposes
- use the new structured restore/runtime field split in the same trace:
restore subset
`[site+0x3cc/+0x3d0]` plus `0x5dc1`-backed `[owner+0x23e/+0x242]`,
and runtime subset
`[site+0x04]`, `[site+0x2a8]`, `[peer+0x08]`
- make the next periodic-company slice about the smaller shellless-simulation question instead:
which subset of persisted site/peer fields (`[site+0x3cc/+0x3d0]`,
`0x5dc1`-backed `[owner+0x23e/+0x242]`, `[site+0x2a8]`, `[peer+0x08]`) is actually
sufficient to run `0x004014b0` and the city-connection sibling without shell state
whether `0x004014b0` and the city-connection sibling only need that restore subset to
reconstruct the runtime subset deterministically, or whether the runtime subset has to become
an explicit headless-state contract
- 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>`,