Lilith Metaverse · Guides & deep dives

V3 Documentation Guide

The feature and architecture sets describe the intended contract and the code-grounded system shape.

6sections4 minread1table

On this page

This guide is the curated front door to V3, Lilith Metaverse: an embodied, multi-user world spanning native Unreal clients, pixel streaming, a web fallback, persistent rooms, avatars and spatial audio, Tara classes, Saraswati performances, Lilith Studio, commerce, rights, safety, and global operations. It complements the separate Lilith handbook, which disambiguates the member persona, V1 policy substrate, service domain, and V3 product.

Documentation map#

V3 documentationMind map: 21 ideas.V3 documentationMember worldRooms presence andmultiplayerAvatars nameplates andspatial audioTiered clients andaccessibilityIdentity safety andprovenanceTenant experiencesTara classes and coachingSaraswati artists andperformancesCommons venues and liveserviceLilith Studio creator toolsPlatformWorld server and gatewayPixel streaming andfallback webContent and assetpipelinesData commerce rights andoperationsDelivery truthV3 backlog anddependenciesProduct review and GAinventoryValidation reports andrunbooksRegion rollout andcertification
Mind map: V3 documentation. Mind map: 21 ideas.

Drawn from its Mermaid source.

As text
Tree:
- V3 documentation
  - Member world
    - Rooms presence and multiplayer
    - Avatars nameplates and spatial audio
    - Tiered clients and accessibility
    - Identity safety and provenance
  - Tenant experiences
    - Tara classes and coaching
    - Saraswati artists and performances
    - Commons venues and live service
    - Lilith Studio creator tools
  - Platform
    - World server and gateway
    - Pixel streaming and fallback web
    - Content and asset pipelines
    - Data commerce rights and operations
  - Delivery truth
    - V3 backlog and dependencies
    - Product review and GA inventory
    - Validation reports and runbooks
    - Region rollout and certification
Show source
mindmap
  root((V3 documentation))
    Member world
      Rooms presence and multiplayer
      Avatars nameplates and spatial audio
      Tiered clients and accessibility
      Identity safety and provenance
    Tenant experiences
      Tara classes and coaching
      Saraswati artists and performances
      Commons venues and live service
      Lilith Studio creator tools
    Platform
      World server and gateway
      Pixel streaming and fallback web
      Content and asset pipelines
      Data commerce rights and operations
    Delivery truth
      V3 backlog and dependencies
      Product review and GA inventory
      Validation reports and runbooks
      Region rollout and certification

The feature and architecture sets describe the intended contract and the code-grounded system shape. The backlog, current runtime, builds, provider readback, validation artifacts, operational evidence, and region/certification records determine what can honestly be called supported.

Start with the question#

Question Canonical starting point What it covers
What experience does V3 promise? Feature hub and focused feature index Worlds, client tiers, avatars, tenants, creation, trust, commerce, quality, and launch.
How does a member enter and remain in a room? World/presence features, world server, and netcode Join, authority, presence, replication, physics, reconnect, and failure behavior.
How do client tiers differ? Client-tier feature guide, tier router, UE client, and fallback client Eligibility, routing, fidelity, assets, capacity, degradation, and accessibility.
How do Tara, Saraswati, and Commons remain distinct? Lilith handbook, Tara architecture, and Saraswati pipeline Tenant identity, authoring, runtime boundaries, rights, and shared-world composition.
How are identity, consent, provenance, and rights enforced? Identity/safety foundations, persona policy, and data/tenancy Account bridge, body policy, recording consent, C2PA, tenancy, residency, takedown, and DSAR.
What is actually launch-ready? V3 backlog, GA inventory, launch readiness, validation records, and current release gates Evidence-backed status by surface, platform, region, provider, and operational capability.
Which systems are shared? Dependency registry and V1 integration V1 identity/contracts/audit plus shared generation, payment, safety, and platform dependencies.
Where are the visuals? V3 diagram atlas and the generated diagram gallery Curated client/world/content/trust models and every authored visual.

Truth and rollout model#

State diagramState diagram: 11 states and 11 transitions.code contract or authored asset existsclient edge world and shared services composetarget-tier functional and quality evidence passesplatform region rights and operations gates passenabled cohort receives the supported capabilitysupported only on named client or fidelity tierresidency rights provider or policy boundaryrequired evidence or production dependency absentnewer quality safety or operations evidence failsrepair returns below rollout readinessDesignedImplementedIntegratedValidatedCertifiedReleasedTierLimitedRegionLimitedWithheldRegressed
State machine: State diagram. State diagram: 11 states and 11 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)
- Designed
- Implemented
- Integrated
- Validated
- Certified
- Released
- TierLimited
- RegionLimited
- Withheld
- Regressed

Connections:
- Start to Designed
- Designed to Implemented: code contract or authored asset exists
- Implemented to Integrated: client edge world and shared services compose
- Integrated to Validated: target-tier functional and quality evidence passes
- Validated to Certified: platform region rights and operations gates pass
- Certified to Released: enabled cohort receives the supported capability
- Implemented to TierLimited: supported only on named client or fidelity tier
- Integrated to RegionLimited: residency rights provider or policy boundary
- Validated to Withheld: required evidence or production dependency absent
- Released to Regressed: newer quality safety or operations evidence fails
- Regressed to Implemented: repair returns below rollout readiness
Show source
stateDiagram-v2
  [*] --> Designed
  Designed --> Implemented: code contract or authored asset exists
  Implemented --> Integrated: client edge world and shared services compose
  Integrated --> Validated: target-tier functional and quality evidence passes
  Validated --> Certified: platform region rights and operations gates pass
  Certified --> Released: enabled cohort receives the supported capability
  Implemented --> TierLimited: supported only on named client or fidelity tier
  Integrated --> RegionLimited: residency rights provider or policy boundary
  Validated --> Withheld: required evidence or production dependency absent
  Released --> Regressed: newer quality safety or operations evidence fails
  Regressed --> Implemented: repair returns below rollout readiness

