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

Census locomotive tail blockers across local saves

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-21 22:15:17 -07:00
commit cbfe0a8df9
16 changed files with 2022 additions and 319 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/README.md
View file

@ -313,8 +313,12 @@ The highest-value next passes are now:
- recovered scalar locomotive availability and locomotive-cost descriptors now import through that
save-native or embedded `RuntimeState.locomotive_catalog` context into the ordinary
`named_locomotive_availability` and `named_locomotive_cost` runtime maps
- the grounded executable lower locomotive prefix now extends through save-backed locomotive id
`61` (`Zephyr`); the unresolved lower tail and upper locomotive bands stay on explicit parity
- the full lower locomotive bands now execute through that save-native ordinal catalog too:
availability `241..351` and cost `352..451`; the checked `29`-save `.gms + .gmx`
`locomotive-catalog-tail-census.json` export now fixes the last save-stable static descriptor
boundary at ordinal `58` (`VL80T`) and leaves descriptor `452` plus the upper bands
`457..474` / `475..502` as external-corpus or dynamic blockers rather than active repo-local
static work
- cargo-production `230..240` and territory-access-cost `453` now execute too through minimal
world-side scalar landing surfaces: slot-indexed `cargo_production_overrides` and
`world_restore.territory_access_cost`
@ -331,8 +335,10 @@ The highest-value next passes are now:
- the company/chairman frontier has moved too: checked-in save-slice documents can now carry that
context natively, so the next work on that axis is broader recovery and eventual raw save
reconstruction rather than overlay-only ownership
- keep in mind that the current local `.gms` corpus still exports with no packed event collection,
so real descriptor mapping needs to stay plumbing-first until better captures exist
- keep in mind that the current local `.gms + .gmx` corpus does carry packed-event collections,
but the checked `29`-save locomotive census still finds no descriptor carriers in `452` or
`457..502`, so further locomotives-page closure now needs either broader save evidence or
dynamic captures
- use `rrt-hook` primarily as optional capture or integration tooling, not as the first execution
environment
- keep `docs/runtime-rehost-plan.md` current as the runtime baseline and next implementation slice