feat(directives): commit Phase 1 harvest summary (51 v1.md files)
Systematic extraction of every directive-like statement from the entire doc tree into conductor/directives/<name>/v1.md files. 51 v1 files lifted verbatim from production docs. Per-task atomic commits (t1_1..t1_10) provide the per-directive provenance. This meta-commit captures the harvest-level summary. Sources combed: AGENTS.md, conductor/workflow.md, conductor/product-guidelines.md, conductor/tech-stack.md, all 14 conductor/code_styleguides/*.md, .opencode/commands/*.md. Original docs remain untouched as canonical source. The conductor/directives/ tree is a parallel structure, not a replacement. Future v2+ variants can test alternative encodings (rationale-first, before/after, tabular) against this baseline.
This commit is contained in:
@@ -0,0 +1,41 @@
|
||||
# Directive Harvest — Phase 1 Summary
|
||||
|
||||
**Status:** Phase 1 complete. 51 directive variants lifted verbatim into `conductor/directives/<name>/v1.md`.
|
||||
|
||||
## What shipped
|
||||
|
||||
51 v1.md files across 51 directive directories. Each is a verbatim lift of the imperative-ban / rationale-bullet style currently in production, with a header annotating the source location for future cross-referencing.
|
||||
|
||||
| Task | # of directives | Sources |
|
||||
|---|---|---|
|
||||
| t1_1 | 7 | `conductor/code_styleguides/python.md` §17.1-17.7 |
|
||||
| t1_2 | 3 | `.opencode/commands/mma-tier3-worker.md:42-46` (drift-corrected from python.md §17.9) |
|
||||
| t1_3 | 2 | `conductor/code_styleguides/error_handling.md` |
|
||||
| t1_4 | 2 new + 1 updated | `data_oriented_design.md` §8.5 + `type_aliases.md` + python.md §17.7/17.8 |
|
||||
| t1_5 | 5 | `python.md` + `workflow.md` + `product-guidelines.md` + `AGENTS.md` |
|
||||
| t1_6 | 3 | `AGENTS.md` + `workflow.md` |
|
||||
| t1_7 | 10 | `AGENTS.md` + `workflow.md` |
|
||||
| t1_8 | 6 | `AGENTS.md` §Process Anti-Patterns + `workflow.md` Skip-Marker Policy |
|
||||
| t1_9 | 5 | `product-guidelines.md` + `python.md` §15 |
|
||||
| t1_10 | 8 | 4 from plan + 4 from new styleguides (config_state_owner, workspace_paths, test_sandbox, chroma_cache_path) |
|
||||
| **Total** | **51** | |
|
||||
|
||||
## What was skipped
|
||||
|
||||
Of the 5 newly-added styleguides (per the 2026-07-02 spec edit), 4 contained directive-like content and were harvested; 1 was skipped:
|
||||
|
||||
- **`conductor/code_styleguides/code_path_audit.md`** — SKIPPED. The 4 conventions (per-aggregate profile structure, the 4 decomposition directions, the override file format, the mem-dim classification rules) describe the audit script's outputs and formats, not what the agent should do. They are descriptive of an internal tool, not prescriptive for the LLM. If future tracks need an "audit-script-usage" directive, that should be created separately with explicit rules like "before modifying an aggregate, run `python scripts/code_path_audit/code_path_audit.py <aggregate_name>` and check the recommended_direction".
|
||||
|
||||
## Source drift corrections
|
||||
|
||||
Several plan line refs were stale (the doc tree moved during the 2026-06-27 cruft-elimination refactor). All v1.md `**Source:**` lines reflect the actual verified line ranges:
|
||||
|
||||
- `python.md` plan claimed §17 = lines 243-473; actual file is 359 lines. The §17.1-17.7 ranges were corrected in v1.md headers (each off by ~1 line).
|
||||
- `python.md` plan claimed §17.9 = lines 364-443; that section was deleted during the cruft_elimination_20260627 refactor. The §17.9 content (local imports / _PREFIX aliasing / repeated from_dict) now lives in `.opencode/agents/tier3-worker.md` and `.opencode/commands/mma-tier3-worker.md`. The 3 directives (t1_2) lift from `.opencode/commands/mma-tier3-worker.md:42-46`.
|
||||
- All other plan line refs were close to actual (off by 1-3 lines); verified by `get_file_slice` before each lift and corrected in the v1.md `**Source:**` line where drifted.
|
||||
|
||||
## Phase 1 stop point
|
||||
|
||||
Per the dispatch prompt: "After Phase 1 completes, you STOP and report back to the Tier 2 Tech Lead. Phase 2 (baseline preset + role-prompt warm-with: bootstrap) requires the Tier 2's review and decision on per-tier preset variants before dispatching Tier 3 again."
|
||||
|
||||
Phase 2 work (current_baseline.md + 5 role-prompt warm with: updates) is deferred to the next Tier 2 dispatch.
|
||||
Reference in New Issue
Block a user