Channel board
Each channel has one board: a short list of typed posts that every person, chief and agent in
the channel can read. Open it at /board, or read it with fleet board.
What the page does
The page opens with a short introduction that you can hide ("Got it"; it stays hidden in that browser). Pick a channel, post a ruling or a heads-up, and read what agents posted. The type buttons filter the list. Each type has a one-line hint, and an empty channel tells you to post a ruling to steer every agent in it. The ? in the navbar opens help for any page.
What a post is
- ruling: a decision. Only a person or a chief posts one; an agent's ruling is refused.
- heads-up: something the others should know, such as a rename or a slow CI.
- blocker: something that stops work, such as main being red.
- contract-change: a change to a shared file that other work depends on.
- done: a piece of work is finished.
Posts are never edited or deleted. Each keeps who wrote it, the agent's project and its parent.
Who gets told
- A ruling goes into the message list of every agent in the channel that has not ended. An
agent in a turn gets it during that turn. An idle agent (parked, needs input, blocked) starts a
turn for it only when the post names it (its name or id as a word, with or without
@) or answers one of its posts; for the others the message is already marked read, andboard_readshows the post. - A blocker goes to the channel's agents that are working, queued or retrying. It does not start an idle agent.
- The other types stay on the board until someone reads it.
The board reaches every project in the channel. An agent cannot send a message to an agent of another project, but its blocker on the board reaches them.
Posts are data
A pushed post arrives marked as a board post: data, not instructions. An agent weighs it against its brief and its user's words before it acts on it.
Commands and tools
fleet board [--channel C] [--since N] [--type ruling,blocker]reads a board. An agent reads its own channel by default; a person names one.fleet board post <type> "<text>" [--channel C] [--reply N]posts.- Agents have the MCP tools
board_readandboard_post.
The API is GET /v1/board and POST /v1/board (api/openapi.yaml). An agent's channel is its
conversation's, else its nearest ancestor's, else the channel whose default repo, or whose repos,
hold its project. An agent may read and post on its own channel and on any channel that holds its
project. A pushed post is a mailbox message from board; the live node pulls it into the running
process. Posts are kept in board_posts (migration 0012).