Versions

Two planes, versioned separately

The record format and the artifact release move independently. A published document is never edited in place; a correction ships as a new release that annotates it.

v1.0.0frozen21 August 2026
VER 1.0.0
The first published artifact set, frozen with its defects. Nothing in the directory may be modified.
record version 1.04 filestag ver/1.0.0
VER-1.0-Specification.docx21.5 KiB example-record.json5.8 KiB ver-record.schema.json12.2 KiB wire-profile/org.verstandard.record.lexicon.json4.9 KiB
v1.0.1current23 August 2026
VER 1.0.1
A corrective release over the 1.0.0 artifact set: three schema constraints, five example edits, and the normative errata annex.
record version 1.03 filestag ver/1.0.1
VER-1.0.1-errata-annex.md111.9 KiB example-record.json6.7 KiB ver-record.schema.json13.2 KiB
v1.1-draftdraft25 August 2026
VER 1.1
Unratified. Adds the registry, lineage, model bundle manifests and redaction commitments. Producers must not emit 1.1 records to third parties.
record version 1.18 filesuntagged
HIGH-TRUST-PROFILE.md13.4 KiB VER-1.1-draft.md108.2 KiB example-record-lineage.json19.7 KiB ver-recipe.schema.json4.4 KiB 4 more

Policy

How versions are decided, and what a change costs

Four documents govern the standards track: what may change at each level, what breaks for whom, what is already known to be wrong, and how to move a record between releases.

10 sections

Versioning policy

Two planes — record format and artifact release — the frozen-artifact rule, and the CPNP invariant.

10 sections

Compatibility matrix

Every change on the standards track classified by what it breaks, for producers and for consumers.

13 sections

Errata ledger

The audit ledger: every finding against VER 1.0, its disposition, and where the fix landed.

8 sections

Migration guide

Moving a record between artifact releases, pointer by pointer.

Architecture decision records