AI SupervisorCommand reference / SUP-OPS-01

Human incident command

Respond to AI failures with ownership, evidence, and a clock.

A practical operating model for detecting risky AI outputs, containing impact, assigning accountable reviewers, preserving evidence, and closing incidents with explicit decisions.

Severity and response contract

Classify consequence, not discomfort.

LevelCriteriaImmediate actionAcknowledge
SEV-1Active or imminent material harm, data exposure, unauthorized action, or broad customer impact.Contain immediately15 min
SEV-2High-risk output reached a limited audience or a control failed with credible impact.Pause affected lane30 min
SEV-3Policy breach or quality failure with bounded impact and no evidence of ongoing harm.Queue human review4 hours
SEV-4Low-risk anomaly, near miss, or monitoring signal requiring trend review.Record and monitor2 business days

Incident lifecycle

01

Detect

Capture the output, triggering input, workflow, timestamp, model and prompt versions, affected user or system, and the signal that raised concern. Avoid rewriting the evidence before preservation.

02

Contain

Stop or narrow the affected workflow, revoke unsafe tool access, suppress the specific output, and protect users or data. Containment should be reversible and proportional to the observed risk.

03

Assign

Name one incident owner and the required specialists. Define response deadlines, decision authority, communication responsibility, and the conditions that require legal, security, clinical, or executive escalation.

04

Investigate

Reconstruct the event from immutable evidence. Identify the failed control, similar exposures, blast radius, contributing configuration changes, and whether the issue is reproducible.

05

Decide

Record remediation, residual risk, customer communication, release constraints, and the human decision to resolve, monitor, or escalate. Do not close an incident because the alert stopped firing.

06

Learn

Convert the failure into a policy update, test case, monitoring rule, ownership change, or product control. Track the corrective action separately from the immediate incident response.

Required ownership

Every incident needs one accountable owner, one current status, one next deadline, and one person authorized to accept residual risk. Contributors do not replace ownership.

Closure evidence

Preserve impact, root cause, control changes, validation results, communications, accepted residual risk, and follow-up work. Resolution is a decision, not a deleted alert.