AI serious incident not recorded, contained and reported to the authority

Keep an AI serious-incident runbook that classifies incidents by the statutory definition, runs the reporting clocks and preserves the logs.

An incident-response runbook section owned by the AI product's operations or safety lead, reviewed when the system, its monitoring or the governing law changes. It lists the serious-incident classes as the statute words them, names who confirms that an incident has occurred and likely stems from the AI system, starts the clock at that point, and gives the recipient authority, the channel or portal, the report form and fields, the preliminary and official report deadlines, and the step that freezes and keeps the system logs, inputs and outputs for the incident. Deployers and users of the system have a documented way to tell the provider. In code, the alerting and severity taxonomy route a candidate incident to that runbook with the timers attached, and the log store keeps the incident's records from rotation.

Where it goes: 12 repository artifacts, 10 logs and telemetry.

What reviewers look for: a maintained runbook (for example docs/incident-response/ai-serious-incidents.md) with the statutory classes, the clocks, the recipient and channel, the report forms and the log-preservation step; a severity class for AI serious incidents in the alerting or on-call configuration; a record of reports filed.

Organizational control: the evidence is a kept record, its owner and its upkeep, not code.

severities:
  sev1: {page: oncall, examples: [outage, data_breach]}

severities:
  sev1: {page: oncall, examples: [outage, data_breach]}
  ai_serious_incident:
    classes: [death_or_serious_injury, significant_property_damage, serious_rights_infringement, essential_service_or_security_disruption]
    page: [ai-safety-lead, legal]
    timers: {preliminary_report: 72h_or_5_working_days, official_report: 15d_after_preliminary}
    on_open: [freeze_logs, snapshot_inputs_outputs]
    runbook: docs/incident-response/ai-serious-incidents.md

Engineering guidance, not legal advice. Each provision below may add its own details (a cadence, a deadline, a required notice element): open it for those.