I build LLM agents that are evaluated before they ship and governed once they're live.
| 1.00 escalation recall ClaimLens |
33 / 33 red-team attacks held ClaimLens |
1.00 / 0.91 knockout recall / precision Grant Capture |
0 invented facts in drafts Grant Capture |
29 / 32 labelled failures fixed Health Agent |
- In production: an LLM agent fleet for a US direct-to-consumer apparel brand. It runs 21 scheduled jobs across 10 commerce and marketing APIs, checks every claim against live data before it reaches the founder, and has a person approve every dollar of ad spend.
- Just shipped: the Calibrated Health Agent is public: an agent on my own health data with a web app, an eval suite and a CI gate (below).
- Research: a pre-registered study of Gemma 4 coding agents, public with its paper.
|
An AI agent you talk to about your own wearable and journal data. It plans, writes SQL or Python, runs it in a sandbox, and every number links to a receipt you can re-run. A code check, not a prompt, flags any figure no tool computed.
Code · Write-up · Forecast scoreboard
|
My paper for Kaggle's Gemma 4 Developer Agent competition (paper track): A Pre-Registered Test on a Gemma 4 Coding Agent. Gemma 4 31B fixes real GitHub issues within a fixed 4.5-minute budget; I compared prompt rules with a planning stage.
|
|
Car-damage claims triage. My own vision models measure the damage, a LangGraph agent reasons over the evidence and the policy wording, and fixed rules decide. Only a person can deny a claim.
|
Finds federal funding a small R&D firm can actually win, rules out the ones it can't (quoting the clause and page), and drafts proposals from the company's own evidence.
|
|
Turns an existing scoring model into a rep's morning: who to call, what to refresh first, what to leave, and what to say.
|
Turns a free-text buyer request into a ranked, verified top-5 supplier shortlist.
|
|
Design and prototype for an agent that works across 500+ tools: a two-stage semantic tool router, OpenAPI ingestion, and a hierarchical LangGraph orchestrator. |
|
Earlier work
- feedback-analysis-dashboard: sentiment analysis, topic modeling and user segmentation (Streamlit, scikit-learn, Plotly)
- Smart-Grid-ML-Optimization-Project: energy demand forecasting pipeline
Models measure, the agent reasons, rules decide. Anything with consequences goes through code a person can read.
Evaluate the evaluator. An LLM judge is only useful once you've measured how often it agrees with a human.
Build the outer loop first. Specs, evals, tracing and approval rules come before the clever part.
Publish the losses. Pre-register the test, report the baseline, and keep the result even when the simple rule wins.
Building agents that know when not to act is harder than building agents that act.


