We Shipped an AI That Confidently Lied About Websites. Here’s How Evals Fixed It.

· Source: LLM on Medium · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering · Depth: Intermediate, long

Summary

DoableClaw's AI audit engine, CLAW, initially produced "hallucinated absence claims," confidently reporting missing website features like pricing pages when its Playwright-based crawler failed to retrieve data due to issues like JavaScript walls or bot-blocking. This critical failure mode, which nearly eroded trust, was traced to pipeline problems rather than the LLM itself, as the model merely laundered insufficient evidence into fluent prose. To counter this, DoableClaw implemented a robust LLM evaluation (evals) system. This involved creating a golden dataset from real production failures, enforcing a "cite-or-drop" rule for all load-bearing claims, and applying a special rule for absence claims to only assert absence with sufficient crawl evidence. They also introduced human-in-the-loop TRUE/BUSTED scorecards and conducted multi-model bake-offs, discovering that the most expensive model was not always the best value for their specific tasks. The system now uses a multi-model parallel architecture, with different models chosen by measured fit.

Key takeaway

For MLOps Engineers building LLM-powered intelligence systems, prioritize robust evaluation of your entire pipeline, not just the model output. Your system's fluency can mask upstream data retrieval failures, leading to "hallucinated absence claims" that erode user trust. Implement "cite-or-drop" gates and specific rules for negative assertions, and use real production failures to build your evaluation datasets. This approach will measurably improve output accuracy and help you select cost-effective models.

Key insights

LLM fluency doesn't equal accuracy; robust evaluation, especially of upstream data pipelines, is crucial for trustworthy AI systems.

Principles

Method

Build golden datasets from real failures. Implement "cite-or-drop" gates and special absence claim rules. Use human-calibrated LLM judges and multi-model bake-offs to measure and optimize quality.

In practice

Topics

Code references

Best for: AI Engineer, Machine Learning Engineer, MLOps Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by LLM on Medium.