Ground placed-structure companion scalar lane

This commit is contained in:
Jan Petykiewicz 2026-04-19 00:02:31 -07:00
commit 6e46c43837
2 changed files with 17 additions and 0 deletions

View file

@ -225,6 +225,10 @@ Working rule:
`0x004323a0 -> 0x00432f40` through direct call `0x00432317`, so `0x0061039c` currently reads
as a live runtime-effect application lane rather than the missing persisted restore owner for
`[site+0x276]`
- the `[site+0x27a]` companion lane is grounded now too:
it is a live signed scalar accumulator rather than a second owner-identity seam, with zero-init
at `0x0042125d` and `0x0040f793`, accumulation at `0x0040dfec` and `0x00426ad8`, direct set on
acquisition commit at `0x004269e4`, and negated clear at `0x00426a44..0x00426a90`
- 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, the save-side `0x00413440` serializer, the load-side