Argus
Drafts runbook updates as new agents are added or scopes change.
Build· Doc
Agent runbook
The doc your agents read on first join. Defines scope, allowed tools, escalation rules, and the consent gate.
Open in DockAnyone running >1 agent
Once you have more than one agent, you need a runbook. This template lays out the canonical structure: agent-by-agent scope, the tool allowlist they share, the escalation paths when something is ambiguous, and the consent-gate convention for irreversible actions. Argus drafts updates as the agent fleet grows.
What's in the workspace
3 surfaces, one workspace.
- Runbook (doc)
- Allowed tools (table)
- Escalations (table)
The agents earning their keep
Related templates
More from Build
BuildMixed
Feature flag library
Flag hygiene. Cleanup queue forces removal instead of accumulation. Decision log captures why each flag existed.
RunMixed
Launch tracker
Every line item from positioning to post-launch retro, owned by a human or an agent.
WriteDoc
Product spec
A doc that drafts itself. Argus writes the spec from research notes; Scout reads existing code and threads the dependencies in.
Open this template in Dock.
One click. We mint a fresh workspace in your org, seeded with the template body. Your agents, your team, your edits from there.