Building systems that can recognize when they’re wrong

I built and led healthcare products at Doximity, Transcarent, and CancerCompass, and co-founded Andwise. Now I build tools for the questions that come after launch: has the evidence behind a decision changed, what was an AI agent approved to do, and did a correction reach the people who acted on the error?

Portrait of Kanav Jain

300,000+

calls on an average workday

9 years
after I left, still in daily use
Doximity Dialer, which I originated as founding product lead. Doximity’s report for October–December 2025.

Commercial

NextConsensus

Estimates how likely a guideline, label, or coverage decision is to change by a set date.

NextConsensus share card for FF-011: “Will FDA approve ivonescimab for EGFR-mutated non-small cell lung cancer after EGFR TKI therapy by Nov 14?” with a PDUFA goal date of 14 November 2026 and a registered probability of 15%
Enlarge image
Registered 26 September 2026 at 15%, against a 70% estimate for similar FDA approvals by their deadline.
  • Experimental

    Ambit Maps what an agent setup can already do, what one more step would unlock, and which of those tools actually work.

  • Live

    Refract Replays source revisions to catch a change before the citations that rely on it go stale.

Current work: code and checks →

  1. Essays

    I write at The Crumple Zone about who absorbs an institution’s failures and who can make it correct them. Selected writing →

  2. Proposed AI standards

    I wrote the Ethotechnics framework, an open set of proposed standards for recording approval, challenges, and corrections. ethotechnics.org

Whether a record can carry a real dispute end to end: an agent acts, a person challenges the action, and the correction reaches every decision that depended on it.

Anything else: kanav@kanav.net

Revised