The handbook

The new Handbook under Halon is where your team writes down how the workspace works, such as how you release, who owns what, what counts as production and when changes are frozen. Halon reads it at the start of every chat and investigation, follows it, and links the page it followed in its answer. See The handbook.

Three ways to start. Draft with Halon reads your resource map, repositories and past incidents and proposes a page for each thing a new teammate would need to know. Import docs brings in a file or folder from a connected repository, or a page from Notion, and keeps it in step with its source. Write a page starts blank or from a common starting page.

Every edit kept. History shows each earlier wording with who wrote it. Short pages are read whole, and a long page is searched when Halon needs it.

Halon proposes edits. When something Halon reads contradicts a page, such as releases running through a different pipeline than the page says, it works from what it read and proposes an edit, with Accept edit, Edit first and Dismiss. Proposals also wait in the handbook under Waiting for review.

Who directs Halon. When two people in an incident ask Halon for opposite things, it says so and follows the person in the role the handbook names, the Incident Lead unless you choose another.

Writing the handbook needs the handbook permission, and everyone can read it. Pages can also be managed over the API and with the list_handbook_pages, get_handbook_page, upsert_handbook_page and delete_handbook_page MCP tools.