Always name the client tier, tenant, platform, region, role, entitlement, consent, provider, and rollout cohort that bound a claim. A working UE room does not prove the fallback client; a rendered avatar does not prove consent or rights; a configured pixel-streaming POP does not prove capacity; and a route or fixture is not a deployed world journey.

From V3 experience to supported rolloutUser journey: 8 stages.1Choose member tenant creator or operator pathOrient. Reader. Score 5 of 5.2Pair feature promise with architecture boundaryOrient. Product, Engineering. Score 5 of 5.3Follow client routing identity and world authorityTrace. Engineering. Score 5 of 5.4Inspect asset rights consent and durable dataTrace. Governance, Engineering. Score 5 of 5.5Run tier platform accessibility and reconnect journeysVerify. QA. Score 5 of 5.6Inspect capacity provider and regional evidenceVerify. SRE, Release. Score 5 of 5.7Certify gated cohort and rollback pathRoll out. Release. Score 5 of 5.8Update docs atlas runbooks and evidenceRoll out. Owners. Score 5 of 5.
User journey: From V3 experience to supported rollout. User journey: 8 stages.

Drawn from its Mermaid source.

As text
Steps:
- 1. Choose member tenant creator or operator path (good). Orient. Reader. Score 5 of 5.
- 2. Pair feature promise with architecture boundary (good). Orient. Product, Engineering. Score 5 of 5.
- 3. Follow client routing identity and world authority (good). Trace. Engineering. Score 5 of 5.
- 4. Inspect asset rights consent and durable data (good). Trace. Governance, Engineering. Score 5 of 5.
- 5. Run tier platform accessibility and reconnect journeys (good). Verify. QA. Score 5 of 5.
- 6. Inspect capacity provider and regional evidence (good). Verify. SRE, Release. Score 5 of 5.
- 7. Certify gated cohort and rollback path (good). Roll out. Release. Score 5 of 5.
- 8. Update docs atlas runbooks and evidence (good). Roll out. Owners. Score 5 of 5.
Show source
journey
  title From V3 experience to supported rollout
  section Orient
    Choose member tenant creator or operator path: 5: Reader
    Pair feature promise with architecture boundary: 5: Product, Engineering
  section Trace
    Follow client routing identity and world authority: 5: Engineering
    Inspect asset rights consent and durable data: 5: Governance, Engineering
  section Verify
    Run tier platform accessibility and reconnect journeys: 5: QA
    Inspect capacity provider and regional evidence: 5: SRE, Release
  section Roll out
    Certify gated cohort and rollback path: 5: Release
    Update docs atlas runbooks and evidence: 5: Owners

Product and experience design#

Use the feature index to choose a member, tenant, creator, trust, commerce, or operations path. Read the companion architecture page before making cross-tier promises. V3 deliberately preserves different fidelity envelopes; accessible equivalence means the same core job and honest disclosure, not pixel-identical realization.

Engineering and content production#

Use the architecture index to trace tier routing, world authority, protocol/versioning, avatars/audio, tenant pipelines, authored assets, data residency, V1 composition, commerce, observability, and release. Follow identifiers and receipts across the BFF, realtime gateway, world server, stores, asset pipeline, and clients.

QA, accessibility, safety, and rights#

Exercise join/rejoin, capacity refusal, degraded tier, stale assets, version mismatch, muted/blocked actors, recording consent changes, takedown, entitlement loss, localization expansion, assistive input, motion/flash/audio alternatives, and provider failure. Safety and rights must remain effective at the embodied surface, not only in a web control plane.

SRE, release, and regional operations#

Pair the operations/launch architecture page with the committed validation, capacity, store-size, transport-security, region, DR, SLO, day-zero patch, and incident runbooks. Treat dated validation as a snapshot; current deployment and provider readback decide whether it is still applicable.

Page-set organization#

  • Feature index — 16 focused topics across product orientation, metaverse platform, Tara, Saraswati, Commons/creation, and trust/commerce/quality/operations.
  • Architecture index — 16 focused topics across client tiers, realtime, embodiment, tenant experiences, authoring/data/V1 integration, trust, commerce, and launch.
  • Lilith handbook — eight cross-cutting identity/product topics that prevent the Lilith names from being conflated.
  • V3 diagram atlas — client, room, identity, content, rights, rollout, and operational mental models.
  • Root validation, operations, runbook, security, release, legal, and regional records — focused evidence rather than replacements for the canonical model.

Documentation quality contract#

Every canonical feature and architecture topic must remain substantial, reachable exactly once from its index, visually explain its principal complex relationship, distinguish product intent from runtime evidence, and link to the owning contracts/code/tests/evidence. The guide, atlas, Lilith handbook, global search, sibling navigation, diagram gallery, links, and desktop/mobile reader must remain generated and verified.

Edit source Markdown and canonical implementation/evidence, then regenerate the Docs Center. Generated HTML is never the authoring surface.