Conformance vectors
Machine-readable test vectors for the normative specs, exercised in CI by
cargo xtask conformance from the first vord-format commit.
Layout (one directory per spec, one JSON file per vector):
conformance/
token-v0/
accept/ # well-formed tokens that MUST verify (given the fixture keys)
reject/ # tokens that MUST be rejected, one failure mode each
keys.json # fixture key material (test keys only — never production keys)
status-list-v0/
accept/
reject/
keys.json
Each vector states its purpose (the spec clause it exercises), the
input artifact, the fixture key references, the clock the verifier
is evaluated at, and the expected outcome. Reject-vectors cover, at
minimum: alg: none, unknown vfmt, alg-vs-kid mismatch, missing kid,
expired token, stale status list, regressed status-list counter, and revoked
index / kid / sid.
No vectors exist yet: they are generated and committed together with the
vord-formatreference implementation (the M0 prerequisite in the implementation arc), so the code and its vectors can never drift apart.