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 “Pause training until ASL-3 Security Standard implemented” was found in RSP · 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: RSP · v2.2 states this provision. The inspected scope of RSP · v3.0 was: RSP v3.0 (effective February 24, 2026), whole text layer, PDF pp. 1–19: Introduction (pp. 3–4); §1 Our Recommendations for Industry-Wide Safety with the threshold table (pp. 4–9); §2 Frontier Safety Roadmap and §3 Risk Reports (pp. 10–15); §4 Governance (p. 15); Appendices A and B (p. 16); Changelog (pp. 17–19). Method: Read every section and compared it with the v2.2 provision (§6.2 'Monitoring pretraining', PDF p. 15). Searched case-insensitively for paus, halt, stop, train, Security Standard, Required Safeguards, until and comparable. No passage stating that Anthropic will pause training until the ASL-3 Security Standard is implemented was found within the operative text (wording narrowed on 2026-10-25). Hits examined and not counted: the Introduction (p. 3) discusses a hypothetical developer that paused development; Appendix A (p. 16) states two different delay commitments, recorded as separate provision records: with Anthropic in the lead, to delay AI development and deployment as needed to achieve a strong argument that catastrophic risk is contained, until and unless it no longer believes it has a significant lead; where competitors have strong safety measures, to delay them as needed until it can meet or exceed their risk reduction posture. Neither is a pause of training tied to a named security standard, and the third scenario (general upleveling) does not necessarily involve delay; ASL-3 Security Standard and Required Safeguards occur only in the reproduced changelog entries for v2.0–v2.2 (pp. 17–19). The conclusion is bounded by that scope and method.
Provision Required action · provision ID rsp-pause-training Subject version v3.0 · Published 2026-02-24 · Effective 2026-02-24 Date 2026-02-24 · effective 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
Responsible Scaling Policy — v3.0 ↗ Anthropic · 2026-02-24
Archived copy, captured 2026-02-24: Responsible Scaling Policy — 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 “Pause training until ASL-3 Security Standard implemented” was found.
Location in source RSP v3.0 (effective February 24, 2026), whole text layer, PDF pp. 1–19: Introduction (pp. 3–4); §1 Our Recommendations for Industry-Wide Safety with the threshold table (pp. 4–9); §2 Frontier Safety Roadmap and §3 Risk Reports (pp. 10–15); §4 Governance (p. 15); Appendices A and B (p. 16); Changelog (pp. 17–19).
Machine-checked · 2026-10-03
Source details and check notes Authors Anthropic Version Responsible Scaling Policy v3.0; effective date 2026-02-24. Version date 2026-02-24 Canonical address Open the canonical source ↗ Accessed 2026-09-18 Language English (en) Archive copy Open archived copy, captured 2026-02-24: Responsible Scaling Policy — v3.0 ↗ . Captured on the recorded version date. An archive copy shows only what the archive retrieved on 2026-02-24. It does not prove what the page said earlier, and it can differ from the copy checked on 2026-09-18.Attribution Anthropic, Responsible Scaling Policy — 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 every section and compared it with the v2.2 provision (§6.2 'Monitoring pretraining', PDF p. 15). Searched case-insensitively for paus, halt, stop, train, Security Standard, Required Safeguards, until and comparable. No passage stating that Anthropic will pause training until the ASL-3 Security Standard is implemented was found within the operative text (wording narrowed on 2026-10-25). Hits examined and not counted: the Introduction (p. 3) discusses a hypothetical developer that paused development; Appendix A (p. 16) states two different delay commitments, recorded as rsp-competitor-lead-delay and rsp-competitor-parity: with Anthropic in the lead, to delay AI development and deployment as needed to achieve a strong argument that catastrophic risk is contained, until and unless it no longer believes it has a significant lead; where competitors have strong safety measures, to delay them as needed until it can meet or exceed their risk reduction posture. Neither is a pause of training tied to a named security standard, and the third scenario (general upleveling) does not necessarily involve delay; ASL-3 Security Standard and Required Safeguards occur only in the reproduced changelog entries for v2.0–v2.2 (pp. 17–19). 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 effective date.
Record ID absent-rsp-v3-0-pause-training