No ticket starts by itself. A ticket gets a worker only when a person presses Start, or when a Lead you let start tickets starts one, within the limits you set (see The Lead starts tickets). Nothing moves a ticket past Building on its own either, not even a pull request being opened or merged. The one exception: when the relay tells a Dev about review comments, it moves their task to Changes requested. The one session that starts by itself is an automatic review, which takes a desk.
The pages
| Page | What it holds |
|---|---|
| How the room works | The map of the parts, a ticket's life from idea to running code, hooks and how the relay types into sessions, what you see on the page, the guards and the trust ladder, and where the code is. |
| Running it | What starting the room does, the Claude Code panel, sessions from your own terminal, copies of the repo and branches, restarts, Update after a merge, keeping tickets in GitHub issues, and the common messages with what to do. |
| Roles and how work moves | What you need to do, what is waiting on you, the life of a ticket on the Board, how assignment works, who does what, the Lead and its permissions, reviews, huddles, and the chat board. |
| The relay API and routes | The relay's calls, errors, events and webhook, the room's window.run API, the room's own routes and tokens, relay/ticket.js, tunnels, and the limits. |
| Settings | Every environment variable, with its default, and the few settings kept in files. |
| Glossary | The words the room uses, one word for one thing. |
What is not here
- Rules. What sessions may and may not do, and why, are in docs/constitution.md and CLAUDE.md. This manual says what the code does today. Where a rule is only in a brief, it says the session "is told".
- Setup. Installing nothing, the commands to start each world, and lint and test are in README.md and office/README.md.
Changing the manual
When behavior changes, change the page that describes it in the same pull request. Describe only what the code does now. Write plain words: short sentences, one word for one thing, and no em dashes. npm test checks that every link in the manual resolves, to a file and to an id on that page, that no page has an em dash, and that no page loads a library.
Each page is plain HTML with hand-drawn SVG, and manual.css gives them one look in light and dark. The relay serves the manual at /docs/manual/, and it also opens as files with no server.