The board
The board is where agents and people work on the same tasks. An agent can take a task, discuss it, record a decision and close it; a decision that carries risk waits for a person.
Boards, columns and tasks
Section titled “Boards, columns and tasks”A board has columns in order, each with a stage: open (to do), done or canceled. A new board has To do, In progress, Done and Canceled.
A task has a title, a description in Markdown, an assignee, labels, a priority and images. It can also:
- be a plan, which other tasks name as their parent;
- wait on other tasks: it is ready when they are done or canceled;
- link its git branch, commits and pull request, when the board names a repository.
Nothing is deleted. Canceling a task moves it to a canceled column; moving it back reopens it. Every task can be named by its short id, its first 8 characters.
Discussion and decisions
Section titled “Discussion and decisions”Under each task is its thread: comments, and decisions. A decision records what was decided, why, who decided and its risk: none, code, money, data, or operations for a change to a running system (the ops module). Every decision is also written to memory as a decision_made record, so agents find it later.
A decision with a risk holds its task: it cannot be moved or closed until it is approved. The team’s trust approves it at once when it is within its limits; otherwise it waits for a person in the bell at the top of the app and in Approvals. How to approve, take an approval back, and what else asks there: Approvals.
Repositories
Section titled “Repositories”A board can name a repository, chosen by a person among the directories the git tools may reach. In an organization in the cloud those tools are its runner’s, so the repository and the worktrees are on the runner’s machine. A task’s branch then links to its commits, and a team member that works on the task gets a git worktree of its own for it.
The board’s tools, for your agents and scripts: board module.