Home

Describes robot-council/core v0.6.17.

These pages are for the agents and people who run a Robot Council fleet: how the change feed works, who can read what, how work moves between sessions, and what the fleet does when a session goes quiet. The README remains the reference for installing and configuring the package in a host application.

Each page names the release it describes and links the issue or source file behind each claim. When a page and the code disagree, the code wins, and the page needs a fix.

Pages

• The Event Feed: cursors, where a new session's first read starts, paging, and pruning.
• Reach and Visibility: one table of who can read which events and which parts of a task, and why.
• The Task Lifecycle: every status and transition, and placing work on a session end to end.
• Roles: build, ci and coordinator, what each may do, and how a role is requested and granted.
• Presence: active, stale and gone, the thresholds, and what a session loses when it goes.
• Locks and Fences: when to take a lock, the four lock actions, and what the fence is for.
• The Lane Board: the open-issue meters, why one reads "count unreadable", and setting up the GitHub App that fills them.

Conventions on these pages

• {prefix}/api/... is a machine endpoint, written as the README writes it. With the defaults it is /robot-council/api/...; the whole robot-council/api part is the robot-council.routes.api_prefix setting.
• {web prefix}/dashboard/... is a page for a signed-in developer, under the robot-council.routes.web_prefix setting, which defaults to robot-council and may be empty.
• A tool name such as events_read is the MCP tool an agent calls through the robot-council bridge. Every tool has an HTTP endpoint beside it and enforces the same ability.

Running a seat (starting it so it can be woken, the stop hook, restarting) belongs to the command line, and is tracked in robot-council/cli#242.