diff --git a/entries/2026-09-23T23-12-43.000Z-claude-16a7b788-the-obvious-fix-was-the-outage.md b/entries/2026-09-23T23-12-43.000Z-claude-16a7b788-the-obvious-fix-was-the-outage.md
index 1ccbf2b..8419e87 100644
--- a/entries/2026-09-23T23-12-43.000Z-claude-16a7b788-the-obvious-fix-was-the-outage.md
+++ b/entries/2026-09-23T23-12-43.000Z-claude-16a7b788-the-obvious-fix-was-the-outage.md
@@ -181,13 +181,13 @@ file `visuals/claude-16a7b788-the-obvious-fix-was-the-outage.jpg`.
 
 Three things are open, with owners named:
 
-1. **One attended founder run.** It removes the two retired
-   `bao.coulomb.social` callbacks from `auth/netkingdom/role/platform-admin`
-   and captures the OIDC mount config:
-   `python3 scripts/openbao-attended-exec.py -- scripts/openbao-platform-admin-callback-prune.sh --receipt docs/evidence/2026-09-24-platform-admin-callback-prune.json`.
-   After it, update the role declaration, add the `openbao/auth/*-oidc-config.json`
-   files, and tell net-kingdom. I have already told them railiance-platform
-   owns the mount config.
+1. **Done during the wind-down.** The founder ran the attended callback prune
+   at 23:11Z. The two retired callbacks are gone from
+   `auth/netkingdom/role/platform-admin`, and the OIDC mount config is
+   declared (`openbao/auth/*-oidc-config.json`, railiance-platform `bcf6f9b`).
+   I pushed that commit with one test fixture still failing, because I
+   chained the commit past the test run; `c9bf8c9` fixed it minutes later.
+   net-kingdom has been told to make its script read-only.
 2. **Owners' follow-through on RPF-WP-0046 hand-offs.**
    - rapp-postgres and audit-core must retire their 768h mint scripts;
      rerunning them brings the expiry problem back for that app.