Add higher-layer rehost trace probes
This commit is contained in:
parent
dc7215f720
commit
6bfe4d043f
7 changed files with 741 additions and 22 deletions
|
|
@ -203,6 +203,12 @@ The highest-value next passes are now:
|
|||
`docs/rehost-queue.md` file is the control surface for that work loop, and after each commit the
|
||||
next queue item should run unless the queue is empty, a real blocker remains, or approval is
|
||||
needed
|
||||
- `rrt-runtime` now also exposes higher-layer probe commands for the current blocked frontier:
|
||||
`runtime inspect-periodic-company-service-trace <save.gms>`,
|
||||
`runtime inspect-region-service-trace <save.gms>`, and
|
||||
`runtime inspect-infrastructure-asset-trace <save.gms>`. These reports make the current
|
||||
shellless city-connection / linked-transit blockers explicit as missing owner seams rather than
|
||||
generic “still unresolved” residue.
|
||||
- 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`
|
||||
|
|
|
|||
|
|
@ -9,6 +9,11 @@ Working rule:
|
|||
|
||||
## Next
|
||||
|
||||
- Follow the new higher-layer probe outputs instead of another blind save scan:
|
||||
`runtime inspect-infrastructure-asset-trace <save.gms>` now shows that the `0x38a5`
|
||||
infrastructure-asset seam is grounded and the old alias hypothesis is disproved on `q.gms`, so
|
||||
the next placed-structure slice should target the consumer mapping above that seam rather than
|
||||
more collection discovery.
|
||||
- Reconstruct the save-side region record body on top of the newly corrected non-direct tagged
|
||||
region seam (`0x5209/0x520a/0x520b`, stride hint `0x06`, `Marker09` record stems) now that the
|
||||
`0x55f3` payload is known to be fully consumed by the embedded profile collection on grounded
|
||||
|
|
@ -65,6 +70,18 @@ Working rule:
|
|||
|
||||
## Recently Done
|
||||
|
||||
- `rrt-runtime` now exposes three higher-layer probe surfaces and matching CLI inspectors:
|
||||
`runtime inspect-periodic-company-service-trace <save.gms>`,
|
||||
`runtime inspect-region-service-trace <save.gms>`, and
|
||||
`runtime inspect-infrastructure-asset-trace <save.gms>`. These reports separate grounded outer
|
||||
owner inputs, runnable shellless branches, and explicit missing owner seams instead of leaving
|
||||
the current city-connection / linked-transit frontier as an opaque blocker.
|
||||
- Those same probes now also sharpen the next queue choice on grounded real saves: the periodic
|
||||
company outer owner shows annual finance and route-preference override as grounded shellless
|
||||
branches while city-connection and linked-transit stay blocked on region/infrastructure owner
|
||||
seams; the region trace keeps the queued kind-`7` notice family on the transient side; and the
|
||||
infrastructure trace now makes the `0x38a5` consumer-mapping blocker first-class after
|
||||
disproving any alias to the `0x36b1` placed-structure triplet corpus.
|
||||
- Save inspection now splits the shared `0x5209/0x520a/0x520b` family correctly: the smaller
|
||||
direct `0x1d5` collection is the live train family and now exposes a live-entry directory rooted
|
||||
at metadata dword `16`, while the actual region family is the larger non-direct `Marker09`
|
||||
|
|
|
|||
|
|
@ -297,6 +297,12 @@ The process rule for the remaining runtime work is explicit too: prefer rehostin
|
|||
real reader/setter families over guessing leaf fields, and use `docs/rehost-queue.md` as the
|
||||
checked-in control surface for the work loop. After each commit, check that queue and continue
|
||||
unless the queue is empty, a real blocker remains, or approval is needed.
|
||||
The same control surface now also has matching runtime probes:
|
||||
`runtime inspect-periodic-company-service-trace <save.gms>`,
|
||||
`runtime inspect-region-service-trace <save.gms>`, and
|
||||
`runtime inspect-infrastructure-asset-trace <save.gms>`. Use those first when the next blocked
|
||||
frontier is “which higher-layer owner seam is still missing?” rather than “which raw save
|
||||
collection exists?”.
|
||||
That same owner seam now also derives live coupon burden totals directly from saved bond slots,
|
||||
which gives later finance service work a bounded runtime reader instead of another synthetic
|
||||
finance leaf.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue