v0.5.0. Published as tag v0.5.0 of UniversalManifest/universal-manifest, with the same wire files as release candidate 1 (v0.5.0-rc.1). It is a mechanism release, not a completed implementation or conformance qualification. Canonical source: UniversalManifest GitHub. Earlier versions were reviewed in the OMA3 Technical Working Group, and publication asserts no OMA3 ratification.
Download all pages (ZIP) Markdown PDF

Universal Manifest v0.5 — Document Set

v0.5.0

v0.5.0. Published as tag v0.5.0 of UniversalManifest/universal-manifest, with the same wire files as release candidate 1 (v0.5.0-rc.1). It is a mechanism release, not a completed implementation or conformance qualification. Immutable versions in UniversalManifest/universal-manifest are normative; main is the working version. Earlier versions were reviewed in the OMA3 Technical Working Group, and publication asserts no OMA3 ratification.

This document:
/spec/v0.5/
Document set:
Universal Manifest v0.5.0 · What changed in v0.5.0
Artifacts:
JSON Schema · JSON-LD context
History:
https://universalmanifest.net/spec/ (version index and changelog)
Author:
Grig Bilham — inventor, architect, and author of the Universal Manifest.

v0.5.0. Published as tag v0.5.0 of UniversalManifest/universal-manifest, with the same wire files as release candidate 1 (v0.5.0-rc.1). Wire version 0.5; namespace https://universalmanifest.net/ns/v0.5; reading routes /spec/v0.5/. It is a mechanism release, not a completed implementation or conformance qualification. Feature-specific PREVIEW and conditional requirements remain in force.

Universal Manifest v0.5 — Document Set (Conformance-Tier Stack)

The v0.5 candidate is organized as a conformance-tier stack: a breadth-first Primer, a Tier-0/Tier-1 Base, four companion profiles that a conformance claim adds by tier or by optional feature, and a Cookbook of worked examples. The question that decides what you read and build is "what level of assurance am I certifying to?"

This is v0.5.0, published as tag v0.5.0 and derived from the accepted v0.4 editorial set. Historical v0.3/v0.4 artifacts remain unchanged. The immutable canonical GitHub release is authoritative; the website is a downstream view. See migration and release notes.

The documents

# Document Role Words Status
1 primer.md Primer — breadth-first overview: what UM is, the shape of a manifest, the lifecycle, the core guarantees, a one-glance map of tiers + extensions. Informative; no MUSTs. ~2,300 Informative
2 core.md Base — everything to build a conformant Tier-0/Tier-1 evaluator and holder, including a top-level manifest object/field map. Names advanced/optional features and points to the extensions for their mechanics. ~11,000 Production-candidate + PREVIEW-named
3 ext-t1.md EXT-T1 — Tier-1 binding mechanics: holder binding, presentation proof, liveness, Stage-2 sub-steps, the 7-step claim-proof path, v0.3 backwards compat. ~3,200 Normative (T1.3.1–T1.3.3 PREVIEW)
4 ext-t2.md EXT-T2 — Tier-2 ZKP proof profiles (2A/2B), the BBS+ selective-disclosure track, post-quantum migration. ~2,400 PREVIEW
5 ext-t3.md EXT-T3 — Tier-3 multi-party ceremony: model, attester-role taxonomy, threshold-protocol guidance. ~1,000 PREVIEW
6 ext-opt.md EXT-OPT — tier-orthogonal optional features: abstract data model + CBOR-LD, statusRef protocol, receipts-as-class, bilateral sessions, federation, profile registration, scope registry, trustWeight/category trust, extended schemas, crypto summary, class registry. ~6,400 Mixed (PREVIEW-tagged per part)
7 cookbook.md Cookbook — all 24 worked examples, by scenario, tagged by tier. Informative. ~2,600 Informative

How to read it, by what you are certifying to

What this restructure does and does not do

Does: relocate and re-frame existing content into a tier-stack architecture; add three net-new artifacts (Primer, Cookbook, this index); apply a concision pass; preserve every normative requirement (moved/deferred, never silently dropped); keep the Base at "what conformance demands" altitude by naming advanced capabilities and specifying them in extensions — the same discipline that kept v0.3 digestible.

Version change: unlike the original tier-stack restructuring, this v0.5 candidate changes the signed version/namespace and Profile A acceptance predicate. It retains the inherited requirements and feature maturity. Each document owns its anchors and cross-citations; fixture/runtime/readers/publishing qualification remains outstanding.

Provenance

The inherited v0.4 set was restructured from its earlier single-file draft into the Conformance-Tier Stack architecture (the "Strategy B" layout) in June 2026. That historical restructuring relocated and re-framed content and added the Primer, Cookbook and index without changing wire shape. This v0.5 candidate retains that complete layout while making the separately stated version and signature-acceptance changes.