Verdict
Regression testing for AI agent products. Verdict runs your app's real code path against a recorded world, with the database, external APIs, messages and clock contained at the edges. It grades what your app did, and tells you whether a code change made things better or worse, beyond noise.
uv sync --extra dev
cd examples/refunds
uv run verdict run -k 3 --label baseline
uv run verdict run -k 3 --app-root candidate --label candidate
uv run verdict compare <baseline-run> <candidate-run> --gate # exit 1: the candidate regressed
uv run verdict generate --dry-run -n 5 # write cases from the generator spec (drop --dry-run to use claude -p)
(cd ../../web && npm install && npm run build) && uv run verdict serve # the web app on :8765
- Your code, our edges. Nothing in your app is mocked except its boundaries.
- Outcomes over wording. Checks run on effects and final state.
- Honest statistics. The case is the unit: an A/A noise floor, Holm-adjusted per-case tests, a holdout split and a regression gate.
- Graders you can trust. Each case can carry a known-good and a known-bad result; a grader that passes the bad one or fails the good one stops the run.
- Traces. OpenTelemetry spans per trial as agent, model and tool steps, with the step behind every failed check; optionally exported to your own backend.
- Cases at scale.
verdict generate: code decides each scenario's correct outcome, Claude Code writes the content, gates and a reviewer decide what is kept.
| Where | What |
|---|---|
src/verdict/ |
the package and the verdict CLI |
web/ |
the front end: the product UI, the landing page and the user docs (web/content/docs), one Vite app built into the package |
docs/ |
product, architecture, decisions and learnings, for contributors |
examples/refunds/ |
a deterministic example app with cases and a generator spec |
Status: early (0.1.0, unreleased), APIs may change. Licence: Apache-2.0.
Metadata
Release files for verdict-evals 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| verdict_evals-0.1.0.tar.gz | 6.9 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| verdict_evals-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.2 MB
Release files / verdict_evals-0.1.0.tar.gz
| Download URL | verdict_evals-0.1.0.tar.gz |
|---|---|
| Size | 6.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0c36eceae64a10f43b61f8120121e7191a66c8227a141d2714d1d339d0ac2fe
|
|
BLAKE2b-256 checksum How to use checksums |
95b4e3da56e0fb2b5a67b59618db0b8a51c627a970365cc06397759887af6cd1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / verdict_evals-0.1.0-py3-none-any.whl
| Download URL | verdict_evals-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56892af3f08280576ab55cc84f39ac31a0b9fdc8e02f5ad86404541883baf1a6
|
|
BLAKE2b-256 checksum How to use checksums |
7c842bd271dbce1c3d695fbaf24ddc430b2d712a0a15f87df1a9c3829721d71b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency log