How Kepler Built Verifiable AI for Financial Services — Vinoo Ganesh @aiDotEngineer
How Kepler Built Verifiable AI for Financial Services — Vinoo Ganesh  @aiDotEngineer
Uploaded July 2026 | Updated September 2026, 3 weeks ago
In finance a number is worthless until you can say where it came from. Vinoo Ganesh, CEO of Kepler, starts from the fact that language models are probability machines, brilliant at next token prediction and unreliable at the deterministic work, like arithmetic, that finance actually runs on. So Kepler treats the model as one part of a system rather than the whole answer, wrapping it in a deterministic substrate that makes every figure traceable.

It rests on three tenets. Atomic provenance means every number is tied to its source and stripped out if it cannot be independently verified. Scope determinism keeps the model on the nondeterministic tasks it is good at and pulls the actual figure, say revenue from a 10K filing, deterministically behind the scenes, with reconciliation on top. The third is treating every extracted number like a pull request that gets reviewed, so entities are caught and nothing is invented. The result is a grounded system where the edge comes not from producing content but from verifying it.

Speaker info:
- https://x.com/vinooganesh
- linkedin.com/in/vinoo-ganesh
- vinoo.io

Timestamps:
0:00 - Introduction: a data background in finance
1:42 - Why trust and verifiability matter now
2:57 - Models are probability machines
4:27 - Why analysts still put in the hours
8:22 - Modeling AI like an overworked VP
9:26 - Atomic provenance
12:01 - Scope determinism
13:52 - Reconciliation and pulling real numbers
15:06 - Extracting entities without misses
16:34 - Toward zero invented securities
20:31 - Where a number really comes from
How Kepler Built Verifiable AI for Financial Services — Vinoo GaneshGTM Engineering: The Technical Bits — Everett Berry, ClayA Song of Types and Agents - Roberto Stagi, RatelHealthcare’s Agent Bytecode: X12 as the Harness for AI Agents — Vasant Kearney, OnlayThe Next Game Engine Wont Have a Manual — Arturo Nunez, NereuThinner Agents on a Smarter Substrate: The Ontology-based Semantic Layer — Emil Eifrem, Neo4jIdentity for AI Agents - Patrick Riley & Carlos Galan, Auth0How We Got LLMs to Recommend Our Open Source Library — Christopher Burns, InthThe Building Blocks of GTM Orchestration — Arman Vaziri, RampIn the Land of AI Agents, the Verifiers Are King — Tariq Shaukat, SonarHow to build an AI-Native Health Company — Dan Feng, Maven ClinicContext Engineering in 2026 — Louis-François Bouchard, Omar Solano & Samridhi Vaid, Towards AI
AI Engineer |

How Kepler Built Verifiable AI for Financial Services — Vinoo Ganesh

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER