Skip to content

Publication sprint: freeze and ship GM-Bench sota-v2 #63

Description

@nedcut

Goal

Make publication readiness the project's primary focus for the next seven days
(2026-07-14 through 2026-07-21). The target is an evidence-complete, frozen
sota-v2 release candidate—or a precise external blocker with every safe
in-repo step finished—not more simulator scope.

The authoritative source of truth is the living checklist in
docs/PUBLISH_READINESS.md.
Update it whenever evidence, a frozen decision, cost, provider state, or a
blocker changes. This issue is the compact execution tracker; #60 remains the
broader roadmap.

Focus rule for the week

  • Publication work is the default priority.
  • Keep Make contract length a strategic decision #62 and all behavior-changing sota-v3 work parked.
  • Do not alter the frozen v2 simulator, scoring, presets, or schemas after
    official model runs begin.
  • Do not replace, retune, or selectively rerun a valid result because of its
    score.
  • Keep all paid calls serial, checkpointed, route-pinned, and behind an explicit
    spend ceiling.

Current state

  • GM-Bench v2: scout contract fix, failed-query telemetry, sota-v2 contract #58 and Harden model panel execution and recovery #59 are merged into main.
  • Build the publishable sota-v2 leaderboard pipeline #61 merged to main after independent review and full finding disposition.
  • 361 local tests, Ruff, contract canaries, calibration, archived-v1
    verification, web lint/build, and empty-v2-leaderboard generation pass on the
    current publication branch.
  • The sweep is frozen at 3 models × 4 common caps (256 / 1,024 / 4,096 /
    16,384) × 3 repeats.
  • The primary endpoint, deterministic cap rule, retry/exclusion/stopping
    policy, and minimum eight-model headline gate are committed.
  • Provider-dependent “uncapped” was removed before official results.
  • JSON mode is standardized on, reasoning is standardized off, and exact
    endpoints are pinned.
  • All three sweep models completed a clean standardized 1,024-token smoke.
  • All 11 intended headline routes accept the common privacy, parameter, JSON,
    reasoning-off, and bounded-output policy.
  • The sweep estimate is recorded: $27 planning, $32.40 with cost
    contingency, $94.51 token-ceiling contingency; 8.96 projected serial API
    hours, 13.44 with runtime contingency.
  • No official sweep or headline result exists yet; the public v2 ranking is
    correctly empty.

1. Land the publication pipeline

Exit: main contains the frozen protocol and safe paid-run path.

2. Run and interpret the output-budget sweep

  • Recheck live OpenRouter prices, account balance, endpoint names,
    capabilities, and route health immediately before the run.
  • Record the approved operator spend ceiling. The committed $100 ceiling is
    a conservative guard, not automatic authorization.
  • Run all 12 official cells serially with one new run directory:
    scripts/run_publication_matrix.py sweep --max-spend-usd <approved>.
  • Preserve raw artifacts, checkpoints, provider failures, stderr/log
    summaries, and account-cost deltas outside git.
  • Do not rerun metered invalid content, protocol failures, illegal actions,
    poor scores, or surprising valid cells.
  • Regenerate results/analysis/output-budget-sweep.json.
  • Audit configured cap versus actual output tokens, score, repairs, failures,
    cost, and latency for every model/cap cell.
  • Apply the predeclared analyzer recommendation: lowest saturated cap, or
    16,384 plus compute-elastic curves if no lower cap saturates.
  • Freeze config/sota_v2_lane.json with the decision, date, artifact hash,
    rationale, and limitations before any full-panel result.

Exit: one compute policy is frozen from complete sweep evidence.

3. Run and validate the headline model panel

  • Re-estimate exact full-panel cost and runtime at the frozen cap and obtain
    explicit spend approval.
  • Recheck all 11 exact routes; document withdrawals rather than substituting
    models after results are visible.
  • Run a benchmark-level smoke for every model at the frozen cap.
  • Run the full API panel serially: 8 seeds × 5 seasons × 3 repeats.
  • Require complete route, input/output token, cost, latency, repair, failure,
    and provenance telemetry.
  • Keep valid poor model behavior in the result; resume only the
    pre-registered infrastructure cases.
  • Strictly validate every row under sota-v2.
  • Put interesting ineligible rows in results/diagnostics/; never weaken
    the headline gate.
  • Require at least eight eligible pre-registered rows before a ranking can
    appear.
  • Compact only after validation, retain canonical raw hashes, and prepare raw
    public traces as release assets.
  • Regenerate tables and site data from artifacts only.

Exit: the generated leaderboard contains a meaningful, compute-comparable,
strictly eligible panel.

4. Analyze, write, and package

  • Report score, uncertainty, paired effect sizes, sign-flip p-values,
    compute, cost, failures, repairs, and per-mechanic outcomes.
  • Treat per-model p-values as descriptive unless the final family-wise
    analysis justifies stronger claims.
  • Run power, score-weight sensitivity, leave-one-seed-out, and
    extreme-episode checks.
  • Show output-budget curves before the ranking and show Oracle →
    pick-trader → best eligible model → random headroom.
  • Keep API and coding-harness results in separate tables.
  • Finish the blog from generated evidence, including the withdrawn-v1 story,
    compute confound, limitations, and exact scope.
  • Update the README/site with the primary result, what the benchmark does and
    does not measure, architecture/evaluation flow, quickstarts, cost guidance,
    and links to evidence.
  • Add CITATION.cff, changelog/release notes, checksums, reproducibility
    manifest, raw assets, and a tagged v2 release.
  • Check mobile, accessibility, commands, internal links, and clean-clone
    behavior.
  • Obtain an independent final read and, if possible, one outside
    clean-clone reproduction.
  • Decide before writing claims whether a salted private-panel precommit/run
    is feasible; otherwise scope v2 explicitly to reproducible public-panel
    evidence.

Release gate

Do not publish a headline ranking unless all are true:

  • Frozen benchmark and compute policies are fingerprinted and reproducible.
  • Every headline row is strictly eligible and compute-comparable.
  • At least eight pre-registered models pass.
  • Raw evidence is available and hash-linked from compact artifacts.
  • Failures, exclusions, uncertainty, compute, cost, and limitations are
    visible.
  • Claims stay inside this synthetic model-plus-scaffold condition.
  • CI, artifact validation, site build, commands, links, and clean-clone
    checks pass.
  • No v3 behavior has leaked into the frozen v2 lane.

Daily operating rhythm

  • Start each work session with this issue and the living document.
  • End each session by checking completed items and linking durable evidence.
  • Record provider/quota drift immediately instead of burning repeat calls.
  • Keep the next unblocked critical-path item explicit.
  • Update cost/runtime estimates whenever observed data materially changes
    them.

Out of scope this week

Closes when v2 is published, or when the only remaining work is an explicitly
documented external run/review blocker and every safe in-repo task is complete.

Related: #60, #58, #59, #61, #62, #46.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions