Carry company stat-band roots into runtime state
This commit is contained in:
parent
8473471a79
commit
1e0f88bd62
9 changed files with 180 additions and 15 deletions
|
|
@ -112,8 +112,9 @@ The highest-value next passes are now:
|
|||
tuning band, derived holdings-at-share-price and cached purchasing-power totals,
|
||||
context, company dword candidate windows, and richer chairman qword cache views; the current
|
||||
rehosted company-side owner state now also includes a typed market/cache map carrying saved
|
||||
outstanding-shares, support/share-price/cache words, salary lanes, calendar words, and
|
||||
connection latches for each live company, so later finance/stat-family readers can attach to
|
||||
outstanding-shares, support/share-price/cache words, salary lanes, calendar words, connection
|
||||
latches, and the first grounded stat-band root windows at `[company+0x0cfb]`, `[company+0x0d7f]`,
|
||||
and `[company+0x1c47]` for each live company, so later finance/stat-family readers can attach to
|
||||
owned runtime data instead of one more guessed save offset
|
||||
- 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
|
||||
|
|
|
|||
|
|
@ -197,7 +197,9 @@ later tranche once stronger evidence exists, but the current project rule is exp
|
|||
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.
|
||||
roster. The current owned company-side roster now includes not just the market/cache lanes but also
|
||||
the first grounded stat-band root windows at `[company+0x0cfb]`, `[company+0x0d7f]`, and
|
||||
`[company+0x1c47]`, so later finance readers can target saved owner state directly.
|
||||
|
||||
## Why This Boundary
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue