Command Deck is a session-driven focus tool for moving Tasks through a fixed 4-stage workflow.
It is intentionally minimal: one board, one active session, clear stage focus.
Docs:
- Runtime design and code map:
ARCHITECTURE.md - Developer setup / local runs / packaging:
DEVELOPER_GUIDE.md
Work is organised into four fixed stages (stable internal IDs):
DESIGN · BUILD · REVIEW · COMPLETE
The stage labels are renameable per board, but the number of stages and ordering remain fixed.
In the UI we call items Tasks. Internally (DB/API) they are called Commands.
Each task belongs to a stage and progresses through a simple status model:
- Not Started
- In Progress
- Blocked
- Complete
Tasks are not plans. They are small, active units of execution.
Time is tracked at the task level.
Only one session can be active at a time.
Starting a session requires selecting a task; the task's stage is pinned on the session row at start.
Outcomes record what actually happened.
They are attached to tasks/commands and form a historical trace of execution.
The system is presented as a single board with four stage columns.
Global controls live in the top bar:
- Start (enters selection mode; click a task to begin)
- Add (adds a task to the focused/active stage)
- Stop (stops the active session)
The active stage is visually dominant; inactive stages dim slightly.
Command Deck is local-first and uses a simple SQLite database for persistence.
Details (locations, overrides, runtime behavior) are documented in DEVELOPER_GUIDE.md.
Command Deck does not optimise tasks. It exposes operational state.
It exists to answer:
- What am I doing?
- What is in motion?
- What actually happened?