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 “Putting deployment or development on hold pending mitigations” was found in FSF · v3.0 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: FSF · v2.0 states this provision. The inspected scope of FSF · v3.0 was: PDF pp. 1–16, all sections, tables and footnotes. Method: Read §1.4 Response Plans and Mitigations (PDF p. 6), §1.6 (PDF pp. 6–7), §2.1.2 (PDF pp. 8–9) and §3.1.2 (PDF pp. 12–13) in full; searched for “hold”, “pause”, “halt”, “stop”, “suspend”, “delay” and “until adequate”. No passage stating that deployment or further development may be put on hold until adequate mitigations can be applied was found; the nearest passages are the pre-deployment reviews (§2.1.2 and §3.1.2, step 2) and the closing paragraphs of those sections on preventing models posing unacceptable risk from being deployed. The conclusion is bounded by that scope and method.
Provision Required action · provision ID fsf-hold-pending-mitigations Subject version v3.0 · Published 2025-09-22 · Effective date not established Date 2025-09-22 · publication 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.
The evidence 01 primary source Supports the claim
Frontier Safety Framework — v3.0 ↗ Google DeepMind · 2025-09-22
Archived copy, captured 2025-09-22: Frontier Safety Framework — v3.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 Within the inspected scope, no passage stating the provision “Putting deployment or development on hold pending mitigations” was found.
Location in source PDF pp. 1–16, all sections, tables and footnotes
Machine-checked · 2026-10-03
Source details and check notes Authors Google DeepMind Version Frontier Safety Framework v3.0; publication date 2025-09-22. Version date 2025-09-22 Canonical address Open the canonical source ↗ Accessed 2026-09-18 Language English (en) Archive copy Open archived copy, captured 2025-09-22: Frontier Safety Framework — v3.0 ↗ . Captured on the recorded version date. An archive copy shows only what the archive retrieved on 2025-09-22. 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 — v3.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 Absence recorded by an automated research assistant on 2026-10-03. Method: Read §1.4 Response Plans and Mitigations (PDF p. 6), §1.6 (PDF pp. 6–7), §2.1.2 (PDF pp. 8–9) and §3.1.2 (PDF pp. 12–13) in full; searched for “hold”, “pause”, “halt”, “stop”, “suspend”, “delay” and “until adequate”. No passage stating that deployment or further development may be put on hold until adequate mitigations can be applied was found; the nearest passages are the pre-deployment reviews (§2.1.2 and §3.1.2, step 2) and the closing paragraphs of those sections on preventing models posing unacceptable risk from being deployed. 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 publication date.
Record ID absent-fsf-v3-0-hold-pending-mitigations