diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md
index 34f7adb..7d445be 100644
--- a/docs/CURRENT-STATE.md
+++ b/docs/CURRENT-STATE.md
@@ -2013,6 +2013,24 @@
   at `life: dead`** -- that moved it BACK to `dying` and re-armed the undertaker loop. It
   did not help and it changed state. Both are now written into Path M as explicit
   prohibitions.
+  **>>> THE v4 VIP REVERT IS EXECUTED AND KEYSTONE'S `Invalid vips` IS CLEARED. <<<** (2026-08-03,
+  operator: *"Yes, drop the v6 problem legs"*.) Done via the RENDER pipeline, not a hand-edit:
+  `render/values/vr1-dc0-vips.yaml` `family: dual -> v4` (the GUA v6 block RETAINED as the D-141
+  reserved record, with an in-file note on how to flip it back); re-rendered to a v4-only overlay
+  (13 v4 legs, 0 v6); gates `render-drift` 4/4, `provider-bundle-check` PASS, repo-lint 0 fail;
+  overlay re-staged to the rack (`cf42b937`, both ends). Live model: the 11 API charms carrying a
+  v6 VIP leg (keystone/barbican/cinder/glance/magnum/neutron-api/nova-cloud-controller/octavia/
+  openstack-dashboard/placement/ceph-radosgw) each `juju config <app> vip=<v4 triple>`, values
+  driven FROM the staged overlay so model and overlay agree; all rc=0, and a re-read confirms
+  ZERO apps still carry a `2602:` leg. **keystone moved from `Invalid vips: [2602:...]` to
+  `(config-changed) PO: Incomplete relations: database`** -- the VIP rejection is gone and it is
+  re-converging on normal relation-settling. **MODEL STATE: 8/9 machines started, 6 units active,
+  ZERO in error**; every `blocked` unit is the expected pre-vault-init set (keystone awaiting the
+  mysql cluster, mysql clustering, `vault/0` needs-init, `octavia` awaiting-configure,
+  `ceph-rbd-mirror` missing its cross-DC peer, `designate` nameservers = Stage 7). **The node
+  planes stay dual-stack** -- only the container-VIP family reverted, per D-141. NEXT: settle to
+  the full pre-vault-init end state, then Step 5 (vault bring-up).
+
   **>>> D-141 ADOPTED 2026-08-03 (GA-R5): IPAM ALLOCATIONS ARE DUAL-STACK, STATUS-DISTINGUISHED
   -- v4 `active`, v6 `reserved` UNTIL THE STACK IS CAPABLE. <<<** Operator, exact utterance:
   *"Yes, but you should expand on the record. It should be noted that when creating future ipam