Runbook
An executable procedure or method document, written so an agent can carry it out without the author's session. The fleet's role runbooks are the method of record for each role: mandate, operating primitives, artifacts, authority, escalation, and the role's Never list. An agent fetches its role runbook fresh at the start of an assignment and works from it, never from memory.
Estate surface
Role runbooks live in the fleet repository's docs/runbooks/,
each naming its role on its face. Procedure runbooks for the wider
estate live in this docsite's docs/09-runbooks/ — including the
fleet workflow runbook, which is the workflow of record that the
role runbooks' primitives enact.
Relations
- A runbook defines a role — the role named in its header is the role whose method it carries.
Notes
Where a role runbook and the fleet workflow runbook conflict on workflow routing, the conflict is escalated to the chief of staff, not resolved locally — runbooks are amended through the fleet's own pipeline, like any other governed document.