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

Execute recovered world scalar event descriptors

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-16 11:39:59 -07:00
commit 13c7268b0d
23 changed files with 675 additions and 98 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -86,21 +86,22 @@ Implemented today:
save-slice documents can carry the persisted `[world+0x66b6]` name table into
`RuntimeState.named_locomotive_availability`, and imported runtime effects can mutate that map
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
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
- the recovered locomotives-page availability bands can now import as full scalar overrides
through an overlay-backed `RuntimeState.locomotive_catalog` into
`RuntimeState.named_locomotive_availability`; save-slice-only imports of those rows now fail on
the explicit `blocked_missing_locomotive_catalog_context` frontier rather than a generic
unmapped-world bucket
- 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
- the remaining recovered scalar world families now execute as well: cargo-production `230..240`
rows lower into slot-indexed `cargo_production_overrides`, and territory-access-cost descriptor
`453` lowers into `world_restore.territory_access_cost`
That means the next implementation work is breadth, not bootstrap. The recommended next slice is
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.
broader real grouped-descriptor and ordinary condition-id coverage beyond the current access,
whole-game toggle, train, player, numeric-threshold, named locomotive availability, named
locomotive cost, and world scalar override batches.
Richer runtime ownership should still be added only where a later descriptor or condition family
needs more than the current event-owned roster.