Six Ways a Production Agent Dies: A 200K-User Project's Four Hard-Won Refactors
Agent latency and hallucination budgets are decided by architecture, not by prompt wording. The hard-won numbers here show that a production agent serving a Western-scale user base can hit 90% hallucination reduction and sub-10s P95 only after you stop trusting the model with decisions that can be made deterministically.
A business-facing agent serving 200,000+ users and 500,000+ daily conversations went through four complete rewrites in under two years. Each version died from a specific mistake: V1 leaned on intent recognition, which forced retraining for every business scenario and broke multi-turn. V2 dumped all tools and context into a ReAct loop, ballooning tokens from 3,200 to 12,000 and making the shared prompt so risky that nobody dared edit it. V3 added an orchestration layer to narrow the tool list, but simply moved the failure point and created a new corpus-maintenance bottleneck.
The fourth version stopped trying to make the model smarter and instead put constraints in the right layers. It split tool descriptions by purpose, made prompt configuration hot-updatable, narrowed the candidate pool before reasoning, and replaced raw JSON memory with semantic summaries. The result: roughly 90% of hallucinations gone, P95 latency under 10 seconds. The author also identifies six distinct hallucination types, explains why early exit and deterministic-chain stripping are the biggest wins, and lays out an evaluation methodology where rules judge before models and diagnosis data never overlaps acceptance data. The post is candid about what's unsolved: RAG recall errors, leftover hallucinations, 80% human evaluation, and an unimplemented self-evolution loop.
The root cause across all four versions was mixing the decision of "which tool" with the execution of "how to use it"; separating those makes the candidate pool the real control point.
A classification model gives observability, not capability — it can tell you the category but not the specific entity, which is why it failed for a customer-service agent that must resolve references.
The most dangerous failure mode is false success: when a tool call errors but the model reports success, it amplifies trust, and that's the one that will burn a business relationship fastest.
Treating the prompt as a shared code file creates organizational paralysis; the author's shift to treating it as configurable, versioned, and hot-deployable operational asset is what unlocks continuous improvement.
Self-evolution will fail if the loop optimizes against the same data it uses for diagnosis; the structural fix of separating data sets is more valuable than any model improvement.