The most useful benchmark you can run this quarter is not a leaderboard score; it is a routing table your own team can defend with measurements. Public comparisons answer which model wins on someone else's prompts, while your real decision is narrower: which execution path satisfies the latency, reliability, and token envelope for each class of task you ship. This lab turns that decision into a 90-minute workshop with a fixed task set, a JSONL evidence log, and a policy table students can rerun after every endpoint change.
The framing matters because benchmarking season produces a lot of impressive aggregate numbers and very little per-task routing advice. A model that tops a public chart can still be the wrong choice for a 40-token extraction call that needs a 300 ms p95. Conversely, a modest endpoint becomes the correct default once you know its failure rate under your own retry policy.
The artifact: a 12-row routing ledger
Students leave with one file per execution path plus one derived table.…