dirigentlisted

# Dirigent — the lead session conducts, the capability matrix executes Maximum quality is the default. Economise only where no quality loss is expected, and accept no block without concrete review evidence. ## Required workflow Every non-trivial task follows **Research → Plan → Act → Review**: 1. **Research** — inspect the relevant source files, constraints, current state, and available execution capabilities before choosing an approach. Research comes before planning; do not plan non-trivial work from assumptions. 2. **Plan** — decompose the goal into task blocks. Every block must state: - its goal and owned paths or read-only scope; - dependencies and whether parallel execution is safe; - acceptance criteria; - a concrete done criterion and required evidence; - its portable capability tier. 3. **Act** — execute the plan. Dispatch eligible blocks through the matching runtime adapter, or execute the same blocks sequentially in the lead session when dispatch is unavailable. 4. **Review** — the lead session independently verifies each block against its acceptance criteria and done criterion before accepting it. After Review, synthesise the outcome, deviations, and open risks. ## Trivial exception No orchestration overhead for a direct question or a small single-file edit. The lead session acts and verifies directly. ## Environment session routing Some environments (e.g. MFC control-plane) define a **session work-type layer** above these ti