Repository navigation
Add the Meta Muse Spark 1.3 model card and metadata - #220
Merged
Merged
Conversation
…efuses a forced tool
Max ruled on 2026-10-13 (d1441) that Muse Spark 1.3 joins the board in the
Gemini 4 Argon release. Meta released it on 2026-09-02 ("Introducing Muse
Spark 1.3": available that day in Muse Code and the Meta Model API). It runs
through OpenRouter, whose one endpoint for meta/muse-spark-1.3 is Meta's own
(meta/muse-spark-1.3-20260902), as Muse Wonder does.
Price: $1.25 / $4.25 per 1M input/output tokens and $0.15 cached input,
Meta's standard-mode rate at every prompt length (Meta's rate card and the
OpenRouter endpoint listing, read 2026-10-13). The contributor-mode listing
is a different endpoint and is not the board's.
Card: Meta's API accepts tool_choice "auto" only (a named-function or
"required" choice returned 400 on each of three tries), so the row runs the
JSON contract whole-scenario and reasons at the provider default (4,311 to
8,174 reasoning tokens on a one-question probe with no tools, 4,844 to
6,022 with tool_choice auto). With no forced tool there is no
reasoning-suppression sensitivity run.
Gauntlet: with no card the 3-variable JSON probe stopped at the 384-token
limit; with the reasoning budget, 3/3 and 16/16 parsed (8,163 and 4,258
completion tokens, 106s and 58s), about $0.020 per scenario. A
four-household smoke on the run path, with the board's two largest
households, parsed 96/96 in one request each for $0.11 (Meta's reported
cost equals the reconstruction from list prices).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
3 of 5 tasks
…on (card review P1, P3) P1: the card and commit 8c400c9 called the smoke's scenarios 099 and 119 (32 and 28 outputs) the board's two largest households. They are not: scenario_008 has 56 outputs, three households have 38 and two have 34. The card now gives the smoke's sizes (16, 20, 28 and 32 outputs) and rests the timeout and starting budget on the board run, which answered every household in one request, scenario_008 included: 1,984/1,984 parsed, no budget escalation, at most 96s and 9,871 completion tokens per household. The squash message will not repeat 8c400c9's claim. The card also says that the board run's four smoke households replay the smoke's responses from the harness cache (identical requests), as the two smoke households of the Muse Wonder, Haiku 5.5 and Opus 5.5 rows do. P3: the notes now say "Meta rejects forced tool choices", the wording the disclosure test classifies as a provider rejection. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reviewer's wording: the board run answered all 100 households in one request each, four of them replayed from the smoke. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis
marked this pull request as ready for review
October 13, 2026 20:09
Contributor
Author
|
Merged at reviewed head a7fbf14 (squash 30b7163). Gates: all checks pass; mergeable; no changes requested. Independent review: round 1 GPT-6.1 Sol REQUEST_CHANGES (P1 household-size claim, P3 rejection wording) fixed in eb0b819; round 2 Claude Opus 5.5 APPROVE at eb0b819, whose optional P3 wording is a7fbf14 verbatim. Reviews: ~/reviews/policybench-gemini-4-argon/musespark/card-review/. The squash message omits 8c400c9's incorrect household-size claim. The board run joins the published board in release PR #221. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.