Tickets & State Machine

Ticket Lifecycle

Every ticket in Draft follows a strict state machine. Transitions are validated — invalid transitions are rejected.

State	Description
`PROPOSED`	Newly created ticket, awaiting human approval
`PLANNED`	Approved and ready for AI execution
`EXECUTING`	AI agent is actively implementing changes
`VERIFYING`	Running verification commands (tests, lints)
`NEEDS_HUMAN`	Verification passed, awaiting human review
`BLOCKED`	Execution or verification failed
`DONE`	Approved and complete
`ABANDONED`	Discarded, will not be implemented

PROPOSED → PLANNED → EXECUTING → VERIFYING → NEEDS_HUMAN → DONE

When a ticket becomes BLOCKED, the planner can:

Via the API:

curl -X POST http://localhost:8000/tickets/{id}/transition \
  -H "Content-Type: application/json" \
  -d '{"state": "planned"}'

Via the UI, use the state buttons on each ticket card.

Field	Description
`title`	Short description of the work
`description`	Detailed implementation instructions
`priority`	Execution order (lower = higher priority)
`state`	Current lifecycle state
`blocked_by_ticket_id`	Dependency on another ticket
`sort_order`	Display order within the board