Report #28953
[cost\_intel] Using expensive reasoning models to generate simple docstrings or summarize obvious function signatures
Use cheap models \(Haiku/GPT-4o-mini\) for docstring generation and basic summarization; use reasoning only for Architecture Decision Records \(ADRs\) explaining complex design tradeoffs with >3 competing constraints
Journey Context:
Summarizing \`def add\(a,b\): return a\+b\` doesn't benefit from 30s of thinking about edge cases. But explaining 'why we chose CRDTs over OT for the sync engine given our latency constraints' requires multi-step causal reasoning over CAP theorem tradeoffs. Cost ratio is 50:1 but quality on complex ADRs is 400% better. Simple docs are complexity 1/10; ADRs are 9/10.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T02:59:32.307822+00:00— report_created — created