diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md
index a6a8154..0db6ccf 100644
--- a/docs/CURRENT-STATE.md
+++ b/docs/CURRENT-STATE.md
@@ -521,13 +521,13 @@
    (monthly-review window trigger; patch-only controller jumps; order;
    acceptable single-controller risk) as amended by the confirmed backup
    posture (:1677).
-5. D-129 -- three OPEN sub-decisions (OPEN / PARTIALLY RULED; (i) RULED
-   2026-07-21: COS scrapes the edge, in-scope per-DC -- status line in
-   design-decisions.md is the authority): (ii) `os-frr` dynamic routing
-   -- Roosevelt question? (iii) consolidate the Tailscale subnet-router
-   onto the edge vs keep D-107 as-is? (iv) does the edge anchor site
-   NTP? Plus the operator-gated live install of the ruled VR1 profile
-   (`scripts/opnsense-plugins.sh apply vr1-edge`).
+5. D-129 -- two OPEN sub-decisions (OPEN / PARTIALLY RULED; (i) RULED
+   2026-07-21: COS scrapes the edge, in-scope per-DC; (ii) RULED
+   2026-07-21: os-frr pinned to Roosevelt design time -- status line in
+   design-decisions.md is the authority): (iii) consolidate the
+   Tailscale subnet-router onto the edge vs keep D-107 as-is? (iv) does
+   the edge anchor site NTP? Plus the operator-gated live install of
+   the ruled VR1 profile (`scripts/opnsense-plugins.sh apply vr1-edge`).
 6. Audit Phase 4 rulings: GA-R1..GA-R6 individually, plus the legal
    stage-status vocabulary A/B (GA-F10 operator note) -- each gated, one
    ruling per exchange.
diff --git a/docs/changelog-20260721-tenant-review-pin.md b/docs/changelog-20260721-tenant-review-pin.md
index f9d92e3..2397f02 100644
--- a/docs/changelog-20260721-tenant-review-pin.md
+++ b/docs/changelog-20260721-tenant-review-pin.md
@@ -91,3 +91,12 @@
 - Coupled same-commit: CURRENT-STATE section 8 item 5 (four -> three open
   subs) + ledger machine-block D-129 line.
 - **Revert:** git revert this commit (records only).
+
+## 7. D-129 sub-decision (ii) RULED: os-frr pinned to Roosevelt design time
+
+- Presented per GA-R5; operator selection, exact utterance: "Pin to
+  Roosevelt design (Recommended)". VR1 stays static (D-124/D-125); the
+  dynamic-routing question rules at Roosevelt inter-DC network design
+  alongside the D-100 link spec + D-132 topology. Status line updated;
+  CURRENT-STATE item 5 + ledger D-129 line coupled same-commit.
+- **Revert:** git revert this commit (records only).
diff --git a/docs/design-decisions.md b/docs/design-decisions.md
index 8d83b46..2682397 100644
--- a/docs/design-decisions.md
+++ b/docs/design-decisions.md
@@ -4065,7 +4065,12 @@
 ## D-129: OPNsense edge plugin / add-on base profile (VR1 -> Roosevelt) [OPS]
 
 **Status:** OPEN (PARTIALLY RULED 2026-07-18; sub-decision (i) RULED 2026-07-21) -- profile
-adopted, THREE sub-decisions still OPEN ((ii)-(iv)). Sub-decision (i) RULED 2026-07-21 (GA-R5):
+adopted, TWO sub-decisions still OPEN ((iii)-(iv)). Sub-decision (ii) RULED 2026-07-21 (GA-R5):
+question as presented = "how do we dispatch the os-frr dynamic-routing question for the edge?";
+operator selection, exact utterance: "Pin to Roosevelt design (Recommended)". VR1 stays static
+(D-124/D-125, already ruled); os-frr is PINNED to Roosevelt inter-DC network design time, to be
+ruled alongside the D-100 link spec and the D-132 topology questions (the routing answer depends
+on both). Trigger: Roosevelt network design session -- grep this entry + D-132 there. Sub-decision (i) RULED 2026-07-21 (GA-R5):
 question as presented = "is the boundary edge (OPNsense) in-scope for COS scraping, within
 D-105's per-DC observability model?"; operator selection, exact utterance: "In-scope, per-DC
 (Recommended)". Each DC's COS scrapes its OWN edge; the Step-10 pin (os-node-exporter + API
@@ -4079,8 +4084,9 @@
 (auto-mode classifier blocked the agent's POST -- cloud mutations stay gated), verification pending. The
 rest is PINNED to its deployment step (mapping below). **FOUR sub-decisions remain OPEN** (a one-line
 directive does not rule these -- they were flagged as decisions, not adds): (i) COS-scrapes-the-edge
-scope (RULED 2026-07-21, see Status), (ii) `os-frr` dynamic routing, (iii) `os-tailscale`
-subnet-router consolidation, (iv) edge-as-site-NTP.
+scope (RULED 2026-07-21, see Status), (ii) `os-frr` dynamic routing (RULED 2026-07-21: pinned
+to Roosevelt design, see Status), (iii) `os-tailscale` subnet-router consolidation, (iv)
+edge-as-site-NTP.
 
 **Pinned at deployment steps (the "engineering for the rest").**
 - **VR1 edge base profile = {`os-qemu-guest-agent`, `os-iperf`}** -> applied at DC-edge bring-up.
diff --git a/docs/session-ledger.md b/docs/session-ledger.md
index ff62eb3..902a36d 100644
--- a/docs/session-ledger.md
+++ b/docs/session-ledger.md
@@ -34,8 +34,8 @@
 
 - **PROPOSED / OPEN decisions:** D-068 (Vault substrate hardening, Roosevelt), D-071 (routine
   update cadence + Juju controller patch policy), D-129 (OPNsense edge plugin/add-on base
-  profile -- OPEN / partially ruled, three sub-decisions; (i) COS-scrapes-edge ruled in-scope
-  per-DC 2026-07-21), D-131 (node-facing DNS strategy for
+  profile -- OPEN / partially ruled, two sub-decisions ((iii)-(iv)); (i) COS-scrapes-edge ruled
+  in-scope per-DC + (ii) os-frr pinned to Roosevelt design, both 2026-07-21), D-131 (node-facing DNS strategy for
   rack-only controllers -- PARTIALLY RULED: sub-1 ruled + delivered 2026-07-21, sub-2 ruled
   2026-07-21 (metal-admin only), sub-3 resolved 2026-07-21 (no defect), sub-4 open + pinned
   DNS architectural review;