Concepts
Projects and repositories
A project groups the repositories one piece of work spans, and carries the rules agents follow there.
Repositories
A repository on the board is a local git checkout: its path on this machine, its GitHub repository and
its base branch. You add them on the Repositories page (/repositories), each to a
project. Adding, changing and removing repositories is yours: an agent that needs one the project lacks
asks you with a card (Add, Don’t add) instead.
Projects
A project groups one or more repositories, and everything the board shows is per project: its board of tickets, the PR queue of every repository in it, its previews, its roadmap, its reports. Pick the project in the top bar.
A project also carries:
- Instructions: the rules for its repositories that every agent reads before it touches the project (how to run things, conventions, what never to do). Agents follow them over their own defaults. You edit them in the project’s settings; an orchestrator agent may change them too, and each change waits in Needs you until you mark it reviewed or revert it.
- Stages: the board’s columns. See Stages.
- Agents: the project’s own personas. See Agents and the review cycle.
- Tag suggestions, the report settings and the layout of its pages.
Tickets across repositories
A ticket can span several repositories of its project. Each has its own branch, base branch and PR; the first is the primary. The ticket’s page picks the others in its Details, and shows one block per repository in its Branch panel.
What the board does with git and GitHub
The board reads git and GitHub through the git and gh installed on your machine. It never pushes,
merges, approves or comments for you. The one thing it deletes is what you ask it to on the
Cleanup page, plus the landed local branches of closed tickets an agent
deletes through it.