From b7cb61ca79150f4a38e86b0f2f64112f2082308f Mon Sep 17 00:00:00 2001 From: Jan Petykiewicz Date: Sun, 19 Apr 2026 14:53:51 -0700 Subject: [PATCH] Correct Tier2 stock import owner strip --- .../map-and-scenario-content-load.md | 14 ++++++------ ...ntime-roots-camera-and-support-families.md | 14 ++++++------ docs/rehost-queue.md | 22 ++++++++++--------- 3 files changed, 26 insertions(+), 24 deletions(-) diff --git a/docs/control-loop-atlas/map-and-scenario-content-load.md b/docs/control-loop-atlas/map-and-scenario-content-load.md index 5b0829c..b01dd1e 100644 --- a/docs/control-loop-atlas/map-and-scenario-content-load.md +++ b/docs/control-loop-atlas/map-and-scenario-content-load.md @@ -57,13 +57,13 @@ `aux_candidate_collection_rebank_or_clone_records_by_availability_pass_and_refresh_owner_links` `0x00419230` before the later world-load side continues, with destructor `aux_candidate_collection_release_templates_queues_and_indexed_storage` `0x00419680`. The fixed - stock source-family layer above that clone pass is bounded now too: `0x004197e0` formats source - names from the `0x005f3c6c` / `0x005f3c80` style tables, routes them through parser - `0x00414490`, and only then falls into the same `0x00419230` rebank-or-clone sweep. The - recovered source-name table is `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, - `Maintenance`, `ClpBrd`, `Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the - remaining Tier-2 load-side question is the style-family row-selection path into that later bank - pass rather than another hidden naming stage. + stock source-family layer above that clone pass is bounded now too: the same `0x004196c0` + import owner walks the `%1*.bty` file set, routes each match through parser `0x00414490`, + calls the stock load callback `0x00416ce0`, and only then falls into the same `0x00419230` + rebank-or-clone sweep. The recovered source-name table is `StationSml`, `StationMed`, + `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, `Kyoto`, `Persian`, `SoWest`, `Tudor`, + and `Victorian`, so the remaining Tier-2 load-side question is the style-family row-selection + path into that later bank pass rather than another hidden naming stage. The fixed tail is explicit now too: `0x00444dd0` writes one direct dword from `[world+0x19]`, one zeroed `0x1f4`-byte slab under `0x32cf`, closes the package, derives the diff --git a/docs/control-loop-atlas/runtime-roots-camera-and-support-families.md b/docs/control-loop-atlas/runtime-roots-camera-and-support-families.md index 8381893..d2124d9 100644 --- a/docs/control-loop-atlas/runtime-roots-camera-and-support-families.md +++ b/docs/control-loop-atlas/runtime-roots-camera-and-support-families.md @@ -1282,13 +1282,13 @@ stay in `named_binding_comparison.binding_only_canonical_stems`. So the numbered Tier-2 families no longer belong under stock `BuildingTypes/*.bty` discovery either; they belong under the scenario/live candidate-table projection seam above the now-grounded bare-name remap. - The stock source-family loader above that remap is bounded now too. `0x004197e0` builds source - names from the table at `0x005f3c6c` plus companion path table `0x005f3c80`, feeds each result - into `0x00414490`, and only then tails into `0x00419230`. The currently recovered source-name - set is `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, - `Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the remaining Tier-2 source frontier - is the style-family row-selection path into the later banked clone pass, not another hidden - name generator. + The stock source-family loader above that remap is bounded now too. `0x004196c0` walks the + `%1*.bty` file set, routes each match through `0x00414490`, calls the stock load callback + `0x00416ce0`, and only then tails into `0x00419230`. The currently recovered source-name set is + `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, `Kyoto`, + `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the remaining Tier-2 source frontier is the + style-family row-selection path into the later banked clone pass, not another hidden name + generator. The exact-match helper under that family is bounded now too. `0x00419590` copies one source-kind name from `0x005f3c6c`, combines it with one style/theme entry from the smaller subset table `0x005f3c80` through format `"%1%2"` at `0x005c8730`, and then scans the live diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md index a35f1e7..2dabe13 100644 --- a/docs/rehost-queue.md +++ b/docs/rehost-queue.md @@ -15,15 +15,17 @@ Working rule: now shows: - `0x00416ce0` is the stock `gpdBuildingTypeDB` `%1*.bty` load callback and already rewrites bare `port` / `warehouse` to `Port00` / `Warehouse00` - - `0x004197e0` iterates the stock style/source-family table at `0x005f3c6c` through - `0x00414490`, not a map-specific alternate catalog; the current recovered source names are + - `0x004196c0` is the stock import owner that walks `%1*.bty` matches, routes them through + `0x00414490`, calls the same `0x00416ce0` load callback, and only then tails into + `0x00419230`; the current recovered source names are `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, `Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian` - `0x00419230` is then the later two-bank, twelve-ordinal clone-and-rename pass that stamps `Warehouse%02d` / `Port%02d` - so the next honest question is which source rows out of that stock style-family strip first satisfy each later `(bank, ordinal)` pair before `0x00419230` clones them - - that means the queue should keep tracing `0x004197e0 -> 0x00414490 -> 0x00419230` and its + - that means the queue should keep tracing `0x004196c0 -> 0x00414490 -> 0x00416ce0 -> 0x00419230` + and its callsites, not return to the older generic hidden-writer hypothesis - Treat the periodic-company trace as the main shellless simulation frontier now that the @@ -814,13 +816,13 @@ Working rule: stock `BuildingTypes/*.bty` discovery for the numbered families either; the remaining `01..11` source work belongs under scenario/live candidate-table projection and row-family choice above the already-grounded bare-name remap. - The stock source-family strip above that remap is grounded now too. `0x004197e0` formats file - names from the source-name table `0x005f3c6c` and companion path table `0x005f3c80`, feeds the - result into `0x00414490`, and only then tails into `0x00419230`. The recovered source-name - table is `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, - `Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the next Tier-2 source question is - no longer “where do numbered names come from?” but “which style-family rows first survive into - the later two-bank, twelve-ordinal clone pass?” + The stock source-family strip above that remap is grounded now too. `0x004196c0` walks the + `%1*.bty` file set, routes each match through `0x00414490`, calls the stock load callback + `0x00416ce0`, and only then tails into `0x00419230`. The recovered source-name table is + `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, `Kyoto`, + `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the next Tier-2 source question is no longer + “where do numbered names come from?” but “which style-family rows first survive into the later + two-bank, twelve-ordinal clone pass?” The exact-match resolver beneath that style-family strip is grounded now too. `0x00419590` copies one source-kind name from `0x005f3c6c`, combines it with one style/theme entry from the smaller subset table `0x005f3c80` through format `"%1%2"` at `0x005c8730`, and then scans the