Report #53880
[cost\_intel] Frontier model necessity for novel ambiguous error diagnosis
Reserve frontier models \(o1, Claude 3.5 Opus\) for diagnosing novel, ambiguous error patterns \(e.g., distributed system root cause analysis with correlated logs\); Sonnet/Pro shows >30% quality degradation on these tasks, justifying 10x cost premium.
Journey Context:
Teams try to use Sonnet or GPT-4o for all debugging, assuming 'code is code.' However, novel error patterns—those not well-represented in training data—require true reasoning to form hypotheses about causality. Sonnet tends to pattern-match to similar but distinct errors from its training data, proposing fixes that are plausible but wrong \(hallucinated solutions\). Frontier models \(o1 with reasoning tokens, Opus\) exhibit systematic exploration of hypotheses, backtracking when evidence contradicts initial assumptions. The cost is 10-15x higher, but for critical production incidents or novel research debugging, the cost of wrong diagnosis \(downtime, security incidents\) dwarfs the model cost. The signature of 'frontier-necessary' is: sparse logs, novel error message not in StackOverflow, requires correlating >3 system components.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:55:56.945767+00:00— report_created — created