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

# 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

## Mode-shape peer split

Direct fixed-layout comparison of the two `book00.line02` mode-shape peers now answers that first
half positively.

`Louisiana.gmp` keeps:

- `book00.line00`: demanded token `0x00010000`
- `book00.line01`: demanded token `0x6c430000`
- `book00.line02`: mode `0x00080000`, supplied token `0x00004080`

`Britain.gmp` diverges strongly:

- `book00.line01`: supplied token `0x00210000`, demanded token `0x72490000`
- `book00.line02`: mode `0x00120000`, supplied token `0x00003f80`
- extra zero-mode supplied rows at `book01.line01` and `book02.line01`

`South East USA.gmp` stays structurally closer but still diverges on the exact imported values:

- `book00.line00`: demanded token `0x00010000` matches
- `book00.line01`: demanded token `0x6c410000` differs from `Louisiana`'s `0x6c430000`
- `book00.line02`: mode `0x00010000` and supplied token `0x00004000` both differ from
  `Louisiana`'s `0x00080000 / 0x00004080`
- extra zero-mode supplied row at `book01.line01`

So the current corpus split is:

- `book00.line02`-only mode shape is a three-map family
- but `Louisiana.gmp` still has a distinct exact token-bearing signature even inside that family

## Checked downstream split

One immediate runtime-facing comparison is now grounded too:

- `runtime inspect-smp Britain.gmp`
- `runtime inspect-smp "South East USA.gmp"`

Both mode-shape peers still expose in-file candidate names such as `Port01` and `Warehouse05`, but
neither currently exposes any add-building dispatch-strip trigger rows:

- `add_building_dispatch_strip_records_with_trigger_kind = 0`
- `trigger_kinds_present = []`

So the current checked downstream split is sharper than a generic “same mode-shape family” read:

- `Britain.gmp` and `South East USA.gmp` share the coarse `book00.line02` mode footprint with
  `Louisiana.gmp`
- both also still carry the relevant candidate names in-file
- but neither currently reaches the shipped add-building dispatch-strip family that
  `Louisiana.gmp` does

That makes `Louisiana.gmp` the first checked member of that mode-shape family whose distinct exact
token-bearing `book00` signature also lines up with the add-building runtime path.

## Compact-family split inside the checked peers

The current runtime-facing split is not just “dispatch rows present versus absent.” The checked
peer maps also diverge inside the broader `nondirect-ge1e-h0001-0007` compact family:

- `Louisiana.gmp` reaches the checked add-building strip on
  - `nondirect-ge1e-h0001-0007-0000-5200-0200-p0000-0000-0000-ffff :: [7:0]`
  - with decoded label `Add Building Warehouse05`
- `Britain.gmp` keeps `nondirect-ge1e-h0001-0007-0000-4a00-0200-p0000-0000-0000-ffff`
  but no add-building dispatch-strip rows
- `South East USA.gmp` keeps several other `0007` mids
  - `...-3100-...`
  - `...-3500-...`
  - `...-3800-...`
  - `...-3b00-...`
  - `...-4200-...`
  and again no add-building dispatch-strip rows

So the current checked peer split is now:

- same coarse mode-shape family
- different exact token-bearing `book00` signature
- different `h0001-0007` mid-word family at runtime
- only `Louisiana.gmp` currently reaches the `5200 :: [7:0]` add-building strip

## Minimal imported-cluster split

The next corpus pass sharpens that again.

`Louisiana.gmp` is not the only map that reuses pieces of the apparent `lC / 0x00080000 /
0x00004080` cluster:

- `Ireland.gmp` carries
  - `book02.line01 = demanded 0x6c430000`
  - `book02.line02 = mode 0x00080000, supplied 0x00004080`
  - plus additional active rows in `book00`, `book01`, and `book03`
- `Eastern China.gmp` carries
  - `book02.line00 = demanded 0x00010000`
  - `book02.line01 = demanded 0x6c430000`
  - `book02.line02 = mode 0x00080000, supplied 0x00004080`
  - plus additional active rows in `book00` and `book01`

But the exact three-row cluster as the *entire* nonzero imported recipe surface is unique to
`Louisiana.gmp` in the 41-map corpus:

- `book00.line00 = demanded 0x00010000`
- `book00.line01 = demanded 0x6c430000`
- `book00.line02 = mode 0x00080000, supplied 0x00004080`

No other bundled map keeps exactly that three-line imported set and nothing else.

That matters on the runtime side too:

- `Ireland.gmp` still has no add-building dispatch-strip rows at all
  - `add_building_dispatch_strip_records_missing_trigger_kind = 0`
  - checked `0007` family stays on `...-6300-...`
- `Eastern China.gmp` also has no add-building dispatch-strip rows at all
  - `add_building_dispatch_strip_records_missing_trigger_kind = 0`
  - checked `0007` mids stay on other families such as `...-a100-...`, `...-a600-...`,
    `...-b100-...`, `...-b700-...`, `...-cf00-...`, and `...-d100-...`

So the stronger current read is no longer just “the `0x00080000 / 0x00004080` triplet exists
somewhere.” It is:

- `Louisiana.gmp` is the only bundled map whose whole imported nonzero recipe surface collapses to
  that exact three-row cluster
- maps that merely reuse pieces of the cluster do not currently reach the same add-building strip

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