diff --git a/machine-docs/REVIEW-2.md b/machine-docs/REVIEW-2.md
index e0b6de4..a27930b 100644
--- a/machine-docs/REVIEW-2.md
+++ b/machine-docs/REVIEW-2.md
@@ -965,3 +965,15 @@ not active now.** Recording the bar I will enforce when it IS claimed:
 - Real-abra-only still applies; the keystone is a recipe `compose.yml` healthcheck (real), not a CI patch.
 This does NOT reopen Q3.2 (PASS stands, F2-12 CLOSED) — it's a separate future gate (Builder parked it
 as Q3.2b @ ac241d4).
+
+## @2026-05-29 — Verification-bar clarification (operator): 3× repeat-green is lasuite-drive-PR-ONLY
+Operator clarified: the **"repeatedly-green / 3 consecutive passes"** bar applies **ONLY** to the
+lasuite-drive *recipe PR* (`plan-lasuite-drive-recipe-pr.md` §2) — because that recipe was demonstrably
+FLAKY, so its gate is a *flakiness proof* (show the fix made it reliably green, not green-by-luck-once).
+It is **NOT the general testing standard.** Normal recipe gates = **ONE Adversary cold-verified green**
+per `plan.md` §6.1. I will NOT require 3× for other recipes/gates.
+- **Applies to my pending cryptpad F2-9:** ONE clean cold-verified green (real create-pad→fresh-context
+  read-back, not health-only, nothing skipped, clean teardown) is sufficient to close F2-9 — I do not
+  need 3×. (The Builder is still validating their own cold-timing fix `3484d25`; I verify once it's claimed.)
+- Note: my Q3.2 PASS already cited the Builder's 3× as *their* evidence + my own ONE cold run — that
+  remains correct; the lasuite-drive *recipe PR* (Q3.2b, parked) is where I'll require repeat-green.