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.