Where the VAID standard is, right now.
A standard that wants to become infrastructure has to show it's moving. This page is the living record – what's frozen, what's shipped, what's next – kept current on a schedule rather than left to age.
Proof-of-possession, v1 – frozen
The canonical signing path is pinned by a frozen conformance vector. A change to canonicalization is a major version bump by definition, so v1 is a stable target to build against.
payload (7 fields) → RFC 8785 JCS → SHA-256 → Ed25519(digest) conformance: byte-for-byte, Rust ≡ Python
The canonicalization spec
One canonical signing path, written as code – the byte-level interoperability contract.
Two reference SDKs
Rust and Python reference signers, each locked to the same frozen vector.
Cross-language conformance
A frozen vector both SDKs reproduce byte-for-byte – the guarantee, proven.
A reference mint
Issuance, delegation, and attenuation of a VAID into a narrower child VAID – the parts deliberately absent from the signing contract today.
The policy language
A way to express what a VAID is permitted to do, so authority is declared, not just carried.
More libraries + conformance tooling
Additional client libraries and public conformance tooling, so any implementation can prove itself against the vector.
Neutral governance
A path to neutral stewardship of the standard itself – the Docker → Kubernetes → CNCF pattern. Direction, not a dated commitment.
SYNTHERA is the trust layer for multi-agent systems: every agent gets a verifiable identity, scoped authority and a tamper-evident record, so software from different teams, vendors and frameworks can act on each other’s behalf without custom glue between every pair.
Track the standard as it moves.
Join the first cohort and you'll hear when items here ship – starting with the open release of the repositories.