agent-evidence-vocabulary
A closed, versioned vocabulary for claims about an agent's execution: what it attempted, what the system beneath it observed or refused, how directly and from what vantage the claim was obtained, and how much of a population the claim covers.
It's for anyone who writes a predicate, a verifier or an evidence format for agents and needs each term to mean one thing across vendors, including teams who want to map their own fields onto it.
Install the Python package for vocabulary v0.4.0: pip install agent-evidence-vocabulary==0.4.0.
Quick start
Pin the registry at a release and check its digest:
curl -fsSLO https://raw.githubusercontent.com/probityai/agent-evidence-vocabulary/v0.5.0/vocabulary.yaml
echo "6555b8c6e6c4fa6ebe3c59f6e95619ec383f93a0615036bed9da8a49f6302e09 vocabulary.yaml" | sha256sum -c
Then read a term:
pip install PyYAML==6.0.3
python3 -c 'import yaml; v = yaml.safe_load(open("vocabulary.yaml")); print(v["evidence_dimensions"]["observation_vantage"]["values"])'
It prints ['substrate', 'artifact']. Every term carries a definition, its allowed values and a
lifecycle status.
To map your own system's fields onto the vocabulary, copy
crosswalk/TEMPLATE.yaml
and run python3 scripts/validate_crosswalks.py before opening a pull request.
Status
Release v0.5.0, tagged October 16, 2026. It adds ten proposed terms. The registry file is CC0-1.0, and the rest of the repository is Apache-2.0. Every term starts as proposed and is promoted only when an independent system emits it; the rules are in GOVERNANCE.md. The first crosswalk came from an independent implementation of the Adversarial Execution Evidence predicate, in pull request 2.
Documentation
| page | read it for |
|---|---|
| About the vocabulary | why it exists, what each file is for, and how the term set was chosen |
| vocabulary.yaml | the registry itself |
| OpenCRE links | which terms link to which OpenCRE requirement, how closely, and why the rest have no link |
| Agent change admission predicate | the signed decision that admits or rejects a change to an agent's harness, and how to verify it |
| Releasing | how a version is cut, tagged and checked |
| GOVERNANCE.md and CONTRIBUTING.md | the promotion rules, and how to file a crosswalk |
| agent-evidence-vectors | the predicate specification and conformance vectors this vocabulary describes |
Metadata
Release files for agent-evidence-vocabulary 0.5.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 | |
|---|---|---|---|
| agent_evidence_vocabulary-0.5.0.tar.gz | 34.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_evidence_vocabulary-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.9 kB
Release files / agent_evidence_vocabulary-0.5.0.tar.gz
| Download URL | agent_evidence_vocabulary-0.5.0.tar.gz |
|---|---|
| Size | 34.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dfdb0d011ac9e9b3c476c3d2173a36e7a6cfac664a0c14a9a5dd5da045975337
|
|
BLAKE2b-256 checksum How to use checksums |
aaf1b9089543416945181727b950e89ca381be13e85dcf94ba18b61b3c388e8d
|
| 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 16, 2026.
Transparency logRelease files / agent_evidence_vocabulary-0.5.0-py3-none-any.whl
| Download URL | agent_evidence_vocabulary-0.5.0-py3-none-any.whl |
|---|---|
| Size | 35.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d46b62e0ebe20345b89838cb75d4369d59d12b8c064fba1d575a7b2270fa338
|
|
BLAKE2b-256 checksum How to use checksums |
29d22fd8f30fcce983a6a796d7859bb025c99da347b7409ed1f007939c6e9497
|
| 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 16, 2026.
Transparency log