diff --git a/briefs/2026-07-18-weekly-founder-review.md b/briefs/2026-07-18-weekly-founder-review.md
new file mode 100644
index 0000000..ff7db3d
--- /dev/null
+++ b/briefs/2026-07-18-weekly-founder-review.md
@@ -0,0 +1,47 @@
+# Weekly Founder Review — 2026-07-18 (prep note)
+
+> Prepared per `OperatingRhythm.md` § Weekly review (~15 min, agent-prepared,
+> founder-consumed). Review week: 2026-07-16 → 2026-07-18 (first review cycle;
+> the operating rhythm started 2026-07-16).
+
+## Read these (in order)
+
+1. Newest daily brief: `briefs/2026-07-18-daily-brief.md`
+2. `SuccessMilestones.md`
+
+## The one question: did anything move a milestone?
+
+**No milestone status changed this week.** `SuccessMilestones.md` is unchanged
+since its v0.1 creation (commit d6d5cf1, 2026-07-16): S1 "in progress",
+S2 "started", S3–S12 open. Per the rule in that file, status changes are
+founder decisions recorded in `DecisionQueue.md` — none were recorded.
+
+**Milestone-relevant activity did happen** (candidate evidence, not yet a
+status change):
+
+- S2 (active operating system): daily rhythm ran all three weekdays (three
+  briefs, queue hygiene, cron bridge healthy); workstation-independent
+  executor is deployable — agent-harness live on Railiance with binky-control
+  as tenant #1 and three clean proof runs (HARNESS-WP-0001-T06/T07).
+- S1 (administratively clean): mailbox read lane live (93-message scan),
+  Stripe webhook failure diagnosed (AWQ-009), IONOS/Sedo account facts
+  recorded, paper-mail intake artifacts filed.
+
+If the founder judges S2 has effectively been reached once the executor
+cutover lands, that is a `DecisionQueue.md` entry with the evidence above.
+
+## RISK-005 watch
+
+RISK-005 ("agentic stack becomes busywork generator instead of progress
+engine") escalates after **two consecutive weeks** of activity without
+milestone movement. This is **week 1 of 2**: high activity, no milestone
+status change. Not escalating yet — but if the week ending ~2026-07-25 also
+closes without a milestone status change (or a recorded founder decision that
+one moved), RISK-005 escalates per the OperatingRhythm rule.
+
+## Pending founder action (from the 2026-07-18 brief)
+
+- **DEC-2026-003 — Go for executor cutover** (~5 min): all gates cleared;
+  approval retires the workstation cron bridge and completes BINKY-WP-0004.
+- Carry-over: two suspicious mails flagged in `mailmeta/mail-log.md` await a
+  human glance.