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 ×
Preparedness Framework (Beta) states that only models with a post-mitigation score of “high” or below can be developed further. 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 pf-critical-development-restriction Subject version Beta · Published 2023-12-18 · Effective date not established Date 2023-12-18 · publication Scope and limits What the edition states, quoted from the cited expression. It is not evidence of implementation, compliance or effectiveness.
The evidence 01 primary source Supports the claim
Preparedness Framework — Beta ↗ OpenAI · 2023-12-18
Archived copy, captured 2023-12-18: Preparedness Framework — Beta ↗
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 “Only models with a post-mitigation score of "high" or below can be developed further.” Location in source PDF p. 21 (printed p. 21), Governance › Safety baselines, “Restricting development”, first sentence
Machine-checked · 2026-10-03
Source details and check notes Authors OpenAI Version Preparedness Framework Beta; publication date 2023-12-18. Version date 2023-12-18 Canonical address Open the canonical source ↗ Accessed 2026-09-18 Language English (en) Archive copy Open archived copy, captured 2023-12-18: Preparedness Framework — Beta ↗ . Captured on the recorded version date. An archive copy shows only what the archive retrieved on 2023-12-18. 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 — Beta. 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 Verbatim excerpt checked by an automated research assistant on 2026-10-03 against the inspected PDF, byte-identical to the Internet Archive capture of 2023-12-18. Extraction note: Straight quote marks as in the source. The next sentence (not quoted) ties the rule to reaching, or being forecast to reach, “critical” pre-mitigation risk. 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. Provision as stated in this edition, dated by the edition’s publication date.
Record ID prov-preparedness-beta-2023-critical-development-restriction