V3 is one platform with three flagship tenant experiences. Each tenant owns its domain behavior and content while reusing the same identity, world, presence, safety, provenance, generation, commerce, and operational substrates.
Shared infrastructure does not flatten tenant policy: a Tara teaching rule, a Saraswati rights decision, and a Commons venue mode remain owned by their tenant domain.
Tenant responsibility split#
| Tenant | Primary experience | Owns | Reuses |
|---|---|---|---|
| Tara Studio | Live and on-demand yoga, breathwork, meditation, and movement. | Instructors, classes, asana sequences, practice plans, coaching, lineage/teaching rules, class economics. | World/presence, Aja pose, Iris continuity, Sophia grounding, Lilith policy, Aje payments, rights. |
| Saraswati Stage | Persistent AI virtual artists, music catalogs, concerts, and fan participation. | Artist personas, discographies, tracks, concert programming, genre/style cells, remix rights, artist/fan economy. | World/presence, Isis generation, Sophia grounding, Psyche realtime, Aje commerce, Themis disputes, provenance. |
| Lilith Commons | Open contemplative gardens, temples, observatories, salons, reading rooms, and civic spaces. | Venue programming, Commons modes, quiet/social rules, launch-localized room presentation. | World/presence and re-rendered V1 domain experiences. |
Tenant boundaries prevent a class policy, artist-rights decision, or Commons venue rule from becoming an accidental platform-wide default.
Tara Studio#
Tara supports verified human instructors and policy-governed supervised AI personas. The complete experience includes:
- instructor onboarding, credential/insurance and region checks;
- live and on-demand class scheduling, capacity, attendance, and recovery;
- asana/sequence authoring with invitational and trauma-informed language;
- Aja body-aware cues and physical-adjustment consent;
- accessible variants, eyes-open defaults, contraindication and safety handling;
- practice-plan continuity through permitted V1 identity/memory records;
- lineage and teaching claims grounded through Sophia;
- cohorts, private/donation classes, tips, compensation, and studio splits;
- recording, TTS/voice, and derivative-content consent;
- supervised AI-instructor sponsor, scope, regional, script, and review rules.
The focused product docs are Tara instructors, classes, and coaching and Tara authoring, personas, tone, and economics.
Saraswati Stage#
Saraswati treats an AI virtual artist as a governed, persistent creative entity rather than a disposable generation preset. The experience spans:
- persona dossier, voice signature, visual identity, policy lock, and grounded backstory;
- governed track creation, stems, mastering, metadata, C2PA/provenance, and discography release;
- scheduled concerts using performance/sequence, avatar, spatial audio, visual, and venue systems;
- genre/style cells that define creative scope without copying protected style;
- collaborations, remix/sample licenses, rights adjudication, and takedown;
- tickets, tips, subscriptions, signed editions, royalties, and creator splits;
- archived/degraded performance fallback when a live generation or fleet dependency is unavailable;
- transparent disclosure of synthetic voice, persona, and media provenance.
Read Saraswati personas, discography, and performance and Saraswati economy, voice, genre, and rights.
Lilith Commons#
Commons is the open venue layer for social and contemplative experiences. It can host gardens, temples, observatories, salons, reading rooms, debate halls, classrooms, weekly-review spaces, and intentionally solitary/quiet rooms. V1 domains can be re-rendered here without losing their source behavior:
- Tara ritual or practice rooms;
- Nyx observatory and shared sky events;
- Nisaba reading rooms and cited discussion;
- Veritas debate/evidence halls;
- Metis classrooms and lectures;
- Arete review and commitment spaces.
Re-rendering does not mean copying all domain data into the world. Each bridge uses the V1 API/authorization and passes only the minimum state needed for the embodied session.
The platform view is in Commons, venues, and live service.
Cross-tenant programming#
The live-service calendar can sequence classes, artist drops, concerts, festivals, reading/debate events, and Commons gatherings. Crossovers are explicit programs with rights and safety review—for example a Tara movement session accompanied by a Saraswati artist—rather than implicit sharing of tenant content.
Programming records should bind tenant, venue, participants/personas, locale, capacity, assets, rights/consent, accessibility profile, moderation posture, fallback, and release status. Calendar visibility is not proof that the event's content bundle or live capacity has cleared its gate.
Shared participant journey#
discover → eligibility/entitlement → launch decision → room join → presence
→ tenant activity → safety/rights/commerce receipts → continuity
→ leave/reconnect/replay or follow-up
Each transition has an honest fallback. A class can move to on-demand media; a concert can use a rights-cleared archived performance; a Commons room can reduce fidelity or capacity. The product must not silently substitute a different paid, recorded, or synthetic experience.
Tenant safety boundaries#
- Tara does not provide diagnosis, individualized medical treatment, or unconsented physical adjustment.
- Saraswati does not impersonate a real artist, clone a voice without consent, or treat generated provenance as a rights license.
- Commons does not weaken domain-specific evidence, conduct, minor-protection, or privacy policy because the interaction occurs in a social room.
- Cross-tenant events require the union of applicable safety and rights rules, not the least restrictive tenant policy.
Content and launch truth#
Inventory constants and readiness gates define the bar for instructors, artists, venues, and events; they do not prove that commissioned/approved content exists. Use the GA inventory, launch readiness, validation reports, and product backlog to assess current release state.