{ "id": "universal-manifest", "name": "Universal Manifest", "description": "The complete space of what Universal Manifest enables: a portable, self-sovereign identity and data manifest that travels with the subject across every digital context. UM is a specification — not a product — defining how identity, consent, credentials, and digital assets are represented, verified, and projected across platforms, devices, and standards.", "status": "proven", "docs": ["docs/explainers/full-briefing.md", "site/src/content/docs/spec/v0.2.md"], "children": [ { "id": "identity-profile-portability", "name": "Identity & Profile Portability", "description": "Carrying your identity across platforms, services, and devices. UM defines how a subject's identity facets — from social handles to professional credentials to device enrollments — are represented in a single portable manifest that the subject controls and selectively projects to any relying party.", "status": "proven", "docs": ["site/src/content/docs/integrations/social.md", "docs/journeys/journey-06-public-profile-projection.md"], "children": [ { "id": "social-media-profiles", "name": "Social Media Profile Portability", "description": "Carry your social identity — handles, display names, avatars, bio, follower attestations — across platforms without re-creating accounts. UM social facets let you project a consistent public identity to Mastodon, Bluesky, LinkedIn, or any platform that reads UM manifests.", "status": "proven", "docs": ["site/src/content/docs/integrations/social.md", "docs/journeys/journey-06-public-profile-projection.md"] }, { "id": "professional-credentials", "name": "Professional Credential Portability", "description": "Carry professional licenses, certifications, employment history, and role attestations across job platforms and professional networks. Employers and clients verify credentials directly from the manifest without contacting issuers each time.", "status": "proposed", "docs": [] }, { "id": "gaming-identities", "name": "Gaming Identity Portability", "description": "Maintain a single gaming identity across multiple game platforms — achievements, rankings, reputation, friend lists, and play history travel with you. Game studios read your manifest to bootstrap your profile instead of starting from scratch.", "status": "proposed", "docs": [] }, { "id": "academic-records", "name": "Academic Record Portability", "description": "Transcripts, degrees, course completions, research affiliations, and academic standing represented as verifiable facets. Universities and employers verify academic history directly from the manifest.", "status": "proposed", "docs": [] }, { "id": "medical-identity", "name": "Medical Identity Portability", "description": "Patient identity, insurance linkage, provider relationships, and care preferences carried across healthcare systems. Emergency responders and new providers access critical identity facets with appropriate consent.", "status": "unexplored", "docs": [] }, { "id": "legal-identity", "name": "Legal Identity Representation", "description": "Government-issued identity documents — passport, national ID, driver license — represented as verifiable facets with selective disclosure. Prove your age without revealing your address; prove citizenship without revealing your birth date.", "status": "unexplored", "docs": [] }, { "id": "financial-identity", "name": "Financial Identity Portability", "description": "Bank account linkages, credit relationships, and financial standing attestations carried across financial institutions. Open a new account by projecting verified financial identity facets instead of re-submitting documents.", "status": "unexplored", "docs": [] }, { "id": "reputation-systems", "name": "Cross-Platform Reputation", "description": "Reputation scores, trust ratings, and behavioral attestations earned on one platform projected to another. A seller's eBay reputation becomes verifiable on a new marketplace; a contributor's Stack Overflow reputation transfers to a new forum.", "status": "proposed", "docs": [] }, { "id": "pseudonymous-identity", "name": "Pseudonymous Identity Management", "description": "Maintain multiple pseudonymous identities with controlled linkability. Prove properties about yourself (age, residency, credentials) without revealing your legal identity. Pairwise identifiers prevent cross-context tracking.", "status": "documented", "docs": ["docs/journeys/J13-portable-identity-profile-pairwise-privacy.md"] }, { "id": "organizational-identity", "name": "Organizational Identity", "description": "Organizations — companies, nonprofits, government agencies, DAOs — carry their own manifests with verifiable attributes: registration, compliance status, authorized representatives, and service endpoints.", "status": "proposed", "docs": [] }, { "id": "device-identity", "name": "Device Identity & Enrollment", "description": "Devices carry manifests describing their capabilities, ownership, security posture, and authorized operators. A new smart home device enrolls by reading the owner's manifest and projecting its own capabilities.", "status": "proposed", "docs": [] }, { "id": "bot-agent-identity", "name": "Bot & Software Agent Identity", "description": "Automated agents — chatbots, trading bots, monitoring services — carry manifests declaring their operator, capabilities, behavioral constraints, and authorization scope. Platforms verify bot identity before granting access.", "status": "unexplored", "docs": [] }, { "id": "ai-agent-identity", "name": "AI Agent Identity", "description": "AI systems carry manifests declaring their model provenance, training data consent status, capability boundaries, operator identity, and behavioral commitments. Relying parties verify AI agent identity before accepting their outputs.", "status": "unexplored", "docs": [] } ] }, { "id": "consent-privacy-management", "name": "Consent & Privacy Management", "description": "Controlling what happens to your data at every level of granularity. UM's consent model is default-deny and facet-granular: nothing is shared unless the subject explicitly grants permission, and permissions can be scoped by audience, time, context, and purpose.", "status": "proven", "docs": ["docs/journeys/J12-portable-identity-profile-projection-and-consent.md", "docs/journeys/J16-mum-consent-propagation-flow.md"], "children": [ { "id": "default-deny-consent", "name": "Default-Deny Consent Model", "description": "Nothing is shared by default. Every facet in a UM manifest is invisible to relying parties until the subject explicitly grants access. This inverts the typical platform model where data is public by default and users must opt out.", "status": "proven", "docs": ["site/src/content/docs/spec/v0.2.md"] }, { "id": "per-facet-consent", "name": "Per-Facet Consent Granularity", "description": "Consent is granted at the individual facet level, not the whole manifest. Share your professional title without sharing your email. Share your age verification without sharing your birth date. Each facet has its own visibility and consent rules.", "status": "proven", "docs": ["docs/journeys/J12-portable-identity-profile-projection-and-consent.md"] }, { "id": "audience-scoped-consent", "name": "Audience-Scoped Consent", "description": "Different audiences see different projections of the same manifest. Your employer sees professional facets; your friends see social facets; a venue sees age verification only. Audience scoping is declarative in the manifest.", "status": "documented", "docs": ["docs/journeys/J12-portable-identity-profile-projection-and-consent.md"] }, { "id": "temporal-consent", "name": "Temporal Consent (Time-Limited Access)", "description": "Consent expires. Grant a venue access to your age verification for the duration of an event. Grant a contractor access to your project files for the duration of their engagement. TTL policies enforce automatic expiration.", "status": "proven", "docs": ["docs/journeys/journey-02-ttl-and-freshness.md"] }, { "id": "contextual-consent", "name": "Contextual Consent (Location/Situation)", "description": "Consent is scoped to context: share health data only when at a hospital, share payment handles only during a transaction, share location only while using a ride-share service. Context-aware consent prevents data leakage outside intended situations.", "status": "proposed", "docs": [] }, { "id": "delegated-consent", "name": "Delegated Consent (Parent/Guardian)", "description": "Parents manage consent for children. Guardians manage consent for dependents. Organizational administrators manage consent for employee manifests. Delegation is explicit, auditable, and revocable.", "status": "proposed", "docs": [] }, { "id": "revocable-consent", "name": "Revocable Consent", "description": "Any consent grant can be revoked at any time. Revocation propagates to all relying parties through the resolver. Previously shared data becomes unverifiable after revocation. The subject is always in control.", "status": "documented", "docs": ["docs/journeys/J14-portable-identity-profile-revocation-aware-policy.md"] }, { "id": "consent-audit-trails", "name": "Consent Audit Trails", "description": "Every consent decision — grant, modify, revoke — is recorded in an auditable trail. Subjects can review who accessed what and when. Regulators can verify consent was properly obtained and maintained.", "status": "proposed", "docs": [] }, { "id": "gdpr-ccpa-alignment", "name": "GDPR/CCPA Regulatory Alignment", "description": "UM's consent model natively supports GDPR (right to erasure, data portability, purpose limitation) and CCPA (right to know, right to delete, right to opt out). Consent facets map directly to regulatory requirements.", "status": "proposed", "docs": [] }, { "id": "consent-ai-training", "name": "Consent for AI Training Data Use", "description": "Explicitly grant or deny permission for your data to be used in AI model training. Track which AI systems have consumed your data. Revoke training consent with verifiable propagation to data processors.", "status": "unexplored", "docs": [] }, { "id": "consent-analytics", "name": "Consent for Analytics & Tracking", "description": "Granular control over analytics data collection. Permit aggregate analytics while denying individual tracking. Allow usage analytics while denying behavioral profiling. Each analytics purpose has its own consent toggle.", "status": "proposed", "docs": [] }, { "id": "consent-marketing", "name": "Consent for Marketing & Advertising", "description": "Explicit opt-in for marketing communications with channel, frequency, and topic granularity. Consent travels with your manifest so new platforms inherit your preferences instead of asking again.", "status": "proposed", "docs": [] }, { "id": "consent-research", "name": "Consent for Research Participation", "description": "Grant or deny consent for your data to be used in academic research, clinical trials, or public studies. Specify allowed research domains, required anonymization levels, and publication restrictions.", "status": "unexplored", "docs": [] }, { "id": "gpc-integration", "name": "Global Privacy Control (GPC) Integration", "description": "UM integrates with the GPC standard, interpreting the GPC signal as a baseline consent constraint. When GPC is active, UM enforces its intent across all facet projections, not just browser-level headers.", "status": "proven", "docs": ["site/src/content/docs/integrations/gpc-global-privacy-control.md", "docs/journeys/J21-gpc-runtime-signal-and-evidence-projection.md"] } ] }, { "id": "digital-assets-ownership", "name": "Digital Assets & Ownership", "description": "Proving you own things and carrying those ownership claims across platforms. UM facets can represent ownership of any digital asset — from avatar meshes to music rights to virtual real estate — with verifiable provenance and transferability.", "status": "documented", "docs": [], "children": [ { "id": "avatar-assets", "name": "Avatar Assets (Meshes, Textures, Animations)", "description": "3D avatar components — meshes, textures, skeletal rigs, animations, blend shapes — represented as owned digital assets with format metadata (glTF, VRM, USD). Platforms load your avatar from your manifest instead of requiring re-upload.", "status": "documented", "docs": ["docs/concepts/avatar-equip-tool.md", "site/src/content/docs/integrations/metaverse.md"] }, { "id": "digital-art", "name": "Digital Art & Visual Works", "description": "Ownership and licensing of digital artworks — images, generative art, photographs, illustrations — with provenance chains, edition tracking, and display rights management across galleries and platforms.", "status": "proposed", "docs": [] }, { "id": "music-rights", "name": "Music Rights & Distribution", "description": "Music ownership, licensing terms, distribution rights, and royalty splits represented as verifiable facets. Platforms verify rights before streaming; collaborators verify splits before release; venues verify performance rights before events.", "status": "proposed", "docs": [] }, { "id": "virtual-real-estate", "name": "Virtual Real Estate Ownership", "description": "Ownership claims on virtual land, buildings, venues, and spaces across metaverse platforms. Carry property deeds, zoning permissions, and access policies in your manifest for cross-platform recognition.", "status": "proposed", "docs": [] }, { "id": "in-game-items", "name": "In-Game Item Portability", "description": "Game items — weapons, armor, vehicles, cosmetics, power-ups — represented as owned assets that can travel between compatible games. Item provenance, rarity, and modification history are verifiable.", "status": "proposed", "docs": [] }, { "id": "collectibles", "name": "Digital Collectibles & Memorabilia", "description": "Collectible items — trading cards, stamps, figurines, limited editions — with verifiable provenance, edition numbers, and ownership history. Collectors prove authenticity without relying on a single marketplace.", "status": "unexplored", "docs": [] }, { "id": "certificates-badges", "name": "Certificates & Achievement Badges", "description": "Earned certificates, completion badges, awards, and honors carried as verifiable facets. Professional certifications, course completions, hackathon wins, and community recognitions are portable across platforms.", "status": "proposed", "docs": [] }, { "id": "intellectual-property", "name": "Intellectual Property Claims", "description": "Patent filings, trademark registrations, copyright claims, and trade secret designations represented as manifest facets with timestamps, jurisdiction, and verification pointers to registries.", "status": "unexplored", "docs": [] }, { "id": "license-keys", "name": "Software License Keys & Entitlements", "description": "Software licenses, seat assignments, and usage entitlements carried in the manifest. Install software on a new device by projecting your license facet instead of hunting for keys in email.", "status": "unexplored", "docs": [] }, { "id": "subscription-entitlements", "name": "Subscription Entitlements", "description": "Active subscriptions — streaming services, SaaS tools, gym memberships, publications — represented as time-bound facets. Prove current subscription status across devices and contexts without re-authenticating.", "status": "unexplored", "docs": [] } ] }, { "id": "metaverse-spatial-computing", "name": "Metaverse & Spatial Computing", "description": "Moving between virtual worlds with your identity, assets, permissions, and social context intact. UM is integrated with the IWPS (Inter-World Portaling System) standard for cross-world movement, and defines how manifests travel through portal transitions.", "status": "proven", "docs": ["site/src/content/docs/integrations/metaverse.md", "docs/explainers/metaverse-portaling.md", "docs/journeys/journey-09-metaverse-crossworld-projection.md"], "children": [ { "id": "cross-world-portaling", "name": "Cross-World Portaling (IWPS Integration)", "description": "Portal between virtual worlds carrying your full manifest. UM integrates with the OMA3 IWPS specification to define identity handshakes during portal transitions, including loading content from the destination world during transit.", "status": "proven", "docs": ["docs/explainers/metaverse-portaling.md", "docs/reports/2026-03-11-iwps-um-alignment-analysis.md"] }, { "id": "avatar-portability", "name": "Avatar Portability Across Worlds", "description": "Your avatar — appearance, animations, accessories, customizations — travels with you between virtual worlds. Destination worlds adapt your avatar to their rendering pipeline while preserving your visual identity.", "status": "documented", "docs": ["docs/concepts/avatar-equip-tool.md", "site/src/content/docs/integrations/metaverse.md"] }, { "id": "metaverse-social-graph-portability", "name": "Social Graph Portability in Metaverse", "description": "Your friend lists, group memberships, guild affiliations, and social connections travel with you between virtual worlds. Arrive in a new world and immediately see which friends are present.", "status": "proposed", "docs": [] }, { "id": "achievement-portability", "name": "Achievement & Progression Portability", "description": "Achievements, levels, skill progressions, and accomplishments earned in one world are verifiable in another. A master builder in one world can prove their status when entering a new platform.", "status": "proposed", "docs": [] }, { "id": "inventory-transfer", "name": "Cross-World Inventory Transfer", "description": "Items, currencies, and resources earned or purchased in one world can be carried to compatible worlds through manifest-mediated inventory projection with asset format adaptation.", "status": "proposed", "docs": [] }, { "id": "venue-policies", "name": "Venue Access Policies & Enforcement", "description": "Virtual venues — concert halls, conference spaces, private clubs — define access policies that UM manifests satisfy. Age verification, membership status, ticket ownership, and behavioral reputation are checked at the door.", "status": "documented", "docs": ["docs/journeys/commercial/venue-operator-journey.md"] }, { "id": "spatial-permissions", "name": "Spatial Permissions & Boundaries", "description": "Define what actions are permitted in specific spatial regions — building rights, interaction permissions, recording consent, voice chat zones. UM manifests carry spatial permission grants from world operators.", "status": "proposed", "docs": [] }, { "id": "ar-overlays", "name": "AR Overlay Identity & Consent", "description": "Augmented reality overlays that interact with your manifest — displaying your preferred name tag, showing your consent status for face recognition, controlling what information others see about you in AR.", "status": "proposed", "docs": [] }, { "id": "mixed-reality-consent", "name": "Mixed Reality Capture Consent", "description": "Control whether and how you appear in other people's mixed reality captures. Your manifest declares recording consent, likeness rights, and permitted use of your captured image/voice in MR contexts.", "status": "documented", "docs": ["site/src/content/docs/integrations/smart-glasses.md"] }, { "id": "haptic-feedback-consent", "name": "Haptic Feedback Consent", "description": "Control haptic interactions in spatial computing — who can trigger haptic feedback on your devices, what intensity levels are permitted, and what types of haptic communication you accept.", "status": "unexplored", "docs": [] }, { "id": "voice-face-capture-consent", "name": "Voice & Face Capture Consent", "description": "Declare whether your voice and facial expressions can be captured, processed, or streamed by spatial computing devices and platforms. Granular control over live capture vs. recording vs. analysis.", "status": "documented", "docs": ["site/src/content/docs/integrations/smart-glasses.md", "docs/journeys/journey-08-smart-glasses-consent-enforcement.md"] }, { "id": "spatial-anchors", "name": "Spatial Anchor Ownership", "description": "Persistent spatial anchors — fixed points in AR/MR space — owned and managed through manifest facets. Place content in the real world and manage access, visibility, and interaction permissions through your manifest.", "status": "unexplored", "docs": [] }, { "id": "world-specific-adaptations", "name": "World-Specific Identity Adaptations", "description": "Adapt your manifest presentation for specific worlds — different avatar styles, different name formats, different privacy levels — while maintaining a single source of truth. World-specific facet overrides without data duplication.", "status": "proposed", "docs": [] }, { "id": "portal-loading-content", "name": "Portal Loading Content", "description": "During portal transitions between virtual worlds, the destination world provides loading content — visuals, audio, context — that the source world displays while the technical handshake completes. UM manifests carry pointers to loading content assets.", "status": "documented", "docs": ["docs/MANDATE-portal-loading-content.md", "docs/explainers/metaverse-portaling.md"] } ] }, { "id": "iot-device-enrollment", "name": "IoT & Device Enrollment", "description": "Configuring and managing devices from identity. When you bring a new device into your ecosystem, it reads your manifest to configure itself — permissions, preferences, network access, data sharing rules — without manual setup flows.", "status": "documented", "docs": ["site/src/content/docs/integrations/smart-home.md"], "children": [ { "id": "smart-home-devices", "name": "Smart Home Device Enrollment", "description": "Smart home devices — thermostats, locks, cameras, speakers, lights — enroll by reading the owner's manifest. Device permissions, automation preferences, and data sharing rules are inherited from the household manifest.", "status": "documented", "docs": ["site/src/content/docs/integrations/smart-home.md"] }, { "id": "wearables", "name": "Wearable Device Identity", "description": "Smartwatches, fitness trackers, AR glasses, and health monitors carry device manifests linked to their owner. Wearables project health data, activity metrics, and notifications according to the owner's consent facets.", "status": "documented", "docs": ["site/src/content/docs/integrations/smart-glasses.md"] }, { "id": "medical-devices", "name": "Medical Device Enrollment", "description": "Medical devices — insulin pumps, pacemakers, continuous glucose monitors — enroll with patient manifests for identity verification, emergency access, and care team notification. Critical device data is always available to authorized responders.", "status": "unexplored", "docs": [] }, { "id": "industrial-sensors", "name": "Industrial Sensor Networks", "description": "Industrial IoT sensors carry manifests declaring their operator, calibration status, data classification, and reporting endpoints. Sensor data is attributed to verified sources for regulatory compliance.", "status": "unexplored", "docs": [] }, { "id": "vehicle-identity", "name": "Vehicle Identity & Enrollment", "description": "Vehicles carry manifests with ownership, insurance, registration, maintenance history, and authorized driver lists. Rental cars configure to your preferences by reading your manifest. Fleet vehicles report to verified operators.", "status": "unexplored", "docs": [] }, { "id": "drone-registration", "name": "Drone Registration & Identity", "description": "Drones carry manifests with operator identity, registration, flight permissions, and operational boundaries. Airspace systems verify drone identity from manifests before granting flight clearance.", "status": "unexplored", "docs": [] }, { "id": "edge-computing-nodes", "name": "Edge Computing Node Identity", "description": "Edge compute nodes declare their operator, security posture, available resources, and data handling policies through manifests. Workloads verify node identity before offloading sensitive computation.", "status": "unexplored", "docs": [] }, { "id": "pos-terminals", "name": "Point-of-Sale Terminal Identity", "description": "POS terminals carry manifests identifying their merchant, payment processor, and certification status. Customers verify terminal authenticity before presenting payment credentials.", "status": "unexplored", "docs": [] }, { "id": "digital-signage", "name": "Digital Signage & Kiosk Identity", "description": "Public-facing digital signs and kiosks carry manifests declaring their operator, content policies, and interaction capabilities. Users verify kiosk authenticity before entering credentials.", "status": "unexplored", "docs": [] }, { "id": "smart-locks", "name": "Smart Locks & Physical Access", "description": "Smart locks verify access rights from visitor manifests — hotel room keys, office access, coworking spaces, event venues. No proprietary apps required; the lock reads your manifest for authorization.", "status": "proposed", "docs": [] } ] }, { "id": "commerce-payments", "name": "Commerce & Payments", "description": "Buying and selling with portable identity. UM facets can carry payment handles, merchant verification, loyalty program links, and transaction preferences — enabling commerce interactions where both parties verify each other through manifests.", "status": "proposed", "docs": [], "children": [ { "id": "payment-handles", "name": "Payment Handle Portability (Fiat + Crypto)", "description": "Carry payment handles — bank links, card tokens, crypto wallet addresses, PayPal, Venmo — as manifest facets. Pay anywhere by projecting the appropriate payment handle for the context without re-entering details.", "status": "proposed", "docs": ["docs/workorders/WO-0142-payment-handles-and-fiat-crypto-gateway-integration.md"] }, { "id": "loyalty-programs", "name": "Cross-Platform Loyalty Programs", "description": "Loyalty points, tier status, and reward balances from multiple programs carried in your manifest. Merchants verify loyalty status instantly; you never miss rewards because you forgot a card.", "status": "unexplored", "docs": [] }, { "id": "subscription-management", "name": "Subscription Lifecycle Management", "description": "Active subscriptions, billing preferences, and renewal status managed through manifest facets. Cancel, pause, or transfer subscriptions from your manifest instead of hunting through provider dashboards.", "status": "unexplored", "docs": [] }, { "id": "merchant-verification", "name": "Merchant Identity Verification", "description": "Merchants carry manifests with business registration, compliance certifications, and reputation attestations. Buyers verify merchant legitimacy from the manifest before transacting.", "status": "proposed", "docs": [] }, { "id": "customer-verification", "name": "Customer Identity Verification", "description": "Merchants verify customer identity, age, membership status, and payment capability from customer manifests — reducing fraud and enabling personalized service without invasive data collection.", "status": "proposed", "docs": [] }, { "id": "cross-border-commerce", "name": "Cross-Border Commerce Identity", "description": "Navigate international commerce with manifest facets for tax residency, customs declarations, import/export permissions, and currency preferences. Verified identity reduces friction in cross-border transactions.", "status": "unexplored", "docs": [] }, { "id": "marketplace-identity", "name": "Marketplace Seller/Buyer Identity", "description": "Carry your marketplace reputation, transaction history, and verification status across platforms. A trusted eBay seller is immediately credible on a new marketplace.", "status": "proposed", "docs": [] }, { "id": "micropayments", "name": "Tipping & Micropayments", "description": "Receive tips and micropayments across platforms through manifest payment facets. Content creators, street performers, and service workers have a single tipping identity that works everywhere.", "status": "unexplored", "docs": [] }, { "id": "donation-profiles", "name": "Charitable Donation Profiles", "description": "Donation preferences, giving history, and tax-receipt linkages carried in the manifest. Nonprofits verify donor identity; donors track giving across organizations from a single source.", "status": "unexplored", "docs": [] }, { "id": "escrow-profiles", "name": "Escrow & Trust Profiles", "description": "Escrow relationships, trust arrangements, and conditional payment terms represented as manifest facets with verifiable release conditions and multi-party authorization.", "status": "unexplored", "docs": [] } ] }, { "id": "credentials-verification", "name": "Credentials & Verification", "description": "Proving things about yourself with verifiable, portable credentials. UM integrates with W3C Verifiable Credentials and DID standards to enable credential presentation through manifest facets — from professional licenses to proof of personhood.", "status": "proven", "docs": ["site/src/content/docs/integrations/did-vc.md", "site/src/content/docs/integrations/proof-of-personhood.md"], "children": [ { "id": "professional-licenses", "name": "Professional License Verification", "description": "Medical licenses, law bar admissions, engineering certifications, and trade licenses carried as verifiable facets. Employers and clients verify current license status directly from the manifest without contacting licensing boards.", "status": "proposed", "docs": [] }, { "id": "academic-degrees", "name": "Academic Degree Verification", "description": "University degrees, diplomas, and academic honors represented as verifiable credentials in the manifest. Employers verify degree authenticity instantly; graduates never need to request transcript copies again.", "status": "proposed", "docs": ["site/src/content/docs/integrations/education-credentials.md"] }, { "id": "certifications", "name": "Industry Certifications", "description": "Professional certifications — AWS, Google Cloud, PMP, CPA, CISSP — carried as time-bound verifiable facets with expiration and renewal status. Training platforms update certifications directly in your manifest.", "status": "proposed", "docs": [] }, { "id": "age-verification", "name": "Age Verification (Zero-Knowledge)", "description": "Prove you meet an age threshold without revealing your actual birth date. A venue verifies you are over 21; a website verifies you are over 13; neither learns your exact age.", "status": "documented", "docs": ["site/src/content/docs/integrations/proof-of-personhood.md"] }, { "id": "proof-of-personhood", "name": "Proof of Personhood", "description": "Prove you are a unique human without revealing your identity. UM integrates with World ID, Gitcoin Passport, and BrightID for sybil-resistant personhood verification across platforms.", "status": "proven", "docs": ["site/src/content/docs/integrations/proof-of-personhood.md", "docs/journeys/J10-multi-provider-personhood-coexistence.md"] }, { "id": "kyc-aml-compliance", "name": "KYC/AML Compliance", "description": "Know-Your-Customer and Anti-Money-Laundering verification status carried as manifest facets. Complete KYC once and project verified status to multiple financial institutions without re-submitting documents.", "status": "proposed", "docs": [] }, { "id": "background-checks", "name": "Background Check Attestations", "description": "Background check results — criminal history, employment verification, reference checks — carried as time-stamped attestations. Employers verify checks without re-running them; subjects control who sees results.", "status": "unexplored", "docs": [] }, { "id": "credit-scores", "name": "Credit Score Portability", "description": "Credit scores and creditworthiness attestations from multiple bureaus carried as manifest facets. Lenders verify creditworthiness from the manifest; borrowers see and control their credit data across bureaus.", "status": "unexplored", "docs": [] }, { "id": "insurance-verification", "name": "Insurance Verification", "description": "Active insurance policies — health, auto, home, liability — represented as verifiable facets with coverage details, policy numbers, and provider contact. Healthcare providers verify insurance at point of care.", "status": "unexplored", "docs": [] }, { "id": "health-credentials", "name": "Health Credentials & Records", "description": "Vaccination records, allergy alerts, blood type, medication lists, and chronic condition notifications carried as consent-gated health facets. Emergency responders access critical health data; routine providers see full history with consent.", "status": "documented", "docs": ["site/src/content/docs/integrations/healthcare-patient-consent.md"] }, { "id": "travel-documents", "name": "Digital Travel Documents", "description": "Passport data, visa status, travel authorizations, and entry permits represented as verifiable manifest facets. Border control verifies documents from the manifest; travelers carry a single digital identity across jurisdictions.", "status": "unexplored", "docs": [] }, { "id": "did-vc-integration", "name": "DID & Verifiable Credentials Integration", "description": "UM integrates with W3C Decentralized Identifiers and Verifiable Credentials standards. DIDs anchor manifest identity; VCs provide the attestation format for credential facets. UM adds the consent and projection layer that DID/VC alone do not provide.", "status": "proven", "docs": ["site/src/content/docs/integrations/did-vc.md"] } ] }, { "id": "creative-media", "name": "Creative & Media", "description": "Managing creative works, attribution, licensing, and distribution rights through portable manifest facets. Artists, musicians, writers, and creators carry their portfolios, rights, and collaboration history as verifiable identity.", "status": "proposed", "docs": ["docs/journeys/commercial/creator-journey.md"], "children": [ { "id": "artist-portfolios", "name": "Artist Portfolio Portability", "description": "Visual artists carry their portfolio — works, exhibitions, commissions, collector relationships — as manifest facets. Galleries and collectors verify provenance; new platforms bootstrap the artist's presence from their manifest.", "status": "proposed", "docs": ["docs/journeys/commercial/creator-journey.md"] }, { "id": "music-distribution", "name": "Music Distribution & Rights", "description": "Musicians carry distribution rights, royalty splits, label agreements, and streaming authorizations as verifiable facets. Platforms verify rights before listing; collaborators verify splits before release.", "status": "unexplored", "docs": [] }, { "id": "video-licensing", "name": "Video Licensing & Distribution", "description": "Video content licensing — broadcast rights, streaming rights, clip licensing, embed permissions — managed through manifest facets with geographic and temporal scoping.", "status": "unexplored", "docs": [] }, { "id": "photography-rights", "name": "Photography Rights & Licensing", "description": "Photographers carry licensing terms, usage rights, model release status, and location permissions for their work. Stock platforms and publishers verify rights from the photographer's manifest.", "status": "unexplored", "docs": [] }, { "id": "3d-model-attribution", "name": "3D Model Attribution & Licensing", "description": "3D artists carry model attribution, licensing terms, format availability (glTF, USD, FBX), and modification permissions. Metaverse platforms and game studios verify rights before importing assets.", "status": "proposed", "docs": [] }, { "id": "open-source-contributions", "name": "Open Source Contribution Identity", "description": "Developers carry their open source contributions — commits, issues, pull requests, maintainer roles — as verifiable facets. Employers verify contributions; communities recognize returning contributors across platforms.", "status": "proposed", "docs": [] }, { "id": "publication-history", "name": "Publication & Writing History", "description": "Authors carry publication history — books, articles, papers, blog posts — with publisher verification, citation counts, and rights status. New platforms bootstrap author profiles from manifest history.", "status": "unexplored", "docs": [] }, { "id": "citation-networks", "name": "Academic Citation Networks", "description": "Researchers carry citation graphs, h-index attestations, and co-author networks as verifiable facets. Grant committees and tenure boards verify publication impact directly from the manifest.", "status": "unexplored", "docs": [] }, { "id": "collaboration-credits", "name": "Collaboration & Co-Creation Credits", "description": "Multi-party creative works carry contributor credits — who did what, when, and under what terms — as verifiable facets. All collaborators independently verify their credit status.", "status": "proposed", "docs": [] }, { "id": "remix-derivative-rights", "name": "Remix & Derivative Work Rights", "description": "Original works carry remix and derivative permissions in the manifest — who can remix, what modifications are allowed, attribution requirements, and revenue sharing for derivatives.", "status": "unexplored", "docs": [] } ] }, { "id": "enterprise-organization", "name": "Enterprise & Organization", "description": "Organizational identity, employee federation, supply chain verification, and compliance evidence. Enterprises use UM manifests for employee identity federation, partner verification, audit trails, and regulatory compliance across organizational boundaries.", "status": "documented", "docs": ["docs/journeys/commercial/enterprise-journey.md"], "children": [ { "id": "employee-federation", "name": "Employee Identity Federation", "description": "Employees carry organizational identity facets that federate across enterprise systems — SSO, access control, project assignments, and role-based permissions — without centralized directory coupling.", "status": "proposed", "docs": ["docs/journeys/commercial/enterprise-journey.md"] }, { "id": "contractor-verification", "name": "Contractor & Vendor Verification", "description": "Contractors and vendors carry verified business identity, insurance status, certification currency, and project clearance as manifest facets. Enterprises verify contractor credentials without manual document collection.", "status": "proposed", "docs": [] }, { "id": "supply-chain-identity", "name": "Supply Chain Identity & Provenance", "description": "Supply chain participants — manufacturers, distributors, retailers — carry manifests with verified business identity, compliance certifications, and product provenance. Each handoff adds verifiable attestations.", "status": "unexplored", "docs": [] }, { "id": "audit-trails", "name": "Organizational Audit Trails", "description": "Business processes generate verifiable audit trails through manifest interactions — who accessed what, when, with what authorization. Auditors verify compliance from manifest records without accessing operational systems.", "status": "proposed", "docs": [] }, { "id": "regulatory-compliance", "name": "Regulatory Compliance Evidence", "description": "Organizations carry compliance attestations — SOC 2, ISO 27001, HIPAA, PCI DSS — as verifiable manifest facets. Partners and customers verify compliance status directly; regulators audit from manifest records.", "status": "proposed", "docs": [] }, { "id": "org-hierarchy", "name": "Organizational Hierarchy & Delegation", "description": "Organizational structure — departments, teams, reporting lines, authority levels — represented in manifests with delegation chains. Managers authorize subordinates; executives delegate to departments; each level is verifiable.", "status": "unexplored", "docs": [] }, { "id": "role-based-access", "name": "Role-Based Access Control via Manifests", "description": "Access control decisions driven by manifest facets — role attestations, clearance levels, project assignments — instead of centralized ACL databases. Distributed access control that works across organizational boundaries.", "status": "proposed", "docs": [] }, { "id": "partner-verification", "name": "Business Partner Verification", "description": "Business partners verify each other's identity, authority, and agreement status through manifest exchange. Partnership agreements, authorized contacts, and shared project scopes are verifiable facets.", "status": "proposed", "docs": [] }, { "id": "vendor-assessment", "name": "Vendor Risk Assessment", "description": "Vendor risk assessments — security posture, financial stability, compliance status, incident history — carried as verifiable facets. Procurement teams verify vendor risk from manifests before engaging.", "status": "unexplored", "docs": [] } ] }, { "id": "governance-standards", "name": "Governance & Standards", "description": "The meta-layer: how the UM ecosystem itself is governed, how compliance is certified, how namespaces are managed, and how the standard evolves. This category covers the infrastructure of the standard itself.", "status": "proven", "docs": ["docs/governance/GOVERNANCE.md", "site/src/content/docs/about/standards-positioning.md"], "children": [ { "id": "namespace-registration", "name": "Ecosystem Namespace Registration", "description": "Application domains, integration lanes, and concept identifiers registered in a managed namespace. Prevents conflicts and squatting while enabling organic ecosystem growth. Future: decentralized namespace management.", "status": "proposed", "docs": [] }, { "id": "compliance-certification", "name": "Compliance Certification Process", "description": "External parties certify their UM implementations against the conformance test suite and receive verifiable compliance badges. Certification levels reflect depth of integration.", "status": "documented", "docs": ["site/src/content/docs/conformance/standalone-suite.md", "docs/governance/CONTRIBUTING-REGISTRY.md"] }, { "id": "conformance-badges", "name": "Standard Conformance Badges", "description": "Implementations that pass the conformance suite earn verifiable badges displayed in registries and documentation. Badges specify version, tier, and scope of conformance.", "status": "documented", "docs": ["site/src/content/docs/conformance/index.md"] }, { "id": "ecosystem-registry", "name": "Ecosystem Implementation Registry", "description": "A registry of known UM implementations, their conformance status, supported versions, and integration coverage. Adopters find compatible implementations; the ecosystem tracks adoption breadth.", "status": "proposed", "docs": [] }, { "id": "version-compatibility", "name": "Version Compatibility Matrix", "description": "Cross-version compatibility tracking — which v0.1 manifests work with v0.2 resolvers, what migration paths exist, and what breaking changes affect which implementations.", "status": "documented", "docs": ["site/src/content/docs/guides/migration-v01-v02.md"] }, { "id": "interoperability-testing", "name": "Interoperability Testing Framework", "description": "Multi-implementation interoperability testing — verify that manifest created by implementation A is correctly processed by implementation B. Cross-implementation test fixtures and expected results.", "status": "proposed", "docs": [] }, { "id": "community-governance", "name": "Community Governance Model", "description": "How the UM standard evolves: RFC process, decision records, maintainer responsibilities, contributor guidelines, and the path from proposal to normative specification.", "status": "documented", "docs": ["docs/governance/GOVERNANCE.md", "docs/governance/RFC-TEMPLATE.md", "site/src/content/docs/governance/how-we-build.md"] }, { "id": "dispute-resolution", "name": "Namespace & Compliance Disputes", "description": "Process for resolving disputes over namespace claims, compliance certifications, and standard interpretations. Transparent, documented resolution with appeal mechanisms.", "status": "unexplored", "docs": [] }, { "id": "deprecation-policies", "name": "Deprecation & Sunset Policies", "description": "How features, versions, and integration patterns are deprecated with advance notice, migration support, and clear sunset timelines. No silent breakage.", "status": "proven", "docs": ["docs/governance/DEPRECATION-POLICY.md", "site/src/content/docs/governance/deprecation-policy.md"] }, { "id": "extension-proposals", "name": "Extension Proposal Process", "description": "How new facet types, integration lanes, and capabilities are proposed, reviewed, tested, and promoted to the standard. The RFC pipeline from idea to normative text.", "status": "documented", "docs": ["docs/governance/RFC-TEMPLATE.md"] } ] }, { "id": "healthcare-wellbeing", "name": "Healthcare & Wellbeing", "description": "Health data portability with patient-controlled consent. UM manifests carry health records, provider credentials, insurance verification, and emergency access profiles with granular consent — the patient decides who sees what.", "status": "documented", "docs": ["site/src/content/docs/integrations/healthcare-patient-consent.md"], "children": [ { "id": "patient-records-portability", "name": "Patient Record Portability", "description": "Medical records — diagnoses, treatments, lab results, imaging — travel with the patient across healthcare systems. New providers access history with patient consent; no more faxing records between offices.", "status": "documented", "docs": ["site/src/content/docs/integrations/healthcare-patient-consent.md"] }, { "id": "provider-credentials", "name": "Healthcare Provider Credentials", "description": "Doctors, nurses, and specialists carry professional credentials — medical licenses, board certifications, hospital privileges — as verifiable manifest facets. Patients verify provider qualifications; hospitals verify incoming staff.", "status": "proposed", "docs": [] }, { "id": "insurance-verification-health", "name": "Health Insurance Verification", "description": "Active health insurance policies, coverage details, copay amounts, and network status carried as manifest facets. Providers verify insurance at point of care without phone calls to insurers.", "status": "proposed", "docs": [] }, { "id": "prescription-management", "name": "Prescription Management", "description": "Active prescriptions, refill status, pharmacy preferences, and drug interaction alerts carried in the manifest. Pharmacies verify prescriptions; new doctors see current medications; patients manage refills from one place.", "status": "unexplored", "docs": [] }, { "id": "allergy-condition-alerts", "name": "Allergy & Condition Alert Facets", "description": "Critical allergies, chronic conditions, and medical alerts carried as always-readable emergency facets. Emergency responders access alerts without full consent flows; the data that saves your life is always available.", "status": "proposed", "docs": [] }, { "id": "emergency-access-profiles", "name": "Emergency Access Profiles", "description": "Define what health data is accessible in emergencies — blood type, allergies, medications, emergency contacts, advance directives — without requiring standard consent flows. Break-glass access with audit logging.", "status": "proposed", "docs": [] }, { "id": "mental-health-consent", "name": "Mental Health Data Consent", "description": "Separate, heightened consent controls for mental health records — therapy notes, psychiatric diagnoses, medication history — reflecting the extra sensitivity and legal protections these records carry.", "status": "unexplored", "docs": [] }, { "id": "fitness-data-sharing", "name": "Fitness & Wellness Data Sharing", "description": "Fitness metrics — steps, heart rate, sleep, nutrition — shared selectively with trainers, insurance providers, researchers, or health coaches through consent-gated manifest facets.", "status": "unexplored", "docs": [] }, { "id": "genomic-data-consent", "name": "Genomic Data Consent & Sharing", "description": "Genomic data — DNA sequences, genetic risk factors, ancestry results — controlled through heightened consent facets. Research institutions request access; pharmaceutical companies negotiate data use; the subject controls every sharing decision.", "status": "unexplored", "docs": [] }, { "id": "clinical-trial-participation", "name": "Clinical Trial Participation Identity", "description": "Clinical trial enrollment, informed consent records, participation history, and adverse event reports carried as manifest facets. Researchers verify participant eligibility; participants track their involvement across studies.", "status": "unexplored", "docs": [] } ] }, { "id": "education-research", "name": "Education & Research", "description": "Learning records, research credentials, and academic identity that travel with the learner and researcher across institutions, platforms, and career stages.", "status": "documented", "docs": ["site/src/content/docs/integrations/education-credentials.md"], "children": [ { "id": "student-records", "name": "Student Record Portability", "description": "Academic records — grades, credits, enrollment status, financial aid — travel with the student across institutions. Transfer students carry verified records; no more waiting for transcript requests.", "status": "documented", "docs": ["site/src/content/docs/integrations/education-credentials.md"] }, { "id": "course-completions", "name": "Course Completion Credentials", "description": "Individual course completions — MOOCs, bootcamps, workshops, corporate training — carried as verifiable facets. Employers verify specific skills; learners accumulate credentials across providers.", "status": "proposed", "docs": [] }, { "id": "research-credentials", "name": "Research Credentials & Lab Access", "description": "Researchers carry institutional affiliations, lab safety certifications, equipment qualifications, and IRB approvals. Visiting researchers gain lab access by presenting verified credentials from their manifest.", "status": "unexplored", "docs": [] }, { "id": "peer-review-identity", "name": "Peer Review Identity", "description": "Peer reviewers carry their review history, domain expertise attestations, and journal relationships as manifest facets. Editors verify reviewer qualifications; reviewers build portable reputation across journals.", "status": "unexplored", "docs": [] }, { "id": "institutional-affiliations", "name": "Institutional Affiliation Portability", "description": "Faculty, students, and staff carry institutional affiliations as verifiable facets — enabling library access, conference registration, and collaboration invitations based on verified affiliation.", "status": "proposed", "docs": [] }, { "id": "scholarship-verification", "name": "Scholarship & Grant Verification", "description": "Scholarship awards, grant funding, and fellowship status carried as verifiable facets. Institutions verify existing funding; funders track recipient outcomes; students prove eligibility for additional support.", "status": "unexplored", "docs": [] }, { "id": "continuing-education", "name": "Continuing Education & CPD", "description": "Continuing professional development credits, CE units, and recertification progress tracked as manifest facets across providers. Licensing boards verify CPD compliance from the manifest.", "status": "proposed", "docs": [] }, { "id": "skill-attestations", "name": "Verified Skill Attestations", "description": "Specific skills — programming languages, laboratory techniques, surgical procedures, language proficiency — attested by qualified evaluators and carried as verifiable facets. Skills are portable across employers and platforms.", "status": "proposed", "docs": [] } ] }, { "id": "government-civic", "name": "Government & Civic", "description": "Public sector identity, civic participation, and government service access. Citizens carry verifiable identity facets that interact with government systems — from voting to tax filing to benefit eligibility — with privacy-preserving selective disclosure.", "status": "proposed", "docs": [], "children": [ { "id": "voter-identity", "name": "Voter Identity & Participation", "description": "Voter registration, district assignment, and participation history as verifiable facets. Prove registration without revealing vote choices; verify eligibility across jurisdictions for those who move.", "status": "unexplored", "docs": [] }, { "id": "tax-identity", "name": "Tax Identity & Filing", "description": "Taxpayer identification, filing status, and withholding preferences carried as manifest facets. Financial institutions report to verified tax identity; cross-border workers manage multi-jurisdiction tax status.", "status": "unexplored", "docs": [] }, { "id": "benefit-eligibility", "name": "Benefit Eligibility & Access", "description": "Government benefit eligibility — unemployment, disability, social security, housing assistance — verified from manifest facets. Prove eligibility without repeatedly submitting documentation to each agency.", "status": "unexplored", "docs": [] }, { "id": "public-service-access", "name": "Public Service Access", "description": "Access government services — libraries, parks, transit, utilities — with verified resident identity from the manifest. One identity for all public services instead of separate accounts per agency.", "status": "unexplored", "docs": [] }, { "id": "municipal-services", "name": "Municipal Service Identity", "description": "City and county services — permits, inspections, waste management, water/sewer — accessed through verified resident manifests. Submit permit applications with pre-verified identity and property ownership.", "status": "unexplored", "docs": [] }, { "id": "property-records", "name": "Property Ownership Records", "description": "Real property ownership, deed records, liens, and easements represented as verifiable manifest facets. Title searches verify ownership from the manifest; property transfers update facets.", "status": "unexplored", "docs": [] }, { "id": "business-registration", "name": "Business Registration & Licensing", "description": "Business registration, operating licenses, and regulatory permits carried as organizational manifest facets. Regulators verify compliance; partners verify legitimacy; customers verify authorization.", "status": "proposed", "docs": [] }, { "id": "public-comment-identity", "name": "Public Comment & Civic Participation", "description": "Participate in public comment periods, town halls, and civic processes with verified resident identity. Prevent astroturfing while protecting privacy through selective disclosure of relevant residency/stakeholder status.", "status": "unexplored", "docs": [] } ] }, { "id": "social-community", "name": "Social & Community", "description": "Social interactions, community memberships, and relationship management. UM manifests carry your social graph, group memberships, moderation history, and community roles — enabling social context to travel with you.", "status": "documented", "docs": ["site/src/content/docs/integrations/social.md"], "children": [ { "id": "social-graph-portability", "name": "Social Graph Portability", "description": "Friend lists, follower relationships, and social connections travel with you between platforms. Arrive on a new social network and immediately see which connections are already there.", "status": "documented", "docs": ["site/src/content/docs/integrations/social.md"] }, { "id": "group-memberships", "name": "Group & Community Memberships", "description": "Memberships in groups, clubs, guilds, unions, and professional associations carried as verifiable facets. New platforms recognize existing memberships; organizations verify member status across contexts.", "status": "proposed", "docs": [] }, { "id": "moderation-history", "name": "Moderation & Trust History", "description": "Moderation actions — warnings, bans, positive contributions — carried as contextual reputation facets. Platforms can check moderation history for risk assessment while subjects can contest inaccurate records.", "status": "proposed", "docs": [] }, { "id": "community-reputation", "name": "Community Reputation Scores", "description": "Reputation earned through participation — helpful answers, quality contributions, mentorship, moderation — carried as verifiable attestations across community platforms.", "status": "proposed", "docs": [] }, { "id": "community-roles", "name": "Community Roles & Positions", "description": "Roles within communities — moderator, admin, mentor, organizer — represented as verifiable facets. Earned authority in one community is recognizable in related communities.", "status": "proposed", "docs": [] }, { "id": "event-attendance", "name": "Event Attendance & Participation", "description": "Conference attendance, workshop participation, meetup history, and event-specific credentials carried as verifiable facets. Event organizers verify past attendance; attendees build professional event histories.", "status": "proposed", "docs": [] }, { "id": "volunteer-records", "name": "Volunteer Service Records", "description": "Volunteer hours, service projects, and community impact attestations carried as verifiable facets. Nonprofits verify volunteer history; volunteers build portable service records across organizations.", "status": "unexplored", "docs": [] }, { "id": "donor-history", "name": "Charitable Donor History", "description": "Donation history, giving levels, and donor recognition carried as manifest facets. Nonprofits recognize returning donors; donors track giving impact across organizations.", "status": "unexplored", "docs": [] }, { "id": "fan-club-memberships", "name": "Fan Club & Membership Portability", "description": "Fan club memberships, loyalty tiers, and fandom engagement history carried across platforms. Creators verify their fans; fans carry earned status and perks between fan platforms.", "status": "unexplored", "docs": [] }, { "id": "dating-profiles", "name": "Dating Profile Portability", "description": "Verified identity attributes for dating contexts — age verification, photo verification, interest attestations — carried between dating platforms. Reduce catfishing through verifiable identity facets while preserving privacy.", "status": "unexplored", "docs": [] } ] }, { "id": "infrastructure-protocol", "name": "Infrastructure & Protocol", "description": "The technical foundation: resolver architecture, cryptographic profiles, schema registries, encoding formats, federation protocols, and caching strategies that make UM work at scale across diverse implementations.", "status": "proven", "docs": ["site/src/content/docs/spec/v0.2.md", "site/src/content/docs/reference/resolver-api.md"], "children": [ { "id": "resolver-architecture", "name": "Resolver Architecture", "description": "The myum.net resolver translates UM identifiers into manifest locations. Resolvers are federated — anyone can run one. The architecture supports caching, failover, and geographic distribution.", "status": "proven", "docs": ["site/src/content/docs/reference/resolver-api.md", "docs/explainers/resolver-deep-dive.md", "docs/journeys/journey-04-umid-resolution-myum.md"] }, { "id": "signature-profiles", "name": "Cryptographic Signature Profiles", "description": "UM manifests are signed using Ed25519 with JCS (JSON Canonicalization Scheme) for deterministic serialization. The spec defines signature profiles, verification algorithms, and key representation formats.", "status": "proven", "docs": ["site/src/content/docs/spec/v0.2.md", "docs/journeys/journey-03-signature-verification-v0-2.md"] }, { "id": "jsonld-context", "name": "JSON-LD Context & Namespace", "description": "UM manifests use JSON-LD for semantic interoperability. The UM context defines the vocabulary; extensions register additional terms. Manifests are both human-readable JSON and machine-processable linked data.", "status": "proven", "docs": ["site/src/content/docs/spec/v0.2.md"] }, { "id": "facet-schema-registry", "name": "Facet Schema Registry", "description": "A registry of known facet types with their JSON schemas, validation rules, and semantic definitions. New facet types are proposed through the RFC process and registered upon acceptance.", "status": "documented", "docs": ["site/src/content/docs/spec/v0.2.md"] }, { "id": "pointer-types-registry", "name": "Pointer Types Registry", "description": "UM pointers link manifest facets to external resources — DID documents, VCs, social profiles, payment endpoints. The pointer registry defines known types and their resolution semantics.", "status": "documented", "docs": ["site/src/content/docs/spec/v0.2.md"] }, { "id": "consent-vocabulary", "name": "Consent Vocabulary & Ontology", "description": "The formal vocabulary for expressing consent in UM manifests — grant types, scope definitions, temporal constraints, audience identifiers, and purpose codes. Machine-readable consent that implementations process consistently.", "status": "documented", "docs": ["site/src/content/docs/spec/v0.2.md"] }, { "id": "ttl-policies", "name": "TTL & Freshness Policies", "description": "Time-to-live policies control manifest caching and freshness. Resolvers respect TTL headers; relying parties re-verify expired manifests. Subjects control how long their data stays cached.", "status": "proven", "docs": ["docs/journeys/journey-02-ttl-and-freshness.md"] }, { "id": "caching-strategies", "name": "Caching & Content Delivery Strategies", "description": "How manifest data is cached across resolvers, CDNs, and edge nodes — ETag-based validation, SHA-256 content hashing, conditional requests, and cache invalidation on manifest updates.", "status": "documented", "docs": ["docs/explainers/hashing-and-data-bundling-deep-dive.md"] }, { "id": "federation-protocols", "name": "Federation & Bridge Protocols", "description": "How UM resolvers federate — discovering peers, synchronizing records, resolving cross-resolver queries, and bridging between UM and external identity systems (OIDC, SAML, ActivityPub).", "status": "documented", "docs": ["docs/reports/2026-03-06-federation-and-bridge-strategy-decision-package.md"] }, { "id": "bridge-specifications", "name": "External System Bridge Specifications", "description": "Bridges between UM and existing identity systems: OIDC token-to-manifest projection, SAML assertion-to-facet mapping, ActivityPub actor-to-manifest linking, and OAuth scope-to-consent translation.", "status": "proposed", "docs": [] }, { "id": "content-addressing", "name": "Content Addressing & Integrity", "description": "Content-addressable manifest storage using cryptographic hashes. Verify manifest integrity without trusting the transport. CID (Content Identifier) support deferred pending ecosystem maturity assessment.", "status": "documented", "docs": ["docs/explainers/hashing-and-data-bundling-deep-dive.md"] }, { "id": "binary-encoding", "name": "Binary Encoding Profiles", "description": "Compact binary representations of UM manifests for bandwidth-constrained contexts — IoT devices, mobile networks, spatial computing handshakes. CBOR-LD profile planned for future specification versions.", "status": "proposed", "docs": ["docs/explainers/hashing-and-data-bundling-deep-dive.md"] }, { "id": "facet-encryption", "name": "Facet Encryption & Selective Disclosure", "description": "Encryption approaches for protecting facet data at rest and in transit — JWE envelope encryption, BBS+ selective disclosure, HPKE hybrid encryption — enabling verifiable facets that only authorized parties can read.", "status": "documented", "docs": ["docs/explainers/facet-encryption-deep-dive.md"] }, { "id": "rp1-spatial-fabric", "name": "RP1 Spatial Fabric Integration", "description": "Integration with the RP1/MSF spatial fabric for decentralized spatial computing — attachment traversal, session context, and spatial anchor identity managed through UM manifests.", "status": "proven", "docs": ["site/src/content/docs/integrations/rp1-spatial-fabric.md", "docs/journeys/journey-07-rp1-spatial-fabric-projection.md", "docs/journeys/J22-rp1-attachment-freshness-and-session-safety.md"] }, { "id": "omatrust-integration", "name": "OMATrust Attestation Integration", "description": "Integration with the OMA3 OMATrust attestation framework for verified trust signals in metaverse and spatial computing contexts.", "status": "proven", "docs": ["site/src/content/docs/integrations/oma-trust.md", "docs/journeys/J11-omatrust-attestation-interoperability.md"] } ] } ] }