Lilith Studio is the governed authoring surface for V3 scenes, rooms, avatars, costumes, personas, classes, music, concerts, and release packages. The studio coordinates domain workbenches and generation services; it is not one model prompt that emits a finished world.
Generation is one middle stage, not publication authority. The released bundle depends on source rights, lineage, domain review, target compatibility, and runtime evidence.
Creator surface map#
| Workspace | Primary artifacts | Key gates |
|---|---|---|
| Projects and scenes | Project, scene, room, shot, environment, prop placement. | Tenant/venue binding, asset compatibility, performance/accessibility profile. |
| Personas | Instructor or artist dossier, tone/policy, voice/avatar binding. | Identity/consent, policy release, cultural review, synthetic disclosure. |
| Tara asana/class | Asanas, sequences, cue scripts, class sessions, practice plans. | Physical safety, invitational language, lineage/source grounding, instructor/sponsor review. |
| Saraswati music | Brief, track/stems, voice, genre cell, discography release. | Reference rights, model/output provenance, similarity/rights, quality, royalty split. |
| Concerts | Set list, performance timeline, avatar/motion, venue, audio/visual cues. | Sync, capacity, rights, accessibility, rehearsal/prewarm, fallback package. |
| Asset library | Image/video/audio/3D/motion assets and variants. | Taxonomy, lineage, license/consent, technical quality, target profiles. |
| Review and release | Review packet, exceptions, provenance, target package, schedule. | Required reviewers, policy/rights/quality checks, transactional publish. |
The customer workflow guide is Lilith Studio publishing, with detailed walkthroughs under Lilith Studio.
Project and scene authoring#
A project establishes tenant, audience, locale/region, target client tiers, rights posture, and collaborators. Scenes and rooms bind world/venue identity, streaming cells, navigation, interaction, lighting, audio, accessibility, and fallback representations. Drafts remain versioned and reviewable; publish uses the authoritative project/release state.
The scene pipeline should preserve stable artifact identifiers across previews, reviews, and package builds. A generated preview is not the release asset, and a successful editor save is not a published room.
Personas, avatars, and costumes#
Persona authoring separates narrative dossier, allowed tone/capabilities, grounded claims, voice rights, avatar identity, costume rules, and release version. Human instructor identity and synthetic artist identity use different verification but share consent, disclosure, and impersonation safeguards.
Avatar/costume artifacts pass skeleton/rig/LOD, clipping, body-safety, cultural adaptation, platform performance, and provenance checks. Premium MetaHuman and community VRM paths may have different technical requirements without creating different safety standards.
Tara class and sequence pipeline#
class brief → instructor/persona eligibility → asana sequence → cue/voice script
→ physical + language + lineage checks → rehearsal/preview
→ schedule/package → live or on-demand release → feedback/continuity
Aja cues, adjustment consent, contraindications, accessible variants, and trauma-informed language are structured inputs/checks. AI-instructor material requires the declared sponsor and review boundary; the model is not treated as a verified human instructor.
Saraswati music and discography pipeline#
creative brief + allowed references → generation plan → model/provider execution
→ stems/voice/mix artifacts → quality + similarity + rights + provenance gates
→ track decision → discography metadata + royalty splits → release/distribution
The brief records intended genre cell and prohibited references; the execution record preserves model/workflow/seed/inputs; lineage links every derivative; quality and rights are separate decisions. A C2PA manifest proves provenance metadata integrity, not ownership or permission by itself.
Concert authoring#
A concert composes rights-cleared tracks, performance timeline, avatar and motion takes, lip sync, spatial/venue audio, camera/visual cues, capacity tier, captions/access modes, ticketing, and fallback media. Rehearsal validates sync, transitions, network/fleet posture, and degraded playback. Prewarming capacity does not replace creative or rights approval.
The canonical pipeline is Concert Authoring Pipeline.
Generation and media services#
Isis owns governed generation planning/execution and quality/provenance controls; Yemaya supports rendering and media outputs; Aja handles embodiment/motion concerns; Psyche supports realtime voice/avatar behavior; Sophia grounds biographical, lineage, and cultural claims. Lilith Studio orchestrates these domains through contracts—it should not reimplement their policy in UI code.
Every execution record should identify the brief, workflow/model versions, inputs and rights, cost/budget, outputs, checks, review decisions, lineage, and replay eligibility.
Review, provenance, and release#
Review packets present the artifact and material variants alongside quality, rights, consent, safety, cultural, accessibility, and technical evidence. An exception is typed, scoped, owned, time-bounded, and visible at release; it is not a free-form bypass.
Publish should be transactional: validate current artifact versions and gates, write release binding and provenance/rights records, emit the domain event, and make rollback/takedown propagation possible. Partial publication must be detectable and recoverable.
Collaboration and permissions#
Roles distinguish viewing, editing, generating, reviewing, rights approval, policy approval, scheduling, and publishing. Comments/threads do not themselves change artifact state. Concurrent editing uses version checks and explicit conflict resolution; assistant- or agent-proposed edits retain actor attribution and the same review requirements.
Failure and recovery#
- Generation/provider failure: preserve plan/run record and retry eligibility; do not orphan cost or partial outputs.
- Quality/rights/safety gate failure: retain evidence and route to revise, reject, exception review, or takedown as policy allows.
- Preview mismatch: identify target profile and prevent preview-only evidence from certifying another tier.
- Publish conflict: reject stale versions and rebuild the review packet.
- Release partial failure: use the release transaction/ledger to resume or roll back without duplicate commerce or provenance records.
- Post-release claim: freeze affected distribution, adjudicate, and propagate recall/takedown through derivatives.