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

This commit is contained in:
ed
2026-07-02 23:47:12 -04:00
parent 68352ee206
commit 5b0f932c4b
18 changed files with 91 additions and 82 deletions
@@ -0,0 +1,10 @@
# scope_creep_track_doc_ban
## v1
**Why this iteration:** Lifted verbatim from `AGENTS.md` §"Process Anti-Patterns" #3 (lines 139-144). This is the baseline encoding — the symptom-rule-pair style currently in production.
Future variants will test alternative encodings (rule-only, tabular) against this baseline.
**Source:** `AGENTS.md:139-144`
---
**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 @@
# scope_creep_track_doc_ban — v1
**Why this iteration:** Lifted verbatim from `AGENTS.md` §"Process Anti-Patterns" #3 (lines 139-144). This is the baseline encoding — the symptom-rule-pair style currently in production.
Future variants will test alternative encodings (rule-only, tabular) against this baseline.
**Source:** `AGENTS.md:139-144`
---
### 3. The Scope-Creep Track-Doc Pattern (kill it)
**Symptom:** The user asks for a 1-line fix. You write a 5-phase "future track" spec with 140 lines of scope, audit findings, recommendations, and "out of scope" sections. The track doc is now larger than the fix it was meant to scope.