diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md
index 84d39a0..e0c7c9e 100644
--- a/docs/CURRENT-STATE.md
+++ b/docs/CURRENT-STATE.md
@@ -2013,6 +2013,15 @@
   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.
+  **>>> PRE-VAULT-INIT END STATE REACHED; VAULT PREFLIGHT PASSES `PROCEED` 2026-08-03. <<<**
+  After the stall fix, the model converged: `scripts/phase-02-vault-preflight.sh vr1-dc0`
+  (staged + sha256-verified on the rack, `90910dfb`) reports **PROCEED** -- mysql cluster 3/3
+  active/ONLINE with exactly 1 R/W, vault/0 fresh (blocked "needs initialization"), and the
+  census clean: **67 units, workload-error=0, agent-error(hook)=0**. Step 5 (`phase-02` vault
+  bring-up) Step 2.1 is the IRREVERSIBLE, SECRET-HANDLING, OPERATOR-ONLY init one-shot
+  (guard-hook blocked for the agent) -- PRESENTED to the operator, awaiting their run. The
+  remaining `blocked` tail is expected (ceph-rbd-mirror cross-DC, designate Stage 7, octavia
+  awaiting-configure, vault needs-init); zero faults.
   **>>> DEPLOY STALL ROOT-CAUSED AND CLEARED 2026-08-03: cloud-init `apt-get update` WEDGED ON
   THREE UNITS FOR ~13h. <<<** (Operator approved the fix: *"Kill the stuck apt-get update on
   the three units"*.) Symptom: machines all MAAS-`Deployed` but juju agents `pending` on