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

Bind Tier2 names to setup payload rows

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 14:13:55 -07:00
commit 4e1023fb29
2 changed files with 17 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1229,6 +1229,12 @@
every current shipped `.bca` stays zero at `0xb8..0xbb` except `MachineShop.bca`, which carries
the lone selector-window exception `(0x00, 0x80, 0x3f, 0x00)` on a `788`-byte row, while the
separate `backup/Bldg/*.bca` corpus stays fully zero there.
Direct map-payload inspection sharpens that split further. The current Tier-2 maps
`Louisiana.gmp`, `Dutchlantis.gmp`, and `South East USA.gmp` all already carry the literal
`Port00` / `Warehouse00` / `Port01` / `Warehouse01` names inside the shared setup payload at
stable offsets `0x6f77`, `0x7087`, `0x70cb`, and `0x7241`, while the same map corpus shows no
`MachineShop` string at all. So the live `PortNN` / `WarehouseNN` family now looks more like a
setup-payload candidate-table / source-row projection problem than a hidden alternate BCA stem.
The direct `+0xba/+0xbb` writer census now rules out a broad false lead too. The obvious new
stores at `0x004ecd42/0x004ecdaa` and `0x004ed5d5/0x004ed625` are only shell-side
portrait/string refresh helpers over a different id-keyed collection rooted through