Skip to content
VERASPEC
Repository
frozen21 August 2026

VER 1.0.0

The first published artifact set, frozen with its defects. Nothing in the directory may be modified.

4Published files
1.0Record version"ver_version": "1.0"
ver/1.0.0Git tagdirectory standards/ver/1.0.0

Artifacts

FileSizesha-256
VER-1.0-Specification.docx21.5 KiBc1193acbea243348d674ff803b9886fe9a0b14a157f8ce9f9a14142c4214789f
example-record.json5.8 KiB0311f4f72bc40e52c46f4d65176509448091807afaa698db2c0914caba076665
ver-record.schema.json12.2 KiBd08f7c9d86155dc695ca6d1579ab8be826d0c1dd06ff95369d43302781cc6373
wire-profile/org.verstandard.record.lexicon.json4.9 KiB34ebead95c6544585785fddf23a48837c35796967586a8367c9ffdec67122186

Status: FROZEN. This directory is the immutable 1.0.0 release of the VER 1.0 artifact set. Nothing in this directory may ever be modified, replaced, or deleted. Corrections ship as new releases (standards/ver/1.0.1/, standards/ver/1.1-draft/, …) per VERSIONING.md at the repository root. The Git tag ver/1.0.0 marks the commit that introduced this directory.

These files are byte-identical copies of the originally published artifacts, which remain at their historical locations (spec/, lexicons/org/verstandard/record.json) because running code and prose still reference those paths.

FileCopied fromSHA-256
VER-1.0-Specification.docxspec/VER-1.0-Specification.docxc1193acbea243348d674ff803b9886fe9a0b14a157f8ce9f9a14142c4214789f
ver-record.schema.jsonspec/ver-record.schema.jsond08f7c9d86155dc695ca6d1579ab8be826d0c1dd06ff95369d43302781cc6373
example-record.jsonspec/example-record.json0311f4f72bc40e52c46f4d65176509448091807afaa698db2c0914caba076665
wire-profile/org.verstandard.record.lexicon.jsonlexicons/org/verstandard/record.json34ebead95c6544585785fddf23a48837c35796967586a8367c9ffdec67122186

The wire-profile lexicon is part of the VER-F federation profile, not the core VER 1.0 record standard; it is frozen here because it was published alongside 1.0.0 and is referenced by deployed producers.

Known defects preserved in this release

This release is frozen with its defects, which are catalogued in docs/standards/VER-1.0-errata.md. Two are worth flagging to anyone using these files directly:

  • example-record.json carries a pdq/1.0 digest of 96 hex characters; the specification (§5) defines pdq/1.0 as 256-bit, i.e. exactly 64 hex characters. Corrected in 1.0.1.
  • example-record.json metadata.raw[0].sha256 is a placeholder value (the SHA-256 of the string "password") that does not match the segment's own bytes. Corrected in 1.0.1.

Do not use this example as a golden conformance artifact; use the 1.0.1 example. Illustrative hashes, URIs, and model references in these files are not verified production resources.