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

Rule down remaining direct acquisition owner stores

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 23:01:36 -07:00
commit 9bac9c3b08
2 changed files with 67 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/rehost-queue.md
View file

@ -147,9 +147,15 @@ Working rule:
it drains queued site ids and coordinate pairs from scratch band `0x006ce808..0x006ce988`,
re-enters `0x0040eba0` at `0x00473c98`, and clears each queued id slot, so it is a local
post-create refresh path rather than a persisted replay owner
- the remaining direct `[site+0x276]` store census is bounded away too:
`0x0042128d` is broad zero-init in the `0x00421430` constructor neighborhood,
`0x00422305` computes a live score/category lane before publishing event `0x7`,
`0x004269c9/0x00426a2a` are acquisition commit/clear helpers, and
`0x004282a9/0x004300d6` are bulk owner-transfer writes
- the remaining owner-company question is therefore narrower than “find any replay seam”:
identify which non-transport persisted source family feeds that tuple and which companion
restore/finalize calls are sufficient to repopulate `[site+0x276]` for shellless acquisition
identify which non-transport persisted source family outside the currently bounded direct
allocator/finalize/store families feeds that tuple and which companion restore/finalize calls
are sufficient to repopulate `[site+0x276]` for shellless acquisition
- the second is narrower in the same way:
the checked-in `0x36b1/0x36b2/0x36b3` triplet seam and the
`0x4a9d/0x4a3a/0x4a3b` side-buffer seam still do not serialize `[site+0x310/+0x338/+0x360]`