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

Split placed-structure writer families

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 12:53:28 -07:00
commit 9d9e2965aa
3 changed files with 19 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/control-loop-atlas/runtime-roots-camera-and-support-families.md
View file

@ -3719,6 +3719,15 @@ The low helper strip beneath that shared family is tighter now too: `0x0052ecd0`
`0x55f1/0x55f2/0x55f3` triplet/scalar bands and re-enters the same base triplet/scalar slots
`0x00455870 / 0x00455930`, so the missing placed-structure owner-company lane `[site+0x276]`
still lies outside the checked-in base load path.
The remaining direct `[site+0x276]` writers are split more cleanly now too. `0x00421200` is the
broad late-field constructor/reset zero-fill over the same `0x23a/0x23e/0x25a/0x25e/...` row
family and clears `[+0x276]` as part of that initialization. `0x00428270` is a collection-wide
live owner remap over `0x0062b26c`, rewriting `[site+0x276]` only for rows that still match one
caller-supplied old owner id. `0x00422280` is narrower again: it buckets local float lane
`[row+0x25e]`, generates one `100000 * rand(bucket)` scalar, stores that into `[+0x276]`, and
immediately publishes localized-id `7`. Those three writes therefore belong to constructor/live
mutation or subtype-local scalar families, not the missing restore-time owner-company replay
seam.
On the wider chooser question, the current evidence is also tighter than before: every recovered
external owner of `0x00402cb0` is still in the city-connection family, so the two later direct
placement lanes currently read as city-connection fallback behavior rather than a broadly shared