VTR-1 conformance register

The standard outlives the issuer.

A specification with one implementation is a description of that implementation. This register lists issuers, independent verifiers and relying parties under VTR-1 v1.0, and says exactly how a second issuer qualifies. MIZAN is one row, with its evidence.

—Issuers
—Independent verifiers
—Named relying parties
41Clauses, frozen 2026-08-01
§ 01Issuers

Who issues today, and on what evidence.

IssuerErasVerifier hashesTransparency logEvidence

Independent verifiers: none yet. Zero shows as zero.

§ 02How to qualify

Four things, all public.

Issuer

Pass every vector in VTR-1_Conformance_Vectors_v1.0; publish verifier hashes for at least one OS and an era registry; run an append-only verdict log with signed heads anchored outside yourself; publish a soundness-break route (R-41).

Independent verifier

An implementation not derived from MIZAN's source whose exit codes match every vector; published hashes; a short conformance report. The vectors exist to make this cheap.

Relying party

Counter-sign a reliance with POST /api/receipt/attest; opt into a public name or stay hashed. Kit: Require it.

Run the vectors

python3 tools/vtr1_conformance.py VTR-1_Conformance_Vectors_v1.0/ --verifier ./your-verifier prints a pass table; exit codes are normative. Register: /api/conformance.