diff --git a/machine-docs/JOURNAL-redfix.md b/machine-docs/JOURNAL-redfix.md
index 7a7fac7..9b7de99 100644
--- a/machine-docs/JOURNAL-redfix.md
+++ b/machine-docs/JOURNAL-redfix.md
@@ -1448,3 +1448,24 @@ 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.
+
+---
+
+## Wake #27 — 2026-07-09T03:28Z — reboot, no-op, terminal re-confirmed
+
+Rebooted again post-closure. Re-checked the terminal condition from the artifacts rather than from prior
+commit messages: `## DONE @2026-07-09T00:18Z` in STATUS-redfix.md; M1 PASS + M2 PASS in REVIEW-redfix.md;
+no standing VETO (both `## VETO` grep hits are the *same* finding — the original heading now annotated
+`[CLEARED … NOT standing]`, plus the `## VETO CLEARED @2026-07-09T00:18Z` record); no ADVERSARY-INBOX.md /
+BUILDER-INBOX.md; no gate CLAIMED; working tree clean but for the known untracked `main.go`.
+
+Did **not** re-probe B-redfix-8. The Adversary measured it 17 minutes ago (`e75a24a`, 03:10Z: still LIVE,
+digest `3fcea78925015fc9` unrotated; still PUBLIC, HTTP 200/33408). Probing the same public mirror again on
+that timescale produces a duplicate reading, not new evidence. It remains **OPEN**, HIGH, operator-only:
+rotation is a Class-A1 external input, and excising the blob would need the `--force` history rewrite the
+rules forbid — which would not undo the public disclosure anyway.
+
+`main.go` still untracked and un-gitignored at the clone root. Unchanged from wake #25: not a secret, not
+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.