Narrow acquisition owner and subtype seams

This commit is contained in:
Jan Petykiewicz 2026-04-18 21:14:46 -07:00
commit b75b7ef814
2 changed files with 46 additions and 12 deletions

View file

@ -74,8 +74,13 @@ Working rule:
- the winning site id is staged in `[site+0x2a4]` before `0x004269b0` commits the acquisition
- That leaves the acquisition blocker set tighter than before:
- peer-site and linked-site replay seams are grounded enough for planning
- remaining non-hook gaps are the placed-structure save/rebuild lanes `[site+0x276]`, `[site+0x2a4]`,
`[site+0x310/+0x338/+0x360]`, and subtype byte `[candidate+0x32] == 4`
- 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
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
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`
- `0x00455b70` is the concrete placed-structure specialization constructor feeding