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 ×
No passage stating the provision “Development restriction does not preclude safety-enhancing development” was found in Preparedness · Version 2 within the inspected scope. Copy claim link
Copy claim reference
Machine-checked, not reviewed by an editor Inferred Supported
Supporting evidence: primary · 1 source
Reasoning and premises Premises: Preparedness · Beta states this provision. The inspected scope of Preparedness · Version 2 was: Version 2, both copies (Internet Archive capture of 2025-04-15 and current file), PDF pp. 1–22: §§1–5, Tables 1–3 and Appendices A (Change log), B (Decision-making practices) and C. Method: Read §1 (third bullet), §2.2 with Table 1 (Critical-capability safeguard guidelines), §4.4 and Appendices A–B; searched both text layers for “safety-enhancing”, “preclude”, “safety research”, “except”, “unless”, “halt”, “further development” and “pause”. No passage stating that restrictions on further development do not preclude safety-enhancing development was found within PDF pp. 1–22. The conclusion is bounded by that scope and method.
Provision Exception · provision ID pf-safety-enhancing-development-exception Subject version Version 2 · Published 2025-04-15 · Effective date not established · Revised 2025-04-15 Date 2025-04-15 · revision Scope and limits A recorded absence within the stated scope: not a claim that the provision was deleted, and not a statement about practice or intent. Text comparison only; no replacement between the editions is asserted by this record.
The evidence 01 primary source Supports the claim
Preparedness Framework — Version 2 ↗ OpenAI · 2025-04-15
Archived copy, captured 2025-04-15: Preparedness Framework — Version 2 ↗
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
Paraphrase Within the inspected scope, no passage stating the provision “Development restriction does not preclude safety-enhancing development” was found.
Location in source Version 2, both copies (Internet Archive capture of 2025-04-15 and current file), PDF pp. 1–22: §§1–5, Tables 1–3 and Appendices A (Change log), B (Decision-making practices) and C
Machine-checked · 2026-10-03
Source details and check notes Authors OpenAI Version Preparedness Framework Version 2; revision date 2025-04-15. Version date 2025-04-15 Canonical address Open the canonical source ↗ Accessed 2026-09-18 Language English (en) Archive copy Open archived copy, captured 2025-04-15: Preparedness Framework — Version 2 ↗ . Captured on the recorded version date. An archive copy shows only what the archive retrieved on 2025-04-15. It does not prove what the page said earlier, and it can differ from the copy checked on 2026-09-18.Attribution OpenAI, Preparedness Framework — Version 2. Reuse No open redistribution licence asserted. 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 Absence recorded by an automated research assistant on 2026-10-03. Method: Read §1 (third bullet), §2.2 with Table 1 (Critical-capability safeguard guidelines), §4.4 and Appendices A–B; searched both text layers for “safety-enhancing”, “preclude”, “safety research”, “except”, “unless”, “halt”, “further development” and “pause”. No passage stating that restrictions on further development do not preclude safety-enhancing development was found within PDF pp. 1–22. Text comparison only; it does not assert that Version 2 replaces the Beta. 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. A recorded absence: within the stated locator scope of an exact edition, no passage stating the keyed provision was found. It is not an inferred deletion and says nothing about other documents, practice or intent.
Date. Absence recorded for this edition, dated by its revision date.
Record ID absent-preparedness-v2-safety-enhancing-development-exception