Taxonomy and severity
Incident types, impact, urgency, affected people and escalation criteria.
The first incident should not be the first time anyone asks who can stop the system.
INCIDENT OWNERSHIP · CONTAINMENT · LEARNING
Aegis Incident Readiness
Prepare the organisation to detect, contain, escalate and learn from AI incidents.
ASSURANCE LOOP
Unit of analysisSystem + portfolio
DecisionFIT · FIT WITH CONTROLS · NOT FIT YET · SPECIALIST REVIEW
EvidenceVersioned Assurance Case
ActivationHuman authorisation only
Prepare the response before it is needed
Owners and escalation
Named owners, channels, timing, authority and substitutes.
Containment
Stop conditions, permission restriction, isolation, evidence preservation and rollback.
Postmortem and re-clearance
Cause, impact, failed controls, corrective action and conditions for returning to operation.
A complete cycle, not an isolated audit
Each stage produces a decision, an accountable owner and enough evidence for the next stage not to rely on blind trust.
NeedOrbyn→DesignBlueprint→AssessmentAegis→PressureARIA→AuthorisationHuman→ObservationVigilance→RevalidationPortfolio
NEXT DECISION
Start a conversationThe first question is not what AI can do.
It is which system you are prepared to authorise, under which limits and with what evidence.