Classify machine shop Tier-2 selector outlier

This commit is contained in:
Jan Petykiewicz 2026-04-19 15:54:32 -07:00
commit 7894c52aea
5 changed files with 6714 additions and 278 deletions

View file

@ -1314,6 +1314,15 @@ Working rule:
So the next Tier-2 source-selection pass should no longer ask whether whole alias clusters map
to nonzero bank bytes; it should ask why one specific stock row inside the `TextileMill`
cluster surfaces a nonzero selector while its peer rows stay zero
- the direct-name plus alias plus selector join narrows that one step further:
inside the same nonzero `0x000001f4` family, the direct
`Warehouse/TextileMill/Warehouse` shape splits into six all-zero selector peers
(`ConcretePlant`, `ConstructionFirm`, `ElectronicsPlant`, `Hospital`,
`PharmaceuticalPlant`, and `Warehouse`) plus one unique selector outlier,
`MachineShop = 0x00/0x80/0x3f/0x00`. The sibling bare `Port/TextileMill/Port` row stays
all-zero. So the remaining Tier-2 question is no longer “does the bare `Port` or
`Warehouse` row carry the seeded selector?”; it is “why does one warehouse-shaped industrial
peer in that alias family carry the lone seeded selector while the bare rows do not?”
- the global stock `.bca` selector report narrows that one step further still: 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 current Tier-2