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

Correlate infrastructure prelude candidate classes

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 14:51:27 -07:00
commit 5219d5a9ce
3 changed files with 187 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/rehost-queue.md
View file

@ -143,6 +143,14 @@ Working rule:
`TrackCapST_Cap.3dp / Infrastructure` row with compact prefix `0xff0000ff / 0x0001 / 0xff`.
So the next infrastructure slice should target the `BallastCap` outlier family first, not the
already-dominant bridge-section class.
- The candidate-pattern classes are now explicit across the whole stream too: `0x0055 / 0x00`
is a pure `BallastCapST_Cap.3dp / Infrastructure` class across `18` rows, always preceded by a
zero-length prior profile span, while `0x0002 / 0xff` is a pure
`BridgeSTWood_Section.3dp / Infrastructure` class across `18` rows with dominant prior profile
span `0x06` (`10` rows). So the next infrastructure pass should split its owner questions:
treat `0x0055 / 0x00` as a `BallastCap`-specific boundary artifact class, and treat
`0x0002 / 0xff` as the likely bridge-specific two-child / clone-path class above
`0x0048a1e0/0x0048dcf0`.
- Reconstruct the save-side region record body on top of the newly corrected non-direct tagged
region seam (`0x5209/0x520a/0x520b`, stride hint `0x06`, `Marker09` record stems) now that the
`0x55f3` payload is known to be fully consumed by the embedded profile collection on grounded