ADR-0002: Keep the Task lifecycle small

• Status: Accepted
• Date: 2026-09-10

Context

Encoding every subworkflow as Task.status creates combinatorial transitions and makes UI loading/progress states into domain states.

Decision

Task states are BACKLOG, READY, WORKING, NEEDS_YOU, REVIEW, and DONE. Planning, review progress, verification, Run startup, and worktree setup have separate lifecycles.

Consequences

Board/List/Tree all use the same small Task status. Subordinate state is shown as badges/details.

Change rule

If implementation evidence proves this wrong, update the canonical architecture/product document first and then supersede/amend this ADR. The ADR is not allowed to keep current docs stale.