A day in the life with UM identity
A five-minute film: one weekend of a festival-goer across a border, a festival and two virtual worlds, where every moment is an identity moment.
Claims carry their own proof.
Each claim names its issuer and can include the issuer's proof, or several proofs, each verified independently. At higher assurance levels, the evaluator also confirms that the party presenting a claim is the party it was issued to.
Permissions travel with the data.
Every facet carries its own consent: which operations are allowed, such as read, display, cache, process or forward; for what declared purpose; and until when. Writing to a facet needs its own consent. A facet without valid consent is not processed, and consent can be withdrawn.
Assurance matched to the stakes.
Assurance comes in levels, each including the one below: signature only; issuer-backed proof bound to the presenter; zero-knowledge proof of control across identifiers; multi-party co-signing. Each evaluator sets the level its risk requires, and a capsule can declare the minimum it demands.
Sensitive data, readable only by named recipients.
A facet can be encrypted for specific recipients, each with its own key. Any other evaluator records it as a sealed entry: present, but unread. Removing a recipient locks it out of every later capsule.
Each evaluator gets only what it needs.
The holder includes only the facets relevant to a given evaluator, purpose and context. The evaluator processes what it received and treats anything missing as not shared, never as absent.
Any change breaks the signature.
Every capsule is signed over its full contents and carries a hard expiry. Altered content fails verification, and expired capsules are rejected. Signing keys can stay in hardware key stores.
Verification needs no network connection.
An evaluator verifies a capsule from its own bytes plus trust material it already holds. No central service is involved, so verification works at the network edge and with no connectivity at all.
Every evaluation leaves a record.
Each evaluation produces a machine-readable receipt of what was checked, what was processed and what could not be opened. Failed checks cannot be left out. Receipts can be signed and chained into a tamper-evident history.
What this is
Universal Manifest is a small signed package of context for fast handshakes between things that meet: people, agents, devices, vehicles, drones, assets, facilities, and public infrastructure.
An airport checkpoint, an autonomous-vehicle intersection, a drone corridor, an AR factory floor, and a hotel door all need the same basic move. Exchange the smallest trustworthy context needed. Verify it. Apply policy. Record what happened.
The manifest is packet-size-aware. It carries claims, proofs, pointers, permissions, terms, freshness, and receipt data instead of dragging every file, record, model, or sensor stream into the handshake. Heavy files stay where they belong. Private data can stay sealed. The receiving system gets enough context to decide, and nothing extra just because the format made it easy to leak.
Universal Manifest is built for changing systems. Today the exchange might happen between a phone and a door, a robot and a facility, a drone and a work zone, an AI agent and a service, or a 3D asset and a spatial scene. Tomorrow it may happen across file formats, devices, networks, and transport layers that do not exist yet. The point is the same: a compact, verifiable context envelope that can travel with the subject and be evaluated by the receiver.
Every exchange leaves a structured receipt. What was verified, accepted, refused, expired, sealed, unsupported, or left unread is recorded instead of guessed. That makes UM useful for personal control, agent delegation, spatial computing, industrial operations, and compliance-aware infrastructure without reducing it to any one of those use cases.
What a manifest contains
Each evaluator runs the same bounded evaluation sequence on the manifest it receives. The result is a fast context handshake with an audit trail, not a silent data dump. See how it works.
Choose your path
Universal Manifest is not only identity, consent, portaling, spatial computing, or payments. Those are entry paths into one open specification for bounded context exchange.
Use cases
Personal, hotel, clinic, agent, spatial, asset, and commerce examples are all concrete uses of the same manifest envelope. None of them is the whole definition.
How it works
When two things meet, each side receives a compact context envelope before it acts. Signatures, freshness, issuer chains, policy terms, pointers, sealed entries, and unsupported claims are evaluated against the receiver's rules. Outcomes can be asymmetric: one side may accept a claim, refuse another, leave a private facet sealed, or record that a future format is unsupported. Every exchange produces a structured receipt, so governed systems can audit what was checked without pretending every packet carried everything.
For builders
Universal Manifest is an open spec, not a platform. It composes with existing standards rather than replacing them. If you already work with verifiable credentials, decentralized identifiers, privacy-preserving encryption, asset formats, spatial systems, or agent protocols, UM carries and references that work inside a portable envelope with a defined evaluation contract.
The spec is the technical reference for implementers. The Standards Registry shows how UM composes with DID, VC, OID4VP, HPKE, mDL, resolver patterns, and conformance fixtures while leaving heavy files and future formats in their native systems.
What comes next