AI Governance Engineer
GitHub

GPAI Code Safety and Security Commitment 9: serious-incident reporting

Report serious incidents to the AI Office within 2, 5, 10 or 15 days by incident class, with intermediate reports at least every four weeks while unresolved and a final report within 60 days of resolution; keep the records at least five years

By Reviewed

From clause to evidenceThe chain from GPAI Code Safety and Security, Commitment 9 to its evidence record, in 6 steps; the text alternative lists them and the facts under the figure state each in full.ClauseGPAI CodeSafety andSecurity,…Duty holderSignatoryproviders of…Applies fromNo dateVoluntaryArtefactIncidentpipeline…LayersLayer 04Layer 05Evidence recordAI incidentrecordSame topic elsewhere: no crosswalk topic files this clause yetAs of 2026-09-24 · illustrative, not a claim of conformity From clause to evidenceThe chain from GPAI Code Safety and Security, Commitment 9 to its evidence record, in 6 steps; the text alternative lists them and the facts under the figure state each in full.ClauseGPAI Code · Safety and Security,…Duty holderSignatory providers of GPAI…Applies fromNo date · VoluntaryArtefactIncident pipeline…LayersLayer 04Layer 05Evidence recordAI incident recordSame topic elsewhere: no crosswalk topicfiles this clause yetAs of 2026-09-24illustrative, not a claim of conformity
From clause to evidence Build the artefact, then file every output it produces as a record that names AIGE-OBL-GPAICOP-SAFETY-C9. Drawn from chapter 08.
Text alternative
  • Clause: GPAI Code, Safety and Security, Commitment….
  • Duty holder: Signatory providers of GPAI….
  • Applies from: No date, Voluntary.
  • Artefact: Incident pipeline….
  • Layers: Layer 04, Layer 05.
  • Evidence record: AI incident record.
  • Record schemas: AI incident record .
  • No crosswalk topic files this clause yet.
Id
AIGE-OBL-GPAICOP-SAFETY-C9
Instrument
GPAI Code of Practice code
Clause
Safety and Security, Commitment 9
In scope
Signatory providers of GPAI models with systemic risk
Applies from
No date Voluntary · published 2025-07-10

The artefact that evidences it

Incident pipeline on the Commission template fields; per-class clocks; five-year retention policy; downstream reporting channel.

Patterns that build it

No pattern in the catalogue names this clause on its "Maps to" line yet; the artefact above is the engineering answer.

Open controls that evidence it

Draft controls in the open control profiles that map to this row: each states a requirement and the evidence it must leave behind.

Source

Chapter 08, section GPAI Code of Practice, checked against its sources on the review date above.

Machine-readable

Cite this obligation

García Aibar, J. (2026). GPAI Code Safety and Security Commitment 9: serious-incident reporting (AIGE-OBL-GPAICOP-SAFETY-C9). In AI Governance Engineering: The Thesis & Body of Knowledge (v0.5.0). https://doi.org/10.5281/zenodo.22956197. https://aigovernanceengineer.com/obligations/aige-obl-gpaicop-safety-c9. CC BY 4.0

BibTeX

@misc{aige2026obligation,
  author       = {Jorge García Aibar},
  title        = {{GPAI Code Safety and Security Commitment 9: serious-incident reporting (AIGE-OBL-GPAICOP-SAFETY-C9)}},
  howpublished = {In AI Governance Engineering: The Thesis \& Body of Knowledge},
  year         = {2026},
  version      = {0.5.0},
  doi          = {10.5281/zenodo.22956197},
  url          = {https://aigovernanceengineer.com/obligations/aige-obl-gpaicop-safety-c9},
  note         = {Version 0.5.0}
}