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

Rule down triplet collection owner in acquisition trace

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 23:03:30 -07:00
commit afff8de214
2 changed files with 34 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/rehost-queue.md
View file

@ -152,6 +152,10 @@ Working rule:
`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 paired tagged collection loader is bounded away too:
`0x00413440` owns the tagged `0x36b1/0x36b2/0x36b3` triplet load path, dispatches each live
record through vtable slot `+0x44`, and keeps that seam on the already-grounded triplet
payload rather than the missing `[site+0x276]` replay owner
- the remaining owner-company question is therefore narrower than “find any replay seam”:
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