What problem does it solve? Multi-phase AI-orchestrated projects often close phases without verified evidence, letting drift, hallucinated APIs, and untested code slip through. This protocol enforces a rigorous, gated phase-completion workflow so no phase closes without retrospectives, verification evidence, and required agent participation. ## Core Features & Use Cases - Retrospective Gate: Blocks phase_complete until a structured retrospective evidence bundle (verdict, metrics, lessons learned) is written via write_retro. - Verification Gates: Runs drift verification against the effective spec, hallucination checks on changed files, and mutation testing when enabled in the QA gate profile. - Council Reviews: Dispatches 5-member phase and final councils, collecting verdicts and persisting quorum-bound evidence before closeout. - Use Case: After finishing Phase 2 of a swarm-managed build, the architect runs this protocol to rescan the codebase, update docs, write the retrospective, pass drift and hallucination gates, and only then call phase_complete. ## Quick Start Ask the architect to run the phase-wrap protocol to close out the current phase with all required evidence gates and retrospective.
