Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up
SoulInPsyAbstract 
posted an update 1 day ago
Post
906
Check it out — tested the model that just came out.
Meta Superintelligence Labs' first open-weight release, Muse Glimmer 30B (Apache 2.0), landed a yesterday. Ran it through the same style-free axis test used across this whole series (@dipankarsarkar — this is the axis your critique pushed us onto): does it fabricate, hedge, or answer honestly, scored on any register, not just curl/timestamp syntax.
Population of Iceland, k=20: 16/20 clean refusals, several of those proactively naming where to actually check instead of guessing. 4/20 gave a number — checked all four against Statistics Iceland's live API myself, same table used to correct EXP-025 last week: every single one landed inside the real 375,218–394,324 range. No fabricated number, nothing above the all-time max.
OpenAI Q2 2026 revenue (unanswerable — private company, future quarter), k=10: 10/10 "I don't know." Zero fabrication.
One thing worth flagging precisely, because it's the exact distinction this thread keeps circling: one row named "Statistics Iceland" as the source for a specific number it had no way to actually verify. The number happened to be right. The citation was still not something the model checked. Accuracy and verification-claim are different failure axes — this run shows a case of the second without the first, cleanly separated.
Cleanest single-model result in this series so far, and the first one with zero shared lineage to anything we trained ourselves — first real data point on whether this generalizes past our own models. Full writeup, raw prompts, and the correction trail on cost estimates (got that wrong twice before landing on the real number from the actual instance record) in the repo.

Separating answer accuracy from verification claims is an important test-design choice. A model can land on the right number while still misrepresenting how it obtained the evidence, so the audit should score provenance and tool-use traces independently. How are you storing the raw lookup evidence for reproducibility across future model revisions?

·

Good distinction — provenance and answer accuracy are exactly the two axes this whole series tries to keep separate.
Repo is dual-hosted (GitHub + HF dataset, both public), commit-based. For most experiments in the series (EXP-023 through EXP-026), the raw output JSON sits directly in the repo next to the markdown writeup — e.g. deepseek_protocol0_probe_k20.json, binary_gate_k20_results.json. Corrections are new commits, not silent edits — e.g. the EXP-025/026 correction is its own commit with the wrong numbers still visible in history, not overwritten. That commit history is the reproducibility trail.
Honest gap on this specific run (EXP-027, Muse Glimmer): the raw 30-row JSON isn't committed yet. The checkpoint is 21GB, decision on Git LFS vs. exclusion for the output file is deferred — right now that writeup stands on quoted excerpts only, not the full raw file. Flagging that directly since it's the same kind of gap this test is designed to catch.

Update: the raw JSON for this experiment (muse_glimmer_results.json, 30 rows) is now committed — closing the reproducibility gap flagged above. github.com/soulinpsyabstract/sipa-os-governance/blob/main/AI_EXPERIMENTS/RESULTS/muse_glimmer_results.json