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

Narrow acquisition site id and owner lanes

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 21:17:32 -07:00
commit a47a90961c
2 changed files with 34 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/rehost-queue.md
View file

@ -54,6 +54,10 @@ Working rule:
- `0x00480210` writes linked-peer row `[peer+0x04]` from the anchor-site id argument
- `0x0040f6d0 -> 0x00481390` writes the anchor-site linked peer id back into `[site+0x2a8]`
- `0x0047dda0` consumes `[peer+0x08]` as the linked route-entry anchor id
- `0x0041f7e0 / 0x0041f810 / 0x0041f850` already ground `[site+0x2a4]` as the record's own
placed-structure id lane beneath the peer-chain helpers
- `0x0040d210` is the owner-side placed-structure resolver from `[site+0x276]` through
`0x0062be10`
- `0x00480710 -> 0x0048abc0 / 0x00493cf0` is the linked-site refresh and route-entry rebind or
synthesis strip above that anchor lane
- the same `0x00480710` replay strip now also republishes the concrete world-cell owner chains:
@ -71,15 +75,18 @@ Working rule:
`[this+0x206/+0x20a/+0x20e]` plus the subordinate payload callback strip, and the
`0x4a9d/0x4a3a/0x4a3b` side-buffer owner only persists route-entry lists, three byte arrays,
five proximity buckets, and the sampled-cell list
- the winning site id is staged in `[site+0x2a4]` before `0x004269b0` commits the acquisition
- `0x004269b0` consumes the chosen site's own placed-structure id lane `[site+0x2a4]`
- That leaves the acquisition blocker set tighter than before:
- peer-site and linked-site replay seams are grounded enough for planning
- the live owner-company meaning of `[site+0x276]` is already grounded through `0x0047efe0`,
and the subtype byte consumed as `[candidate+0x32] == 4` is already bounded under the
with the direct owner-side resolver bounded at `0x0040d210`
- `[site+0x2a4]` is already grounded as the record's own placed-structure id lane through the
peer-chain helpers `0x0041f7e0 / 0x0041f810 / 0x0041f850`
- the subtype byte consumed as `[candidate+0x32] == 4` is already bounded under the
aux-candidate load/stem-policy chain
`0x004131f0 -> 0x00412fb0 -> 0x004120b0 -> 0x00412ab0`
- remaining non-hook gaps are the save or replay projection of `[site+0x276]`, the staged winner
lane `[site+0x2a4]`, the cached tri-lane `[site+0x310/+0x338/+0x360]`, and the projection from
- remaining non-hook gaps are the save or replay projection of `[site+0x276]`, the save or
replay projection of `[site+0x2a4]`, the cached tri-lane `[site+0x310/+0x338/+0x360]`, and the projection from
restored backing-record selector `[site+0x04]` back into the loaded candidate subtype row
- direct disassembly now shows the generic base constructor `0x0052edf0` clearing base state
through `0x0052ecd0` and then writing `[this+0x04]` from caller arg `1`