Ground peer-site runtime reconstruction contract
This commit is contained in:
parent
1d6eed09ab
commit
210a1c28d2
2 changed files with 30 additions and 7 deletions
|
|
@ -119,10 +119,13 @@ Working rule:
|
|||
`[site+0x3cc/+0x3d0]` plus `0x5dc1`-backed `[owner+0x23e/+0x242]`,
|
||||
and runtime subset
|
||||
`[site+0x04]`, `[site+0x2a8]`, `[peer+0x08]`
|
||||
- use the new structured reconstruction status in the same trace:
|
||||
`restore_subset_and_bring_up_reconstruct_runtime_subset`
|
||||
- treat the runtime subset as reconstructible from the restore subset plus the already-grounded
|
||||
bring-up path for planning purposes
|
||||
- make the next periodic-company slice about the smaller shellless-simulation question instead:
|
||||
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
|
||||
which persisted region/company linkage fields are still missing for `0x004014b0` and the
|
||||
city-connection sibling once the peer-site runtime subset is no longer the blocker
|
||||
- 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>`,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue