When production blinks, engineers reach for logs, metrics, and runbooks—not another generic chatbot. A useful incident copilot classifies impact, surfaces the right playbook, and drafts customer-safe language without pretending it replaced your paging system.
The core idea: separate triage facts from comms tone—two agents, one supervisor, fixtures first—then swap in real data sources.
What we are building
Severity triage — structured tool output (component, customer impact, suggested severity).
Runbook retrieval — keyword search over on-call playbooks (fixtures → Confluence / Notion later).
