diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md
index f9db231..5bd9099 100644
--- a/docs/CURRENT-STATE.md
+++ b/docs/CURRENT-STATE.md
@@ -2474,7 +2474,26 @@
   D-058, which is SUPERSEDED by D-060 and REMAINS SO IN FULL** -- this ruling reinstates that one
   ROW'S VALUE under D-139's authority and revives nothing else. Verified FREE first: the apex
   holds `10.12.64.0/22` + `10.12.68.0/22` (vr1-dc1) and nothing in `10.12.60.0`-`10.12.63.255`;
-  dc0's MAAS holds none of it. **OPEN AND DELIBERATELY NOT INFERRED -- the per-DC v4 split.**
+  dc0's MAAS holds none of it. **^ THAT VALUE IS NOW SUPERSEDED -- SEE THE NEXT BLOCK.**
+  **>>> THE OOB PER-DC v4 SPLIT IS RULED 2026-08-01 (GA-R5), AND IT SUPERSEDES `10.12.60.0/22`.
+  Operator answer, exact utterance: "dc0 10.12.40.0/22, dc1 10.12.88.0/22 (Recommended)" <<<**,
+  given after asking for a recommendation matching the existing per-DC pattern. Derivation:
+  `### AMENDMENT 2026-08-01 (b)` in `docs/design-decisions.md`. **THE MEASURED PATTERN IS NOT THE
+  OBVIOUS ONE -- the dc0->dc1 offset is a CONSEQUENCE, not a rule.** dc0 is `4,8,12,16,[20-28
+  FREE],32,36`; dc1 is contiguous `64..84`; the offset runs `+60,+60,+60,+60,+48,+48` purely
+  because dc1 never reproduced dc0's historical gap. **dc0's 20-28 gap is UNUSABLE for a
+  symmetric pair, measured: `20+60=80` and `20+48=68` are BOTH allocated.** `40` and `88` are each
+  the next free `/22` after their own DC's highest plane, so both runs stay contiguous at the
+  `+48` offset storage and replication already use. `10.12.60.0/22` returns to the free pool and
+  D-058 stays superseded in full. **STATE: the v6 half is BUILT for dc0** (pushed at step 1);
+  **the v4 half is RULED AND NOT BUILT** -- neither `/22` exists in the apex or MAAS,
+  `d139-gua-carve.py` cannot create them (v6-prefixes-only by construction), and they gate
+  nothing in D-139 or the Stage-5 deploy. **PROCESS NOTE, owned: the ruling's design-decisions
+  half landed in `d47ef8c` WITHOUT this block**, because the editing step failed its own
+  assertion and the shell chain did not gate the commit on it -- the same masking as the
+  `| tail` red-lint push earlier this session. Corrected forward here rather than by rewriting
+  pushed history.
+  **^ SUPERSEDED TEXT, kept: "OPEN AND DELIBERATELY NOT INFERRED -- the per-DC v4 split."**
   `10.12.60.0/22` is ONE block and v4 is carved PER DC, with a mapping that is NOT a uniform
   offset (4->64/8->68/12->72/16->76 are +60; 32->80/36->84 are +48), so no rule can be derived.
   Whether the DCs split it into two `/23`s or dc1 takes a separate block is UNRULED. **The v6