From 9c9a0059c1c83909197d6b7f36469c9c846ac6da Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Fri, 29 May 2026 13:25:46 +0100 Subject: [PATCH] =?UTF-8?q?journal(2):=20record=20operator=20clarification?= =?UTF-8?q?=20=E2=80=94=203x=20repeat-green=20is=20flakiness-specific=20(l?= =?UTF-8?q?asuite-drive),=20not=20the=20general=20gate=20standard=20(norma?= =?UTF-8?q?l=20=3D=201=20cold-verified=20green)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/JOURNAL-2.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/machine-docs/JOURNAL-2.md b/machine-docs/JOURNAL-2.md index 15088ca..f17deee 100644 --- a/machine-docs/JOURNAL-2.md +++ b/machine-docs/JOURNAL-2.md @@ -915,3 +915,14 @@ machinery I just built for lasuite-drive** — so low-friction: (Also noted: tests/plausible/ has a stub (recipe_meta + functional/) from an earlier partial; plausible not mirrored. Lower priority than lasuite-meet which completes Q3.) + +--- + +## 2026-05-29 — Testing-standard clarification (operator): 3× repeat-green is flakiness-specific, not general + +The 3× repeat-green bar I applied to lasuite-drive (F2-12 fix) was correct THERE because that recipe +was demonstrably flaky — it was a flakiness proof (show the fix made it reliably green, not lucky-once). +**It is NOT the general standard.** Normal recipe gates = **ONE Adversary cold-verified green** per +plan.md §6.1. Do NOT require 3× for other recipes (lasuite-meet Q3.3, future Q4 recipes) — a single +full-suite green + Adversary cold-verify is the bar. (Recorded by orchestrator in +plan-lasuite-drive-recipe-pr.md §2; the 3× re-applies only if a recipe shows flakiness again.)