Expose company periodic side-latch trio
This commit is contained in:
parent
b5d194f678
commit
05e5ade1d8
6 changed files with 49 additions and 2 deletions
|
|
@ -181,6 +181,9 @@ The highest-value next passes are now:
|
|||
`[world+0x65/+0x69/+0x6d]`, the complement trio `[world+0x71/+0x75/+0x79]`, and the scaled
|
||||
companion trio `[world+0x7d/+0x81/+0x85]` from the bucket scalar instead of preserving stale
|
||||
save-time residue
|
||||
- the same save-native company direct-record seam now also carries the full outer periodic-company
|
||||
side-latch trio rooted at `0x0d17/0x0d18/0x0d56`, including the preferred-locomotive
|
||||
engine-type chooser byte beside the city-connection and linked-transit finance gates
|
||||
- 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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue