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

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
@@ -0,0 +1,10 @@
# atomic_per_task_commits
## v1
**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Standard Task Workflow" step 9 (line 112) + `AGENTS.md` "Critical Anti-Patterns" (line 55). This is the baseline encoding — the imperative-bullet style currently in production.
Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
**Source:** `conductor/workflow.md:112 + AGENTS.md:55`
---
**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 @@
# atomic_per_task_commits — v1
**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Standard Task Workflow" step 9 (line 112) + `AGENTS.md` "Critical Anti-Patterns" (line 55). This is the baseline encoding — the imperative-bullet style currently in production.
Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
**Source:** `conductor/workflow.md:112 + AGENTS.md:55`
---
From `conductor/workflow.md` §"Standard Task Workflow" step 9:
- **CRITICAL - ATOMIC PER-TASK COMMITS**: You MUST commit your changes immediately after completing and verifying a single task. Do NOT move on to the next task in the plan without committing the current one. This ensures precise tracking and safe rollback points.
- Stage all code changes related to the task.
+11
View File
@@ -0,0 +1,11 @@
# ban_any_type
## v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.2 (lines 267-277).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:267-277`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
-10
View File
@@ -1,13 +1,3 @@
# ban_any_type — v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.2 (lines 267-277).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:267-277`
---
### 17.2 Banned: `Any`
```python
@@ -0,0 +1,10 @@
# ban_arbitrary_core_mocking
## v1
**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Structural Testing Contract" #1 (line 262) + `AGENTS.md` §"Critical Anti-Patterns" (line 53). This is the baseline encoding — the imperative-bullet style currently in production.
Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
**Source:** `conductor/workflow.md:262 + AGENTS.md:53`
---
**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 @@
# ban_arbitrary_core_mocking — v1
**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Structural Testing Contract" #1 (line 262) + `AGENTS.md` §"Critical Anti-Patterns" (line 53). This is the baseline encoding — the imperative-bullet style currently in production.
Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
**Source:** `conductor/workflow.md:262 + AGENTS.md:53`
---
From `conductor/workflow.md` §"Structural Testing Contract":
1. **Ban on Arbitrary Core Mocking:** Tier 3 workers are strictly forbidden from using `unittest.mock.patch` to bypass or stub core infrastructure (e.g., event queues, `ai_client` internals, threading primitives) unless explicitly authorized by the Tier 2 Tech Lead for a specific boundary test.
2. **`live_gui` Standard:** All integration and end-to-end testing must utilize the `live_gui` fixture to interact with a real instance of the application via the Hook API. Bypassing the hook server to directly mutate GUI state in tests is prohibited.
@@ -0,0 +1,10 @@
# 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`
---
**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 @@
# 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'.")
+11
View File
@@ -0,0 +1,11 @@
# ban_dict_any
## v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.1 (lines 247-265).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:247-265`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
-10
View File
@@ -1,13 +1,3 @@
# ban_dict_any — v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.1 (lines 247-265).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:247-265`
---
### 17.1 Banned: `dict[str, Any]`
```python
@@ -0,0 +1,11 @@
# ban_dict_get_on_known_fields
## v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.6 (lines 340-350).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:340-350`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,13 +1,3 @@
# ban_dict_get_on_known_fields — v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.6 (lines 340-350).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:340-350`
---
### 17.6 Banned: `.get('field', default)` on a `dict[str, Any]`
```python
@@ -0,0 +1,11 @@
# ban_getattr_dispatch
## v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.5 (lines 328-338).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:328-338`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,13 +1,3 @@
# ban_getattr_dispatch — v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.5 (lines 328-338).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:328-338`
---
### 17.5 Banned: `getattr(x, 'field', default)` for type dispatch
```python
@@ -0,0 +1,11 @@
# ban_hasattr_dispatch
## v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.4 (lines 300-326).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:300-326`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
@@ -1,13 +1,3 @@
# ban_hasattr_dispatch — v1
**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §17.4 (lines 300-326).
This is the baseline encoding — the imperative-ban style currently in production.
Future variants will test alternative encodings (rationale-first, before/after, tabular) against this baseline.
**Source:** `conductor/code_styleguides/python.md:300-326`
---
### 17.4 Banned: `hasattr()` for entity type dispatch
```python