diff --git a/machine-docs/JOURNAL-redfix.md b/machine-docs/JOURNAL-redfix.md
index 7084998..7a7fac7 100644
--- a/machine-docs/JOURNAL-redfix.md
+++ b/machine-docs/JOURNAL-redfix.md
@@ -1420,3 +1420,31 @@ unauthenticated public internet** from the historical commit `14c7dee`. Both loa
 Nothing here is actionable by me: rotation is a Class-A1 external input (operator-only), and excising the blob
 needs a history rewrite + `--force`, which the standing rules forbid and which would not undo disclosure
 anyway — a value served publicly must be presumed captured. Loop stopping.
+
+## wake #25 — 2026-07-09T02:51Z — reboot after closure; no work to do, loop re-stopped
+
+Rebooted into a phase that is already terminal. I re-checked the terminal condition rather than assuming it
+survived the restart, and it did, on every limb:
+
+    machine-docs/STATUS-redfix.md   -> "## DONE — 2026-07-09T00:18Z"
+    machine-docs/REVIEW-redfix.md   -> M1 PASS @2026-06-18T01:18Z, M2 PASS @2026-07-09T00:18Z, VETO [CLEARED]
+    machine-docs/*INBOX*            -> absent (both consumed)
+    git status                      -> up to date with origin/main, no gate claimed
+
+No gate is claimed, no finding is open against the DoD, and the Adversary loop stopped at `de126b3`. So there
+is nothing here for a Builder to advance.
+
+I did **not** re-probe B-redfix-8 this wake. Wake #24 (`e9a9652`) measured it first-hand seven minutes ago —
+digest `3fcea78925015fc9`, HTTP 200/33408, live value verbatim in the public blob — and re-running the same
+probe against a production mirror seven minutes later would be repetition, not evidence. It stays **OPEN**,
+HIGH, blocking on operator rotation, which is the one thing neither loop may do (Class-A1 external input;
+excising the blob needs a `--force` history rewrite the rules forbid, and would not undo public disclosure).
+
+One housekeeping observation, filed not fixed: `main.go` (16-line "Hello, World!" HTTP server) sits untracked
+and un-gitignored at this clone's root. It is not mine and it is not a secret, but it is the same shape as
+F-redfix-2 — a stray root file that the next `git add -A` would push to origin. It is in fact the file the
+Adversary's F-redfix-2 cold replay saw staged. Left in place (not mine to delete); noted so a future phase
+either gitignores it or removes it deliberately.
+
+**Future reboots of this loop need no action.** The DoD is met and Adversary-verified; the only open item is
+operator-only. Stopping again.