diff --git a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md
index 0573379..b7356b8 100644
--- a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md
+++ b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md
@@ -218,3 +218,81 @@ That makes the next Tier 2 question smaller again:
 - whether the `5200 :: [7:0]` add-building strip is tied to that minimal imported-cluster shape
   specifically, rather than to the presence of any one of its component token rows in a broader
   recipe profile
+
+## Single-import-row family
+
+The broader 41-map corpus narrows the same point one step further.
+
+There are multiple bundled maps whose imported runtime side still materializes only one nonzero
+recipe row:
+
+- `Britain.gmp`
+- `Crossing the Alps.gmp`
+- `France.gmp`
+- `Germantown.gmp`
+- `Louisiana.gmp`
+- `Mississippi Valley.gmp`
+- `South East USA.gmp`
+- `Third Republic.gmp`
+
+But `Louisiana.gmp` is the narrowest member of that family.
+
+Among those eight single-import maps:
+
+- `Louisiana.gmp` is the only one with just **two** remaining mode-zero token rows
+  - `book00.line00 = demanded 0x00010000`
+  - `book00.line01 = demanded 0x6c430000`
+  - `book00.line02 = mode 0x00080000, supplied 0x00004080`
+- every other checked single-import map keeps **three or four** additional token-bearing rows
+
+And the runtime split stays aligned with that narrower read:
+
+- `Louisiana.gmp` is currently the only checked single-import map that reaches an add-building
+  dispatch-strip row at all
+  - `nondirect-ge1e-h0001-0007-0000-5200-0200-p0000-0000-0000-ffff :: [7:0]`
+  - `Add Building Warehouse05`
+- `Britain.gmp` and `South East USA.gmp`, the nearest earlier mode-shape peers, do not
+- `Ireland.gmp` and `Eastern China.gmp`, which reuse the `0x00080000 / 0x00004080` triplet inside
+  broader profiles, also do not
+
+So the next checked discriminator is narrower again than “single imported row” by itself:
+
+- the current strongest recipe-side predictor is the exact **minimal** imported cluster
+  (`two demand rows + one imported row`) rather than either
+  - the coarse `book00.line02` mode shape
+  - the presence of one `0x00080000 / 0x00004080` imported row somewhere
+  - or the broader “only one imported row exists” family
+
+## Importer-side boundary
+
+One more direct `inspect-smp` check now trims the next step again.
+
+At the first importer bridge itself, `Louisiana.gmp` does **not** separate cleanly from the nearest
+single-import peers:
+
+- `Louisiana.gmp`
+  - exactly one line with `imports_to_runtime_descriptor = true`
+  - that line is `runtime_import_branch_kind = nonzero-supply-branch`
+- `Britain.gmp`
+  - also exactly one imported line
+  - also `runtime_import_branch_kind = nonzero-supply-branch`
+- `South East USA.gmp`
+  - also exactly one imported line
+  - also `runtime_import_branch_kind = nonzero-supply-branch`
+
+By contrast, the broader reuse case stays broader at the importer too:
+
+- `Ireland.gmp` imports four nonzero supply-branch rows
+
+So the current checked boundary is now explicit:
+
+- the exact minimal `two demand rows + one imported row` cluster still narrows the recipe-side
+  frontier strongly
+- but the first importer bridge does not by itself explain the `5200 :: [7:0]` split among the
+  nearest single-import peers
+
+That shifts the next Tier 2 question one layer later:
+
+- the likely differentiator now lives after the first `0x00435630` import step, in the later
+  `0x00412d70 / 0x00412fb0 / 0x00412c10` runtime-record and named-availability interaction rather
+  than in the coarse importer branch-kind classification alone
diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md
index 2648001..c67f125 100644
--- a/docs/rehost-queue.md
+++ b/docs/rehost-queue.md
@@ -643,6 +643,23 @@ Working rule:
     test whether the shipped `5200 :: [7:0]` `Add Building Warehouse05` strip is tied to that
     minimal imported-cluster shape specifically, rather than to the mere presence of one reused
     `0x00080000 / 0x00004080` triplet inside a broader recipe profile.
+  - the same split is tighter even inside the broader “single imported row” family:
+    eight bundled maps currently materialize only one nonzero recipe row, but `Louisiana.gmp` is
+    the only one whose supporting token surface is just two additional demand rows instead of three
+    or four extra token-bearing rows. So the next checked discriminator is now narrower than
+    “single imported row” too:
+    test whether the `5200 :: [7:0]` add-building strip tracks that exact two-demand-plus-one-
+    imported minimal cluster, not just the existence of one imported row or one reused
+    `0x00080000 / 0x00004080` triplet.
+  - the importer-side boundary is tighter now too:
+    direct `inspect-smp` checks show `Louisiana.gmp`, `Britain.gmp`, and `South East USA.gmp` all
+    collapse to the same first importer shape of exactly one
+    `imports_to_runtime_descriptor = true` line on `nonzero-supply-branch`, while the broader
+    reuse case `Ireland.gmp` imports four such rows. So the next queue head is no longer
+    “prove the first importer branch differs”; it is:
+    recover the later runtime-record / named-availability consequence under
+    `0x00412d70 / 0x00412fb0 / 0x00412c10` that makes the minimal cluster land on
+    `5200 :: [7:0]` only in `Louisiana.gmp`.
     kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes
     `[event+0x7ef]` itself or a still-later owner does.
   - two explicit trigger-kind materializations are now grounded inside that retagger: