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 586b138..8381893 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
@@ -1289,6 +1289,13 @@
   `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
+  auxiliary pool `0x0062b2fc` for the first exact `[entry+0x04]` match. So the
+  `0x005f3c6c/0x005f3c80` pair is no longer an anonymous bank-byte helper; it is the stock
+  style-family-to-combined-name resolver immediately below the remaining Tier-2 source-selection
+  frontier.
   The direct `+0xba/+0xbb` writer census now rules out a broad false lead too. The obvious new
   stores at `0x004ecd42/0x004ecdaa` and `0x004ed5d5/0x004ed625` are only shell-side
   portrait/string refresh helpers over a different id-keyed collection rooted through
diff --git a/docs/control-loop-atlas/station-detail-overlay.md b/docs/control-loop-atlas/station-detail-overlay.md
index a7cbbaa..2cf45bd 100644
--- a/docs/control-loop-atlas/station-detail-overlay.md
+++ b/docs/control-loop-atlas/station-detail-overlay.md
@@ -180,9 +180,10 @@ split: `0xb3bd` selects family `1`, while the sibling controls select family `2`
 linked-site flag bits `[entry+0xc3]` to one action index `0..5` and resolves the resulting
 `(action_index, family)` pair through
 `aux_candidate_collection_find_entry_id_by_station_detail_action_index_and_family` `0x00419590`,
-which formats one localized action stem from the fixed tables at `0x005f3c6c/0x005f3c80` and scans
-the auxiliary candidate pool `0x0062b2fc` for the first matching stem at `[entry+0x04]`. Only
-after that auxiliary id resolves does the branch enter the deeper world-side validation owner
+which copies one source-kind name from `0x005f3c6c`, combines it with one style/theme entry from
+the smaller subset table `0x005f3c80` through `"%1%2"` at `0x005c8730`, and then scans the
+auxiliary candidate pool `0x0062b2fc` for the first exact combined-name match at `[entry+0x04]`.
+Only after that auxiliary id resolves does the branch enter the deeper world-side validation owner
 `placed_structure_validate_station_detail_aux_candidate_action_and_optionally_apply_linked_site_mutation`
 `0x0040dc40` plus the two confirmation-modal branches rooted at localized ids `0x0bfe` and
 `0x0bff`. The constructor-side special-action strip is explicit now too:
diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md
index a76f60d..a35f1e7 100644
--- a/docs/rehost-queue.md
+++ b/docs/rehost-queue.md
@@ -821,6 +821,13 @@ Working rule:
     `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
+    live auxiliary pool `0x0062b2fc` for the first exact `[entry+0x04]` match. So the
+    `0x005f3c6c/0x005f3c80` pair is no longer an anonymous bank byte table; it is the stock
+    style-family-to-combined-name resolver that sits immediately below the remaining Tier-2 source
+    selection frontier.
     The direct `+0xba/+0xbb` writer census is narrower now too. The obvious newly surfaced stores
     at `0x004ecd42/0x004ecdaa` and `0x004ed5d5/0x004ed625` are only shell-side portrait/string
     refresh helpers: they walk a separate id-keyed collection through `0x0053f830`, free and