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

Box in Tier-2 source family rows

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 16:18:10 -07:00
commit 07ae8b693a
5 changed files with 485 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1364,6 +1364,14 @@
all-zero. So the remaining Tier-2 source question is no longer whether the bare `Port` or
`Warehouse` row carries the seeded selector; it is why one warehouse-shaped industrial peer in
that alias family carries the lone seeded selector while the bare rows do not.
The exact stock resolver-family strip is boxed in now too. The checked-in
`recovered_source_family_summaries` report shows every `0x00419590` source-family row
(`VictorianStation*`, `TudorStation*`, `SoWestStation*`, `PersianStation*`, `KyotoStation*`,
`ClpBrdStation*`, `Maintenance`, and `ServiceTower`) stays on `type_id = 0x000003ec` with
`dword_0xbb = 0`, and almost all of them have no `.bca` pair at all; the only paired standalone
row is `ServiceTower`, and it still carries `byte_0xba = 0x00`, `byte_0xbb = 0x00`. So the
remaining Tier-2 source question is no longer whether the exact `0x00419590` strip itself
carries seeded nonzero bank bytes; current evidence says it does not.
The global stock `.bca` selector report narrows that again: the exact `MachineShop.bca`
signature (`byte_0xb8 = 0x00`, `byte_0xb9 = 0x80`, `byte_0xba = 0x3f`, `byte_0xbb = 0x00`) is
unique across the checked-in stock corpus. So the remaining Tier-2 source frontier is not a