Lilith Metaverse · Guides & deep dives

V3 Diagram Atlas

Tier selection changes realization and capacity, not the governing member, room, tenant, rights, and safety identities.

9sections2 minread

On this page

This atlas provides the cross-cutting visual models for Lilith Metaverse. It shows client-tier routing, room join, durable identity and consent, session state, contract composition, tenant ownership, creator-to-live delivery, and rollout evidence. Focused pages remain authoritative for detail and current runtime/validation evidence determines support.

Client, world, and tenant landscape#

FlowchartFlowchart: 15 steps and 16 connections.Member device andeligibilityTier routerNative UE5 clientPixel-streamed UE sessionFallback web clientRealtime gatewayPixel-streaming fleetAuthoritative world serverRooms presence physicsand interactionTara classes and coachingSaraswati stage and artistsLilith Commons andvenuesLilith StudioContent asset rights andreview pipelineIdentity data commercesafety provenance andaudit
Flowchart: Flowchart. Flowchart: 15 steps and 16 connections.

This picture is wider than it can be shown here. Move across it, or read it as text.

Drawn from its Mermaid source.

As text
Parts:
- Member device and eligibility
- Tier router
- Native UE5 client
- Pixel-streamed UE session
- Fallback web client
- Realtime gateway
- Pixel-streaming fleet
- Authoritative world server
- Rooms presence physics and interaction
- Tara classes and coaching
- Saraswati stage and artists
- Lilith Commons and venues
- Lilith Studio
- Content asset rights and review pipeline
- Identity data commerce safety provenance and audit

Connections:
- Member device and eligibility to Tier router
- Tier router to Native UE5 client
- Tier router to Pixel-streamed UE session
- Tier router to Fallback web client
- Native UE5 client to Realtime gateway
- Pixel-streamed UE session to Pixel-streaming fleet
- Pixel-streaming fleet to Realtime gateway
- Fallback web client to Realtime gateway
- Realtime gateway to Authoritative world server
- Authoritative world server to Rooms presence physics and interaction
- Rooms presence physics and interaction to Tara classes and coaching
- Rooms presence physics and interaction to Saraswati stage and artists
- Rooms presence physics and interaction to Lilith Commons and venues
- Lilith Studio to Content asset rights and review pipeline
- Content asset rights and review pipeline to Rooms presence physics and interaction
- Authoritative world server to Identity data commerce safety provenance and audit
Show source
flowchart TB
  Member[Member device and eligibility] --> Router[Tier router]
  Router --> UE[Native UE5 client]
  Router --> Pixel[Pixel-streamed UE session]
  Router --> Web[Fallback web client]
  UE --> Gateway[Realtime gateway]
  Pixel --> Fleet[Pixel-streaming fleet]
  Fleet --> Gateway
  Web --> Gateway
  Gateway --> World[Authoritative world server]
  World --> Rooms[Rooms presence physics and interaction]
  Rooms --> Tara[Tara classes and coaching]
  Rooms --> Saraswati[Saraswati stage and artists]
  Rooms --> Commons[Lilith Commons and venues]
  Studio[Lilith Studio] --> Pipeline[Content asset rights and review pipeline]
  Pipeline --> Rooms
  World --> Shared[Identity data commerce safety provenance and audit]

Tier selection changes realization and capacity, not the governing member, room, tenant, rights, and safety identities. Studio publishes governed content; it does not write directly into a live authoritative world.

Room join sequence#

sequenceDiagram actor Member participant Surface as Client surface participant Router as Tier router participant Identity as Identity and policy participant Gateway as Realtime gateway participant World as World server participant Room as Room shard Member->>Surface: Open room Surface->>Router: Device network entitlement and preferences Router->>Identity: Resolve account tenant region consent and policy alt denied or unavailable Identity-->>Surface: Named refusal and recovery options else admitted Identity-->>Router: Scoped room capability Router-->>Surface: Tier endpoint asset and protocol versions Surface->>Gateway: Authenticated join envelope Gateway->>World: Reserve presence and route shard World->>Room: Spawn governed avatar and state Room-->>Surface: Snapshot peers capabilities and disclosures Surface-->>Member: Interactive room end

