Status: Methodology published. Independent benchmark results are only added after reproducible runs are completed.

Principles

  • Record the exact model ID or snapshot and test date.
  • Keep prompts and scoring criteria stable across compared models.
  • Run multiple trials where randomness or latency matters.
  • Separate correctness, speed and cost instead of collapsing them into one score.
  • Publish failures and ambiguous cases, not only successful examples.

Planned test groups

TestPrimary metricNotes
Python codingPass rateUnit-test based tasks
SQLCorrectnessSchema-grounded queries
Structured outputSchema validityRepeated JSON-schema trials
Long contextRetrieval accuracyControlled needle placement
LatencyMedian / p95Same region and request shape
Tool useTask completionMulti-step tool workflows

Reproducibility record

Every published test should include prompt set version, runtime settings, reasoning effort, input/output token counts when available, and any scoring code needed to reproduce the result.