Claim · 2026-10-23 · revision · Inferred · Supported

No passage meeting the model-card question “Release decision” was found in Muse Spark 1.3 Evaluation Report within the inspected scope.

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 1.3 Evaluation Report → has no matching provision within the inspected scope → Release decision

Where it appears

No collection page holds this claim. It is listed with its records in the explorer.

Claim and evidence

Muse Spark 1.3 Evaluation Reporthas no matching provision within the inspected scope ↓Release decision

Machine-checkedInferredSupported

Supporting evidence: primary · 1 source

Reasoning and premisesPremises: the model-card question asks for the following. A passage stating that a decision to release, deploy or launch was made (decided, chose, deemed acceptable for deployment, determined that safeguards suffice for launch), quoted. Stated if the decision is described and its maker is identifiable: a named person, office or committee, or the developer in its own voice (“we”), which counts as the company as such. Partly if a release is stated as following from an assessment without a decision being described (“we therefore release”), if a decision is described without any maker, or if a maker is named only for a capability or safeguards determination and not for the release. The inspected scope of Muse Spark 1.3 Evaluation Report was: Section 1 (including 1.2 Governance); section 2.3.1; searches across the report. Terms searched: “decision”, “decide”, “approv”, “release”, “launch”, “Chief AI Officer”, “Director of Alignment”. Passages read and not counted: Section 1.2 Governance, PDF pp. 11-12: States that the framework includes 'oversight and decisionmaking processes'; no decision about this model or its maker is stated. Section 2.3.1, PDF p. 34: 'Reliable pre-deployment evaluations help ensure deployment decisions are properly informed' is a general statement, not a decision. The conclusion is bounded by that scope and method.

Provision: Model-card question · provision ID model-card-q15
Subject version: The expression dated October 23, 2026 · Publication date unknown · Effective date not established · Revised 2026-10-23
Date: 2026-10-23 · revision Records dated 2026 →

Scope and limitsNo passage stating a release or deployment decision was found. The search is recorded below. A recorded absence within the stated scope of the card read: not evidence that the developer did not do the thing asked about, or did not disclose it elsewhere.

The evidence 01

primary sourceSupports the claim

Muse Spark 1.3 Evaluation Report

Meta · Publication date unknown

Cite the original source

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

Paraphrase

Within the inspected scope, no passage meeting the model-card question “Release decision” was found.

Location in source Muse Spark 1.3 Evaluation Report: Section 1 (including 1.2 Governance); section 2.3.1; searches across the report

How it was read Retrieved directly from the publisher

Machine-checked · 2026-11-03

Source details and check notes

Authors: Meta
Version: Retrieved for the candidate pack on 2026-11-02 (SHA-256 84df67c9f4610e574fd82f39227b0e6a266e6e1fd0e6ea21c3420f1661e0835e) directly from the publisher’s host. Retrieved again on 2026-11-03 with the same SHA-256. PDF served at the address linked from Meta's announcement of September 2, 2026; the report prints 'Date: October 23, 2026' (PDF metadata also records creation on 2026-10-23). An earlier text at the same address, if any, was not retrieved.
Version date: 2026-10-23
Canonical address: Open the canonical source ↗
Accessed: 2026-11-02
Language: English (en)
Attribution: Meta, “Muse Spark 1.3 Evaluation Report”.
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: Absence recorded for the model-cards candidate pack (research/model-cards) on 2026-11-02 by an automated research assistant and audited in a fresh context by the same model family. A cross-family machine check (2026-11-03, item 42) checked this cell and agreed with the pack. 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. 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. Dated as the card read is dated: the date of its revision, as the source records it.

Record ID mc-cell-meta-muse-spark-1-3-q15