diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md
index 70fabf1..bf2f25b 100644
--- a/docs/CURRENT-STATE.md
+++ b/docs/CURRENT-STATE.md
@@ -112,9 +112,18 @@
   pod is IMPOSSIBLE with snap MAAS. **This refutes the mechanism stated in
   D-123 Model B and in `modules/maas-vm-host`'s header** (intent survives,
   mechanism does not); both need an amendment once the replacement is ruled.
-  Measured-feasible replacement: `qemu+ssh://jessea123@172.31.0.2/system`
-  (snap ships ssh; the rack user is in `libvirt`), needing a key the snap
-  can read. Session changelog item 15. THEN: netem (step E).
+  The `qemu+ssh` replacement was then wired with an operator-ruled DEDICATED
+  key and PROVEN reachable from both snaps -- but the pod apply failed again,
+  finally on `domblkinfo ... missing storage backend for 'volume' storage`,
+  REPRODUCED LOCALLY on the rack with an active pool. So **MAAS virsh pods
+  are incompatible with `modules/node-vm`'s pool+volume disk refs**; the pod
+  would require converting node-vm to file-path disks and re-applying all
+  nine domains. **The pod is however UNNECESSARY** -- its D-103 job was
+  DISCOVERY, already done via PXE -- and per-machine `power_type=virsh` is
+  MEASURED WORKING (`query-power-state` -> `{"state":"off"}` on the canary),
+  which is also the Roosevelt shape (per-node IPMI). **AWAITING RULING**
+  between per-machine power and the node-vm disk conversion; session
+  changelog items 15-16. THEN: netem (step E).
 - The grounding audit is COMPLETE and EXITED (2026-07-19): Phases 1-6 all
   closed (charter `148dcef`; rulings `docs/audit/ga-rulings.md`; the
   Phase-5 sweep ran as six operator-gated batches in one session; exit