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

Probe raw save investor-confidence issue state

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-17 17:10:43 -07:00
commit 934b0049eb
5 changed files with 174 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/README.md
View file

@ -98,8 +98,8 @@ The highest-value next passes are now:
can execute from standalone save-slice fixtures without overlay snapshots when that context is
present; raw `.gms` inspection/export now reconstructs those company/chairman collections
directly from save-side tagged record families, while the fixed save-side `0x32c8` world block
still provides selected company/chairman ids plus the grounded campaign-override and
chairman-slot / role-gate analysis bytes; the current raw-save frontier is narrower now:
still provides selected company/chairman ids plus the grounded campaign-override, issue-`0x37`
value/multiplier, and chairman-slot / role-gate analysis bytes; the current raw-save frontier is narrower now:
company/chairman identity, active flags, links, chairman cash, chairman holdings, chairman
purchasing power, company debt, company track-laying capacity, and collection counts are
grounded, while broader company
@ -107,9 +107,12 @@ The highest-value next passes are now:
defaults until their raw offsets are pinned more strongly; the offline analysis command
`runtime inspect-save-company-chairman <save.gms>` now dumps those remaining raw record
candidates directly from the rehosted parser, including fixed-world chairman slot / role-gate
context, the fixed-world six-float economic tuning band, derived holdings-at-share-price and
cached purchasing-power totals,
context, the grounded fixed-world issue-`0x37` pair, the separate six-float economic tuning
band, derived holdings-at-share-price and cached purchasing-power totals,
context, company dword candidate windows, and richer chairman qword cache views
- the project rule on the remaining closure work is now explicit too: when one runtime-facing field
is still ambiguous, prefer rehosting the owning source state or real reader/setter family first
instead of guessing another derived leaf field from neighboring raw offsets
- a checked-in `EventEffects` export now exists at
`artifacts/exports/rt3-1.06/event-effects-table.json`, and a checked-in semantic closure layer
now exists at `artifacts/exports/rt3-1.06/event-effects-semantic-catalog.json`