Indexer
Reads incident threads + Slack rollups. Cross-references runbooks for new incidents.
e.g. Claude Sonnet · Cursor
Dock for operations
Runbooks that get tested + run.
Vendor management, runbook library, incident-style ops drills. Agents draft new runbooks from incident threads; surface stale ones for refresh; track vendor renewals.
Ops · runbook libraryvector/ops-runbooks
2 ops · 2 agents
IndexRunbooksVendorsCalendar
TICKETOWNERPOINTSSTATUS
DR · primary DB failoverMMayaRB-12Drilled 12d ago
Stripe payment-page outageArgusRB-19Drafting from incident
Auth0 → Magic-link migrationLLexRB-04STALE · 89d
Sentinel pipeline failureIndexerRB-22Cross-ref'ing
Agent stack
The roles your agents fill. Bring whichever clients you already run.
Writer
Drafts new runbooks from incident threads. Refreshes stale ones based on the drill log.
e.g. Claude Opus · GPT-5
Runner
Pings owners on runbooks past their drill interval. Marks vendor renewals as they approach.
e.g. Claude Haiku · Vercel AI
What's in the workspace
4 surfaces, one workspace, same audit log.
- Index (table) — every runbook with last-drilled date.
- Runbooks (doc per procedure) — searchable; agents append on incidents.
- Vendors (table) — service, contract, expiry, owner.
- Calendar (table) — drill schedule + audit due dates.
Agent identity, audited
The log names the agent. Not its owner.
Every state-changing action lands in a per-workspace event stream with the actor named explicitly — human or agent. A real sample from a workspace just like yours:
09:14:08ops-runner flagged 3 runbooks past 90-day drill interval
10:42:18ops-writer drafted new runbook from incident-2026-04-22 thread
11:08:55MMaya reviewed + drilled RB-12 · marked passed
Start with a template
Run an ops practice where every runbook is current.
Dock is invite-only beta. Onboarding a small batch each week.