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

Correlate engine cargo sidecars

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-21 23:27:12 -07:00
commit 16d04c18e4
3 changed files with 116 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
docs/rehost-queue.md
View file

@ -18,6 +18,7 @@ This file is the short active queue for the current runtime and reverse-engineer
The checked PK4 linkage split is now explicit too: `132 / 145` side-view resource names resolve directly, but the remaining `13` are the missing `CarSideView_3.imb` cohort and that hole exists in both checked installs, while `43 / 145` derived `{internal_stem}_NE.imb` names resolve and all of those hits belong to matched locomotive pairs.
The packaged profile metadata is stable enough to summarize: `CarSideView_1` is `512x512` at `0.04` VRAM, `CarSideView_2` is `512x256` at `0.02`, and every packaged `_NE` profile is `512x128` with `HorizontalScaleModifier = 0.75` and `MaxPercentOfInterfaceVRAM = 0.09`.
The `_NE` split is now aligned with the locomotive display census too: all `43` packaged `_NE` hits live inside the grounded display prefix, and all `5` unmatched display-tail families are still missing packaged `_NE` profiles.
The cargo side is partially linked now as well: the `.cgo` ladder families and `.cct` sidecar identifiers share the same cargo-family keys for ten checked families, with `Troop` left as the only `.cct`-only outlier.
The next honest static work is to keep promoting those fixed lanes into stable parser fields, explain the five remaining distinct auxiliary-stem cases, and decide how far the `.cgo` ladders plus the low-cardinality `.lco` lanes can be grounded without overclaiming semantics.
Preserved checked parser detail now lives in [EngineTypes parser semantics](rehost-queue/engine-types-parser-semantics-2026-04-21.md).
Preserved checked format inventory detail now lives in [RT3 format inventory](rehost-queue/format-inventory-2026-04-21.md).

8
docs/rehost-queue/engine-types-parser-semantics-2026-04-21.md
View file

@ -49,6 +49,11 @@ first `.car` / `.lco` / `.cgo` / `.cct` inspector pass landed.
- `55 -> 85` for `Auto_Carrier`
- `6 -> 13 -> 27 -> 53` for `Passenger`
- `7 -> 13 -> 27 -> 53` for `Mail`
- The cargo-side sidecars now have one grounded join seam:
- `cgo_scalar_values_by_content_stem` keys line up directly with the `.cct` identifiers for
`Auto_Carrier`, `Box`, `Covered_Hopper`, `Flatbed`, `Mail`, `Open_Hopper`, `Passenger`,
`Reefer`, `Stock_Car`, and `Tanker`
- `Troop` remains the only checked `.cct` identifier with no matching `.cgo` content stem
- `.cct` remains the least ambiguous sidecar: current shipped files still look like narrow one-row
text metadata.
- The side-view resource seam is no longer a loose-file dead end:
@ -100,6 +105,7 @@ first `.car` / `.lco` / `.cgo` / `.cct` inspector pass landed.
- leading scalar lane
- content stem
- scalar ladder counts by shared cargo-car family
- shared-key map from `.cgo` content stem to `.cct` sidecar value
- `.cct`
- tokenized identifier/value row
- `.imb`
@ -130,6 +136,8 @@ first `.car` / `.lco` / `.cgo` / `.cct` inspector pass landed.
- `.cgo`
- whether the leading scalar ladders are enough to justify a named typed field, or whether they
should stay conservative report-only ladders until more binary/code correlation exists
- whether the matching `.cct` sidecar values justify a named field, or whether they should stay
as cargo-family sidecar codes until more binary/code correlation exists
## Next Static Parser Work