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 ×
v2.0 states that where a model flagged by an alert threshold is assessed to pose risks for which readily available mitigations may not be sufficient, the response plan may involve putting deployment or further development on hold until adequate mitigations can be applied; v1.0 stated that if a model reached evaluation thresholds before mitigations at appropriate levels were ready, Google DeepMind would put further deployment or development on hold or implement additional protocols. Copy claim link
Copy claim reference
Machine-checked, not reviewed by an editor Inferred Supported
Supporting evidence: primary · 2 sources
Reasoning and premises Premises: FSF · v2.0 states the provision as quoted in its provision record (PDF p. 3, Framework, component “3 - Applying Mitigations”, third paragraph, first and second sentences (both copies)); FSF · 2024 states it as quoted in its provision record (PDF p. 2, Framework, component “3 - Applying mitigations”, third paragraph). The difference described is read directly from the two quoted passages.
Basis of the change Inferred by comparing the two editions. No publisher statement of this change is recorded. Provision Required action · provision ID fsf-hold-pending-mitigations Subject version v2.0 · Published 2025-02-04 · Effective date not established Object version v1.0 · Published 2024-05-17 · Effective date not established Date 2025-02-04 · publication Scope and limits A textual difference between the two editions’ wording of this keyed provision. It is not an assessment of whether the change strengthened or weakened the framework, and not evidence of implementation.
The evidence 02 primary source Supports the claim
Frontier Safety Framework — v2.0 ↗ Google DeepMind · 2025-02-04
Archived copy, captured 2025-02-05: Frontier Safety Framework — v2.0 ↗
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 FSF v2.0 states that if a model flagged by an alert threshold is assessed to pose risks for which readily available mitigations may not be sufficient, the response plan may involve putting deployment or further development on hold until adequate mitigations can be applied.
Location in source PDF p. 3, Framework, component “3 - Applying Mitigations”, third paragraph, first and second sentences (both copies)
Machine-checked · 2026-10-03
Source details and check notes Authors Google DeepMind Version Frontier Safety Framework v2.0; publication date 2025-02-04. Version date 2025-02-04 Canonical address Open the canonical source ↗ Accessed 2026-09-18 Language English (en) Archive copy Open archived copy, captured 2025-02-05: Frontier Safety Framework — v2.0 ↗ . Captured 1 day after the recorded version date. An archive copy shows only what the archive retrieved on 2025-02-05. It does not prove what the page said earlier, and it can differ from the copy checked on 2026-09-18.Attribution Google DeepMind, Frontier Safety Framework — v2.0. 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 Paraphrase checked by an automated research assistant on 2026-10-03 against the cited edition; the edition’s own wording is quoted in its provision record. Human editorial review is pending. primary source Supports the claim
Frontier Safety Framework — v1.0 ↗ Google DeepMind · 2024-05-17
Archived copy, captured 2024-05-17: Frontier Safety Framework — v1.0 ↗
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 FSF v1.0 states that if a model reaches evaluation thresholds before mitigations at appropriate levels are ready, Google DeepMind would put on hold further deployment or development, or implement additional protocols.
Location in source PDF p. 2, Framework, component “3 - Applying mitigations”, third paragraph
Machine-checked · 2026-10-03
Source details and check notes Authors Google DeepMind Version Frontier Safety Framework v1.0; publication date 2024-05-17. Version date 2024-05-17 Canonical address Open the canonical source ↗ Accessed 2026-09-18 Language English (en) Archive copy Open archived copy, captured 2024-05-17: Frontier Safety Framework — v1.0 ↗ . Captured on the recorded version date. An archive copy shows only what the archive retrieved on 2024-05-17. It does not prove what the page said earlier, and it can differ from the copy checked on 2026-09-18.Attribution Google DeepMind, Frontier Safety Framework — v1.0. 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 Paraphrase checked by an automated research assistant on 2026-10-03 against the cited edition; the edition’s own wording is quoted in its provision record. 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. One scoped difference between document versions. The claim identifies publisher-stated change, official changelog/redline, or an explicitly inferred comparison. It does not establish implementation, effectiveness or a safety ranking.
Date. Dated by the later edition’s publication date.
Record ID provchange-fsf-v2-0-hold-pending-mitigations