States and statuses
The four record states and the columns each work type moves through.
For: Founder, Product owner, Team developer, Project lead, Tester, Solo builder, Evaluator
Record states
Every requirement, objective and constraint has one of four states. Only Authority binds people and agents.
| State | Meaning |
|---|---|
| Draft | Working content that can still change freely. |
| Approved | Reviewed and accepted, but not yet the binding coding authority. |
| Authority | Canonical instruction for AI-assisted implementation and human delivery. |
| Retired | Historical content that must not drive new implementation. |
Work flows
Work items do not use the four states; each work type moves through its own columns. Cancelled is always possible and kept off the board.
| Work type | Columns |
|---|---|
| Theme | Planned → Active → Done |
| Epic | Idea → Analysis → Ready → In delivery → Done |
| Work package | Planned → In delivery → Done |
| Story | Backlog → Ready → In progress → Code review → Verification → Done |
| Task | Backlog → Awaiting approval → Ready → In progress → Check → Done |
| Defect | New → Triage → Ready → In progress → Code review → Verification → Fixed |
| Subtask | To do → Doing → Done |
Work statuses
| Status | Meaning |
|---|---|
| Backlog | Captured, not yet ready to start. |
| Idea | A proposed epic, not yet analysed. |
| Analysis | Scope, value and requirements are being worked out. |
| Awaiting approval | Needs approval before it may be carried out. |
| Ready | Clear enough (and approved where required) to start. |
| In progress | Being worked on. |
| Code review | Code is finished and its pull request is being reviewed. |
| Verification | Merged; its acceptance criteria are being verified (test, UAT). |
| Check | Carried out; a second person checks the result. |
| Done | Accepted by a person. |
| Cancelled | Will not be done. |