- Built for
- Michelin x AI Tinkerers Harness Engineering Hackathon, Pune (Operations and Compliance track), extended afterwards
- When
- 2026
0wrong automatic verdicts, against 28 for a single-reading baseline
194generated contracts evaluated
108tests in the suite
Outcome-based fleet contracts pay on results such as uptime, so every period someone has to read the contract, pull the vehicle telemetry and decide whether the service level was met. Wording is vague, clauses conflict, precedence rules change the answer, and the telemetry itself is sometimes doubtful.
An AI that simply answers is dangerous here. One invented threshold or a misread clause turns into a wrong payment. The hackathon, run by Michelin with AI Tinkerers in Pune, asked for a harness around the model that makes automation safe to trust.
Verdict is an agentic auditor that automates a verdict only when it is the same under every reasonable reading of the contract and the data. Otherwise it escalates to a person with a brief that includes the dollar range at stake.
The model never decides. It acts as a reader that proposes numbers together with the exact sentence they came from; a quote verifier and a deterministic decision engine check the quote and make the call, so an invented threshold can never reach a verdict. A verdict envelope then tests conflicts, vague wording and precedence clauses against both trusted and doubtful telemetry views.
It was built at the Michelin x AI Tinkerers Harness Engineering Hackathon in Pune (Operations and Compliance track) and extended afterwards. It ships with a tamper-evident audit trail with offline replay, a role-based review console, a secured REST API, run tracing and a test suite of 108 tests.
Beyond generated contracts, the system ran on real public cloud SLAs from AWS and Google, added tiered service-credit support, and surfaced three reader defects that were fixed and locked in with regression tests.
On 194 generated contracts, about 83,000 telemetry rows, Verdict produced 0 wrong automatic verdicts, against 28 for a single-reading baseline. An ablation that removed the verdict envelope caused 19 wrong automatic verdicts, which shows the envelope is what makes the automation safe.
- Python
- LLM reader
- Deterministic decision engine
- REST API
- Tamper-evident audit log
How it works
- 1ReadAn LLM reads the contract and proposes values, each with the exact source sentence
- 2VerifyA quote verifier checks every proposed number against the contract text
- 3TestA verdict envelope tests each plausible reading of the contract against trusted and doubtful telemetry
- 4DecideDeterministic code decides, and only when the outcome is the same under every reading
- 5EscalateAnything unstable goes to a person with a brief and the dollar range at stake