agent-evidence-vectors

Agent Evidence Vectors

Test an agent-evidence verifier against saved records with known outcomes. The corpora cover valid records, altered bytes, missing evidence and open specification interpretations.

The recording is demo/four-arms.sh from a fresh clone; vhs demo/four-arms.tape re-records it.

Add it to a project with uv add agent-evidence-vectors==0.23.0, then pip install agent-evidence-vectors==0.23.0. Verified by Probity (github.com/probityai/probity); the probityai command line is planned, not yet released: uv add probityai, then pip install probityai.

Try it

Run every vector in the default corpus through the bundled reference verifier. You need Python 3.11+ and uv; there is nothing to clone or build, and a cold run takes about six seconds:

uvx agent-evidence-vectors==0.23.0

At v0.23.0 the default corpus is suiteRevision 32, and the run prints one row per vector and ends with:

totals: 288 vectors, 288 pass, 0 fail; report written to conformance-report.json

Now run the same corpus against a verifier other than the reference. The Go reference verifier installs with Go 1.26+ and Go's executable directory on your PATH; put your own command in its place:

go install github.com/probityai/agent-evidence-vectors/cmd/aee-verify@v0.23.0
uvx agent-evidence-vectors==0.23.0 --verifier "aee-verify --json"

Open conformance-report.json for the per-vector results. A complete external run has rail: external, verifier.vectorsExecuted equal to totals.vectors, and zero totals.suiteRefusals. The report separates conformance from reason-code agreement. --list-corpora names the other shipped corpora and --corpus <name> selects one.

The release is v0.23.0 on GitHub and PyPI. To run from a reviewed source checkout instead, follow the source build. Installation routes and release identity covers package availability and signature checks.

Test your verifier

The harness calls your executable with a vector-file path. Return a verdict through the exit status and a JSON object on the last line of stdout. The verifier contract covers output fields, key policy and comparison rules.

Use the GitHub Action to run the same check in your build and retain its report. The CI guide gives a workflow step and the available inputs.

Verifiers that pin this corpus

agmi, Rul1an/aee-checker and MoltyCel/moltrust-api run a corpus from this repository in their own CI at a pinned release or commit, and this repository's CI runs agmi's anchored-chain verifier back against vectors-anchored-chain. The verifier table gives each one's corpus, pin and CI run.

Choose your next step

Each corpus manifest records its source revision, digest and expected outcomes. DISTRIBUTION.md lists the shipped corpora and installation routes.

For fixture coverage, see Corpus measurements. To check signed release bytes, use Release verification.

Source maps: repository layout, corpus readers and witness attestor.

Contribute

Open an issue with the corpus revision, verifier build and report. For patches, start with CONTRIBUTING.md. For citations, use the citation guide.

Need to check a supplied claim against saved evidence? See Probity Verify. Browse the Probity projects for records, vocabulary and admission tools.

Apache-2.0. LICENSE.