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 “Commitment not to train or deploy without adequate safeguards” was found in RSP · v3.4 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.4 was: RSP v3.4 (effective July 8, 2026), whole text layer, PDF pp. 1–21: Introduction (pp. 3–4); §1 with the threshold table (pp. 4–10, columns on p. 9 read individually because the text layer interleaves them); §2–§3 Risk Reports (pp. 11–16); §4 Governance (p. 16); Appendix A and Appendix B (p. 17); Changelog (pp. 18–21). Method: Same reading, comparison and case-insensitive search terms as for v3.0, plus a word-level comparison with v3.3 (differences: Automated R&D threshold, Risk Report coverage date, internal sharing, redaction disclosure, external review split). No passage stating a commitment not to train or deploy models unless adequate safeguards are implemented, or a commitment to pause training or deployment until such safeguards are in place, was found within the operative text. Hits examined and not counted: the Introduction (p. 3), §1 (p. 4) and Appendix A scenario commitments (p. 17) as in v3.0; the Appendix A introduction sentences on cautionary action and considering pausing (p. 17), as in v3.1; the reproduced RSP v2.0 changelog entry (p. 18). The conclusion is bounded by that scope and method.
Provision Required action · provision ID rsp-no-train-deploy-without-safeguards Subject version v3.4 · Publication date unknown · Effective 2026-07-08 Date 2026-07-08 · 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.4 ↗ Anthropic · Publication date unknown
Archived copy, captured 2026-07-10: Responsible Scaling Policy — v3.4 ↗
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 “Commitment not to train or deploy without adequate safeguards” was found.
Location in source RSP v3.4 (effective July 8, 2026), whole text layer, PDF pp. 1–21: Introduction (pp. 3–4); §1 with the threshold table (pp. 4–10, columns on p. 9 read individually because the text layer interleaves them); §2–§3 Risk Reports (pp. 11–16); §4 Governance (p. 16); Appendix A and Appendix B (p. 17); Changelog (pp. 18–21).
Machine-checked · 2026-10-03
Source details and check notes Authors Anthropic Version Responsible Scaling Policy v3.4; effective date 2026-07-08. Version date 2026-07-08 Canonical address Open the canonical source ↗ Accessed 2026-09-18 Language English (en) Archive copy Open archived copy, captured 2026-07-10: Responsible Scaling Policy — v3.4 ↗ . Captured 2 days after the recorded version date. An archive copy shows only what the archive retrieved on 2026-07-10. 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.4. 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: Same reading, comparison and case-insensitive search terms as for v3.0, plus a word-level comparison with v3.3 (differences: Automated R&D threshold, Risk Report coverage date, internal sharing, redaction disclosure, external review split). No passage stating a commitment not to train or deploy models unless adequate safeguards are implemented, or a commitment to pause training or deployment until such safeguards are in place, was found within the operative text. Hits examined and not counted: the Introduction (p. 3), §1 (p. 4) and Appendix A scenario commitments (p. 17) as in v3.0; the Appendix A introduction sentences on cautionary action and considering pausing (p. 17), as in v3.1; the reproduced RSP v2.0 changelog entry (p. 18). 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-4-no-train-deploy-without-safeguards