From c9f79fdf768f2adc219886b22a8de62567f5ced7 Mon Sep 17 00:00:00 2001 From: Jan Petykiewicz Date: Tue, 21 Apr 2026 18:37:43 -0700 Subject: [PATCH] Preserve Tier2 rebuild sequencing evidence --- docs/rehost-queue.md | 2 + docs/rehost-queue/README.md | 2 + .../tier2-rebuild-sequencing-2026-04-21.md | 68 +++++++++++++++++++ 3 files changed, 72 insertions(+) create mode 100644 docs/rehost-queue/tier2-rebuild-sequencing-2026-04-21.md diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md index fea8be4..bdc6cf9 100644 --- a/docs/rehost-queue.md +++ b/docs/rehost-queue.md @@ -17,11 +17,13 @@ This file is the short active queue for the current runtime and reverse-engineer The grounded owner strip is `0x004196c0 -> 0x00414490 -> 0x00416ce0 -> 0x00419230`, and the checked candidate-table export now keeps the concrete row families explicit too: among the `37` probe-bearing maps, `Port00/Warehouse00` stay at `35/43` on `30` maps and shift earlier to `10/18` on `7`, while `Port01..11` / `Warehouse01..11` stay fixed at `45..55` / `56..66` and the numbered trailer family splits independently at `0x00000001 -> 28 maps` versus `0x00000000 -> 9 maps`. The new crossover matrix stays mixed rather than collapsing to one side too: `35/43 :: 0x00000001 -> 25 maps`, `35/43 :: 0x00000000 -> 5 maps`, `10/18 :: 0x00000000 -> 4 maps`, and `10/18 :: 0x00000001 -> 3 maps`. The stock `BuildingTypes` side is narrower too: across `77` checked `.bca` files only `MachineShop.bca` carries nonzero selector bytes at `0xb8..0xbb`, while the broader nonzero stock signal lives in the `22`-file `.bty` alias-root family with `dword_0xbb = 0x000001f4`, especially the `TextileMill` branch that already covers `Port.bty` and `Warehouse.bty`. The active open question is therefore which earlier seed/projection path lifts that narrow stock-side signal and the fixed numbered cluster into nonzero live `[candidate+0xba/+0xbb]` before `0x00412d70` and `0x00419230` consume it. Preserved checked row-family detail now lives in [Tier2 candidate row families](rehost-queue/tier2-candidate-row-families-2026-04-21.md). Preserved checked stock selector-byte detail now lives in [Tier2 selector-byte sources](rehost-queue/tier2-selector-byte-sources-2026-04-21.md). + Preserved checked rebuild sequencing detail now lives in [Tier2 rebuild sequencing](rehost-queue/tier2-rebuild-sequencing-2026-04-21.md). ## Preserved Detail - [Archive snapshot](rehost-queue/archive-2026-04-19.md) - [Periodic company control lane](rehost-queue/periodic-company-control-lane-2026-04-21.md) - [Tier2 candidate row families](rehost-queue/tier2-candidate-row-families-2026-04-21.md) +- [Tier2 rebuild sequencing](rehost-queue/tier2-rebuild-sequencing-2026-04-21.md) - [Tier2 selector-byte sources](rehost-queue/tier2-selector-byte-sources-2026-04-21.md) - [Progress history](history/progress-history.md) diff --git a/docs/rehost-queue/README.md b/docs/rehost-queue/README.md index 5bbac32..b5375e7 100644 --- a/docs/rehost-queue/README.md +++ b/docs/rehost-queue/README.md @@ -9,5 +9,7 @@ useful as evidence, but should not stay in the short active queue file. maps. - `tier2-candidate-row-families-2026-04-21.md`: checked candidate-table row-family, trailer-family, and crossover carrier-map split for the active Tier-2 `0x00412d70` queue head. +- `tier2-rebuild-sequencing-2026-04-21.md`: checked late bringup sequencing across + `0x00435630 / 0x00412d70 / 0x00412fb0 / 0x00412c10` for the active Tier-2 queue head. - `tier2-selector-byte-sources-2026-04-21.md`: checked stock `BuildingTypes` selector-byte and alias-root evidence for the active Tier-2 `0x00412d70` queue head. diff --git a/docs/rehost-queue/tier2-rebuild-sequencing-2026-04-21.md b/docs/rehost-queue/tier2-rebuild-sequencing-2026-04-21.md new file mode 100644 index 0000000..debdd7d --- /dev/null +++ b/docs/rehost-queue/tier2-rebuild-sequencing-2026-04-21.md @@ -0,0 +1,68 @@ +# Tier2 Rebuild Sequencing (2026-04-21) + +This note preserves the currently grounded sequencing around the active Tier-2 queue head, so the +short queue does not have to restate the same late bringup strip every time. + +## Preserved Artifact Notes + +- `artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-sequencing-note.md` +- `artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-runtime-note.md` + +## Coupled Rebuild Strip + +The current Tier-2 bringup evidence no longer reads as one isolated helper. The grounded rebuild +owners form one coupled strip: + +- `0x00435630` + - rebuilds scenario-side port/warehouse recipe runtime tables + - re-enters `0x00412d70` +- `0x00412d70` + - rebuilds candidate runtime records from scenario state + - does not consult the scenario-side recipe-book name at `[state+0x0fe8]` + - re-enters `0x00435630` + - also re-enters `0x00411ce0` and `0x00411ee0` +- `0x00412fb0` + - broader collection-load owner + - re-enters `0x004120b0` + - then `0x00412d70` + - then `0x00412ab0` + - and only after the later catalog rebuild re-enters `0x00412c10` +- `0x00437737` + - late preseed of named candidate-availability records from the live pool + - upserts through `0x00434f20` +- `0x00434f20` + - writes the boolean named-availability override bit + - immediately re-enters `0x00412c10` when the live candidate pool exists +- `0x00412c10` + - refreshes `[candidate+0x7ac]` from named availability + - then tails into `0x0041eac0` + +## Late Bringup Placement + +The preserved sequencing note keeps the late `0x197` checkpoint concrete too: + +- `0x00444ac1` sits after: + - `0x004354a0` + - territory overlay sweep `0x00487de0` +- and then falls through into: + - `0x00437737` + - followed by the later candidate-side availability refresh `0x00412c10` + +So the late Tier-2 strip begins with named-availability preseed and latch refresh, not with the +shell progress or territory overlay helpers that precede it. + +## Current Reading + +This keeps the active Tier-2 owner question on sequencing and data handoff, not on bare naming: + +- one side of the strip is the coupled recipe/runtime rebuild family + `0x00435630 -> 0x00412d70 -> 0x00412fb0` +- the other side is the later named-availability preseed/latch family + `0x00437737 -> 0x00434f20 -> 0x00412c10` +- the remaining non-hook question is how that interaction lets candidate-table rows + `35/43/45..66` reach `0x00412d70` with nonzero `[candidate+0xba/+0xbb]` before the later + `0x00419230` rebank-or-clone pass consumes them + +So the next Tier-2 pass should keep tracing the handoff between those two late rebuild bands, +rather than reopening the direct `Warehouse05` availability bit or the already-bounded stock asset +corpus.