ed/manual_slop
Private
Public Access
0
0
Fork 0
Code Activity

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

Browse Source
This commit is contained in:
ed
2026-07-02 23:46:04 -04:00
parent c9f30abffc
commit e9a19523d6
19 changed files with 2159 additions and 77 deletions
Download Patch File Download Diff File Expand all files Collapse all files
conductor/directives/ban_day_estimates/v1.md
-9
View File
@@ -1,12 +1,3 @@
# ban_day_estimates — v1
**Why this iteration:** Lifted verbatim from `AGENTS.md` "Critical Anti-Patterns" HARD BAN (line 61) + `conductor/workflow.md` §"Tier 1 Track Initialization Rules" §1 (lines 605-625). This is the baseline encoding — the imperative-bullet-with-rationale style currently in production.
Future variants will test alternative encodings (tabular, replacement-patterns-table) against this baseline.
**Source:** `AGENTS.md:61 + workflow.md:605-625`
---
From `AGENTS.md` "Critical Anti-Patterns":
- **HARD BAN: Day estimates in track artifacts (Tier 1).** Do NOT include day / hour / minute estimates in spec.md, plan.md, metadata.json, or any other track artifact. Day estimates are inaccurate noise; Tier 2 capacity is bounded by attention, not time. Measure effort by **scope** (N files, M sites, N tasks). The user / Tier 2 agent decides the actual pacing. See `conductor/workflow.md` §"Tier 1 Track Initialization Rules" for the full rule, replacement patterns, and rationale. (Added 2026-06-16 per user feedback: "Day estimates are inaccurate. Tier-2s can only do so much in a single track and there is no way in hell its going to be 'DAYS'.")