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

Add save-slice company and chairman context

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-16 17:08:03 -07:00
commit 3a88fd3347
29 changed files with 3223 additions and 62 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -53,6 +53,12 @@ Implemented today:
purchasing-power thresholds plus company book-value-per-share thresholds; wider chairman target
ordinals and the still-unpinned investor-confidence / management-attitude condition ids remain
parity frontier
- checked-in save-slice documents can now carry explicit company rosters and chairman profile
tables too, and runtime projection/import will seed or replace company/chairman context from
those save-owned surfaces; that lets the currently supported company-targeted and
chairman-targeted descriptor/condition batches execute from standalone save-slice fixtures
without overlay snapshots when the checked-in documents include that context, while raw `.gms`
inspection/export still leaves those company/chairman surfaces absent
- a minimal event-owned train surface and an opaque economic-status lane now exist in runtime
state, and real descriptors `8` = `Economic Status`, `9` = `Confiscate All`, and `15` =
`Retire Train` now import and execute through the ordinary runtime path when overlay context
@ -125,9 +131,10 @@ That means the next implementation work is breadth, not bootstrap. The recommend
broader real grouped-descriptor and ordinary condition-id coverage beyond the current access,
whole-game toggle, train, player, chairman selected-scope grouped effects, grounded
chairman/governance conditions, numeric-threshold, named locomotive availability, named locomotive
cost, world scalar override, and world-scalar condition batches. Richer runtime ownership should
still be added only where a later descriptor or condition family needs more than the current
event-owned roster.
cost, world scalar override, and world-scalar condition batches, plus eventual raw save
reconstruction for company/chairman context once stronger evidence exists. Richer runtime ownership
should still be added only where a later descriptor or condition family needs more than the
current event-owned roster.
## Why This Boundary