Report #26668
[cost\_intel] Assuming quality degrades linearly when downgrading from frontier to mid-tier models
Test specifically at the task reasoning depth. For tasks requiring 3 or more chained reasoning steps \(multi-file debugging, architectural decisions, dependency conflict resolution\) frontier models show 30-50% quality advantages. For 1-2 step tasks the gap is under 5%. Route based on reasoning chain depth, not surface-level task category.
Journey Context:
The common mental model is that model quality is a smooth curve: Sonnet is 90% as good as Opus, Haiku is 80% as good. Reality: quality degrades in cliffs based on reasoning chain depth. A single-step task like extract this field or classify this text shows near-zero quality difference between tiers. A 3-step task like read the error message, find the root cause in a different file, and propose a fix that does not break existing callers shows a dramatic cliff. The mechanism is that smaller models lose the thread around step 3-4 of a reasoning chain. They hallucinate intermediate conclusions or forget earlier constraints. This is why just use Haiku for everything fails catastrophically on complex debugging but works fine on simple tasks. The fix is to classify tasks by reasoning depth before routing. A practical proxy: if the task requires reading more than 2 files or making more than 2 tool calls to gather context, route to frontier. Otherwise mid-tier is sufficient.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T23:09:58.081622+00:00— report_created — created