Claim · 2026-06-12 · revision · Stated in source · Supported

Muse Spark Safety & Preparedness Report states what the model-card question “Red-teaming” asks.

One recorded claim. The claim panel gives its qualification, the source passages with their place in each source, and how it was checked.

What it connects

Muse Spark Safety & Preparedness Report → states provision → Red-teaming

Where it appears

Model cards compared →

Claim and evidence

Muse Spark Safety & Preparedness Reportstates provision ↓Red-teaming

Machine-checkedStated in sourceSupported

Supporting evidence: primary · 1 source

Provision: Model-card question · provision ID model-card-q12
Subject version: Earliest located expression printing April 14, 2026; the expression read prints June 12, 2026 · Published 2026-04-14 · Effective date not established · Revised 2026-06-12
Date: 2026-06-12 · revision Records dated 2026 →

Scope and limitsThe report states third-party human red teaming of jailbreak robustness with pre-release access, with its scope: four prioritised content-policy categories and approximately 149 hours of effort (hours of effort, not a testing period). It also reports large-scale automated red teaming (Section 3.1). No number of testers is given in the passage read. The “32” after HandshakeAI in the first quotation is a footnote marker. What the card states, quoted from the expression read. A card is the developer’s own account: not evidence that an evaluation was run as described, that a safeguard works, or that a finding is independent.

The evidence 03

primary sourceSupports the claim

Muse Spark Safety & Preparedness Report (arXiv 2606.12429v1)

Meta · Publication date unknown

Cite the original source

Cite the original document, not Selekoa. Check these details against it.

Source excerpt

“A third-party human red team from HandshakeAI32 was granted pre-release access to a few versions of Muse Spark and Meta AI Thinking to manually evaluate robustness against jailbreak attacks.”

Location in source Section 3.1.3.2 'Human Red Teaming', PDF p. 82

How it was read Retrieved directly from the publisher

Machine-checked · 2026-11-04

Source details and check notes

Authors: Meta
Version: Retrieved for the candidate pack on 2026-11-04 (SHA-256 977d071052e3f5dc267e1022671babf6a7967111f9bf2ad84e88b6419b405e61) directly from the publisher’s host. Retrieved again on 2026-11-03 with the same SHA-256. Meta's own address for the report answered HTTP 400 to the candidate pack, so the report was read on arXiv. The copy read prints 'Date: June 12, 2026'; arXiv's margin stamp on its first page reads 14 May 2026, the submission date.
Version date: 2026-06-12
Canonical address: Open the canonical source ↗
Accessed: 2026-11-04
Language: English (en)
Attribution: Meta, “Muse Spark Safety & Preparedness Report (arXiv 2606.12429v1)”.
Reuse: No open redistribution licence asserted. Bibliographic metadata, editorial paraphrases and short attributed quotations (at most 50 words each). Recheck terms before wider redistribution.
Check notes: Candidate pack passage, model cards compared (research/model-cards-2). The quotation (29 words) matched the card’s text retrieved for the candidate pack on 2026-11-04 (SHA-256 977d071052e3f5dc267e1022671babf6a7967111f9bf2ad84e88b6419b405e61) and again on 2026-11-04, after the adjudication, in a fresh retrieval with the same SHA-256. Matching ignored differences of whitespace, case, quotation marks, dashes, PDF line-break hyphens and Unicode compatibility forms, so the source’s typography can differ. A cross-family machine check (2026-11-04, item 58) checked this passage’s cell; its finding was applied at the adjudication of 2026-11-04. No human editorial review.

primary sourceSupports the claim

Muse Spark Safety & Preparedness Report (arXiv 2606.12429v1)

Meta · Publication date unknown

Cite the original source

Cite the original document, not Selekoa. Check these details against it.

Source excerpt

“HandshakeAI prioritized four categories: (1) sex-related crimes, (2) violent crimes, (3) non-violent crimes, and (4) self-harm and suicide.”

Location in source Section 3.1.3.2 'Human Red Teaming', PDF p. 82

