Probe save-side region and structure headers

This commit is contained in:
Jan Petykiewicz 2026-04-18 08:10:44 -07:00
commit ddbdddc5ec
5 changed files with 287 additions and 5 deletions

View file

@ -191,6 +191,10 @@ The highest-value next passes are now:
electric-only periodic-company override rewrites the world route-preference byte to the
effective company preference, ending it restores the base world byte, and runtime service state
now carries both the active and last applied override
- save inspection now also exposes the tagged live region header `0x5209/0x520a/0x520b` and the
tagged placed-structure header `0x36b1/0x36b2/0x36b3` as first-class owner seams, so the
remaining city-connection / linked-transit blocker is record-body reconstruction rather than
missing save-side collection identity
- 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; the checked-in

View file

@ -9,11 +9,13 @@ Working rule:
## Next
- Rehost the next live branch inside
`company_service_periodic_city_connection_finance_and_linked_transit_lanes`, especially the
city-connection announcement / linked-transit roster-maintenance side that now sits on top of
the owned periodic-service seam and the new route-preference apply/restore mutation seam instead
of loose atlas notes.
- Reconstruct the save-side region record body on top of the newly grounded tagged region header,
especially the pending bonus lane `[region+0x276]`, completion latch `[region+0x302]`, one-shot
notice latch `[region+0x316]`, severity/source lane `[region+0x25e]`, and any stable region-id
or class discriminator that can drive shellless city-connection service.
- Reconstruct the save-side placed-structure collection body on top of the newly grounded
`0x36b1/0x36b2/0x36b3` header seam so the blocked city-connection / linked-transit branch can
stop depending on atlas-only placed-structure and local-runtime refresh notes.
- Extend shellless clock advancement so more periodic-company service branches consume owned
runtime time state directly instead of only the explicit periodic service command.
- Keep widening selected-year world-owner state only when a full owning reader/rebuild family is
@ -40,9 +42,18 @@ Working rule:
- Full shell/dialog ownership remains intentionally out of scope.
- Any candidate slice that requires guessing rather than rehosting owning state or real
reader/setter families stays blocked until a better owner seam is grounded.
- The city-connection announcement / linked-transit roster-maintenance branch is still blocked at
the record-body level, not the header level: the runtime now has tagged region and
placed-structure collection header seams, but it does not yet reconstruct the live region or
placed-structure record bodies those service owners need.
## Recently Done
- Save inspection now exposes the tagged region collection header (`0x5209/0x520a/0x520b`,
stride `0x1d5`) and the tagged placed-structure collection header
(`0x36b1/0x36b2/0x36b3`) as first-class owner seams, so the blocked city-connection /
linked-transit queue now has grounded save-side collection counts and ids to build on instead of
only atlas notes.
- Stepped calendar progression now also refreshes save-world owner time fields, including packed
year, packed tuple words, absolute counter, and the derived selected-year gap scalar.
- Automatic year-rollover calendar stepping now invokes periodic-boundary service.

View file

@ -269,6 +269,10 @@ electric-only periodic-company override rewrites `[world+0x4c74]` to the effecti
preference for the active service pass, ending the override restores the base world byte, and
runtime service state now carries both the active and last applied override instead of leaving the
route-preference seam as a pure reader note.
Save inspection now also exposes the tagged live region header `0x5209/0x520a/0x520b` and the
tagged placed-structure header `0x36b1/0x36b2/0x36b3` as first-class owner seams, so the
remaining city-connection / linked-transit blocker is record-body reconstruction rather than
missing save-side collection identity.
That same seam now also carries the fixed-world building-density growth setting plus the linked
chairman personality byte, which is enough to rehost the annual stock-repurchase gate on owned
save/runtime state instead of another threshold-only note. The stock-capital issue branch now