Admission, tier allocation, protocol compatibility, world presence, avatar spawn, and visible readiness are separate. A reservation is not a completed join, and a client frame is not proof that the authoritative presence exists.

Entity-relationship diagramEntity-relationship diagram: 14 entities and 15 relationships.bindsholdsgrantsownshostsjoinscontrolsversionsrequiresdecidespublishescontainsrecordsrequiresproducesACCOUNTIDENTITY_LINKMEMBERSHIPTENANTROOMPRESENCE_SESSIONAVATAR_PROFILEAVATAR_VERSIONRECORDING_CONSENTCONTENT_RELEASEASSETPROVENANCERIGHTS_GRANTAUDIT_EVENT
Entity-relationship diagram: Entity-relationship diagram. Entity-relationship diagram: 14 entities and 15 relationships.

This picture is wider than it can be shown here. Move across it, or read it as text.

Drawn from its Mermaid source.

As text
Parts:
- ACCOUNT
- IDENTITY_LINK
- MEMBERSHIP
- TENANT
- ROOM
- PRESENCE_SESSION
- AVATAR_PROFILE
- AVATAR_VERSION
- RECORDING_CONSENT
- CONTENT_RELEASE
- ASSET
- PROVENANCE
- RIGHTS_GRANT
- AUDIT_EVENT

