Universal Manifest v0.5.0, published 2026-11-08 as tag v0.5.0 of UniversalManifest/universal-manifest. Compared with the published v0.4 document set.
In one line. v0.5 tightens what a signature accepts and what it covers, adds a second signature profile, and is released as a mechanism with reference suppliers, at conformance level "none".
Each item links to the specification text that states it. Where this page and the specification differ, the specification governs. The full release notes are on GitHub.
Version and migration
What an implementer must change to produce or accept v0.5 manifests:
Sign every new v0.5 manifest fresh, over its exact signing input. Changing the version or context of a v0.4 document invalidates its old signature. Keep original v0.4 bytes and rules unchanged. Overview: Migration
Route each document by its declared version, to that version's rules. A consumer with no supported path for the declared version rejects the document; it does not downgrade or relabel it. Overview: Migration
The v0.5 context omits five terms from the published v0.4 snapshot: facetSensitivityOrdering, labels, order, profile and trustWeight. Shared term definitions are unchanged. Overview: Migration
Signature rules
Signature Profile A (JCS + Ed25519) has an explicit acceptance rule: canonical non-identity prime-order A and R, canonical S, and the full-challenge uncofactored equation. Some inputs that older library routes accept are refused. The rule does not change verification of earlier versions. Base §1.6.1.1
The schema supports Signature Profile B (JCS + ES256 over P-256) beside Profile A. Profile B signatures are raw 64-byte R || S; DER signatures are rejected. Overview: Migration
signature.created and signature.keyRef are not covered by the envelope signature. An evaluator must not use signature.created as evidence of signing time, freshness or ordering. Base §1.6.2
receiptSignature.created and receiptSignature.keyRef are not covered by the receipt signature. Receipt authorship needs a separate check of the verifying key against the author's authority. Base §3.3.1
Contract clarifications
The whole manifest as received must be I-JSON, including members outside the signing input such as signature. An evaluator rejects other input at the Arrive stage, before the limits and the signature check. Base §1.6.3
The resource-limit terms are defined: a megabyte is 1,000,000 octets over the JCS-canonical form, depth counts containers, and the array limit applies to every array. Base §6.3
When more than one consent entry governs a facet, every entry must be satisfied. A withdrawn or expired entry is not satisfied. Base §3.1.4
An informative paragraph states how identity behaves across a change of control. v0.5 defines no handover operation. Base §4.2
Every time check depends on the clock that supplies the evaluation time. Base §6.2
Sealed-facet labels are not hidden: a party that sees a sealed facet learns its plaintext members. Base §2.3.1
ceremonyProof.protocol is OPTIONAL in v0.5. EXT-T3 §T3.1
The post-quantum suite (JCS + ML-DSA-65) is not registered in v0.5, and provisional is a listing status. Registry Profiles
Changes to the specification are proposed as issues and pull requests on the canonical repository and accepted by its maintainers after review. Overview: Status
Conformance suite
The v0.5 suite has 198 cases. 127 of its 129 evaluation fixtures assert both signatureCheck and freshnessCheck. Six cases test the resource limits at each boundary. Conformance §5
The suite adds ES256 controls for Profile B. The v0.4 sensitivity-ordering fixture stays in v0.4 and is not in the v0.5 index. Overview: Migration
The conformance runner and the TypeScript reference are in the canonical repository under the Apache License 2.0. A copy of the repository alone builds and runs the suite. v0.5 conformance suite
The supported runtimes are the two reference evaluators: TypeScript (universal-manifest 0.1.0 on Node.js 22) and Rust (um-core, macOS on Apple silicon). Each matches all 198 cases. No browser, game-engine or device runtime is supported in v0.5. Overview: Status
What v0.5 does not claim
v0.5 claims conformance level "none". The reference results are finite evidence for named implementations, inputs and dates. They certify no product, device or deployment. Overview: qualification notes
v0.5 is a mechanism with reference suppliers. It claims no real-world identity, issuer or revocation result. Real suppliers are later work. Overview: Release boundary
High-privacy mode is an unresolved draft and is not offered. v0.5 claims no unlinkability, full or partial. Overview: High-privacy mode
All requirements stay in force. PREVIEW sections remain PREVIEW. Overview: Status
The sd-jwt-kb and bbs-derived presentation proofs stay PREVIEW and at risk. EXT-T1 §T1.2
What moves to v0.6
The protected exchange, with its release obligations, permission outcomes and protected cases, is not part of v0.5. It is planned for v0.6. Overview: Status
Release candidate 1 and the final release
v0.5.0 has the same wire files as release candidate 1 (v0.5.0-rc.1, 2026-11-07): the context, schema.json and the conformance index are byte-identical. A manifest or implementation built against release candidate 1 needs no change. The final release corrects text only. The frozen schema.json description still names release candidate 1, because the file cannot change.