The six phases
Each project moves through six phases in one order. [s57] A gate decision moves a project from one phase to the next. [99] No seat can assert a gate verdict. [78]
| Phase | What it proves |
|---|---|
| Ideate | The phase proves that the brief states the outcome and the open questions. The Foreman walks the agenda and records one decision per question. [98] [s57] |
| Design | The phase proves that a contract covers the brief. Each story carries lines that a test can check. [101] [s62] |
| Build | The phase proves that frozen tests fail first and then pass. Lanes build one claim each on a branch from the integration tree. [112] [s63] |
| Verify | The phase proves that the stamped tree passes every check. Panels try to refute the candidate from that tree. [176] [s66] |
| Release | The phase proves that the candidate serves traffic in health. A failed health step rolls traffic back to the prior revision. [s86] [124] |
| Operate | The phase proves that the live site stays in health. A breach writes a row back to Build or stops the project at its cap. [s107] [125] |
What has run live
Live run 1 stopped on a factory fault and spent no lap. [110] Live run 2 lost its workspace to a test run on the wrong database. [103] That loss closed the test path to the engine database. [103]
Live run 3 is the gate 1 run of the self-build. [129] It has run the Ideate, Design, and Build phases against its own brief. [176] It has not yet recorded its pass decision. [129]
A factory fault spends no lap for the customer. [110] The engine re-runs the work from the record after the fix lands. [124]