Skip to content

Refreeze manuscript on the 33-model board - #161

Merged
MaxGhenis merged 1 commit into
add-fable-5-1from
refreeze-33
Sep 2, 2026
Merged

Refreeze manuscript on the 33-model board#161
MaxGhenis merged 1 commit into
add-fable-5-1from
refreeze-33

Conversation

@MaxGhenis

Copy link
Copy Markdown
Contributor

Stacked on #160 (retargets to main when that merges).

What

Refreezes paper/snapshot/20260501 on the 33-model board published as dashboard-data-20260901. Standing rule: the manuscript refreezes with every model add.

  • Frozen run exports, analysis CSVs, model_serving_config.json, and annotation pins re-derived from the publish run; the frozen data.json recombines byte-exact to the published artifact (1b2de096…f3dea, 87,392,615 bytes).
  • Snapshot date 2026-09-01; response window 2026-06-12 to 2026-09-01; annotation expectations 7,840 wrong rows (7,211 llm_error, 629 parse).
  • Table 2 gains the Claude Fable 5.1 row from the harness registry: claude-fable-5-1, released 2026-09-01, 1,984/1,984 parsed, whole scenario, provider-default reasoning.
  • Prose: one sentence in the tool_choice paragraph records that Fable 5.1 rejects forced tool use, so its row answers through the JSON transport and reasons at the provider default, with the auto sensitivity 1.2 points above it. The open-weight lag sentence is now count-aware ("trails two closed models; the earliest released of them, GPT-5.6 Sol…") because "trails only Sol" became false once Fable 5.1 scored above Kimi K3. Lag numbers are unchanged: 7 days by API availability, 18 by weights, 128 for the pre-July cut.
  • freeze_snapshot.py resolves the source run from the main clone whether it runs there or from a worktree beside it, and appends the Ox Alpha case-note supplement only when the row is absent (the repo copy already carries it; the old unconditional append would have duplicated it).
  • The /paper page labels had drifted to 2026-08-17 while the site said 2026-08-22; they now follow the snapshot date.

Verification

  • scripts/freeze_snapshot.py ran clean; --rendered-only re-pinned the render.
  • Full pytest in the worktree against the new snapshot: 594 passed, 5 skipped (recombination, completeness, serving-config, rendered-paper hash tests included).
  • Rendered PDF is 33 pages; Table 2 and the lag paragraph visually checked (no clipping).
  • App bun test 86/86, eslint clean.

🤖 Generated with Claude Code

Snapshot 2026-09-01: Claude Fable 5.1 joins at exact 86.3, second of 33.
Frozen run exports, analysis CSVs, serving-config table, and annotations
re-derived from results/local/fable51/publish; the frozen data.json
recombines byte-exact to the dashboard-data-20260901 artifact
(1b2de096…f3dea, 87,392,615 bytes). Annotation expectations move to
7,840 wrong rows (7,211 llm_error, 629 parse) for the 33-model roster.

Prose: the tool_choice paragraph notes that Fable 5.1 rejects forced
tool use, so its row answers through the JSON transport and reasons at
the provider default, with the auto sensitivity 1.2 points above it. The
open-weight lag sentence is now count-aware ("trails two closed models;
the earliest released of them, GPT-5.6 Sol") because "trails only Sol"
became false once Fable 5.1 scored above Kimi K3; the lag numbers are
unchanged (7 days by API, 18 days by weights; 128 days pre-July).

freeze_snapshot.py resolves the source run from the main clone whether
it runs there or from a worktree beside it, and appends the case-note
supplement only when the row is absent (the repo copy already carries
it). The /paper page labels, which had drifted to 2026-08-17, follow the
snapshot date.

Rendered HTML and PDF (33 pages) re-pinned with --rendered-only.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
policybench-site Ready Ready Preview Sep 2, 2026 1:20am UTC

Request Review

@MaxGhenis
MaxGhenis merged commit cc0c182 into add-fable-5-1 Sep 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant