rrt/docs/rehost-queue/tier2-candidate-row-families-2026-04-21.md

Tier2 Candidate Row Families (2026-04-21)

This note preserves the concrete row-family evidence behind the current Tier-2 queue head, so the short queue can stay focused on the owner question rather than restating export details.

Checked Export

• artifacts/exports/rt3-1.06/candidate-table-named-runs.json
• artifacts/exports/rt3-1.06/candidate-table-header-clusters.json

The export now keeps the row-family split explicit instead of burying it only inside per-map samples:

• files_with_port01_11_run_at_45_55_count = 37
• files_with_warehouse01_11_run_at_56_66_count = 37
• port00_warehouse00_row_pair_map_counts
  • 35/43 -> 30
  • 10/18 -> 7
• numbered_port_warehouse_trailer_family_map_counts
  • 0x00000001 -> 28
  • 0x00000000 -> 9
• row_pair_and_numbered_trailer_family_map_counts
  • 35/43 :: 0x00000001 -> 25
  • 35/43 :: 0x00000000 -> 5
  • 10/18 :: 0x00000000 -> 4
  • 10/18 :: 0x00000001 -> 3
• candidate-table-header-clusters.json
  • 0x00000000 / 0x00000000 -> 27
  • 0xcdcdcdcd / 0xcdcdcdcd -> 9
  • 0x10000000 / 0x00009000 -> 1

Off-Row Carrier Maps

The earlier 10/18 family is narrow and fully enumerated in the checked export:

• Crossing the Alps.gmp
• East Coast, USA.gmp
• Germany.gmp
• Go West!.gmp
• Rhodes Unfinished.gmp
• State of Germany.gmp
• War Effort.gmp

Everything else in the current probe-bearing corpus keeps the 35/43 Port00 / Warehouse00 pair while still preserving the fixed numbered runs at 45..55 and 56..66.

Header Clusters

The checked header-cluster export keeps the root scan bounded too:

• only 3 stable header families exist across the 37 probe-bearing maps
• the dominant family is 0x00000000 / 0x00000000 on 27 maps
• the secondary family is 0xcdcdcdcd / 0xcdcdcdcd on 9 maps
• Alternate USA.gmp is the lone 0x10000000 / 0x00009000 outlier

So the candidate-table header side is no longer an unbounded per-map surface either.

Header / Row / Trailer Crossover

The header-cluster export and named-run export now join cleanly enough to keep one more matrix explicit:

• 0x00000000 / 0x00000000 :: 35/43 :: 0x00000001 -> 19
• 0x00000000 / 0x00000000 :: 35/43 :: 0x00000000 -> 2
• 0x00000000 / 0x00000000 :: 10/18 :: 0x00000001 -> 2
• 0x00000000 / 0x00000000 :: 10/18 :: 0x00000000 -> 4
• 0xcdcdcdcd / 0xcdcdcdcd :: 35/43 :: 0x00000001 -> 5
• 0xcdcdcdcd / 0xcdcdcdcd :: 35/43 :: 0x00000000 -> 3
• 0xcdcdcdcd / 0xcdcdcdcd :: 10/18 :: 0x00000001 -> 1
• 0x10000000 / 0x00009000 :: 35/43 :: 0x00000001 -> 1

That keeps the mixed families concrete:

• the off-row 10/18 subset is mostly the dominant 0x00000000 / 0x00000000 header family, but it keeps one 0xcdcdcdcd / 0xcdcdcdcd outlier
• the ordinary-row 35/43 :: 0x00000000 subset is mixed across both main header families
• Alternate USA.gmp stays the lone 0x10000000 / 0x00009000 outlier and still lands on the ordinary 35/43 :: 0x00000001 side

So the row/trailer split still does not collapse to one header family either.

Crossover Reading

The new crossover field keeps the row-family and trailer-family interaction explicit too:

• the dominant family is still the ordinary 35/43 :: 0x00000001 case on 25 maps
• the off-row 10/18 family stays mixed, splitting 4 maps on trailer 0x00000000 and 3 maps on trailer 0x00000001
• the ordinary 35/43 family is mixed too, with a smaller 5-map 0x00000000 subset

So the row shift and numbered trailer split do not collapse to one underlying map family.

Mixed Carrier Sets

The checked crossover paths keep the mixed subfamilies concrete too:

• off-row 10/18 :: 0x00000001
  • Crossing the Alps.gmp
  • Go West!.gmp
  • Rhodes Unfinished.gmp
• off-row 10/18 :: 0x00000000
  • East Coast, USA.gmp
  • Germany.gmp
  • State of Germany.gmp
  • War Effort.gmp
• ordinary-row 35/43 :: 0x00000000
  • Britain.gmp
  • British Isles.gmp
  • Greenland Growing.gmp
  • Ireland.gmp
  • Spanish Mainline.gmp

So the 0x00000000 trailer lane is not merely “the off-row 10/18 family.” It also survives on one smaller ordinary-row 35/43 subset.

Immediate Reading

This keeps the Tier-2 frontier narrower than a generic “candidate table varies by scenario” claim:

• the Port01..11 / Warehouse01..11 numbered families are structurally fixed across all 37 probe-bearing maps
• only the 00 pair moves, and it does so in one small 7-map family
• the numbered trailer split stays mixed across both row-pair families instead of collapsing to the off-row subset
• the row/trailer split stays mixed across both main header families too, instead of collapsing to one header word pair
• so the next owner question is still the earlier seed or projection seam that feeds nonzero [candidate+0xba/+0xbb] into 0x00412d70, not the mere existence of the stable named rows or one fixed header family by itself