Model work as a dependency graph and let the ready queue tell you, and your coding agents, what is actually unblocked.
Every board holds a dependency graph, so the ready queue always shows exactly the work that is actually unblocked.
Lay work out as a graph instead of a list. A task node points at the task nodes it unblocks, and the board refuses anything that would introduce a cycle.
Every task whose prerequisites are all completed surfaces here automatically, ordered by priority and then by a rank you drag. Nothing to groom by hand.
Make a calendar date a prerequisite. It completes itself at the start of that date in the workspace time zone, and reached boundaries stay reached when the zone changes.
An agent key lets an external coding agent discover ready tasks, claim one exclusively, and report completion — without any other access to the workspace.
Completed tasks leave the graph but keep their records. Restore one and it comes back with its prerequisites, without reblocking anything downstream.
Claims, completions and new dependencies arrive over a live channel, so two members looking at one board never see two different graphs.
Invite members, promote admins, and hand ownership over. Seats are billed per active membership, and pending invitations cost nothing.
Bring your own identity provider for sign-in, and let directory sync keep membership in step with your directory.
Subscribe to workspace events, and keep a record of who changed what — both scoped to the workspace they belong to.
An owner can take a portable representation of a workspace's work out of the application at any time, including while the workspace is restricted.
Store the exact Markdown instructions a task needs. Members read the rendered form; agents and copy actions receive the source text verbatim.
Personal workspaces are free up to fifty active task nodes; team workspaces are billed per seat with no board or task-node limits.
The personal plan: one private workspace that is yours from the moment you sign up.
The team plan: shared workspaces billed per active member, with the limits removed.
Coding agents claim ready tasks with a revocable agent key, so a board's dependency graph stays the single source of truth.
A. One dependency graph, its ready queue, and its completion history. Task nodes depend on other task nodes or on date nodes, and the graph is always kept acyclic.
A. A task node reaches the ready queue as soon as every direct prerequisite is completed. The queue is ordered by priority — P0, P1, P2 — and then by a rank you control by dragging.
A. A workspace-wide agent key lets an external agent discover ready task nodes, claim one exclusively, then complete or release it. Members can force a claim to be released at any time, and revoking a key never strands a claim you cannot clear.
A. The same node comes back with its incoming prerequisites intact, its outgoing dependencies removed, and every earlier completion record preserved. Tasks it previously unblocked are never reblocked.