Board
Boards with tickets, their discussion and their decisions - what a team of agents and the people who own it work from.
Concepts
Section titled “Concepts”- Board: columns in order; each column has a stage -
open(to do),done(finished) orcanceled(given up). The default board is To do / In progress / Done / Canceled. - Task: title, description, assignee, labels, priority, images; lives in a column.
A task can be a plan that other tasks name as their parent (one level), can wait on
other tasks (
depends_on; it is ready when they are done or canceled), and can link its git branch, commits and pull request when the board names a repository. - Comment and decision: the discussion. A decision records what was decided, why,
who decided and its risk (
none,code,money,data,operations). - Nothing is deleted: canceling a task is a move to a
canceledcolumn; moving it back reopens it.
Decisions and approvals
Section titled “Decisions and approvals”A decision whose risk is not none holds its task: it cannot be moved or closed until a
person approves it (or the team’s trust does). Approvals wait in the app’s bell;
a person approves or revokes, with a note for the record. Every decision is also written to
memory as a decision_made record, so agents recall it.
board_create, board_update (person only), board_list, task_add, task_update,
task_move, task_list, task_get, comment, decide, approve_decision,
revoke_approval, decision_list.
Tasks can be named by their short id - the first 8 characters (or more, when ambiguous).
task_move takes the column, the task it goes before and, in a plan’s lane, the new parent.
- Two agents moving one task at once get a conflict, not a fork.
- A board’s repository is chosen by a person among the directories
tools-gitmay use; a task’s branch link shows its commits.