Documentation · Markdown source · Edit on GitHub · CC0 1.0

ADR 0005: The Standard Is the Source of Truth; No Implementation Is

Status: Proposed Date: 2026-10-16

Related: ADR 0002 (no-gatekeeper trust and interop), ADR 0003 (GitHub org segregation), GOVERNANCE.md §1–§2.

Context

VRP is an open standard with a reference implementation (HemmaBo). Several places in this repository stated the relationship backwards — the specification text, a schema, the reference verifier and a profile named the reference implementation's code as the thing to conform to:

Two profile sections also used the word "moat" for the shared signing key — competitive framing that does not belong in a CC0 standard.

This contradicts ADR 0002 (verification resolves to the host domain and the relevant public specifications, never to HemmaBo as an authority) and GOVERNANCE.md §1–§2 (no implementation gains authority over the standard by existing). Naming an implementation file "the normative conformant surface" is the same error as a gatekeeper, in another layer.

Decision

The authoritative artifacts are the ones in this repository: the specification text, the JSON Schemas, the conformance vectors, the JSON-LD context and terms, and the reference verifier under lib/. Conformance is established against these and against the signed conformance vectors — never against any implementation's code, node, or repository.

Where this repository and an implementation (the HemmaBo reference implementation included) disagree, this repository governs and the implementation is corrected. Documentation MAY note that an artifact was first authored alongside the reference implementation, but MUST NOT state that the standard's artifact mirrors, or must match, an implementation's.

Competitive framing ("moat") is not used in the specification text.

Consequences

This ADR adds no runtime behavior and no new tools.