diff --git a/docs/changelog-20260724-stage5-committee-fork1.md b/docs/changelog-20260724-stage5-committee-fork1.md
index 8b26750..157aaf3 100644
--- a/docs/changelog-20260724-stage5-committee-fork1.md
+++ b/docs/changelog-20260724-stage5-committee-fork1.md
@@ -254,6 +254,21 @@
 -> 8 hits, all driver/chart/CAPO, zero VIP-context.
 **Revert:** `git revert <commit>` -- text-only across four files, no behavioural effect.
 
+## Item 16 -- DOCFIX-202: buildout-scope section 5 demoted to a D-111 pointer
+
+**What:** `docs/dc-dc-netbox-buildout-scope.md` section 5 presented the per-DC v6 subcarve
+(sub-decision 1) as open/un-ratified at lines 5, 132, 138 -- contradicting the ratified
+pointer already present at line 146 ("RATIFIED as D-111 (2026-07-11)"). Demoted the three
+open-framing sites to acknowledge D-111 (ADOPTED); kept the reasoning below as history.
+**Why:** `## D-111` is ADOPTED 2026-07-11 and names this exact sub-decision; the stale open
+framing misled the Chat seat 2026-07-25 (it treated the subcarve as a blocking trust gate,
+withdrawn only after reading the register). Committee-confirmed the targets; the rest of
+section 5 has no other adopted-decision contradiction.
+**Verify:** `bash scripts/ledger-scan.sh` -- D-111 not under PROPOSED/OPEN; `grep -n
+"un-ratified\|candidate D-111" docs/dc-dc-netbox-buildout-scope.md` -- no hit presenting
+the subcarve as open.
+**Revert:** `git revert <commit>` -- single-file text change, no behavioural effect.
+
 ## Next (not done this session; gated)
 
 Commit+push this batch (GA-R5: rulings land before dependent work). Then, each
diff --git a/docs/dc-dc-netbox-buildout-scope.md b/docs/dc-dc-netbox-buildout-scope.md
index 0d0a419..235592d 100644
--- a/docs/dc-dc-netbox-buildout-scope.md
+++ b/docs/dc-dc-netbox-buildout-scope.md
@@ -2,7 +2,7 @@
 
 **Status:** planning/scope reference for the Code stream. NOT a decision record -- it
 consolidates ADOPTED decisions and flags the sub-decisions still needing operator ratification
-(candidate D-111+; assign via `ledger-scan` at adoption).
+(sub-decision 1 = the v6 subcarve, RATIFIED as D-111 on 2026-07-11; DOCFIX-202).
 **Authority order:** repo `design-decisions.md` (ADOPTED) > this doc > live NetBox (a
 reconciliation target, not a source) > design-exploration chats. NetBox is the IPAM apex
 (D-010, D-103) -- everything below it consumes it; it is never read back as a planning input.
@@ -129,13 +129,13 @@
 
 ---
 
-## 5. Sub-decisions requiring operator ratification (candidate D-111+)
+## 5. Sub-decisions (item 1 = v6 subcarve RATIFIED as D-111 2026-07-11 -- DOCFIX-202 demoted this from open; check the register before treating any item below as open)
 
 None of these block *reading* NetBox; they block *trusting the exact values written*. Each is a
 grep-before-assign D-NNN when ruled.
 
 1. **Per-plane subcarve (the big one).** `dc-dc-prefixes-import.py`'s ULA/GUA subdivision is the
-   script's OWN proposal, explicitly un-ratified: ULA = a `/56`-per-DC out of the org `/48` (dc1
+   script's OWN proposal, RATIFIED as D-111 (2026-07-11; DOCFIX-202 -- was mislabeled un-ratified): ULA = a `/56`-per-DC out of the org `/48` (dc1
    `::0/56`, dc2 `::1:00/56`), then a `/64` per ULA-bearing plane in fixed order; GUA =
    provider-public gets the whole `DC_GUA_PREFIX` as one `/64`. **Two conflicts to resolve:** (a)
    this does NOT use the deployed `NN` role mnemonic (provider at `NN=10`, etc.) -- decide whether