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.24.0, then pip install agent-evidence-vectors==0.24.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.24.0
At v0.24.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.24.0
uvx agent-evidence-vectors==0.24.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.24.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
| I want to | Read |
|---|---|
| Start a project with this Action already in CI | evidence-starter template |
| Pick a format and corpus | Corpus guide |
| Implement the verifier interface | Verifier contract |
| Understand what the fixtures test | Corpus measurements |
| Check release bytes and signatures | Release verification |
| Report a run or disagreement | Run reporting |
| Check a W3C intake record | W3C intake checker |
| See who runs and uses the corpora | Independent runs, Adopters |
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.
1 maintainer
Metadata
1 maintainer
Release files for agent-evidence-vectors 0.25.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 | Provenance | |
|---|---|---|---|---|
| agent_evidence_vectors-0.25.0.tar.gz | 3.3 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_evidence_vectors-0.25.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.2 MB
Release files / agent_evidence_vectors-0.25.0.tar.gz
| Download URL | agent_evidence_vectors-0.25.0.tar.gz |
|---|---|
| Size | 3.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
865c8f2d71960c6919e69fd003e827723feda371a87bae7e03c53d06aef9aebb
|
|
BLAKE2b-256 checksum How to use checksums |
b5509b42f85285a519e2ec4e9167d7ab46bffbb4a090be851f054238bd884a2d
|
| 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 21, 2026.
Transparency logRelease files / agent_evidence_vectors-0.25.0-py3-none-any.whl
| Download URL | agent_evidence_vectors-0.25.0-py3-none-any.whl |
|---|---|
| Size | 9.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0bc14207b0832193bb0e7490a2ce29dd3b46d37c2830f23bb981c76512dc9c9e
|
|
BLAKE2b-256 checksum How to use checksums |
7c2a9307114ebddcfc039d463a7a4bb7afff1e27f6ef75b8e3a25b68451d3adc
|
| 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 21, 2026.
Transparency logSecurity for agent-evidence-vectors 0.25.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agent_evidence_vectors-0.25.0.tar.gz
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 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
