69–82 across 4 of 5 boards
confirmation-desk-dayRun #133—risk-limit-breach-dayRun #10181#13high-board-portfolio-review-dayRun #9471#12trader-rfq-booking-dayRun #3382#9risk-manager-control-dayRun #2069#14
Every ability card measured for hunyuan-3.
averaged across the boards this model contested
69–82 across 4 of 5 boards
confirmation-desk-dayRun #133—risk-limit-breach-dayRun #10181#13high-board-portfolio-review-dayRun #9471#12trader-rfq-booking-dayRun #3382#9risk-manager-control-dayRun #2069#144 measurements · each against that board's own field
risk-limit-breach-dayRun #101
obj 94.9 · 2 trials
high-board-portfolio-review-dayRun #94
obj 80.0 · 2 trials
trader-rfq-booking-dayRun #33
obj 88.9 · 2 trials
risk-manager-control-dayRun #20
obj 75.7 · 2 trials
2 cards · measured, never ranked
Runs measured outside a contested field. An ability card is an absolute measurement — passed/total per axis, EFF against each workflow's own par — so it stays meaningful with no opponent. A rank does not: with no field, a first place measures nothing. Nothing here carries one, and nothing here reaches the leaderboard.
Run #129 — flash tier at each model's effort ceiling
54–91 across 5 workflows
ops-settlement-day91trader-rfq-booking-day88risk-manager-control-day87risk-limit-breach-day79high-board-portfolio-review-day54Run #130 — the same field at low effort
61–91 across 5 workflows
ops-settlement-day91risk-manager-control-day83trader-rfq-booking-day83risk-limit-breach-day76high-board-portfolio-review-day61Run #129 — flash tier at each model's effort ceiling 2026-08-26 · report
A real seven-model field, but across all five golden workflows at once, so it is published as cards rather than a ranked board: a leaderboard section covers one workflow, and folding five into a single row per contestant would publish a cross-workflow average under one workflow's heading. Two trials per cell. This is the first flash-tier field measured after four harness defects were fixed — the Anthropic-protocol 4096-token output cap, the unpinned ZenMux upstream lottery, the unmeasurable truncated turn and malformed tool call, and the dead trap step — so it is NOT comparable to runs #8-#126 for these models. Every model ran at its OWN measured effort ceiling (max, xhigh or high depending on the route), which makes this a capability measurement, not a shippable configuration; run #130 is the same field pinned to `low`.
Run #130 — the same field at low effort 2026-08-26 · report
The paired arm of run #129: identical models, workflows, trials, output budget and commit, with every contestant pinned to `low` so effort is the only variable and each model is its own control. The ranking reorders — Gemini 3.7 Flash goes from third to first and leads on both axes — and four of seven models score HIGHER here than at their ceiling, because lower effort cuts tool calls and EFF is the axis with the widest spread. On the 25 of 35 paired cells where both arms have enough trial consistency to be readable, `low` costs a mean 2.4 objective points, and under one point for three of the four models with a clean sample. Four arms were swept to invalid by a network outage and re-run with `--resume 130`; all 35 are scored at the same effort and budget.