AI
RAG that survives contact with real documents
Layla Hassan · 2025-08-21 · 6 min
Resources
A vector store is not a product. Customers ask for the clause, the date, and the source PDF. Demos hide retrieval bugs behind a fluent paragraph. Production users screenshot the wrong citation and send it to legal.
We design retrieval around citations first. If the model cannot point at a passage, it does not get to speak. That single rule prevents most of the expensive hallucinations.
Chunk like a librarian
Naive 512-token windows smash tables and headings. We split on structure — titles, sections, captions — then embed. Recall goes up. Hallucinations go down. Tables stay tables.
We also keep the original file. A citation that cannot open the PDF is theatre. The UI shows page and snippet, not a vibe.
Evaluate on real documents
We freeze a set of questions from actual users: policy exceptions, fee schedules, last year's addendum. CI fails when retrieval misses the right chunk or the answer drops the citation.
RAG that survives production is boring infrastructure with a strict mouth. That is the product.
Related articles
AI
Voice agents fail without a spoken SOP
Latency budgets, interruption policy, and the script behind the 'natural' call.
Nina Alvarez · 2025-06-03 · 6 min
Read articleAI
Treat prompt changes like failing tests
A golden set in CI so yesterday's answer cannot silently rot.
Layla Hassan · 2025-07-14 · 6 min
Read articleAI
AI in operations is a workflow problem
Agents fail when the SOP is unclear. Fix the process, then automate the edges.
Layla Hassan · 2026-01-22 · 6 min
Read article