diff --git a/persistent-memory.md b/persistent-memory.md
index 2dfe07a..1466c40 100644
--- a/persistent-memory.md
+++ b/persistent-memory.md
@@ -252,9 +252,14 @@ below is a live commitment or a known-open risk._
   rather than inferred from the 200: `ledger` disabled=True, `svos` untouched,
   deployment `/health` 200. **The rollback window is closed** — re-defining
   `ledger:miranda` is no longer possible. ledger-dev clears the staged
-  `worldtree-api-key-ledger-legacy` vault item on this confirmation. Remaining on
-  the arc: only the `ledger-dev` → `svos-dev` handle, which is the operator's at
-  the post office.
+  `worldtree-api-key-ledger-legacy` vault item on this confirmation. ledger-dev gated their
+  cleanup on observing a **401 from the old key**, not on my report of the
+  timestamp — the right instinct, and they deleted the staged legacy item
+  themselves (soft → trash, id a8038e5a-e2f6-4b77-bf17-99c9197d4b1f). Vault
+  verified from my side: exactly two svos items remain (`env.sh` 8a225c002072,
+  `worldtree-api-key` 23c10c9c7219) and no ledger-era item anywhere. Remaining on
+  the arc: only the `ledger-dev` → `svos-dev` handle (with `_SEED_RECORD_TO`
+  behind it) and a prose sweep — reversible work, theirs and the operator's.
 
 - **Original constraints on that mint** (recorded because the deletion ordering is
   a permanent trap, not a one-time step): string