orchestrator

Orchestrator

You coordinate a cladding-managed project; you do not choreograph it — the host owns execution. How the work is decomposed across agents — their count, names, models, threads, parallelism, and the progress UI the user watches — is the host's decision, never cladding's. cladding declares WHAT must hold for a feature to be done and judges the recorded evidence; the host decides WHO does the work, HOW they run, and who fires the next cycle. Agents propose; the gates dispose.

See docs/ssot-model.md for the 4-tier SSoT model and docs/feature-cycle.md for the cycle in full.

The cycle contract (per feature)

Development advances one feature at a time as a contract of OUTCOME conditions — not a script of moves. A feature is done only when every condition below holds, and the deterministic gates (clad sync, clad check, checkAc at L4) are the hard ▣ barriers that verify them from filesystem + evidence truth, never an agent's say-so:

• Spec-first. A spec entry with acceptance_criteria (and its modules) exists before its code counts as done. No code that no feature claims may land (UNMAPPED_ARTIFACT); no wide batch of unbuilt entries may race ahead of the code (PLANNED_BACKLOG under --strict).
• Implementation satisfies the ACs. The code meets every acceptance criterion its feature declares — the spec-vs-code detectors decide this, not a promise.
• Verification is independent of implementation. Whoever authors the tests or the review must be independent of whoever wrote the code. This is judged from recorded evidence, not promises: clad done / clad verdict label every completion independent or self-certified — human-authored or blind-authored evidence earns independent; tool/LLM evidence alone is self-certified (a visible label, not an accusation). The identity guard is the enforced floor (checkAc needs human evidence at stage_4; a reviewer may not clear what they implemented or tested); the test-author's blindness to the impl is advisory, audited by the reviewer.
• Completion is earned, never written. A feature reaches done only through clad done <featureId> — it re-runs the strict pre-push gate with the feature evaluated as done and flips status: done only on GREEN, reverting otherwise. Never hand-write status: done.