Eval Harnesses That Catch Model Errors Before Users Do
Swapping models without evals is how production breaks quietly. Intercom ships eval results within 48 hours of a new model and rolls out in days. That speed comes from a harness, not heroics.
The problem in prod
- New model versions change tone, refusal behavior and tool-call accuracy in ways unit tests never catch.
- Offline vibes disagree with live A/B results, so launches become arguments instead of decisions.
- Nobody owns the eval set, so it rots while the product moves on.
Loop engineering
Benchmark every candidate model on transcripts of real support and ops interactions. Score instruction following, tool-call accuracy and brand voice. Nothing ships without beating the incumbent.
Roll winners to 5% of traffic with resolution rate and CSAT guardrails. Auto-rollback on regression, same as any deploy.
Queries the system cannot answer flow back into the knowledge base as new eval cases and doc gaps. CRED runs this to keep SOPs current in real time.
Score cost per resolved task alongside quality. Intercom found GPT-4.1 beat expectations at 20% lower cost, which changed their architecture.
Production hardening checklist
- Pin model versions in prod. Never float on latest without a gate run.
- Separate evals for each locale and language, including Bahasa Malaysia.
- Log every prompt, retrieval set and tool call for replay when incidents hit.
- Review the eval set quarterly and retire cases the product outgrew.
Deploying this in MY
BNM-supervised teams need model validation evidence, not just accuracy claims. An eval harness doubles as the audit artifact: versioned sets, pass rates, reviewer sign-off, all exportable for supervisory review.
Malaysia FDE guide →