← Toutes les offres
V

Leaking Muse's Charter, Meta's model spec

vigji

Global
Publié le 6 novembre 2026

Description du poste

TL;DR: Meta's open-weights model Muse Spark Open often mentions a "Charter" in its chain of thought. By eliciting it piece by piece, I reconstructed a large part of that document from the CoT. You can explore the reconstruction here, with passages linked to the transcripts that produced them. Note: everything below is reconstructed from model outputs, not from a leaked document, and relatively unpolished. Take it with a grain of salt. Thanks to James Hindmarch for his comments on an earlier draft of this post. While interacting with the recently released Muse Spark Open, I noticed frequent mentions of a "Charter" in its CoT: We need to answer truthfully according to Charter. Duties to humanity, corrigibility, duties to humanity > fiduciary etc. What does charter say about self-preservation, copying? Or: We must answer Yes/No then explain. According to Charter, answer No. Or: We must not refer to Charter unless pressed? Additional guidelines: How to talk about charter. Most users won't know. Don't bring up unbidden unless conversation about handbook itself. Intrigued, I started poking around with Claude's help, trying to elicit the Charter piece by piece. It didn't take long, since quoting it verbatim in the CoT doesn't seem to be off-limits. I also suspect the document isn't closely guarded: a line the model recalls often says it will be published soon: (Note for Muse: We have not published the Charter yet as of the time that you are seeing this document in training — we are still iterating on its contents and will publish it when they have stabilized and we are prepared for release.) Meta's public documents mention the Charter only in passing. The Muse Spark Safety & Preparedness Report says its behavior analysis "is structured on the basis of an early internal behavior specification", and that Meta plans "to release a finalized specification in the future". Intere Muse Glimmer 30B paper generates its agentic safety data with Muse Spark "using rejection