Claim and evidence Close ×
Frontier AI Framework v1.1 states that chemical and biological risks are within its scope, that red teaming is conducted when relevant capability levels are reached, with external experts where appropriate, and that a release decision is taken on the residual risk left after evaluations and mitigations, with leadership able to require further testing, information or mitigation first. Copy claim link
Copy claim reference
Machine-checked, not reviewed by an editor Stated in source Supported
Supporting evidence: primary · 1 source
Provision Statement · provision ID meta-faf-v1-1-cb-risk-process Subject version v1.1 · Published 2025-02-03 · Effective date not established Date 2025-02-03 · publication Scope and limits What the edition states, at policy level. It is not evidence of implementation, compliance or safeguard effectiveness, and it names no model. The edition was read only by the cross-family machine check of 2026-10-30, in the archive capture the source names; this admission could not reach the Internet Archive, so the reading is not independently repeated here. The provision kind is `statement`, the dataset’s kind for a document’s stated content, because the schema’s other kinds require a verbatim quotation of the edition and none could be taken. Policy-level provisions only; the edition’s threat-scenario and evaluation detail was excluded by the check and is not recorded.
The evidence 01 primary source Supports the claim
Frontier AI Framework — Version 1.1 ↗ Meta · 2025-02-03
Archived copy, captured 2025-02-13: Frontier AI Framework — Version 1.1 ↗
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 Chemical and biological risks are in scope; red teaming is conducted when relevant capability levels are reached, with external experts where appropriate; and release decisions rest on residual risk after evaluations and mitigations, with leadership able to require further testing, information or mitigation.
Location in source PDF pp. 3, 8, 13 and 16–18; §2.1.2 and Table 1
Machine-checked · 2026-10-30
Source details and check notes Authors Meta Version Frontier AI Framework, Version 1.1, as captured by the Internet Archive on 2025-02-13, the earliest complete capture located. The original address has returned HTTP 500 since April 2026; a revised expression under the same label was captured from 2025-03-28 and is recorded separately. Version date 2025-02-03 Canonical address Open the canonical source ↗ Accessed 2026-10-03 Language English (en) Archive copy Open archived copy, captured 2025-02-13: Frontier AI Framework — Version 1.1 ↗ . Captured 10 days after the recorded version date. An archive copy shows only what the archive retrieved on 2025-02-13. It does not prove what the page said earlier, and it can differ from the copy checked on 2026-10-03.Attribution Meta, Frontier AI Framework, Version 1.1 (2025). 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 Added at the admission of the AI and biosecurity pack (research/ai-bio). The edition could not be read for the candidate pack or at admission: the publisher’s address failed and the Internet Archive refused this environment throughout. On 2026-10-30 the cross-family machine check opened the Internet Archive capture of 13 February 2025 (web.archive.org/web/20250213105620/https://ai.meta.com/static-resource/meta-frontier-ai-framework/), which is the expression the dataset source already names, and reported the edition’s policy-level provisions. This record rests on that reading, which this admission could not repeat. The passage is Selekoa’s policy-level paraphrase of what the check reported, not a quotation of the edition. No human editorial review. 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, or another document with an exact expression, 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), a stated exception, or another statement of its content, such as a licence term or a prospectus statement. The passage records what the document says, not implementation, compliance or effectiveness. Provisions with the same key align across editions of one family.
Date. Provision as the edition states it, dated by the edition’s publication date, 3 February 2025, as the dataset records it. The capture read is of 13 February 2025.
Record ID ab-fw-meta-faf-v1-1-cb-risk-process