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

Recover scalar-band packed event metadata

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-16 11:02:21 -07:00
commit e2174713a9
8 changed files with 685 additions and 39 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/README.md
View file

@ -125,8 +125,9 @@ The highest-value next passes are now:
`blocked_unmapped_world_descriptor` frontier
- the next recovered locomotives-page descriptor batch is partially executable too:
descriptors `454..456` (`All Steam/Diesel/Electric Locos Avail.`) now lower through checked-in
metadata into keyed `world_flags`, while the wider locomotive availability/cost scalar bands
remain recovered-but-parity-only until per-locomotive identity is grounded
metadata into keyed `world_flags`, while the wider locomotive availability/cost scalar bands now
split cleanly between executable boolean availability rows and recovered metadata-rich parity
rows for the remaining cargo-production, locomotive-cost, and territory-access-cost families
- the runtime now also carries both the save-owned named locomotive availability table and an
overlay-backed locomotive catalog context: checked-in save-slice documents can populate
`RuntimeState.named_locomotive_availability`, and boolean `0/1` availability descriptors can

11
docs/runtime-rehost-plan.md
View file

@ -88,12 +88,15 @@ Implemented today:
through the ordinary event-service path without requiring Trainbuy or live locomotive-pool parity
- the boolean `0/1` subset of the recovered locomotives-page availability bands can now import
through an overlay-backed `RuntimeState.locomotive_catalog`; non-boolean availability payloads
and the adjacent locomotive-cost/cargo-production/access-cost families remain parity-only
and the adjacent locomotive-cost/cargo-production/access-cost families now surface as recovered
metadata-rich parity rows with checked-in slot labels and locomotive ids where grounded, but
execution for those scalar families remains deferred
That means the next implementation work is breadth, not bootstrap. The recommended next slice is
broader real grouped-descriptor and ordinary condition-id coverage beyond the current access,
whole-game toggle, train, player, numeric-threshold, named locomotive availability, and
overlay-resolved locomotive availability batches.
honest landing surfaces for one or more of those recovered scalar families, plus broader real
grouped-descriptor and ordinary condition-id coverage beyond the current access, whole-game
toggle, train, player, numeric-threshold, named locomotive availability, and overlay-resolved
locomotive availability batches.
Richer runtime ownership should still be added only where a later descriptor or condition family
needs more than the current event-owned roster.