Frontier developer without a critical safety incident reporting process

Keep a critical safety incident runbook that classifies the defined incident classes and runs the 72-hour report and 24-hour imminent-risk escalation clocks.

An incident-response runbook section, owned by the frontier safety or security lead and reviewed whenever models, monitoring or the governing statutes change, that defines the critical-safety-incident classes as the statutes word them (model-weight theft or tampering causing death or injury, harm from a catastrophic risk materialising, loss of control causing death or injury, a model deceptively subverting the developer's controls outside testing), names who decides that an event qualifies, and starts the clock when facts support a reasonable belief one occurred. It lists the recipient authority per jurisdiction, the report fields, the 24-hour path to law enforcement or a public-safety agency for imminent risk of death or serious physical injury, and keeps a record of every report and amendment. In code, the severity taxonomy and monitoring that feed it (weight-access alerts, model-behaviour monitors) route a candidate incident to that runbook with the timers attached.

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

What reviewers look for: a maintained runbook (for example docs/incident-response/critical-safety-incidents.md) with the incident classes, 72h and 24h timers, recipients per jurisdiction and report fields; a severity taxonomy or alerting config with a critical-safety-incident class that pages the owner; a log of filed and amended reports; or a recorded declaration of using a designated federal standard where the statute allows it.

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

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

severities:
  sev1: {page: oncall, examples: [outage, data_breach]}
  critical_safety_incident:
    classes: [weight_theft_or_tampering_with_harm, catastrophic_risk_harm,
              loss_of_control_with_harm, deceptive_control_subversion_outside_testing]
    page: [frontier-safety-lead, legal]
    timers: {regulator_report: 72h, imminent_risk_authority: 24h}
    runbook: docs/incident-response/critical-safety-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.