Classify tier2 kind-8 recipe signatures

artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md

@@ -0,0 +1,92 @@
+# Runtime Effect Kind-8 Tier2 Recipe Signature Note
+
+This note records a direct fixed-layout scan over all 41 bundled `rt3_105/maps/*.gmp` files,
+using the already-grounded recipe-book payload layout:
+
+- recipe-book root `0x0fe7`
+- book stride `0x4e1`
+- line root `0x3f1`
+- line stride `0x30`
+- imported mode dword at `line+0x00`
+- supplied token dword at `line+0x08`
+- demanded token dword at `line+0x1c`
+
+The goal is narrower than general recipe-book comparison:
+
+- classify the imported nonzero-mode footprint that can actually feed `0x00435630`
+- then check whether `Louisiana.gmp` is unique on that runtime-relevant surface
+
+## Mode-signature groups
+
+Across the 41-map corpus there are 23 distinct nonzero-mode path signatures.
+
+Largest groups:
+
+- 7 maps: no nonzero mode rows at all
+  - `East of Mississippi.gmp`
+  - `Greenland Growing.gmp`
+  - `Mexico.gmp`
+  - `Pacific Coastal.gmp`
+  - `Russia.gmp`
+  - `Southern Pacific.gmp`
+  - `War Effort.gmp`
+- 4 maps: `book00.line02`, `book01.line02`, `book02.line02`
+  - `Argentina Opens Up.gmp`
+  - `Central Pacific.gmp`
+  - `Eastern Canada.gmp`
+  - `Rhodes Unfinished.gmp`
+- 3 maps: `book02.line02`
+  - `Crossing the Alps.gmp`
+  - `Germantown.gmp`
+  - `Mississippi Valley.gmp`
+- 3 maps: `book00.line02`, `book01.line02`, `book02.line02`, `book03.line02`
+  - `East Coast, USA.gmp`
+  - `Go West!.gmp`
+  - `Ireland.gmp`
+- 3 maps: `book00.line02`
+  - `Britain.gmp`
+  - `Louisiana.gmp`
+  - `South East USA.gmp`
+
+So `Louisiana.gmp` is not unique at the coarse nonzero-mode-path level. It belongs to a small
+three-map family whose imported mode footprint is just one active line:
+
+- `book00.line02`
+
+## Exact imported signature
+
+When the token lanes are included, `Louisiana.gmp` does become unique in the 41-map corpus.
+
+Current exact imported signature:
+
+- nonzero mode rows:
+  - `book00.line02 = 0x00080000`
+- nonzero supplied token rows:
+  - `book00.line02 = 0x00004080`
+- nonzero demanded token rows:
+  - `book00.line00 = 0x00010000`
+  - `book00.line01 = 0x6c430000`
+
+Exact signature group size:
+
+- `1`
+
+Current exact group:
+
+- `Louisiana.gmp`
+
+## Current implication
+
+This narrows the Tier 2 recipe/runtime question again:
+
+- the decisive runtime-relevant surface is not the broad recipe-book family and not only the raw
+  setup-core tuple
+- `Louisiana.gmp` is rare but not singular on the imported nonzero-mode-path shape
+- it becomes unique only when the token-bearing rows around that minimal imported shape are
+  included
+
+So the next concrete comparison question is:
+
+- whether the two mode-shape peers `Britain.gmp` and `South East USA.gmp` diverge from
+  `Louisiana.gmp` strongly enough on token lanes and later Tier 2/runtime-facing state to explain
+  why only `Louisiana.gmp` currently lines up with the shipped `Add Building Warehouse05` path

docs/rehost-queue.md

@@ -614,7 +614,15 @@ Working rule:
     still stays zero across the checked recipe-book surface, and the same-header peer
     `Argentina Opens Up.gmp` keeps additional nonzero `book01/book02` content. So the next pass
     should bias toward finding other maps that share Louisiana's minimal imported nonzero
-    recipe-runtime set, rather than reopening broader setup-core or header-class hypotheses.
+    recipe-runtime set, rather than reopening broader setup-core or header-class hypotheses. That
+    scan is now checked in at
+    `artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-recipe-signature-note.md`:
+    across all 41 bundled `rt3_105` maps there are 23 nonzero-mode path signatures, and
+    `Louisiana.gmp` sits in a small three-map `book00.line02`-only mode family with
+    `Britain.gmp` and `South East USA.gmp`. But `Louisiana.gmp` becomes unique again once the
+    supplied and demanded token lanes are included. That makes the next concrete Tier 2 recipe pass
+    smaller: compare `Louisiana.gmp` directly against `Britain.gmp` and `South East USA.gmp` on
+    the token-bearing minimal imported set and then on any downstream runtime-facing differences.
     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: