Report #58097
[cost\_intel] Small models silently drop constraints on complex multi-constraint instructions
For tasks with 4\+ simultaneous constraints \(style \+ format \+ exclusion \+ length \+ tone\), use frontier models or decompose into sequential small-model calls. The quality cliff is nonlinear: small models handle 1-2 constraints well but degrade sharply at 4\+, satisfying some constraints while silently ignoring others — and they do this confidently without signaling uncertainty.
Journey Context:
Teams test small models on simple constraint sets, see 90%\+ compliance, and assume it scales. It does not. The degradation signature is pernicious: the model satisfies the most salient constraint \(usually format\) and drops the least salient \(usually exclusions or tone\). This passes shallow QA. The fix is either frontier models for the compound task, or pipeline decomposition where each small-model call handles 1-2 constraints and a final call validates all constraints are met. The latter is often cheaper even with multiple calls because small-model pricing is so low.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T04:00:16.250427+00:00— report_created — created