This directory holds the V3 (Lilith Metaverse — an embodied, multi-user world)
feature map, decomposed from the single ../V3_features.md
hub into focused, in-depth, code-grounded pages. The hub remains the canonical
entry point and preserves every section heading (so existing features§"…"
cross-references keep resolving); each page below expands one part of the
product with far richer, code-grounded detail and an honest implemented /
spec-only status. The companion architecture reference lives in
../architecture/.
Cross-reference convention. Page-to-page links are relative (
./<slug>.md); the architecture companion for a feature page is linked as../architecture/<slug>.md. Platform-foundation links point at the sharedplatform/space.
Feature landscape#
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: - Lilith member - Identity entitlement consent and client tier - World rooms presence multiplayer avatars and spatial audio - Tara instructors classes authoring and Aja coaching - Saraswati artists discography stage fan economy and rights - Commons venues programming and V1 experiences - Lilith Studio creator - Scene room avatar and content pipeline - Safety provenance recording consent commerce and takedown - Accessibility localization quality rollout and operations Connections: - Lilith member to Identity entitlement consent and client tier - Identity entitlement consent and client tier to World rooms presence multiplayer avatars and spatial audio - World rooms presence multiplayer avatars and spatial audio to Tara instructors classes authoring and Aja coaching - World rooms presence multiplayer avatars and spatial audio to Saraswati artists discography stage fan economy and rights - World rooms presence multiplayer avatars and spatial audio to Commons venues programming and V1 experiences - Lilith Studio creator to Scene room avatar and content pipeline - Scene room avatar and content pipeline to Tara instructors classes authoring and Aja coaching - Scene room avatar and content pipeline to Saraswati artists discography stage fan economy and rights - Scene room avatar and content pipeline to Commons venues programming and V1 experiences - Tara instructors classes authoring and Aja coaching to Safety provenance recording consent commerce and takedown - Saraswati artists discography stage fan economy and rights to Safety provenance recording consent commerce and takedown - Commons venues programming and V1 experiences to Safety provenance recording consent commerce and takedown - Safety provenance recording consent commerce and takedown to Accessibility localization quality rollout and operations
Show source
flowchart TB
Member[Lilith member] --> Access[Identity entitlement consent and client tier]
Access --> World[World rooms presence multiplayer avatars and spatial audio]
World --> Tara[Tara instructors classes authoring and Aja coaching]
World --> Saraswati[Saraswati artists discography stage fan economy and rights]
World --> Commons[Commons venues programming and V1 experiences]
Creator[Lilith Studio creator] --> Pipeline[Scene room avatar and content pipeline]
Pipeline --> Tara
Pipeline --> Saraswati
Pipeline --> Commons
Tara --> Trust[Safety provenance recording consent commerce and takedown]
Saraswati --> Trust
Commons --> Trust
Trust --> Operations[Accessibility localization quality rollout and operations]
The landscape keeps the member world, tenant experiences, creator pipeline, trust plane, and operational envelope distinct while showing their composition. A tenant feature is not automatically shared-world behavior; a Studio preview is not a released room; and fidelity can differ by client tier without changing identity, rights, safety, or core task semantics.
Use the index in three passes. Start with the page that owns the member, creator, tenant, trust, commerce, or operations promise. Pair it with the corresponding architecture page to trace routing, authority, content/data, providers, and evidence. Then inspect the backlog, dependencies, GA/launch records, current builds/tests, regional posture, and operational validation before describing a capability as supported.
Every focused feature topic appears exactly once below. Cross-links preserve the relationships without creating competing canonical homes. The V3 documentation guide provides role and truth-oriented reading paths, the Lilith handbook disambiguates the related identities/products, and the diagram atlas provides client, world, content, rights, and rollout models.
Orientation#
- Overview, Subsystem Glossary & Product Promise — what V3 commits to as an embodied metaverse, and every subsystem mapped to code.
- Product Surfaces — the tiered clients, Lilith Studio authoring, and the operator/web surfaces.
Metaverse Platform#
- World, Rooms, Presence & Multiplayer — the world model/scenes, rooms/sharding/capacity, presence, and multiplayer.
- Avatars, Nameplates & Spatial Audio — the avatar pipeline, nameplate LOD, and 3D spatial audio.
- Client Tiers, Fidelity & the Stadium Envelope — cross-platform clients, the tier-2 fidelity envelope, and stadium-scale audiences.
- Identity, Embodied Safety & Provenance Foundations — the identity/account bridge, embodied safety/persona policy, and provenance.
Tara Studio#
- Tara Studio: Instructors, Classes & Coaching — instructor onboarding/verification, live class sessions, and body-aware coaching.
- Tara Studio: Sequence Authoring, Personas, Tone & Economics — the asana/sequence editor, AI personas, tone/lineage/citation, and economics.
Saraswati Stage#
- Saraswati Stage: Personas, Discography & Performance — persistent AI artist personas, the discography/generation pipeline, and live shows.
- Saraswati Stage: Fan Economy, Voice, Genre & Rights — the fan economy, voice/genre models, and collaboration/remix/sampling rights.
Commons, Creator Suite & Live-Service#
- Lilith Commons, Venues & Live Service — persistent venues, re-rendered V1 experiences, and live-service programming.
- Creator Suite — Lilith Studio — scene/room authoring, avatar/costume authoring, and the creator workflow.
Trust, Commerce, Quality & Operations#
- Governance, Safety & Recording-Consent — minor-protection mode, harassment/abuse response, and the recording-consent flow.
- Commerce, Rights & Takedown — tickets/tips/ subscriptions, cancellation/refund policy, and rights/takedown.
- Accessibility, Localization & Quality — accessibility in 3D, localization, and the telemetry/eval/quality sets.
- Operations, Rollout & Launch — cross-platform/cross-progression, region rollout, operator staffing, and launch.