Connections:
- ACCOUNT to IDENTITY_LINK (one to zero or many): binds
- ACCOUNT to MEMBERSHIP (one to zero or many): holds
- TENANT to MEMBERSHIP (one to zero or many): grants
- TENANT to ROOM (one to zero or many): owns
- ROOM to PRESENCE_SESSION (one to zero or many): hosts
- ACCOUNT to PRESENCE_SESSION (one to zero or many): joins
- ACCOUNT to AVATAR_PROFILE (one to zero or many): controls
- AVATAR_PROFILE to AVATAR_VERSION (one to zero or many): versions
- ROOM to RECORDING_CONSENT (one to zero or many): requires
- ACCOUNT to RECORDING_CONSENT (one to zero or many): decides
- TENANT to CONTENT_RELEASE (one to zero or many): publishes
- CONTENT_RELEASE to ASSET (one to zero or many): contains
- ASSET to PROVENANCE (one to zero or many): records
- CONTENT_RELEASE to RIGHTS_GRANT (one to zero or many): requires
- PRESENCE_SESSION to AUDIT_EVENT (one to zero or many): produces
Show source
erDiagram
  ACCOUNT ||--o{ IDENTITY_LINK : binds
  ACCOUNT ||--o{ MEMBERSHIP : holds
  TENANT ||--o{ MEMBERSHIP : grants
  TENANT ||--o{ ROOM : owns
  ROOM ||--o{ PRESENCE_SESSION : hosts
  ACCOUNT ||--o{ PRESENCE_SESSION : joins
  ACCOUNT ||--o{ AVATAR_PROFILE : controls
  AVATAR_PROFILE ||--o{ AVATAR_VERSION : versions
  ROOM ||--o{ RECORDING_CONSENT : requires
  ACCOUNT ||--o{ RECORDING_CONSENT : decides
  TENANT ||--o{ CONTENT_RELEASE : publishes
  CONTENT_RELEASE ||--o{ ASSET : contains
  ASSET ||--o{ PROVENANCE : records
  CONTENT_RELEASE ||--o{ RIGHTS_GRANT : requires
  PRESENCE_SESSION ||--o{ AUDIT_EVENT : produces

Account links, tenant membership, room presence, avatar versions, consent, content versions, rights, provenance, and audit remain independently addressable so unlinking, takedown, DSAR, and incident review can be correct.

Presence session lifecycle#

State diagramState diagram: 12 states and 16 transitions.identity policy and tier admittedentitlement region safety or capacityendpoint and compatible assets reservedauthoritative snapshot appliedasset protocol or provider failurequality capacity or modality fallbacktarget service restoredtransient transport lossbounded session resumeresume budget expiresleave kick ban or room closurereceipts and presence cleanupRequestedAllocatingRefusedLoadingPresentFailedDegradedReconnectingEndedRemoved
State machine: State diagram. State diagram: 12 states and 16 transitions.

This picture is wider than it can be shown here. Move across it, or read it as text.

Drawn from its Mermaid source.

As text
Parts:
- Start (initial)
- Requested
- Allocating
- Refused
- Loading
- Present
- Failed
- Degraded
- Reconnecting
- Ended
- Removed
- End (final)

Connections:
- Start to Requested
- Requested to Allocating: identity policy and tier admitted
- Requested to Refused: entitlement region safety or capacity
- Allocating to Loading: endpoint and compatible assets reserved
- Loading to Present: authoritative snapshot applied
- Loading to Failed: asset protocol or provider failure
- Present to Degraded: quality capacity or modality fallback
- Degraded to Present: target service restored
- Present to Reconnecting: transient transport loss
- Reconnecting to Present: bounded session resume
- Reconnecting to Ended: resume budget expires
- Present to Removed: leave kick ban or room closure
- Removed to Ended: receipts and presence cleanup
- Failed to End
- Refused to End
- Ended to End
Show source
stateDiagram-v2
  [*] --> Requested
  Requested --> Allocating: identity policy and tier admitted
  Requested --> Refused: entitlement region safety or capacity
  Allocating --> Loading: endpoint and compatible assets reserved
  Loading --> Present: authoritative snapshot applied
  Loading --> Failed: asset protocol or provider failure
  Present --> Degraded: quality capacity or modality fallback
  Degraded --> Present: target service restored
  Present --> Reconnecting: transient transport loss
  Reconnecting --> Present: bounded session resume
  Reconnecting --> Ended: resume budget expires
  Present --> Removed: leave kick ban or room closure
  Removed --> Ended: receipts and presence cleanup
  Failed --> [*]
  Refused --> [*]
  Ended --> [*]

The reader and telemetry should distinguish refusal, failure, degraded service, reconnect, and governed removal. Cleanup must not leave ghost presence, recording, voice, entitlement, or billing state.

Shared contract composition#

classDiagram class JoinEnvelope { accountId tenantId roomId protocolVersion } class TierDecision { tier endpoint obligations } class RoomCapability { role grants consentState } class PresenceSnapshot { sessionId avatarVersion peers worldRevision } class ContentManifest { releaseId assetVersions provenanceRefs } JoinEnvelope --> TierDecision : evaluated into JoinEnvelope --> RoomCapability : authorized as TierDecision --> PresenceSnapshot : realizes RoomCapability --> PresenceSnapshot : scopes ContentManifest --> PresenceSnapshot : pins assets

Concrete protocols are richer, but the roles must remain visible: routing does not authorize, capability does not allocate capacity, and a snapshot pins the content and avatar versions that produced the visible world.

Tenant and platform estate#

Lilith MetaverseMind map: 21 ideas.Lilith MetaverseShared worldRooms presence andmultiplayerAvatars nameplates andspatial audioClient tiers andaccessibilityIdentity safety andprovenanceTaraInstructor verificationClass and sequenceauthoringLive sessions and AjacoachingLineage tone andeconomicsSaraswatiArtist personas anddiscographyMusic voice genre andrightsStage performance and faneconomyCollaboration remix androyaltiesCommons and creationPersistent venues andprogrammingLilith Studio and assetpipelineCommerce governance andtakedownOperations rollout and liveservice
Mind map: Lilith Metaverse. Mind map: 21 ideas.

Drawn from its Mermaid source.

As text
Tree:
- Lilith Metaverse
  - Shared world
    - Rooms presence and multiplayer
    - Avatars nameplates and spatial audio
    - Client tiers and accessibility
    - Identity safety and provenance
  - Tara
    - Instructor verification
    - Class and sequence authoring
    - Live sessions and Aja coaching
    - Lineage tone and economics
  - Saraswati
    - Artist personas and discography
    - Music voice genre and rights
    - Stage performance and fan economy
    - Collaboration remix and royalties
  - Commons and creation
    - Persistent venues and programming
    - Lilith Studio and asset pipeline
    - Commerce governance and takedown
    - Operations rollout and live service
Show source
mindmap
  root((Lilith Metaverse))
    Shared world
      Rooms presence and multiplayer
      Avatars nameplates and spatial audio
      Client tiers and accessibility
      Identity safety and provenance
    Tara
      Instructor verification
      Class and sequence authoring
      Live sessions and Aja coaching
      Lineage tone and economics
    Saraswati
      Artist personas and discography
      Music voice genre and rights
      Stage performance and fan economy
      Collaboration remix and royalties
    Commons and creation
      Persistent venues and programming
      Lilith Studio and asset pipeline
      Commerce governance and takedown
      Operations rollout and live service

The map prevents tenant concepts from being mistaken for shared-world authority. Each tenant composes platform services under its own product, content, rights, and operator boundaries.

Creator-to-live journey#

From V3 creator intent to live world contentUser journey: 8 stages.1Create room scene avatar class or performanceAuthor. Creator. Score 5 of 5.2Pin sources rights consent and tenant ownershipAuthor. Creator, Rights. Score 5 of 5.3Validate assets accessibility policy and performanceReview. QA, Governance. Score 5 of 5.4Approve immutable content releaseReview. Tenant operator. Score 5 of 5.5Bake tier variants and prewarm deliveryStage. Pipeline, SRE. Score 4 of 5.6Verify clients world server and rollbackStage. QA, Release. Score 5 of 5.7Publish cohort observe receipts and incidentsOperate. SRE. Score 5 of 5.8Takedown correct or roll back with auditOperate. Rights, Operators. Score 5 of 5.
User journey: From V3 creator intent to live world content. User journey: 8 stages.

Drawn from its Mermaid source.

As text
Steps:
- 1. Create room scene avatar class or performance (good). Author. Creator. Score 5 of 5.
- 2. Pin sources rights consent and tenant ownership (good). Author. Creator, Rights. Score 5 of 5.
- 3. Validate assets accessibility policy and performance (good). Review. QA, Governance. Score 5 of 5.
- 4. Approve immutable content release (good). Review. Tenant operator. Score 5 of 5.
- 5. Bake tier variants and prewarm delivery (good). Stage. Pipeline, SRE. Score 4 of 5.
- 6. Verify clients world server and rollback (good). Stage. QA, Release. Score 5 of 5.
- 7. Publish cohort observe receipts and incidents (good). Operate. SRE. Score 5 of 5.
- 8. Takedown correct or roll back with audit (good). Operate. Rights, Operators. Score 5 of 5.
Show source
journey
  title From V3 creator intent to live world content
  section Author
    Create room scene avatar class or performance: 5: Creator
    Pin sources rights consent and tenant ownership: 5: Creator, Rights
  section Review
    Validate assets accessibility policy and performance: 5: QA, Governance
    Approve immutable content release: 5: Tenant operator
  section Stage
    Bake tier variants and prewarm delivery: 4: Pipeline, SRE
    Verify clients world server and rollback: 5: QA, Release
  section Operate
    Publish cohort observe receipts and incidents: 5: SRE
    Takedown correct or roll back with audit: 5: Rights, Operators

The live result depends on authoring, rights, review, tier variants, runtime compatibility, and operations. A Studio preview proves only one part.

Rollout evidence order#

timeline title V3 rollout evidence Contract : Tenant room identity consent and rights model : Client-tier and protocol compatibility Runtime : World authority presence avatar audio and interaction : Asset pipeline shared services and regional data Validation : Functional accessibility quality and reconnect journeys : Capacity latency security rights and provider evidence Certification : Platform store region staffing DR and day-zero patch : Staged cohort observability and rollback Support : Named tiers platforms tenants regions and capabilities : Current incidents regressions and operational proof

This is an evidence sequence rather than a date promise. Each tier, platform, tenant, and region earns support through its own applicable gates.

How to use this atlas#

Use the landscape and estate to locate ownership, trace a join with the sequence/state diagrams, review identity and content with the ER/class models, and use the creator journey and rollout order at release review. Continue to the V3 guide, feature index, architecture index, and Lilith handbook.