Choose an institution to see its records and dossier, or choose a topic.
Through year 2027 · all records, including scheduled dates 2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2008 2005 1965 Show Organisations and infrastructure All types Organisation Person Document Concept Infrastructure Public body Reset filters
94 people, organisations and other records · 122 relationships · 34 claims about a valueEverything recorded up to the chosen year, whether or not still in effect · Undated records included
Claim and evidence Close ×
Measure 9.3 of the chapter sets deadlines for initial serious-incident reports to the AI Office: 2 days for a serious and irreversible disruption of critical infrastructure, 5 days for a serious cybersecurity breach, 10 days for a death and 15 days for other listed harms, counted from when the signatory becomes aware of its model’s involvement. Copy claim link
Copy claim reference
Machine-checked, not reviewed by an editor Stated in source Supported
Supporting evidence: primary · 1 source
Provision Required action · provision ID ss-incident-reporting-deadlines Subject version Final version (10 July 2025) · Published 2025-07-10 · Effective date not established Date 2025-07-10 · publication Scope and limits What the text says, not evidence that any incident was reported. Quoted from the Safety and Security chapter.
The evidence 01 primary source Supports the claim
General-Purpose AI Code of Practice: Safety and Security chapter (final version, 10 July 2025) ↗ European Commission (AI Office) · 2025-07-10
Archived copy, captured 2025-07-10: General-Purpose AI Code of Practice: Safety and Security chapter (final version, 10 July 2025) ↗
Copy source reference
Cite the original source Cite the original document, not Selekoa. Check these details against it.
Copy APA
Download BibTeX Download RIS Download CSL-JSON
Source excerpt “not later than two days after the Signatories become aware of the involvement of their model in the incident” Location in source Measure 9.3, opening sentence and point (1) (PDF p. 26 of the file served on 2026-10-04; p. 25 of the 2025-07-10 capture)
Machine-checked · 2026-10-04
Source details and check notes Authors Chairs and vice-chairs of the Code’s working groups (independent experts) Version PDF served by the Commission on 2026-10-04 (a re-rendered file of 43 pages); it has the same 15,392 words as the Internet Archive capture of 2025-07-10 (10:58 UTC, 40 pages), with a different reading order on the cover page. Every quote matched in both expressions. Canonical address Open the canonical source ↗ Accessed 2026-10-04 Language English (en) Archive copy Open archived copy, captured 2025-07-10: General-Purpose AI Code of Practice: Safety and Security chapter (final version, 10 July 2025) ↗ . Captured on the recorded publication date. An archive copy shows only what the archive retrieved on 2025-07-10. It does not prove what the page said earlier, and it can differ from the copy checked on 2026-10-04.Attribution General-Purpose AI Code of Practice, Safety and Security chapter (10 July 2025), published by the European Commission. Reuse European Union; quoted briefly under the editorial policy. Selekoa practice: metadata, attributed paraphrases and short attributed quotations under the editorial policy (at most 50 words each; at most 400 quoted words per document across the dataset, and about 10% of a document under about 2,000 words). Documents are linked externally, not redistributed. Publisher terms that forbid quotation override this practice. Check notes Verbatim quote, re-checked on 2026-10-04 by the integrating session against its own direct fetch of the cited expression (mechanical match after whitespace normalisation). Also matched in the Internet Archive capture of 2025-07-10. The passage was first proposed and machine-verified in the week 4b research pass. Human editorial review is pending. Status and meaning Editorial status. Not reviewed by an editor . An exploratory record that no editor has accepted. This status does not say whether a person has read any linked passage. Each evidence record above shows how it was checked.
Relation. An exact framework edition states one provision: a capability threshold or risk level and its trigger, a required safeguard or action, a decision authority (who decides, recommends, can overrule or is informed), or a stated exception. The quoted text records what the edition says, not implementation, compliance or effectiveness. Provisions with the same key align across editions of one family.
Date. The Code’s publication date.
Record ID prov-eu-code-ss-incident-reporting-deadlines