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

Execute locomotive cost packed event descriptors

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-16 11:19:53 -07:00
commit 09039d24e4
18 changed files with 785 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/README.md
View file

@ -132,6 +132,10 @@ The highest-value next passes are now:
overlay-backed locomotive catalog context: checked-in save-slice documents can populate
`RuntimeState.named_locomotive_availability`, and boolean `0/1` availability descriptors can
lower through `RuntimeState.locomotive_catalog` into the same ordinary event-service path
- that same overlay-backed locomotive catalog now unlocks the recovered locomotive-cost bands too:
nonnegative scalar rows from descriptors `352..451` and `475..500` can lower into the new
event-owned `RuntimeState.named_locomotive_cost` map through the ordinary runtime path, while
cargo-production and territory-access-cost rows remain metadata-rich parity-only families
- 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
- use `rrt-hook` primarily as optional capture or integration tooling, not as the first execution

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

@ -88,15 +88,19 @@ 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 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
still remain parity-only, but the adjacent locomotive-cost bands `352..451` and `475..500` now
import too through the same overlay-backed catalog into the event-owned
`RuntimeState.named_locomotive_cost` map when their scalar payloads are nonnegative
- cargo-production `230..240` and territory-access-cost `453` rows now remain as the primary
recovered scalar-band parity families: their labels, target masks, and slot identities are
checked in, but execution for those families is still deferred until a grounded landing surface
exists
That means the next implementation work is breadth, not bootstrap. The recommended next slice is
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.
honest landing surfaces for one or more of the remaining 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 named locomotive cost
batches.
Richer runtime ownership should still be added only where a later descriptor or condition family
needs more than the current event-owned roster.