Preserve Tier2 candidate row family evidence

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

@@ -0,0 +1,46 @@
+# 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`
+
+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`
+
+## 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`.
+
+## 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 is independent of the row-pair split, 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 themselves