Engineering brief
The architecture that makes AI stop inventing financial numbers
At a glance
The brief is enough
- Relevance
- Practical value
- Radar
- Time horizon
- Now
- Warnings
- None
Most AI financial tools generate numbers that cannot be trusted. Kepler built a system where every number is clickable, traceable, and verified—refusing nearly 11,000 hallucinations in one evaluation run.
Naive RAG tools produce wrong financial numbers at scale. This architecture offers a proven alternative.
Watch if you are building or buying financial AI tools and want to understand the trade-offs of deterministic citation architectures.
Summary
The core problem. Financial analysts need numbers that clients and portfolio managers can explicitly validate. Current LLM-based tools treat this as a semantic search problem, attaching sources after the fact. But LLMs do not actually read documents—they chunk, embed, and retrieve semirelevant information. This produces wrong sources, right sources with wrong numbers, or numbers without context (billion vs million, 2023 vs 2025). For mission-critical financial work, this is unacceptable.
The architecture. Kepler developed a system where the model plans the answer but never writes a number. Retrieval finds the correct source (using Turbopuffer's hybrid BM25 + approximate nearest neighbors search). Deterministic code—written by humans, not the LLM—performs all arithmetic. A post-processing filter strips any number the system cannot trace back to a verified citation. The invariant is simple: every number in Kepler is clickable and leads directly to the source document.
What makes it hard. XBRL data is wrong roughly 10% of the time. Analysts also work with internal documents from SharePoint, Box, OneDrive, and Outlook, not just SEC filings. Kepler must handle structured data (XBRL tags) and unstructured data (internal memos) within the same architecture. Tenant isolation is critical—one firm's desks must never see another's research. Every query is reauthorized in Postgres, and every filter is built incrementally.
The numbers that matter. When Kepler ran its filter across native Claude or ChatGPT output, it refused 10,981 citations from its evaluation set. Of those, 3,810 were flat-out wrong numbers. This is the hidden cost of naive RAG: hooking an LLM to a vector database is not enough for numerical accuracy. A third of all citations in Kepler's corpus are numbers the model did not write—they come from the deterministic compute layer.
The trade-off. Kepler's guarantees come with a cost. The platform is "structurally incapable of producing hallucinated numbers," but this also means it cannot be a creative thought partner. It is not useful for marketing content or speculative investment banking where numerical accuracy is secondary. The system can attempt citation repair—figuring out on the fly where a number came from—but this is where Kepler maintains its proprietary edge.
Where this leads. The speaker argues that the current generation of AI financial tools are limited by architecture, not by model capability. Fully managed agents can generate ideas from existing information but cannot produce a defensible discounted cash flow model. The future is "quantamental"—combining unique retrieval mechanisms with deterministic computation. This lets AI handle the work nobody wants to do while leaving creative analysis to humans.
My take
I have seen multiple teams build financial AI tools that fail in production exactly as described here. The naive RAG approach produces confidence intervals that look right but are structurally wrong. Kepler's architecture is not new in theory, it is what Palantir and Citadel did for years, but packaging it as a platform is the real contribution. The hard part most teams will skip is the citation registry and post-processing filter. That is where 80% of the trust engineering lives. I am skeptical about the claim that this works generically across internal documents at the same quality as SEC filings. Internal data is far messier. Still, this is the right direction. The disrespect is that most competitors will not invest in the plumbing.
What to do with this
- Audit your current RAG pipeline for hallucinated numbers: run a sample query set and trace every citation manually.
- Design a citation verification layer that refuses unverifiable claims before displaying results to users.
- Evaluate whether your team's current architecture can guarantee idempotent, reproducible answers for financial workflows.
Watch the video
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
300 agents in 60 people: The ungoverned AI agent sprawl
A 60-person company discovered 300 AI agents running daily. The security and cost surprises that followed apply to every team deploying agents today.
Google's managed agents: convenience vs lock-in for agent deployment.
Google's managed agents promise seamless scaling and multi-agent workflows. But the real signal is the operational overhead tradeoff and vendor lock-in risk.
AI Engineers: Stop Writing Features, Start Building the Loop
The AI engineer role is pivoting from coding features to building self-improving agent loops. But enterprise data messiness and eval trust are open questions.
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.