Do Not Let Models Invent Numbers - Vinoo Ganesh, Kepler

20:583 min readAI Engineer10/25/2026Computing/Software · Stocks · Internet Technology

Key Takeaway

Reliable financial AI requires separating probabilistic language models from computation by forcing models to cite pre-extracted data rather than writing numbers themselves.

Highlights

  • Language models operate as probability machines, making them unreliable for mission-critical numerical tasks without strict architectural constraints.

  • Native RAG tools and vector databases fail in financial analytics by producing thousands of unverified or incorrect citations.

  • Kepler uses an architecture where language models plan and cite numbers, while deterministic code handles all arithmetic and calculations.

  • The platform processes over 30 million SEC documents and registers citable numerical anchors to ensure full reproducibility.

  • Any citation that cannot be verified against trusted sources is aggressively stripped out by a post-processing filter to prevent hallucinations.

Timeline

  1. The core challenge of numerical accuracy in language models

    Financial analysts operate under strict accuracy standards where unvalidated numbers are unacceptable. Although large language models excel at creative tasks, their probabilistic nature causes severe reliability issues when applied to finance. Attaching sources after the fact often fails because semantic search retrieves semi-relevant documents or pulls numbers out of context, such as confusing page numbers, currencies, or historical fiscal years with current data.

    • Financial analysis requires numbers that can be explicitly traced and validated.
    • Language models are probability machines that create challenges in mission-critical numerical situations.
    • Traditional source attachment fails because models perform semantic search rather than reading documents, leading to wrong sources or incorrect numerical contexts.
  2. The Kepler architecture: Retrieval, code, and post-processing

    The platform solves numerical inaccuracy by implementing a rigid division of labor. Retrieval systems pull verified sources, pre-written deterministic code handles calculations, and language models manage the overarching workflow. By preprocessing massive corpuses of SEC filings and establishing a citation registry, the system ensures every displayed number maps back to an auditable source document.

    • Kepler processes over 30 million SEC documents to register citable numerical anchors.
    • Deterministic code performs all math while language models handle high-level planning.
    • Unverifiable citations are completely refused by the platform to prevent hallucinated outputs.
  3. Hybrid search infrastructure and tenant isolation

    Operating effectively requires integrating public filings with internal corporate documents stored across various enterprise platforms. The search infrastructure avoids embedding bottlenecks by searching wide with approximate nearest neighbors and BM25, followed by cross-encoder re-ranking. Security is enforced at the document level, ensuring that internal research and proprietary data remain strictly isolated between different teams.

    • Hybrid search combines approximate nearest neighbors and BM25 across public filings and internal enterprise data.
    • Cross encoders re-rank retrieved results to de-conflict discrepancies between different document types.
    • Every search hit undergoes strict authorization checks in Postgres to maintain tenant isolation and data security.
  4. Evaluating native RAG failure rates and enforcing deterministic guarantees

    Standard vector database and RAG implementations fail rigorous financial evaluations, generating thousands of incorrect numbers that make them dangerous for auditing. To eliminate this risk, the platform enforces a strict invariant where models can never write numbers they cannot cite. While this prevents the model from acting as a speculative thought partner, it creates a reliable ground truth engine capable of automating tedious financial data extraction.

    • Standard evaluation tests reveal that native RAG setups generate thousands of straight-up wrong numbers.
    • Post-processing filters strip out unverified citations to enforce structural incapability of producing hallucinated metrics.
    • The architecture shifts the industry toward quantum-mental workflows where AI handles tedious data extraction instead of creative ideation.

Description

In finance, you never show a figure you can't trace. Vinoo Ganesh, CEO of Kepler (previously Palantir and Citadel), explains Kepler's architecture where models cite numbers but never write them: retrieval finds the source, deterministic code does the math, and a post-processing filter strips any figure that can't be verified. He covers the citation registry built from more than 30 million SEC documents, hybrid search and re-ranking on turbopuffer, tenant isolation, and why plain RAG produced thousands of wrong numbers in their evals. Chapters 00:00 Intro 01:47 Why LLMs and financial numbers don't mix 04:02 Models cite numbers, code does the math 04:30 Building a citation registry from SEC filings 06:03 How Kepler answers a question end to end 08:27 Structuring facts: value, unit, scale, period 09:48 Hybrid search and re-ranking on turbopuffer 11:30 Tenant isolation and security 12:37 Making every number traceable 14:42 Stripping what can't be verified 16:41 What plain RAG gets wrong 18:32 Kepler in action 19:46 Where the guarantees end Vinoo Ganesh, Kepler Join us in SF for the second annual AIE CODE summit: https://aie.codes our last flagship summit of 2026. Applications live now!

Write about this video