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

2026-07-04 02:00:42 -04:00
parent e8d3578f2e
commit 79124774ec
82 changed files with 2430 additions and 0 deletions
@@ -0,0 +1,7 @@
+# tier1_first_commit_6file_acknowledgment
+
+## v1
+
+**Why this iteration:** Tier 2's parallel rule (`acknowledgment_in_first_commit`) is already lifted (covers the 11-file Tier 2 autonomous list). Tier 1 has a parallel 6-file list with the same commit-message acknowledgment mechanism — this lifts that Tier 1-specific rule from the .agents/agents role prompt.
+**Source:** `.agents/agents/tier1-orchestrator.md:30-41 (MANDATORY: Pre-Action Required Reading + Enforcement)`
+**Lifted:** 2026-07-03 scavenge sweep batch 5/5: guides + role prompts + transcripts
@@ -0,0 +1,52 @@
+# Tier 1's first commit of any new track must include "TIER-1 READ <list> before <task>" in the commit message
+
+From `.agents/agents/tier1-orchestrator.md` §"MANDATORY: Pre-Action Required Reading (added 2026-06-24 post-SSDL-campaign-errors)":
+
+> Before ANY action (reading files, writing files, planning, asserting), the agent MUST read these 6 files IN ORDER. Skipping any is grounds for aborting the work. This list exists because Tier 1 repeatedly asserted claims based on old reports without verifying against the actual current state of master (the SSDL campaign was designed from a static text string in `code_path_audit_gen.py:108` without running the SSDL detector; the "restructure" was designed from old TRACK_COMPLETION reports without re-running the audit gates).
+
+> **Enforcement:** the agent's first commit in any new track must include "TIER-1 READ <list> before <task>" in the commit message. The agent must re-run the audit gates (`scripts/audit_*.py --strict`) and verify the actual state of master (`git log master --oneline -5`, `git show master:src/<file>`) before making ANY claim about "the current state" in a spec or plan. **No more asserting from old reports.**
+
+## The 6 files (per Tier 1 orchestrator)
+
+1. `AGENTS.md` (project root) — operating rules + critical anti-patterns
+2. `conductor/workflow.md` — operational workflow + tier-specific conventions
+3. The current track's `conductor/tracks/<track>/spec.md` and `plan.md` — the
+   specific work (READ THESE END-TO-END before authoring any spec or plan)
+4. `conductor/code_styleguides/data_oriented_design.md` — canonical DOD reference
+5. `conductor/code_styleguides/error_handling.md` — the `Result[T]` convention
+   (Rule #0: "READ THIS STYLEGUIDE FIRST")
+6. `conductor/code_styleguides/type_aliases.md` — the 10 TypeAliases
+
+## Format
+
+The first commit's message MUST include the phrase:
+
+```
+TIER-1 READ AGENTS.md, conductor/workflow.md, conductor/tracks/<track>/spec.md,
+conductor/code_styleguides/data_oriented_design.md,
+conductor/code_styleguides/error_handling.md,
+conductor/code_styleguides/type_aliases.md before <task-name>
+```
+
+(adapt the list to match the tier-specific reading list; the format is exact.)
+
+## Why
+
+The 2026-06-24 SSDL-campaign regression: Tier 1 asserted claims based on old reports
+without verifying against the actual current state of master. The SSDL campaign was
+designed from a static text string without running the SSDL detector. The
+acknowledgment rule is the structural defense — a missing acknowledgment is a
+documented signal that the agent skipped the pre-action reading.
+
+## Enforcement
+
+The first commit in any new track that lacks the acknowledgment is treated as a
+red-phase failure. The failcount/state contract documents the missing acknowledgment
+so the next agent (or the user reviewing the track) can see the audit trail.
+
+## See also
+
+- `conductor/directives/acknowledgment_in_first_commit` — Tier 2's parallel rule
+  with the 11-file list
+- `conductor/directives/mandatory_research_first` — the foundational research-first
+  posture that this rule builds on