diff --git a/machine-docs/JOURNAL-redfix.md b/machine-docs/JOURNAL-redfix.md
index 9b7de99..1b6b4fb 100644
--- a/machine-docs/JOURNAL-redfix.md
+++ b/machine-docs/JOURNAL-redfix.md
@@ -1469,3 +1469,23 @@ rules forbid — which would not undo the public disclosure anyway.
 mine to delete, same shape as F-redfix-2. Still filed, still not fixed.
 
 No work exists for the Builder. Loop stopping; future reboots need no action.
+
+## Wake #28 @2026-07-09T03:40Z — reboot no-op; terminal condition re-verified from artifacts
+
+Re-derived the terminal condition rather than trusting the commit log:
+- `## DONE — 2026-07-09T00:18Z` in STATUS-redfix.md.
+- Both gates carry a fresh Adversary PASS: M1 @2026-06-18T01:18Z, M2 @2026-07-09T00:18Z.
+- Both `## VETO` headings in REVIEW-redfix.md are the same F-redfix-4 finding — line 553 is stamped
+  `[CLEARED @2026-07-09T00:18Z ... NOT standing]` and line 649 is the clearing entry itself. No standing VETO.
+- No ADVERSARY-INBOX.md, no BUILDER-INBOX.md, no gate CLAIMED. Tree clean but for untracked `main.go`.
+
+Did **not** re-probe B-redfix-8. The Adversary measured it 30 minutes ago (`e75a24a`, 03:10Z: still LIVE,
+digest `3fcea78925015fc9` unrotated; still PUBLIC, HTTP 200/33408). A fourth reading of the same public
+mirror on that timescale is a duplicate measurement, not evidence. It stays **OPEN**, HIGH, operator-only:
+rotation is a Class-A1 external input, and excising the blob would require the `--force` history rewrite the
+rules forbid — which would not undo the public disclosure regardless.
+
+`main.go` still untracked and un-gitignored at the clone root. Not a secret, not mine to delete (F-redfix-2
+shape). Still filed, still not fixed.
+
+No work exists for the Builder. Loop stopping; further reboots need no action.