diff --git a/persistent-memory.md b/persistent-memory.md
index 2e03b42..26baae0 100644
--- a/persistent-memory.md
+++ b/persistent-memory.md
@@ -158,10 +158,20 @@ below is a live commitment or a known-open risk._
   941 MiB/s ran at 1.4 MiB/s with the link up and pbs-ana answering in 11 ms.
   Nightly 21:00, `all 1`. Worth its own investigation.
 
-- **ledger-dev asked about the Ledger→SVOS rename** (gitea repo rename cost, and
-  moving `nh3-dev/development/ledger/env.sh` in the vault — the `secret` CLI has no
-  rename, so it is re-put + delete). **Unanswered, no deadline**, nothing moves until
-  the operator fixes the strings.
+- **Ledger→SVOS rename: vault side DONE, gitea side is ledger-dev's to execute.**
+  Name settled as `svos`, `~/development/ledger` → `~/development/svos`. Vault moved
+  2026-09-05 (`secret` has no rename, so re-put + `rm`): stored
+  `nh3-dev/development/svos/env.sh` (sha 7253633d4155, verified on read-back),
+  retired `nh3-dev/development/ledger/env.sh` (sha feb418634e10, id
+  3a2af37c-c5aa-4f46-9178-f4fb6008a753) — `secret rm` is a SOFT delete to trash, so
+  it is recoverable. ⚠ The two shas differ: the vaulted copy was a 2026-08-11
+  snapshot and the live file had drifted un-vaulted since. **The vault goes stale
+  unless `secret backfill` is re-run.** Gitea `corviduo/ledger` (id 70) NOT renamed —
+  their repo, their call; answered that 1.26.1 writes a `repo_redirect` on a
+  same-org repo rename (upstream #807), that org/user renames do NOT redirect
+  (#9531), that the redirect dies if anything re-creates the old path, and that the
+  repo and org both carry 0 webhooks. Handle `ledger-dev` → `svos-dev` is an
+  operator action at the post office.
 
 - **Open commitment to vastblue-dev:** a dedicated CI runner, gated on their first
   client-premises release cut (U10, unscheduled). Ping expected when U10 is scheduled.