Lilith Metaverse · Architecture

V3 — Architecture (Page Index)

A focused page within the Lilith Metaverse Architecture documentation. The full map and every sibling page live in the Architecture hub.

7sections3 minread1diagram

On this page

This directory holds the V3 (Lilith Metaverse — an embodied, multi-user world) architecture reference, decomposed from the single ../V3_ARCHITECTURE.md hub into focused, in-depth, code-grounded pages. The hub remains the canonical entry point and preserves every section heading (so existing arch§"…" cross-references keep resolving); each page below expands one part of the system with far richer, code-grounded detail and an honest implemented / spec-only status. The companion feature map lives in the ../V3_features.md hub.

Cross-reference convention. Page-to-page links are relative (./<slug>.md); a bare §N points at a section of the V3 backlog, and arch§"<anchor>" points at a named section of the ../V3_ARCHITECTURE.md hub. Platform-foundation links point at the shared platform/ space.

Architecture landscape#

FlowchartFlowchart: 13 steps and 15 connections.Member device networkand eligibilityTier router and identitypolicyNative UE5 clientPixel-streaming edge andfleetFallback web clientRealtime gatewayAuthoritative world serverand room shardsAvatars animation spatialaudio and interactionTara Saraswati Commonsand tenant pluginsAuthoring and contentpipelinesTenant data contentversions residency andprovenanceV1 identity contracts auditsafety and commerceObservability performancesecurity certification andlaunch
Flowchart: Flowchart. Flowchart: 13 steps and 15 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 network and eligibility
- Tier router and identity policy
- Native UE5 client
- Pixel-streaming edge and fleet
- Fallback web client
- Realtime gateway
- Authoritative world server and room shards
- Avatars animation spatial audio and interaction
- Tara Saraswati Commons and tenant plugins
- Authoring and content pipelines
- Tenant data content versions residency and provenance (data)
- V1 identity contracts audit safety and commerce
- Observability performance security certification and launch

Connections:
- Member device network and eligibility to Tier router and identity policy
- Tier router and identity policy to Native UE5 client
- Tier router and identity policy to Pixel-streaming edge and fleet
- Tier router and identity policy to Fallback web client
- Native UE5 client to Realtime gateway
- Pixel-streaming edge and fleet to Realtime gateway
- Fallback web client to Realtime gateway
- Realtime gateway to Authoritative world server and room shards
- Authoritative world server and room shards to Avatars animation spatial audio and interaction
- Authoritative world server and room shards to Tara Saraswati Commons and tenant plugins
- Authoring and content pipelines to Tara Saraswati Commons and tenant plugins
- Tara Saraswati Commons and tenant plugins to Tenant data content versions residency and provenance
- Authoritative world server and room shards to V1 identity contracts audit safety and commerce
- Tenant data content versions residency and provenance to Observability performance security certification and launch
- V1 identity contracts audit safety and commerce to Observability performance security certification and launch
Show source
flowchart TB
  Device[Member device network and eligibility] --> Router[Tier router and identity policy]
  Router --> UE[Native UE5 client]
  Router --> Pixel[Pixel-streaming edge and fleet]
  Router --> Web[Fallback web client]
  UE --> Gateway[Realtime gateway]
  Pixel --> Gateway
  Web --> Gateway
  Gateway --> World[Authoritative world server and room shards]
  World --> Embodiment[Avatars animation spatial audio and interaction]
  World --> Tenants[Tara Saraswati Commons and tenant plugins]
  Studio[Authoring and content pipelines] --> Tenants
  Tenants --> Data[(Tenant data content versions residency and provenance)]
  World --> Shared[V1 identity contracts audit safety and commerce]
  Data --> Operations[Observability performance security certification and launch]
  Shared --> Operations

The diagram is a responsibility map, not a claim that all tiers, tenants, platforms, or regions are live. Tier routing, admission, realtime authority, embodiment, tenant content, durable data, shared services, and operations each produce different evidence and failure states.

Use this index to trace one experience from eligibility and tier selection through protocol/version negotiation, gateway/world authority, tenant and embodiment behavior, content/data/rights, shared V1 services, visible recovery, and operational receipts. Pair the trace with the feature index so infrastructure readiness is evaluated against the actual member or creator job.

Every focused architecture page appears exactly once below. The V3 documentation guide supplies the truth/rollout model and role paths, the Lilith handbook keeps names and product boundaries explicit, and the diagram atlas supplies the shared visual vocabulary. Current builds, validation, provider and regional evidence, backlog, and release gates govern completion.

Orientation#

Client Tiers and Edge Delivery#

Realtime Backbone#

Avatars, Audio, and Tenant Experiences#

Authoring, Data, and Platform Integration#

Trust, Rights, Commerce, and Operations#