Skip to content
Universal Manifest

Metaverse

This page captures the metaverse integration lane for Universal Manifest.

Metaverse Integration

Lineage note

Section titled “Lineage note”

Universal Manifest is explicitly descended from the earlier Metaverse Universal Manifest (MUM) concept.

Universal Manifest generalizes that origin into a broader cross-domain standard while preserving metaverse portability as a first-class integration path.

Boundary: normative vs non-normative

Section titled “Boundary: normative vs non-normative”
  • Normative contract: Specification and Conformance
  • Non-normative guidance: this page

What to implement

Section titled “What to implement”
  • Validate manifest freshness and version rules before world projection
  • Map identity, profile, avatar, and social graph references through shards and pointers
  • Apply consent controls before publishing profile, voice, and social graph data
  • Default to deny when a required consent is absent

Suggested pointer names

Section titled “Suggested pointer names”
  • metaverse.profile
  • metaverse.avatar
  • metaverse.inventory
  • metaverse.socialGraph
Section titled “Suggested consent keys”
  • metaverse.profilePublic
  • metaverse.socialGraphShare
  • metaverse.voiceCapture
  • metaverse.recording.faceVisible

Next

Section titled “Next”