Link infrastructure footer gate to layout state

This commit is contained in:
Jan Petykiewicz 2026-04-18 18:00:56 -07:00
commit 2b3b32ab90
2 changed files with 7 additions and 2 deletions

View file

@ -226,11 +226,14 @@ Working rule:
`0x005295f0..0x005297b7` repopulates candidate cells through `0x00533ba0`, walks candidate
child lists through `0x00556ef0/0x00556f00`, and honors the same controller mode byte
`[owner+0x3692]` that the atlas already places under the world-window presentation dispatcher.
- The neighboring helpers tighten that owner family further: atlas-backed `0x00533ba0` is the
nearby-presentation cell-table helper under the layout/presenter strip, direct disassembly shows
`0x00548da0` walking layout list root `[layout+0x2593]`, and direct disassembly of `0x0054bab0`
mutates layout slots `[layout+0x2637/+0x263b/+0x2643]`.
- That means the remaining infrastructure question is no longer both footer bytes. It is
specifically why the stable `0x000055f3 / 0x0001 / 0xff` tunnel family sets the first footer
byte / bit-`0x20` admission gate while the sparse `0xff0000ff / 0x0001 / 0xff` outlier class
clears it, inside that nearby-presentation/controller owner family rather than at the serializer
layer.
clears it, inside that layout/presentation owner family rather than at the serializer layer.
- Source-side constructor analysis is narrower now too. `0x00490960` takes:
- mode at stack arg 1
- stem at stack arg 2