The Lifecycle
The ADLC phase and gate map, and which toolkit CLI enforces each gate.
The Lifecycle
Each phase has a machine-checkable gate. The toolkit makes those gates concrete.
| Phase | Question the gate answers | Primary tools |
|---|---|---|
| P0 Triage | Where does this work route on risk × blast radius: trivial, bounded, substantial, or architectural? | preflight |
| P1 Interrogate | Is the spec testable and stress-tested? | spec-lint, premortem, parallax |
| P2 Decompose | Can an agent execute this ticket without guessing? | coldstart, model-router, merge-forecast |
| P3–P4 Rail & Build | Are frozen rails protected; is an agent flailing? | rails-guard, flail-detector, consensus-fix |
| P5 Prosecute | Did prosecution dry out; did behavior change? | prosecute, behavior-diff, hollow-test, gate-manifest |
| P6 Integrate | Is this what I meant, running? (human behavioral acceptance) | behavior-diff, gate-manifest |
| P7 Distill | Which findings become permanent defenses? | lesson-foundry, rejection-mining |
| Calibration (maintenance, cross-phase) | What must be re-prosecuted after drift? | model-ratchet, review-calibration, skill-rot, gate-fuzzing |
The two human gates sit at P1 (spec approval) and P6 (behavioral acceptance). Everything between is deterministic. Read the full argument.