Specifications
The normative core. Specifications are versioned and use RFC 2119 language; they
ship with conformance test vectors under conformance/. A specification is the
one class of document that must remain stable, because data outlives software.
| Spec | Covers | Status |
|---|---|---|
| vord-token-v0 | The external OIDC JWT: envelope, header/claim register, verification procedure | DRAFT (v0, unstable) |
| vord-status-list-v0 | The signed revocation projection: container, freshness/replay rules, kid/sid revocation | DRAFT (v0, unstable) |
| conformance/ | Vector layout; vectors land with vord-format |
scaffold |
Both v0 specs are unstable by declaration: they bind the reference implementation and its conformance vectors, but carry no migration promise until stamped stable (ADR-0003 — a second independent verifier or a sustained conformance run). The Troth SD-JWT-VC credential spec is authored when that primitive is built.