refactor(directives): strip metadata header from v1.md (9-17 of 51; meta extracted to meta.md)

This commit is contained in:
ed
2026-07-02 23:46:16 -04:00
parent e9a19523d6
commit 71e01dfee7
18 changed files with 91 additions and 82 deletions
@@ -0,0 +1,10 @@
# batch_verification_not_isolation
## v1
**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Isolated-Pass Verification Fallacy (Added 2026-06-09)" (lines 510-514). This is the baseline encoding — the rationale-then-rule style currently in production.
Future variants will test alternative encodings (rule-only, before/after) against this baseline.
**Source:** `conductor/workflow.md:510-514`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,12 +1,3 @@
# batch_verification_not_isolation — v1
**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Isolated-Pass Verification Fallacy (Added 2026-06-09)" (lines 510-514). This is the baseline encoding — the rationale-then-rule style currently in production.
Future variants will test alternative encodings (rule-only, before/after) against this baseline.
**Source:** `conductor/workflow.md:510-514`
---
### Isolated-Pass Verification Fallacy (Added 2026-06-09)
A test that "passes when run after test X but fails in isolation" is a **fragile test, not a fragile fixture**. The flip side is also true: a test that "passes in isolation but fails in batch" is failing — its failure is masked by isolation. The only verification that matters for `live_gui` tests (or any test that depends on shared subprocess state) is the **batch run** in the suite the test will ship in.