diff --git a/docs/re/BACKLOG.md b/docs/re/BACKLOG.md
index 39b1598..1a739db 100644
--- a/docs/re/BACKLOG.md
+++ b/docs/re/BACKLOG.md
@@ -332,8 +332,16 @@ search cannot find a *schedule*.
   and `Acropolis` all come out at exactly **2×** `sum(n)`. An undershoot is
   explainable by phases; an overshoot is not. `n` back to ❔. Formation slot count
   also rejected (630 turret slots vs 214 live). ✅ Side result: `FormationSet`
-  `FrameCount` = slot count. ❔ **Open: the 116 roster records and the 298 live
-  entities are different structures; the expansion rule between them is unknown.**
+  `FrameCount` = slot count. 🔴 **A direct pointer link between them is REFUTED**
+  (2026-08-24, [`roster-to-craft-link.md`](roster-to-craft-link.md)): 0/116
+  roster records point at a craft base and 0/300 craft point at a roster base.
+  They sit in distinct regions (`0xbc372c00`–`0xbc9bc720` vs
+  `0xbdb2fd80`–`0xbdcd1d80`). Craft count varies run to run (296/298/300), so it
+  must only be compared WITHIN a run. ❔ **Still open: the expansion rule.** Four
+  candidates now dead — `Count`, `n`, formation slots, head pointers.
+  **Next test:** for the 5101 craft words pointing into the roster VA *range*,
+  plot the distance to the nearest roster-record base; a spike at one delta means
+  a link at `base+X`, a flat distribution kills the thread.
 * 🟡 **COMPETING MODEL (user, 2026-08-24): waves are event-gated, not
   clock-driven** — released by kills/objectives rather than at a fixed time, with
   the route's start time being a post-trigger delay. Fits the evidence better: