Skip to main content

Probity 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.

Try it

From a reviewed source checkout, build the Go verifier and a wheel, then run the installed harness outside the checkout. You need Go 1.24+, Python 3.12+ and uv. Record the checkout's full commit ID with your report.

git rev-parse HEAD
run_dir="$(mktemp -d)"
GOWORK=off go build -o "$run_dir/aee-verify" ./cmd/aee-verify
uv build --wheel --out-dir "$run_dir"
wheel="$(find "$run_dir" -maxdepth 1 -name 'agent_evidence_vectors-*.whl')"
cd "$run_dir"
uv run --no-project --with "$wheel" agent-evidence-vectors --verifier "$run_dir/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.

See installation routes and release identity for package availability and signature checks.

Select v0.17.6 on GitHub and PyPI. Install the matching release with Go's executable directory on your PATH:

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

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.

Choose your next step

I want to Read
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
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.

Metadata

Release files for agent-evidence-vectors 0.17.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agent-evidence-vectors 0.17.7
File Size Uploaded
agent_evidence_vectors-0.17.7.tar.gz 1.4 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for agent-evidence-vectors 0.17.7
File Interpreter ABI Platform
agent_evidence_vectors-0.17.7-py3-none-any.whl Python 3 none any Details

Total release size: 4.1 MB

Release files / agent_evidence_vectors-0.17.7.tar.gz

Download URL agent_evidence_vectors-0.17.7.tar.gz
Size 1.4 MB
Tags Source
SHA-256 checksum
How to use checksums
351a131706752aa0e680d4fc08b25eee09c3c3197ee55f3b5ac287e37fbca462
BLAKE2b-256 checksum
How to use checksums
85666c67ad3d048a136a7edc8f2e51360f72888766e111eaaf4b093029038d25
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 10, 2026.

Transparency log

Release files / agent_evidence_vectors-0.17.7-py3-none-any.whl

Download URL agent_evidence_vectors-0.17.7-py3-none-any.whl
Size 2.7 MB
Tags Python 3
SHA-256 checksum
How to use checksums
76fd06c83b6638160c57d12c9a20b457ee32df57c93702f5c663265883b6898a
BLAKE2b-256 checksum
How to use checksums
e33dead518a179821663df6f6dc0a7752dd17d656f97d0b06a66e80945d10938
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 10, 2026.

Transparency log

Release history Release notifications | RSS feed

0.17.9

2 release files

This release

0.17.7 This release

2 release files

0.16.0

2 release files

0.15.0

2 release files

0.14.1

2 release files

0.14.0

2 release files

0.13.0

2 release files

0.12.1

2 release files

0.12.0

2 release files

0.11.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page