Skip to the content.

Response Start

If you are responding to an AI agent incident RIGHT NOW, this is your starting point. Four files, in order, take you from 3am page to a defensible 60-minute checkpoint.

The 60-minute navigation path

Minute Open Why
0–2 The AI-BOM YAML for the affected agent (per templates/ai-bom.yaml schema; one file per agent in production) Know what the agent is, what it can do, what it writes to. If you don’t have an AI-BOM for this agent, you have an inventory problem, not just an incident
2–15 triage/six-questions.md Walk the six questions in order. The “Where each answer routes” table at the end points you to the right playbook
10–20 kill-switches/overview.md At Question 5, pick the Mode (M1–M4) and variant. Use the Variant Selector quick reference for fast matching. Activation SLA: ≤ 10 minutes from IC order
30–60 framework/04-materiality-and-disclosure.md Convene the Materiality and Disclosure call if Mode ≥ M3 OR any condition trigger applies (customer data, external recipients, regulated data, financial actions, customer-facing trust, public attention). CISO + General Counsel + Incident Commander within 1 hour

During response, you may also need

After response

What this file is not

This is not a playbook. This is the entry-point map for paged responders. The disciplined response that survives a board review, a regulator inquiry, or a legal deposition is in the playbooks themselves; this file just gets you to the right playbook fast.

For adoption (not response), see QUICKSTART.md (30-day path) or QUICKSTART-startup.md (4-week startup-minimum path). For the framework’s structural reference, see MATRIX.md and CONTENT_MAP.md.


Source: AI IR Overlay framework, by Jacob Ideji.

Last revised: 2026-06-30 (v0.33.0 A1.3 navigation fix).

https://www.linkedin.com/in/jacobideji/