Skip to content

Verifiable Agent Trust Envelope v0.2.0 - AL2 Verifier Admission Profile Draft

Pre-release
Pre-release

Choose a tag to compare

View all tags
@Poke-nushi Poke-nushi released this 05 May 18:35
· 90 commits to main since this release
v0.2.0
36a1177

Verifiable Agent Trust Envelope v0.2.0

AL2 Verifier Admission Profile Draft

v0.2.0 DOI: https://doi.org/10.5281/zenodo.20043166
Concept DOI: https://doi.org/10.5281/zenodo.19839768

This is a pre-release discussion draft, not a production-ready protocol release.

v0.2.0 freezes a review snapshot for the AL2 verifier-side admission boundary: how a relying party can evaluate a risky external agent action before execution, decide allow / attenuate / deny, and bind that decision to later receipt evidence.

What Changed

This release adds a narrower v0.2 profile around verifier-side admission for AL2 external digital actions.

It keeps VATE adjacent to A2A, MCP, OAuth, VC, DID, OID4VP, Web Bot Auth, AP2, x402, ACP, and delegated payment-token systems. Those systems remain evidence or transport layers. VATE defines how a relying party evaluates those inputs before execution and records the decision.

Added

  • docs/profiles/vate-al2-verifier-admission-profile-v0.2.md
  • docs/a2a-metadata-binding-v0.2.md
  • docs/receipt-model-v0.2.md
  • docs/v0.2-in-5-minutes.md
  • docs/a2a-maintainer-brief-v0.2.md
  • conformance/al2-vate-v0.2/
  • v0.2 schemas for admission requests, artifact references, evidence references, A2A metadata, admission receipts, and post-execution receipts
  • v0.2 examples for A2A metadata, admission allow, admission attenuate, admission deny, and post-execution success
  • mini conformance cases for valid admission, max-amount attenuation, expired permit denial, audience mismatch denial, and post-execution receipt linkage

What A2A Maintainers Can Evaluate

This release is designed to make one narrow question reviewable:

Can A2A carry digest-bound references to verifier-side admission and receipt artifacts without expanding A2A core?

Relevant files:

  • docs/a2a-maintainer-brief-v0.2.md
  • docs/a2a-metadata-binding-v0.2.md
  • schemas/a2a-vate-metadata.schema.json
  • examples/a2a/metadata-admission-issued.json
  • conformance/al2-vate-v0.2/cases/attenuate-max-amount.json

Not Production Ready

This release does not provide:

  • final proof packaging requirements
  • a multi-implementation certification suite
  • a normative A2A extension accepted by A2A governance
  • production security review
  • stable persistent namespace assignment

Main Feedback Question

Is a metadata-only, by-reference admission / receipt binding compatible with A2A's extension model, or should it remain entirely as an adjacent VATE profile outside A2A governance?

Verification

Validated before release:

python3 scripts/check_repo.py
python3 scripts/check_repo_strict.py
Assets 2
Loading