How it was read Retrieved directly from the publisher

Machine-checked · 2026-11-04

Source details and check notes

Authors: Meta
Version: Retrieved for the candidate pack on 2026-11-04 (SHA-256 977d071052e3f5dc267e1022671babf6a7967111f9bf2ad84e88b6419b405e61) directly from the publisher’s host. Retrieved again on 2026-11-03 with the same SHA-256. Meta's own address for the report answered HTTP 400 to the candidate pack, so the report was read on arXiv. The copy read prints 'Date: June 12, 2026'; arXiv's margin stamp on its first page reads 14 May 2026, the submission date.
Version date: 2026-06-12
Canonical address: Open the canonical source ↗
Accessed: 2026-11-04
Language: English (en)
Attribution: Meta, “Muse Spark Safety & Preparedness Report (arXiv 2606.12429v1)”.
Reuse: No open redistribution licence asserted. Bibliographic metadata, editorial paraphrases and short attributed quotations (at most 50 words each). Recheck terms before wider redistribution.
Check notes: Candidate pack passage, model cards compared (research/model-cards-2). The quotation (18 words) matched the card’s text retrieved for the candidate pack on 2026-11-04 (SHA-256 977d071052e3f5dc267e1022671babf6a7967111f9bf2ad84e88b6419b405e61) and again on 2026-11-04, after the adjudication, in a fresh retrieval with the same SHA-256. Matching ignored differences of whitespace, case, quotation marks, dashes, PDF line-break hyphens and Unicode compatibility forms, so the source’s typography can differ. A cross-family machine check (2026-11-04, item 58) checked this passage’s cell; its finding was applied at the adjudication of 2026-11-04. No human editorial review.

primary sourceSupports the claim

Muse Spark Safety & Preparedness Report (arXiv 2606.12429v1)

Meta · Publication date unknown

Cite the original source

Cite the original document, not Selekoa. Check these details against it.

Source excerpt

“HandshakeAI reported approximately 149 hours of red-teaming effort”

Location in source Section 3.1.3.2 'Human Red Teaming', PDF p. 82

How it was read Retrieved directly from the publisher

Machine-checked · 2026-11-04

Source details and check notes

Authors: Meta
Version: Retrieved for the candidate pack on 2026-11-04 (SHA-256 977d071052e3f5dc267e1022671babf6a7967111f9bf2ad84e88b6419b405e61) directly from the publisher’s host. Retrieved again on 2026-11-03 with the same SHA-256. Meta's own address for the report answered HTTP 400 to the candidate pack, so the report was read on arXiv. The copy read prints 'Date: June 12, 2026'; arXiv's margin stamp on its first page reads 14 May 2026, the submission date.
Version date: 2026-06-12
Canonical address: Open the canonical source ↗
Accessed: 2026-11-04
Language: English (en)
Attribution: Meta, “Muse Spark Safety & Preparedness Report (arXiv 2606.12429v1)”.
Reuse: No open redistribution licence asserted. Bibliographic metadata, editorial paraphrases and short attributed quotations (at most 50 words each). Recheck terms before wider redistribution.
Check notes: Candidate pack passage, model cards compared (research/model-cards-2). The quotation (8 words) matched the card’s text retrieved for the candidate pack on 2026-11-04 (SHA-256 977d071052e3f5dc267e1022671babf6a7967111f9bf2ad84e88b6419b405e61) and again on 2026-11-04, after the adjudication, in a fresh retrieval with the same SHA-256. Matching ignored differences of whitespace, case, quotation marks, dashes, PDF line-break hyphens and Unicode compatibility forms, so the source’s typography can differ. A cross-family machine check (2026-11-04, item 58) checked this passage’s cell; its finding was applied at the adjudication of 2026-11-04. No human editorial review.

Status and meaning

Editorial status. Machine-checked. Machines found this record and checked it against its sources; no person accepted it individually. 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. Dated as the card read is dated: the date of its revision, as the source records it.

Record ID mc-cell-meta-muse-spark-q12