How the Universal Manifest specification grew, version by version, and who shaped it.
The Universal Manifest is a portable state capsule: one verifiable, cache-friendly envelope that carries who-you-are references, what-you've-permitted, the devices in play, and pointers to canonical data, designed to work even when the network is partial or absent. It did not arrive whole. It grew in four releases, each closing a concrete gap that real use surfaced, following one repeating pattern: someone describes a real need, the team finds the matching web-standards pattern, and that pattern becomes a normative mechanism in the next version.
| Version | What it made the manifest | The defining move |
|---|---|---|
| v0.1 · The Envelope | An envelope | Ship the shape; defer trust on purpose. |
| v0.2 · Making It Trustworthy | Verifiable | A real signature profile and claim proofs. |
| v0.3 · Making It a Contract | A contract | A normative evaluation sequence and structured receipts. |
| v0.4 · Format Independence and Edge Interoperability | Format-independent and interoperable | An abstract data model, plus the hard real-world flows. |
| v0.5 · A Stricter Contract, Released as a Mechanism | Stricter and released as a mechanism | Tighter signature rules, a second signature profile and a stated release boundary. |
v0.1
The Envelope
Published 15 February 2026Establish the shape. Make it cache-safe and offline-tolerant. Defer trust on purpose.
The initial draft defined the Universal Manifest as a JSON-LD envelope: core members, the structural state arrays (facets, claims, consents, devices, pointers) that still anchor the manifest today, a lifecycle and caching model, conformance targets for Consumer and Issuer, and time-to-live enforcement as the first line of replay defense.
Attribution: Project-led (foundational draft). The top-level facets / claims / consents / pointers / devices structure laid down here is the same architecture an external reviewer later validated at a working-group meeting on 28 May 2026.
v0.2
Making It Trustworthy
Published 1 April 2026Turn the permissive envelope into something you can actually verify.
v0.2 kept the v0.1 base intact and added the trust layer: a normative signature profile, an identity-binding framework with a tiered trust model, a field for claim-authenticity proofs, and conventions for cross-DID binding and agent delegation introduced as non-normative conventions.
Attribution: Project-led (spec build-out).
v0.3
Making It a Contract
Published 19 May 2026Specify not just the data, but exactly what a conforming evaluator must do with it, and make it prove it did so.
v0.3 added a normative six-stage evaluation sequence, structured receipts as the auditable output of evaluation, encrypted inline facets, and promoted several v0.2 conventions to firm requirements. It is the baseline against which v0.4 is measured.
Attribution: Project-led (spec build-out). The structure was independently validated by the working group shortly after.
v0.4
Format Independence and Edge Interoperability
Published Working draft, June 2026Stop being tied to one wire format, and make the multi-party and privacy-preserving flows that real use cases demand into normative mechanisms.
v0.4 is the largest delta in the project's history. It splits into two stories: the format-independence turn (the headline change) and a use-case-driven mechanism build-out.
Attribution: The zero-knowledge and selective-disclosure family was named on the record by Alfred Tom (see contributors). Format independence and the remaining mechanism build-out (receipt disposition, forwarding, bilateral sessions, presentation binding) realize requirements the use-case document had already derived, and are project-led.
v0.4 went through an external, iterative review designed to catch the kind of internal contradiction that creeps into a large draft. Each round ran in a fresh context (less carry-over bias), wrote a new versioned file (never overwriting the prior round), and adversarially re-checked the previous round's own edits. Round one cleared the blocker class and reconciled a set of contradictions across the new v0.4 surface. Round two closed the residue and corrected three of round one's own edits, requiring HTTPS on the one unauthenticated network exchange the spec defines and surfacing the last unflagged built-in default as a visible working-group decision. The review stopped when findings became genuinely the working group's calls, not when some arbitrary count hit zero.
v0.5
A Stricter Contract, Released as a Mechanism
Published 8 November 2026Tighten what a signature accepts and what it covers, add a second signature profile, and release the result as a mechanism with reference suppliers, with no real-world identity, issuer or revocation result.
v0.5.0 is published as tag v0.5.0, with the same wire files as release candidate 1 (v0.5.0-rc.1, 7 November 2026). It is a mechanism release, not a completed implementation or conformance qualification.
Attribution: Project-led. This release adds no new named credit. The zero-knowledge and selective-disclosure family named by Alfred Tom carries forward as preview profiles.
Person, contribution, and where it landed. Each named contribution is backed by a dated, quoted entry in the project's internal change record; the project does not paraphrase who-asked-for-what. A named person means a specific, traceable request, recorded with its date and channel in the project's internal change record. Project-led means the project lead's own design call or an internal cleanup, with no single external requester. It is an honest label, not a stand-in for an unknown name. Where a single detail can only be confirmed by the project lead, it is marked pending confirmation rather than asserted as fact.
Alfred Tom
— OMA3Named the v0.4 known gaps: zero-knowledge proofs and the selective-disclosure family.
“You brought up some of these things, known gaps to be introduced in v0.4, zero-knowledge proofs and all that.”
Directed that every new use of UM goes into the use-case document, which is what the standard is evaluated against. This is the practice that drives the use-case-led mechanism build-out in every release.
“When you come across a new use, you should put it in here. It'll be evaluated against the use case.”
Validated the spec architecture: a use-case-independent framework and schema first, then per-use-case data, where each use case defines a profile that conforms to the framework. Confirmed the existing facets / claims / consents / pointers / devices structure.
Tracey Swales
Originated the 'Digital You' concept, carried as an attributed use case.
The Web of Worlds 'User Manifest' pillar, introduced as a subset of UM and mapped field-by-field to the Universal Manifest in integration research.
Rob Watts
— IntelObject manifests with timestamped history, surfaced via Intel SceneScape: an integration surface for device facets, consent in monitored spaces, and timestamped object history.
These shaped the spec but were the project lead's own design calls or internal, review-driven cleanups, with no single external requester. They are credited as project-led rather than attributed to a guessed name.
This page is the public companion to the specification. For normative definitions and the full conformance contract, read the latest specification, browse all versions, or see the terms. Attribution is quoted from the project's internal change record and is never paraphrased; details that can only be confirmed by the project lead are marked pending confirmation.