Compare placed-structure side-buffer name corpus

This commit is contained in:
Jan Petykiewicz 2026-04-18 12:09:08 -07:00
commit 564b8b6641
3 changed files with 410 additions and 3 deletions

View file

@ -26,8 +26,9 @@ Working rule:
name rows now make it the grounded placed-structure dynamic side-buffer owner; the remaining
blocker is semantic closure of the compact prefix regimes now summarized in real saves as seven
stable patterns on `q.gms` and their relation to the embedded `0x55f1/0x55f2/0x55f3` row
subset, especially the dominant bridge-section `0xff000000/0x0001/0xff` group and the smaller
`0x000055f3/0x0001/0xff` group that matches the embedded profile tag directly.
subset, especially now that the side-buffer name-pair corpus is proven disjoint from the
grounded `0x36b1` triplet name-pair corpus on `q.gms`; the next pass should treat `0x38a5` as
a separate infrastructure-asset owner seam, not a compact alias over the triplet records.
- Extend shellless clock advancement so more periodic-company service branches consume owned
runtime time state directly instead of only the explicit periodic service command.
- Keep widening selected-year world-owner state only when a full owning reader/rebuild family is
@ -110,6 +111,12 @@ Working rule:
rows, the `0xff0000ff/0x0001/0xff` and `0xf3010100/0x0055/0x00` groups concentrating cap-like
rows, and a smaller `0x000055f3/0x0001/0xff` group carrying 17 tunnel-section / cap rows whose
leading dword matches the embedded placed-structure profile tag directly.
- The save-company/chairman analysis path now also compares that grounded `0x38a5` side-buffer
name-pair corpus against the grounded `0x36b1` triplet name-pair corpus directly; on `q.gms`
the overlap is currently zero (`0/138` decoded side-buffer rows and `0/5` unique side-buffer
name pairs match the 56-triplet corpus), which shifts the remaining placed-structure work away
from “prove these are aliases” toward “find how the separate infrastructure-asset owner seam is
consumed by city-connection / linked-transit service.”
- The placed-structure tagged save stream now also exposes repeated `0x55f1/0x55f2/0x55f3`
triplets with dual name stems, a fixed five-`f32` policy row, and a compact `0x5dc1...0x5dc2`
footer carrying one raw `u32` payload lane plus one live `i32` status lane, so the remaining