How it works
Stages: todo → doing → built (code-complete, not live) → deployed (live, unverified) → done (verified live); a root task shows its least-advanced sub-task's stage.
Estimate of a root task with sub-tasks = sum of its sub-tasks. Left = estimate − spent, zero only when done.
Dates: each owner has one queue across all root tasks, in list order. An item starts after the hours queued ahead of it and ends (ETA) when its own left-hours are worked at hours/day; weekends optional; no owner = its own queue.
Notes are Markdown (headings, lists, - [ ] tasks, tables, links, code) or, if they start with <, HTML — shown through an allow-list, so scripts, styles, images and event handlers are removed.
Accounts: anyone can view; sign in (editor / admin) to change things. Several people can edit at once — simultaneous saves are merged field by field. Reports makes a live link to the whole tracker or one root task, either public (no login) or login-only; public ones leave out notes and checklists unless you include them. Activity shows who changed what. Account has your password and API tokens for MCP (POST /mcp lets Claude read and edit this tracker).
Backlog: a ranked list of ideas and unscheduled work. It has no ETA and delays nothing; Promote to root task moves an item to the end of the task list (lowest queue priority), and Backlog on a task that has not started sends it back.
Keys: / filter · n new root task · Esc clears the filter. Deleting offers Undo. Opened as a plain file (no server) it saves in this browser only.