Use Cases
These use-case stories demonstrate Universal Manifest in action through the eyes of five different personas. Each story follows a real-world journey from frustration with the status quo to the moment where UM clicks — showing what changes, how it works technically, and which UM capabilities are involved.
These are narrative documents written for non-technical and technical audiences alike. Each story ends with a “How UM Works Here” section that maps the narrative to concrete UM concepts and fields.
The Journeys
Section titled “The Journeys”Alex Rivera, a mixed-media artist, is tired of rebuilding their profile on every platform. With UM, Alex creates one manifest, shares a single UMID, and their portfolio, bio, and consent preferences follow them everywhere — to galleries, social platforms, and virtual worlds.
Jordan Park runs Sunset Gallery and currently spends hours onboarding each new artist. With UM, three UMIDs replace three email threads, file uploads, and manual data entry. Artist content appears on screens in minutes, and expired manifests clean themselves up automatically.
Sam Chen is building a social platform for creators and is tired of writing scrapers and import tools. With UM, users bring their own profiles by entering a UMID. Consent enforcement, profile updates, and even data deletion requests are handled by the manifest — not by custom code.
Riley Torres manages privacy settings across 15 different platforms using a spreadsheet. With UM’s default-deny consent model, Riley sets preferences once in one manifest. Every platform checks the manifest before acting — and when Riley changes their mind, one toggle propagates everywhere.
Morgan Williams builds venue management software with nine custom platform integrations. With UM, a single consumer implementation replaces all of them. Profiles, device enrollment, trust attestations, proof of personhood, and consent management — all read from the same manifest format.
What These Stories Demonstrate
Section titled “What These Stories Demonstrate”Each journey highlights different UM capabilities:
| Capability | Creator | Venue | Developer | Privacy | Enterprise |
|---|---|---|---|---|---|
| Manifest creation | Yes | Yes | — | Yes | — |
| UMID resolution | Yes | Yes | Yes | Yes | Yes |
| Shard-based data compartments | Yes | Yes | Yes | — | Yes |
| Pointer-based canonical references | Yes | Yes | — | — | Yes |
| Default-deny consent enforcement | Yes | Yes | Yes | Yes | Yes |
| TTL-driven freshness | Yes | Yes | Yes | Yes | Yes |
| Device enrollment | — | Yes | — | — | Yes |
| Signature verification (v0.2) | — | — | Yes | — | — |
| Trust attestation claims | — | — | — | — | Yes |
- Concepts — Learn the five core ideas behind Universal Manifest.
- Quick Start — Build your first manifest step by step.
- Integration Catalog — See how UM applies to specific domains and industries.