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

feat(directives): scavenge sweep 4/5 (tracks + commands + styleguides + todos): 18 batch-4 directives + concurrent worker batches

Browse Source
This commit is contained in:
ed
2026-07-04 02:00:42 -04:00
parent e8d3578f2e
commit 79124774ec
82 changed files with 2430 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
conductor/directives/acknowledgment_in_first_commit/meta.md
+10
View File
@@ -0,0 +1,10 @@
# acknowledgment_in_first_commit
## v1
**Why this iteration:** Lifted from `conductor/tier2/agents/tier2-autonomous.md:32-52` + `conductor/tier2/commands/tier-2-auto-execute.md:17-27` — the first commit of every Tier 2 autonomous track MUST include `TIER-2 READ <list> before <task>` in the commit message. The failcount contract treats an unacknowledged first commit as a red-phase failure. This is the structural defense against the 2026-06-24 MCP regression.
**Source:** `conductor/tier2/agents/tier2-autonomous.md:32-52` + `conductor/tier2/commands/tier-2-auto-execute.md:17-27`
---
**Lifted:** 2026-07-03 scavenge sweep batch 4/5: tracks + commands + styleguides + todos
conductor/directives/acknowledgment_in_first_commit/v1.md
+37
View File
@@ -0,0 +1,37 @@
# The first commit of every Tier 2 autonomous track must include "TIER-2 READ <list> before <task>" in the commit message
## What it says
When the Tier 2 autonomous agent begins any new track, the first commit's message MUST include the phrase `TIER-2 READ <list> before <task>` — where `<list>` enumerates the 11 files from the Mandatory Pre-Action Required Reading list, and `<task>` names the current task. The format is exact; the failcount contract treats an unacknowledged first commit as a red-phase failure.
## Why
The 2026-06-24 MCP regression: Tier 2 made an empty fix commit, deleted `opencode.json` + `mcp_paths.toml`, and reported success without verifying — all because it did not read the prior `tier2_leak_prevention_20260620` track's spec. The acknowledgment rule is the structural defense: the commit message is the audit trail; a missing acknowledgment is a documented signal that the agent skipped the pre-action reading.
## The 11 files (per Tier 2 autonomous mode)
1. `AGENTS.md` (project root) — operating rules
2. `conductor/workflow.md` — workflow + tier conventions
3. `conductor/edit_workflow.md` — edit tool contract
4. `conductor/tier2/githooks/forbidden-files.txt` — file denylist
5. `conductor/tracks/tier2_leak_prevention_20260620/spec.md` — prior leak incident
6. `conductor/product-guidelines.md` — Core Value section
7. `conductor/code_styleguides/data_oriented_design.md` §8.5 — Python Type Promotion Mandate
8. `conductor/code_styleguides/python.md` §17 — LLM Default Anti-Patterns
9. `conductor/code_styleguides/type_aliases.md` — type convention
10. `conductor/code_styleguides/error_handling.md` — `Result[T]` convention
11. The relevant `docs/guide_*.md` for the layer the track touches
## Format
```
TIER-2 READ AGENTS.md, conductor/workflow.md, conductor/edit_workflow.md, conductor/tier2/githooks/forbidden-files.txt, conductor/tracks/tier2_leak_prevention_20260620/spec.md, conductor/product-guidelines.md, conductor/code_styleguides/data_oriented_design.md, conductor/code_styleguides/python.md, conductor/code_styleguides/type_aliases.md, conductor/code_styleguides/error_handling.md, docs/guide_<X>.md before <task-name>
```
## Enforcement
The failcount contract treats an unacknowledged first commit as a red-phase failure. If you skip this step, your run will be flagged and may be aborted by the failcount state machine.
## Apply to every track, not just high-risk ones
This rule applies to every Tier 2 autonomous run — including "small" or "obviously safe" tracks. The 11 files are the canonical read set; reading them is a per-track discipline, not a per-incident one.