# Lilith Studio Creator Publishing Guide

guide: `v3-lilith-studio-publishing.v1` audience: creators and editorial
producers

Each publishable artifact type lists required inputs, authoring steps, review
gates, output, and verification. A creator should be able to publish from this
guide without another source of truth.

## artifact: persona-dossier

- Surface: Saraswati persona dossier editor
- Inputs: persona name, voice-rights summary, backstory citations, policy lock,
  contributor rights, region availability.
- Steps: open Lilith Studio personas, complete all dossier panels, attach Sophia
  citations, run persona-policy review, request editorial signoff, and publish
  to preview before production.
- Review gates: voice ownership, cultural-adaptation review, persona-policy
  lock, provenance inspector.
- Output: versioned persona dossier with signed provenance bundle.
- Failure handling: return to draft on missing citation, policy breach, or
  rights hold.
- Verification: `pnpm verify:v3 saraswati-persona-dossier-editor`

## artifact: track-catalog-release

- Surface: Lilith Studio music authoring
- Inputs: track title, stem bundle, master reference, lyric policy verdict,
  fingerprint result, C2PA track manifest, royalty waterfall.
- Steps: import stems, attach rights metadata, run fingerprint check, approve
  mix/master, attach provenance, select catalog visibility, and publish.
- Review gates: music provider routing, lyric tone policy, pre-release
  fingerprint, track C2PA manifests, royalty settlement.
- Output: catalog track with C2PA manifest and royalty split.
- Failure handling: block publish on unresolved rights or fingerprint conflict.
- Verification: `pnpm verify:v3 lilith-music-authoring`

## artifact: concert-sequencer-package

- Surface: Saraswati concert master template
- Inputs: setlist, per-song motion preset, lighting cue track, Niagara cue
  track, audience choreography bindings, pre-show warmup, recording model.
- Steps: assemble Sequencer package, bind cues to the persona and venue, run
  staging rehearsal, capture operator notes, and publish the concert template.
- Review gates: concert scheduling, stage transition, per-song execution,
  recording pipeline, crowd interaction.
- Output: versioned concert package ready for pre-warm reservation.
- Failure handling: unpublish calendar entry and return package to rehearsal
  when any cue binding or consent gate fails.
- Verification: `pnpm verify:v3 saraswati-concert-master-template`

## artifact: tara-class-sequence

- Surface: Tara scene and asana authoring
- Inputs: class title, instructor credential id, asana library references, Aja
  cue script, timing map, recording consent model, accessibility notes.
- Steps: build sequence, simulate timing, attach instructor nameplate and
  lineage display, run Aja cue validation, approve schedule, and publish.
- Review gates: credential intake, Yoga Alliance lookup, Aja cue generator,
  class scheduling, physical-adjustment consent.
- Output: scheduled live or recorded Tara class with practice-mode continuity.
- Failure handling: hold publish on expired credential, unsafe cue, or missing
  minor-safety review.
- Verification: `pnpm verify:v3 tara-sequence-editor`

## artifact: avatar-costume

- Surface: Lilith Studio avatar costume authoring
- Inputs: costume mesh, materials, LOD policy, rights statement, safety tags,
  platform budget report.
- Steps: import assets, bind avatar slots, run LOD validation, inspect rights,
  preview on target clients, and publish to the approved catalog.
- Review gates: avatar costume validation, asset-size budgets, rights review,
  platform certification constraints.
- Output: versioned costume artifact with target-platform budget evidence.
- Failure handling: reject publish when LOD, rights, or platform budget gates
  fail.
- Verification: `pnpm verify:v3 lilith-avatar-costume`

## artifact: commons-venue-experience

- Surface: Lilith Studio scene editor
- Inputs: V1 experience reference, venue id, room tiers, accessibility settings,
  capacity policy, moderation policy, and provenance bundle.
- Steps: import or re-render the V1 experience, bind room actions, validate
  accessibility controls, attach capacity policy, and publish to Commons.
- Review gates: scene capacity, scene accessibility, daily programming, DSAR
  coverage, provenance inspector.
- Output: Commons venue experience available to the launch router.
- Failure handling: return to staging when capacity, consent, or provenance
  checks fail.
- Verification: `pnpm verify:v3 lilith-scene-editor`

## artifact: signed-edition-drop

- Surface: Saraswati signed-edition publishing
- Inputs: edition metadata, artifact hash, C2PA export, AJE mint policy, royalty
  waterfall, cancellation policy, and takedown cascade policy.
- Steps: create edition, attach provenance, run mint preview, approve pricing,
  schedule drop, and publish.
- Review gates: signed-edition drop, secondary sale, cancellation, takedown
  cascade, royalty settlement.
- Output: signed edition with public provenance and settlement routing.
- Failure handling: cancel drop and notify holders if provenance or minting
  fails before public sale.
- Verification: `pnpm verify:v3 saraswati-signed-edition-drop`