Variant A — the Tufte ledger

Design thesis: every number a skeptical reader might dispute is printed, not hidden in a tooltip — one ledger table per workload, exact values with provenance-classed quality scores, dominated rows kept visible with their dominators named, and a hand-drawn sparkline of the frontier embedded in each table so the shape is glanceable without any chart library.

Marks: ★ on frontier · ≈ dominated but within 10% of the frontier (see definition under each table) · · dominated · † cap is an UNVERIFIED model assumption. Hover a sparkline point for its exact values.

Sources: AA Intelligence Index v4.1.1 (current scale only — older articles use renormalized scales and are never mixed in) · GPQA Diamond AA-run · SWE-bench Verified via vals.ai independent same-harness (Mini-SWE-agent); openlm.ai rows are aggregator/vendor-reported · prices: OpenCode Go + ClinePass published tables and the live OpenRouter catalog · workload shapes: agent-chat from real 30-day traces, coding-session from OpenCode Go published request patterns. † caps are UNVERIFIED models: ClinePass assumed $35; $20-tier subscriptions modeled at 8× purchase price ($160) per community reporting. Y-axis labels follow each frontier's per-row secondary_label (note: math-smarts-coding's axes string says SWE-bench-Verified but its rows carry GPQA-Diamond values — the label shown is the authoritative one). Models without verified scores are excluded-with-reason (muse-glimmer; GLM-5.3/Flash and muse-spark lack verifiable GPQA — notable because GLM-5.3 leads the general index). ≈-near is computed client-side as: within 10% of the nearest strictly-better-or-tie row on the frontier's primary axis (cost or speed); it reproduces the generator's (+X% off) chips in 13 of 14 cases — the one divergence is qwen3-30b-a3b-2507 on chat-metered-responsiveness, where the generator reports +8% off and this rule finds no dominator within 10% of its speed.