What Is Universal Manifest?
A plain-language overview of Universal Manifest: one portable, signed envelope that carries your identity, credentials, and preferences wherever you go.
Watch and learn
Short videos that build on each other. Start with the overview, then follow the branch that fits you. Each one carries the same idea one step further: a portable, signed envelope that holds your identity, your assets, how you present yourself, and the permissions you set, and presents the right version of you whenever two parties meet.
A plain-language overview of Universal Manifest: one portable, signed envelope that carries your identity, credentials, and preferences wherever you go.
How the same you stays recognizable across apps and worlds, with proof of who you are that you carry and control.
How you share only what you choose, keep the rest private, and can take that permission back at any time.
How your identity, preferences, and belongings travel with you from one world to the next instead of being left behind.
How Universal Manifest works alongside the standards you already use, adding a trusted wrapper rather than replacing anything.
How organizations use Universal Manifest for governance, compliance, and a clear audit trail of who shared what.
What the shared receipt proves after two parties exchange information, and why both sides can rely on it later.
How you can prove a fact about yourself, like being old enough, without revealing the underlying personal data.
How you let an AI assistant act for you while strictly limiting what it is allowed to do on your behalf.
How a space can check age or suitability and tailor access, without learning who you actually are.
How a system confirms a piece of software is genuine and unaltered before it lets the code run.
How a device announces what it can do so nearby devices can decide what to share and how to connect.
How Universal Manifest carries the address of a place in RP1 as a signed, consent-gated bookmark that a world checks on entry.
How a visitor proves their RP1 service access to a world locally, without re-presenting credentials, leaving both sides a receipt.
How RP1 grants permission to build into a sub-world or overlay, checked at the point of entry before anything is added.
How an RP1 world verifies that every imported asset and module is genuine and not revoked before it loads into the scene.
How a main RP1 world and the worlds layered onto it stay separately permissioned and fully auditable as you move between them.
How a 3D model or avatar carries who made it and the terms it travels under, so it stays trusted across tools and worlds.
More explainers are being published. This page lists the ones that are ready now and adds new ones as they go up.
The use cases put the handshake in eighteen everyday rooms. The specification is the technical reference for implementers, every rule the receiver runs.