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

Rehost save-native company market cache state

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-17 18:28:53 -07:00
commit 5198f80cd9
9 changed files with 630 additions and 79 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -69,7 +69,10 @@ Implemented today:
the same fixed world payload now exposes the grounded issue-`0x37` pair at `[world+0x29/+0x2d]`
and the separate six-float economic tuning band `[world+0x0be2..+0x0bf6]` through save
inspection too, but current atlas evidence still keeps that editor-tuning family separate from
the company-governance issue lanes;
the company-governance issue lanes; the next shared company-side owning state is rehosted now
too, because save-native company direct records now project into a typed runtime
`company_market_state` cache map carrying outstanding shares, support/share-price/cache words,
chairman salary lanes, calendar words, and connection latches for each live company;
and `runtime inspect-save-company-chairman <save.gms>` now exposes the remaining raw
company/chairman scalar candidates directly from the rehosted parser, including fixed-world
chairman slot / role-gate context, company dword candidate windows, richer chairman qword
@ -189,8 +192,11 @@ frontier is no longer anonymous id recovery; it is the remaining recovered-but-n
families from the checked-in semantic catalog, especially cargo-price, add-building, and other
descriptor clusters that now have explicit shell-owned or evidence-blocked status but not yet a
bounded executable landing surface. Raw save reconstruction for company/chairman context is still a
later tranche 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.
later tranche once stronger evidence exists, but the current project rule is explicit: prefer
rehosting shared owner state and reader/setter families first, and only guess at one more leaf
field when that richer owning-state path is blocked. Richer runtime ownership should still be added
where later descriptor, stat-family, or simulation work needs more than the current event-owned
roster.
## Why This Boundary