# Lilith V1.4 — the channels: scope (2026-09-28)

Status: **draft for Elikem's approval.** Author: Claude (claude-mac-worker),
2026-09-28, from Elikem's brief the same day. Board family: `lilith-v1-4`. Every
task starts as `later` and the family as `unstarted`, so no worker picks
anything up until this scope is approved. Release name in code:
`LILITH_CHANNELS_RELEASE` in `libs/oshun/navigation/src/release-scope.ts`.
An independent read-only review (Codex, 2026-09-28) was folded in before
filing. It raised 18 findings:

- The Kick Terms prohibit "machine-generated content", so Kick's written
  position was made a blocker (K09).
- The capability gate was split into rehearsal and public permissions.
- A launch-readiness gate was added, along with media-level screening,
  inventory replenishment, failover, programme recording, audience screenings
  and integrated grids.
- The claims on licences, OAuth scopes and minors were corrected.
- The likeness rule was made single and strict.

**Revised the same day (revision 3)** after Elikem decided that the network's
home is Oshun's own streaming platform inside Lilith, with Kick, YouTube,
Rumble and others as copies. The revision adds sections 3.4–3.5 and 6.25–6.28,
principle 12, and decisions 12–15. Outside creators come later (Z08–Z10). Kick
now blocks only its own copy.

A second read-only Codex pass on the platform change raised 18 more findings,
all applied. It added CSEA reporting, child-safe viewing, moderated chat
delivery that fails closed, emergency withdrawal, security verification,
broadcast and on-demand classification, destination composition, delivery
spend controls, platform-state recovery, accessible playback conformance and
audience accounting. It also corrected the Rumble and YouTube rules, softened
the Online Safety Act applicability, and removed the circular public-release
gate.

Later the same day, Elikem accepted the recommendations on decisions 2, 4, 6,
8, 9, 10, 12, 13 and 14 (section 10). They are now settled and wired into the board;
the launch order is enforced as task dependencies.

Revision 14 answers the review of revision 12: production hosting is server
work, which belongs to the platform operator, so it is now the task
`platform-ops:lilith-v1-4-production-hosting-2026-09-28` in that role's inbox. O08 delivers
the capacity plan and deploy package it needs; O10, O13, O14 and T05 no longer
change servers themselves; the launch gate G11 and the recovery tasks depend on
the platform-ops task (sections 6.14, 10 and 13).

Revision 17 answers the review of revision 16: the launch gate G11 now depends
on the audience screenings (W12) and each room's integrated 24-hour grid (G10)
and cites both in its readiness record; Twitch's ban on combined activity from
other platforms, merged chat included, is in the destination policy (3.4, 6.14)
and checked in Y10 and Y05.

## 0. The brief (Elikem, 2026-09-28, verbatim)

> "I would like to add a V1.4 that creates multiple 24hour channels on kick
> which contain content that we generate from like out materials like veritas
> metis nisaba nyx tara arete and then later as more versions of oshun come out
> more full blown media etc do you get what i mean and can we scope it"

> "mean to bring people to lilith but also be good engaging content on its own,
> monetization right now is not a concern at all. lilith prominent persona sure
> but i expect many different personas in tara, nyx, many newscasters in
> veritas, many lecturers in metis so like a rich universe. for paid avatar
> services trying to migrate away towards like more openrouter + home built
> harness/system so like are they still a must have must be considered. launch
> lineup multople personalities as appropirate (creative brainstorming should
> also be included to come up with all of these) across all oshun v1 including
> metis. veritas, arete, tara. nyx. nisaba, again if more ideas and
> brainstorming and world building and more creative processes and task need
> to be added then lets fully scope all those just like any full featured aaa
> production would have as appropirate. monthly budget we will decide later."

> "actually lets make building a "kick" of our now part of the scope with that
> being the home and then multicasting across kick, youtube, rumble etc as
> appropriate but our own streaming platform being our home base the building
> of which now becimes part of 1.4 scope"

> "for the open decisions we can go with your recommendations"

> "proceed" (accepting the recommendations on decisions 9 and 10)

Answers given to direct questions the same day: the platform is for Oshun's
own channels first, with outside creators later; the platform is part of
Lilith.

## 1. Summary

V1.4 puts the rooms on air. It builds **Lilith's own streaming platform**
(working name Lilith TV) inside Lilith as the network's home. It launches
always-on channels there: at least one per room (Nyx, Tara, Arete, Nisaba,
Metis and Veritas) plus a flagship hosted by Lilith. Each channel is also copied
to Kick, YouTube, Rumble and others wherever that platform's rules allow. The
home platform never depends on any of them. Every show, host, voice, set and piece of music comes
from the rooms' own material and is made by Oshun's own production crew: a
home-built multi-agent harness on the OpenRouter route, with open models on our
own hardware where OpenRouter has no fit. No paid avatar vendor is needed.

The channels have two jobs, in this order:

1. **Be worth watching on their own.** They should be engaging, beautiful,
   truthful programming that people leave on.
2. **Bring people to Lilith.** Every channel is a doorway into its room.

Monetisation is not a goal of V1.4. The platform carries Oshun's own channels
first. It is built so outside creators can join later, which is a Horizon item
(Z08–Z10), not V1.4 GA.

The network is built like a AAA production. It has a universe with a canon, a
writers' room that brainstorms and develops formats, casting, voice design, art
direction, music, a segment factory, standards and practices, a playout
operation that never goes black, and live interaction that makes each channel
live rather than looped. Later Oshun products (films, games, detective cases,
worlds, concerts) join through an adapter contract as they ship (section 6.25).

## 2. What exists today (code, 2026-09-28)

These findings come from a source inventory done on 2026-09-28. Statuses were
spot-checked in the code, not taken from READMEs. "Tested" means the module has
its own specs; they were not re-run for this draft.

**Nothing is joined into a broadcast yet.** No Kick integration exists anywhere.
No home-built talking head or avatar works today: every face path is either
paid or a planner. No playout engine runs around the clock, and no GPU host
exists. The parts below are what V1.4 builds on.

| Area | What exists | Status | Where |
|---|---|---|---|
| 24/7 news channel design | Scheduler (in-memory, `setInterval`), node-media-server with ffmpeg relay, SVG lower thirds, OpenRouter chat moderation and viewer Q&A, health monitor, YouTube Live client | Real, partly tested; nothing imports it | `libs/veritas/live-stream` |
| RTMPS pusher | ffmpeg reads a playlist in real time and pushes RTMPS to YouTube | Real and exported, but no production caller | `apps/veritas/video/src/services/live-stream.ts` |
| Live media plumbing | MediaMTX edge, WHIP publishing, browser canvas composition, player, HLS/DASH packager, SQL live chat, viewer sessions, transcoding, recording (about 33k lines) | Real and Playwright-tested. But the packager writes VOD playlists, the player's low-latency mode is off, and live manifests, WebRTC and CDN answer 501. Its apps (streaming, chat, viewer) belong to the Aphrodite adult domain; its chat moderator fails open on errors | `libs/shared/live-media`, `apps/aphrodite/{streaming,chat,viewer}`, `libs/aphrodite/chat-moderation` |
| Rundown engine | Rundowns and cue sheets | Real and tested | `libs/aphrodite/production/src/rundown` |
| Personas (governance) | 11-persona launch roster, avatar packs with 19 visemes, voice profiles, consent ledger, likeness denylist, disclosure and impersonation checks; four Tara mentors | Real, tested, wired to the BFF and admin `/personas`. These are governance records, not written characters | `libs/oshun/persona-registry` |
| Lilith | Chat persona prompt ("voice, host, and main persona"); tone, crisis, spiritual-boundary and unsafe-claim policy with evals | Real and tested. It is not yet an on-air host | `libs/oshun/shell-assistant/src/system-prompt.ts`, `libs/oshun/persona-policy-lilith` |
| Continuous-video safety | Per-room caps on brightness, contrast and motion; strobe and crisis-frame rules; six persona classes matching the six channels | Real and tested, unwired | `libs/lilith/continuous-video-policy` |
| Veritas anchors | Five Ghanaian anchor personas; Twi, Ga and Ewe presets | Vendor-bound (Tavus, HeyGen, D-ID, ElevenLabs) | `apps/veritas/video/src/services/personas.ts`, `libs/veritas/video-production/src/avatars` |
| Local voice | Kokoro 82M on CPU; Kokoro and Chatterbox on a RunPod ComfyUI endpoint (declared, not provisioned); Piper/espeak engine used by a table-read synthesizer | Real; fails closed until configured | `apps/oshun/bff/src/generation/local-kokoro-voice-provider.ts`, `comfy-voice-provider.ts`, `libs/yemaya/tts-integration/src/local-engine` |
| Alignment and visemes | wav2vec2 forced alignment (measured ≤ 81 ms onset error); phoneme to 19-class viseme track with ARKit blendshape weights | Real and tested | `tools/human-video/forced-align.py`, `libs/psyche/avatar-lipsync` |
| Character rendering | three.js loader for VRM, glTF and FBX with blendshapes and spring bones; VRM export; 57k-line rigging library; a toy 2D talking head; a splat/FLAME avatar engine (no weights, no GPU) | Real, but unwired for on-air characters | `libs/aphrodite/avatar-renderer`, `libs/isis/3d-post-pipeline/src/export/vrm-export.ts`, `libs/isis/universal-rigging`, `libs/metis/multimedia/src/video/talking-head.ts`, `apps/psyche/avatar-engine` |
| Governed human video | About 250 modules: shot planning, likeness authorisation, identity packs, lip-sync scoring, loudness. The self-hosted speech-to-video slot is `no-implementation` | Real and wired, but batch-only and vendor-bound (OpenRouter video models, HeyGen) | `apps/oshun/bff/src/generation/human-video-*.ts` |
| Planners without inference | Visual dubbing, face synthesis, portrait studio, portrait animation, voice cloning, foley, music-generation enum | Stubs; do not build on them | `libs/isis/{visual-dubbing,face-synthesis,portrait-studio,voice-cloning,foley-studio,music-generation}`, `libs/nous/portrait-animation` |
| Music | ACE-Step 1.5 Turbo on RunPod, from Comfy-Org's ComfyUI repackage (card: Apache-2.0; the upstream ACE-Step 1.5 card says MIT, see 3.3); Magenta RealTime 2 | Real; fails closed until configured | `apps/oshun/bff/src/generation/comfy-music-provider.ts`, `realtime-music-provider-env.ts`, `docker/runpod/comfyui/Dockerfile` |
| Loudness | EBU R128 probes (−16 LUFS / −1 dBTP) | Real and tested | `apps/oshun/bff/src/generation/audio-probe.ts`, `human-video-loudness.ts`, `tools/tara/process-audio.ts` |
| Trust | C2PA signing; spread-spectrum watermarks (the video mark survives only lossless H.264 4:4:4, so not a lossy stream); spoken AI disclosure; crisis classifier contract (model supplied separately); chat moderation | Real and tested; C2PA and watermark fail closed without keys | `libs/oshun/c2pa-export`, `apps/oshun/bff/src/generation/*-watermark.ts`, `synthesis-disclosure.ts`, `libs/yemaya/living-scenes-runtime/src/cues/crisis-classifier.ts`, `libs/aphrodite/chat-moderation` |
| Rights | Model-licence registry; in-memory content-licence tracking in a Lilith service. No persistent broadcast-rights registry exists | Real, not broadcast-ready | `libs/isis/model-governance-3d/src/license-registry.ts`, `apps/lilith/svc-rights-management/src/rights.ts` |
| Creative tooling | Series bible and table read; Fountain-derived screenplay parser and compilers; continuity canon graph; a showrunner-led writers' room (built for mystery cases); podcast generator; production-management API; OpenTimelineIO in Rust | Real and tested, mostly unwired | `libs/hathor/ideation/src/screen`, `libs/hathor/pre-production`, `libs/hathor/lore-compiler`, `libs/yemaya/canon-graph`, `libs/yemaya/case-writers-room`, `libs/yemaya/podcast-generator`, `apps/yemaya/api`, `libs/neith/conform` |
| Operator surfaces | Admin app (personas, RunPod endpoints, human video); workbench shell with SchedulingBoard, TimelineEditor, CalendarViews and JobQueueView; editorial calendar. No EPG exists | Real and tested | `apps/oshun/admin`, `apps/oshun/web/src/components/workbench`, `libs/oshun/workbench-kit` |
| Nyx | 12 WebGL renderer libraries (about 58k lines); react-three-fiber star map; Meeus ephemeris; live NASA, JPL, CelesTrak and SDO feeds; about 79 myths; events, lessons and quizzes | Real and tested; the most broadcast-ready room | `libs/nyx/*`, `apps/nyx/star-map` |
| Tara | Content library, session API and seed script; meditation-script generation (fails closed until an LLM and TTS are injected) | Real, but the catalogue ships nearly empty | `libs/tara/content`, `apps/tara/api`, `apps/lilith/svc-meditation-generation` |
| Arete | Coaching, affirmations and habits as templates and rules; no model | Real and tested | `libs/arete/*` |
| Nisaba | Perseus, ETCSL, CDLI and ORACC URL builders, TEI/ATF parsers, licence strings; translations and editions | Real, but the corpora code never fetches | `libs/nisaba/*` |
| Metis | Course, verification and tutoring logic; a deployed lecture-generation service (script, narration variants, captions, slides) | Real and tested | `libs/metis/*`, `apps/metis/service/src/metis/services/lecture_generation_service.py` |
| Veritas | Article generation, journalism agents and claims (OpenRouter); fact-checking (ClaimBuster, Google Fact Check); automated content (GMet weather, fuel, load-shedding, markets, sport); video script generation | Real, thinly tested | `libs/veritas/*` |
| Infrastructure | 30 RunPod endpoints declared, but only two dev endpoints exist (both scale to zero); a GPU dispatcher; one CCX23 per environment on Hetzner (4 vCPU, 16 GB, no GPU); no 24/7 media service | Mostly unprovisioned | `infra/runpod/endpoints/desired-state.json`, `apps/infra/gpu-dispatcher`, `infra/hetzner` |

## 3. The field in September 2026

### 3.1 Kick, now one destination among several

| Fact | Source (read 2026-09-28) | Consequence for V1.4 |
|---|---|---|
| The Community Guidelines permit AI content. Realistic AI content must be disclosed in the stream title or an on-screen overlay. Synthetic media may not mislead about real-world events or simulate a real person's presence or endorsement without permission. | Kick Community Guidelines, effective 19/03/2026 | The AI disclosure goes in every title (K03) and a persistent overlay (D03). No synthetic real people, ever, and Veritas is the strictest case (VE04). |
| **But the Terms of Service §1.4(q) list "machine-generated content" among prohibited uploads**, next to spam and unsolicited messages. | Kick Terms of Service, updated 23/03/2026 | The two documents conflict, so the policy is uncertain, not permission. Kick's written position is a launch blocker (K09, Decision 3), and nothing streams to Kick before it. If Kick declines, Kick is simply not a destination. The home platform never depends on it. |
| "Avoid mirror streams, blank streams, or pre-recorded content." This is listed as grounds to refuse or revoke verification and the Partner Program. | Kick Help Center, "Grounds for revoking or refusing verification or the KICK partner program" | Monetisation is not a goal, but discoverability and account standing matter. Every channel is assembled live, with at least one real-time layer (principle 5). |
| Bots or third-party tools that inflate views, followers or interactions are prohibited. | Community Guidelines | No cross-channel raid farming or fake engagement. Analytics are observational only. |
| Streamers grant Kick a royalty-free, perpetual, irrevocable, worldwide licence to their content. | Kick Terms of Service, updated 23/03/2026 | Only rights-cleared material may air (S03, NI02, VE06). |
| Users must be 13 or older, or the local age of digital consent; under-18s need parental consent. The guidelines require parental supervision for streams featuring minors and forbid unsupervised interactions with minors on randomized video-chat platforms. | Terms 1.1; Community Guidelines | Viewers include minors. There are no private or one-to-one paths; handles and questions are read only under a participation notice; crisis disclosures and personal data are never broadcast (S07). |
| The public API has OAuth, channels (`PATCH /public/v1/channels` for title and category, scope `channel:write`), and scopes `streamkey:read`, `chat:write`, `events:subscribe`, `moderation:ban` and `moderation:chat_message:manage`. | docs.kick.com (scopes page) | Titles, categories, chat, moderation and keys can be automated per channel (K01–K05). |
| Ingest accepts H.264 only, at most 8,000 kbps and 60 fps, over RTMPS. | Kick Help Center (secondary guides agree) | This is the encoder profile for O01/O03. |
| Multistreaming is allowed. It only affects a Partner's payout. | Streams Charts multistreaming guide, 2026 (secondary) | Simulcasting is Elikem's choice (Decision 2), and the playout engine supports it cheaply. |
| Neither the guidelines nor the terms address running several accounts or 24/7 automated channels. | Community Guidelines, Terms | This is part of the question put to Kick in K09. |

### 3.2 What 24/7 AI programming has already taught

- **Nothing, Forever** was an AI-generated sitcom streamed around the clock on
  Twitch. In February 2023 it was suspended after a character made transphobic
  remarks. Its creators attributed this to switching to a less-moderated model
  during an outage. Two lessons follow: a failover must never lower the safety
  bar (S08), and everything that airs is screened (S02).
- **AI VTubers** such as Neuro-sama showed that a stylised character, a
  distinctive voice and real chat interaction can hold a large live audience
  without photorealism. That is the basis of presence tier 1 (section 6.9).
- **Ambient 24/7 streams** (lo-fi study and sleep channels) show that
  long-form, low-intensity programming keeps viewers for hours. That fits Tara
  and Nyx deep-sky programming.
- **Veritas already contains a 24/7 news-channel design** (section 2). V1.4
  generalises it rather than starting over.

### 3.3 Home-built tooling available now

- **Voice through OpenRouter.** `POST /api/v1/audio/speech` exposes many TTS
  models priced per character. Examples: Kokoro 82M at $0.62/M characters
  (open weights), Orpheus 3B at $7/M (open weights), Qwen Audio 3.0 TTS Flash at
  $15/M, Fish Audio S2 Pro at $15/M bytes, Voxtral Mini TTS at $16/M,
  MAI-Voice-2 at $22/M, and Gemini 3.8 Flash TTS (token-priced). No word
  timestamps are returned, so V04 aligns audio itself.
  - A rough order of magnitude: one channel speaking non-stop reads about 1.2M
    characters a day (150 words a minute). That is under $1 a day on Kokoro and
    about $18 a day on a $15/M model. Real channels speak less than that. V01
    measures the actual figure.
- **Music with commercial-use licences.** ACE-Step 1.5 was released on
  2026-01-28. Its upstream model card (`ACE-Step/Ace-Step1.5`) says MIT, and
  states that generated music may be used for commercial purposes.
  - The Oshun RunPod image downloads a different artifact: Comfy-Org's ComfyUI
    repackage (`Comfy-Org/ace_step_1.5_ComfyUI_files`,
    `ace_step_1.5_turbo_aio.safetensors`), whose card declares Apache-2.0. The
    repository's provider comment repeats that.
  - Both licences permit commercial use, but they differ. M01 therefore pins
    the exact weights file, the upstream licence, the repackage licence and the
    output terms separately before anything airs.
  - YuE's terms differ by version: YuE2 weights reportedly need a commercial
    licence for company use.
  - Stable Audio Open is free commercially only under US$1M revenue.
  - Some popular weights are non-commercial.
  - M01 pins the code, weights and output terms of each version separately.
- **Presence.** Open real-time 2D/3D character frameworks and viseme lip-sync
  are mature (Open-LLM-VTuber, AITuber OnAir, three-vrm-class renderers).
  Open-source streaming photoreal avatars are an active research field in 2026
  (Live Avatar, Avatar Forcing, SoulX-FlashTalk, Avatar-Forever). They are fast
  but GPU-heavy, and diffusion-quality avatars are still rendered offline.
- **OpenRouter has no avatar or lip-sync lane with supplied audio**, except Wan
  2.6/2.7 through provider passthrough (2–10 s clips; measured 2026-09-09).
  Performances longer than a clip therefore run on our own RunPod workers
  (P04).

### 3.4 The other destinations

| Destination | What its rules mean for us (read 2026-09-28) | Where it sits |
|---|---|---|
| **YouTube** | Realistic altered or synthetic content must be disclosed, and YouTube's own list includes AI-generated music, so every channel of ours with generated music or voices discloses there, even where the visuals are stylised. Unrealistic animation needs no disclosure on its own. The "inauthentic content" policy hits mass-produced AI video, but only for Partner Program monetisation. The Data API supports live broadcasts and chat. | M2, Y03 |
| **Rumble** | RTMP ingest from a live dashboard. The terms (modified 1 September 2026) forbid automated access without Rumble's prior written permission, and the site is 18+ only. The position on AI content is unverified. | M2, Y04, after Rumble's written permission |
| **Twitch** | Simulcasting is allowed, provided the Twitch experience is at least as good and Twitch viewers are not directed to a concurrent stream elsewhere, so the Twitch overlay omits the watch-on-Lilith call. Nor may the Twitch stream show combined activity from other platforms, merged chat included, so its output carries Twitch chat only (Y10, Y05). Since August 2026, Amazon may train generative AI on streamers' content by default. | M3, Y05, if the licence register allows |
| **Kick** | See 3.1: the Terms forbid "machine-generated content", so Kick waits for its written position (K09). | M3, K08 |
| **X, Facebook, TikTok** | Evaluated later (Y06). | M3 |

Each destination is a row in the destination policy register (Y02), dated and
re-checked. A destination airs only while its row is current and compatible
with the rights of what it carries.

### 3.5 Running our own platform

- **It is probably a regulated service.** Oshun Synthetics LTD is a UK
  company. A platform where viewers chat with each other is likely a
  user-to-user service under the Online Safety Act 2023, unless the
  limited-functionality exemption for comments on provider content applies.
  Live chat between viewers probably goes beyond it, and R01 decides with
  counsel. That brings an illegal content risk assessment, a children's access
  assessment (and a children's risk assessment if children are likely to use
  it), record keeping, the child sexual exploitation and abuse reporting duty,
  and terms, reporting and complaints duties. Serving EU viewers may bring EU
  Digital Services Act duties. A catalogue of replays may count as an
  on-demand programme service to notify to Ofcom (R13). The R pillar covers
  all of this, with counsel engaged in M1.
- **Egress is the cost that scales.** Video delivered to viewers costs money
  per gigabyte through any CDN. T05 prices each audience size before it
  happens. Monetisation is not a goal, so this is the number to watch.
- **Reach comes from the destinations.** A new platform has no audience of its
  own. The destinations are how people find the channels, and the home is where
  they come to stay, one tap from the rooms.
- **Much of the machinery exists, but not the live half.**
  `libs/shared/live-media` has publishing, a player, an HLS/DASH packager,
  SQL-backed live chat, viewer sessions, transcoding, recording and a MediaMTX
  edge. But the packager writes VOD playlists, the player runs with its
  low-latency mode off, live manifests and WebRTC answer 501, and CDN delivery
  is an honest gap. Live packaging and delivery are new work (T04–T06). Its current apps belong to Aphrodite, the adult
  creator-economy domain, so the Lilith platform is built as its own apps that
  share nothing with Aphrodite but the libraries (T01).

## 4. The network: concept and seed lineup

**The House of Lilith.** The network is one universe. Lilith is the host of the
house, as she is in the app. Each room is a place in the house with its own
residents, and each channel is a window into one room. The writers' room (W01)
and the universe bible (U01) develop this. The seeds below are starting points
for the brainstorm, not decisions. Every channel, show and character still
passes through the greenlight gate (W03).

| Room | Seed channel(s) | Seed shows and formats | Real-time layer | Seed ensemble (archetypes) |
|---|---|---|---|---|
| **Lilith** (flagship) | The network channel | A daily cross-room show visiting every room; premieres; highlights; hand-offs | What is live on every channel now; chat | Lilith, plus guests from every room |
| **Nyx** | Live Sky | *Follow the Night*: the real sky over a place where it is night right now, moving around the globe. *Myth Hour*: star lore across cultures, including West African sky traditions. *Mission Control*: eclipses, meteor showers, launches, ISS passes. *Deep Field*: slow deep-sky sleep programming | Real ephemeris at the aired second; event countdowns; chat picks the next target | An observatory night shift: astronomer, myth-keeper, navigator, a young apprentice |
| **Tara** | Sanctuary | Guided sits and breathwork; sleep stories; focus blocks; sunrise practice that follows the dawn around the world | Dayparting to the listener's night and day; chat check-ins; generative soundscapes | A circle of guides from different traditions, each with a distinct voice |
| **Arete** | Agora | Live co-working and focus rooms; habit challenges; coaching shows; vision and goal clinics | Chat accountability, streaks and check-ins | A bench of coaches: a sports psychologist, a stoic, a planner, a motivator |
| **Nisaba** | Scriptorium | *The Reading Room*: readings of ancient texts. Translation side-by-sides. Paleography walk-throughs. *Lost Libraries* documentaries | Chat picks the next passage; live deciphering | Scribes, a librarian, translators; historical figures only as labelled dramatisation |
| **Metis** | Academy | Lectures by a faculty across subjects; daily wonder explainers; quiz nights; office hours; revision marathons in exam season | Live quizzes and leaderboards; chat questions answered by lecturers | A faculty with one lecturer per subject, each with a teaching style |
| **Veritas** | Newsroom | Top-of-hour bulletins for Ghana and pan-Africa; a claim-check segment; explainers; magazine shows; language desks later | Breaking news after the editorial gate; rolling ticker | Anchors on rotating shifts, regional correspondents, and fact-check, sport, markets and weather specialists. All fictional, all labelled AI |

Each room may grow to several channels in M3, for example Tara Sleep and Tara
Focus, or a Veritas language desk.

**Home and destinations.** Every channel lives first in the watch area inside
Lilith: live now, channel and show pages, the schedule, replays, clips, chat,
follows, and each room showing its channel live. Kick, YouTube, Rumble, Twitch
and others carry copies for reach, each within its own rules.

## 5. Principles (binding on every V1.4 task)

1. **Honest AI.** Every channel carries the AI disclosure in its title and in a
   persistent overlay. Personas are fictional characters and say they are AI
   characters when asked. Nothing is presented as a human broadcast.
2. **No synthetic real people.** V1.4 uses no real person's likeness or voice
   at all, with no consent exception. Venerated figures are refused (the Mentor
   Presence denylist). Historical figures appear only as clearly labelled,
   stylised dramatisation of figures long dead, never photoreal, never
   venerated or religious, never anyone from living memory (Decision 10).
   News quotes appear as text
   with their source and are never voiced by a synthetic copy of the speaker.
3. **Truth traces to a source.** Every factual claim goes through its room's
   gate (Veritas claim ledger and fact-check, Metis verification, Nyx ephemeris
   for the aired time, Nisaba edition citations) and shows its citation on
   screen.
4. **Rights-cleared only.** Every asset on air has a licence record compatible
   with the home platform and with each destination's licence over what it
   carries (Kick's is perpetual; Twitch lets Amazon train AI by default). A
   destination that may not carry a segment gets a cleared replacement
   (Y10). Music comes only from sources whose licences
   permit commercial use. No third-party music.
5. **Live-assembled, never looped.** Every channel has a real-time layer.
   Repeat budgets and expiry are enforced. A slate takes over on any upstream
   gap. A standby host takes a channel over when its playout host fails, within
   the recovery bound in section 9 (O13). Programme, slate and outage time are
   measured separately.
6. **Screened before air, safe on failure.** Every script and every live reply
   passes the standards review before air, and so does the generated media
   itself: synthesized speech is checked against its approved text, frames are
   classified, and approval is bound to the output hash (S11). A failure or
   timeout blocks it. A
   failed model falls back to approved library content or slate, never to a
   model with a weaker safety profile.
7. **Home-built, cheapest capable, measured.** The crew runs on OpenRouter
   models chosen by measured bake-off (the price-the-route method), with open
   weights on our own hardware where OpenRouter has no fit. No paid avatar
   vendor on any default path. Frontier models only with Elikem's approval.
   Tests bind the CLAUDE.md harness route. GPT-6 Astra is reachable only through
   the Codex subscription, operator-side, never on an unattended air path.
8. **Provenance on everything.** Every segment file is C2PA-signed with its
   models and sources. Every aired second is in the as-run log. The programme
   output is recorded in hashed chunks, with every live element logged against
   its screening record (F09). The existing video watermark does not survive a
   lossy stream, so the live output's disclosure rests on the title, overlay,
   spoken disclosure and as-run log (F06).
9. **One universe, one canon.** Characters, places and events live in the canon
   registry, and every script is continuity-checked.
10. **Elikem greenlights; the machine proposes.** Channels, shows, cast, looks,
    voices and the universe bible need Elikem's recorded approval. Machine
    approvals never count. Reviews are batched so one human is never the
    bottleneck on routine output that has already passed the gates.
11. **A doorway, not a billboard.** Calls to action are in-world and
    frequency-capped. No engagement manipulation.
12. **Home first.** Every channel airs on the home platform first. A
    destination is added only through the multicast relay and the policy
    register, and a destination's failure or refusal never affects the home.
13. **Machine limits hold.** Heavy work (rendering, alignment, encoding soaks)
    runs on the Linux dev server, RunPod or production hosts, never stacked on
    the Mac (CLAUDE.md machine limits).

## 6. Scope

The work is organised in 29 groups ("pillars"): 17 production crafts, 6 room
channels plus the flagship, 4 home-platform pillars (6.25–6.28), and the
horizon (6.29). The home platform was added on 2026-09-28, after the first
filing. Its sections sit after the rooms so earlier section numbers stay
stable. Each pillar is an epic on the
board (section 13).

### 6.1 Programme, production office and release gate [`G`]

The V1.4 capability gate, the network architecture ADR, kill switches, the production office (slate, greenlight register, production calendar, dailies), the cost ledger with per-channel caps, and the milestone exit runner.

Tasks: `G01`, `G02`, `G03`, `G04`, `G05`, `G06`, `G07`, `G08`, `G09`, `G10`, `G11` (board map, section 13).

### 6.2 Crew harness (home-built, OpenRouter) [`H`]

The production crew as a home-built multi-agent harness on the OpenRouter route: showrunner, head writer, researcher, fact-checker, standards reviewer, director, editor, composer and voice director, each bound to the cheapest model that measures capable, with budgets, traces and replay.

The crew is a home-built multi-agent harness, not a vendor product. Each role
(showrunner, head writer, researcher, fact-checker, standards reviewer, director,
editor, composer, voice director) is a prompt, a tool set, an output schema and a
model binding on OpenRouter. The binding is chosen by measured bake-off (H02),
and prompts are promoted only on a replayed gain (H03).

Tasks: `H01`, `H02`, `H03`, `H04`, `H05` (board map, section 13).

### 6.3 Evaluation and quality measurement [`E`]

Measurement for everything the network makes: rubric judges labelled as model judgement, persona drift, factuality per room, technical audio/video QC, and cost per broadcast hour.

Tasks: `E01`, `E02`, `E03`, `E04`, `E05` (board map, section 13).

### 6.4 Universe, canon and worldbuilding [`U`]

One universe for the whole network: the House of Lilith bible, a canon registry every script is checked against, a living in-world calendar tied to the real one, and change control for canon.

Tasks: `U01`, `U02`, `U03`, `U04`, `U05` (board map, section 13).

### 6.5 Writers' room and creative development [`W`]

The creative engine: a wide brainstorm across every room, scoring and shortlisting, Elikem's greenlight, format bibles, the episode and segment generator, script doctoring and table reads, series arcs, tone guides, programme grids, promos and pilots.

The creative process follows a real development slate:

1. **Brainstorm** (W01).
2. **Score and shortlist** (W02).
3. **Elikem greenlights** (W03).
4. **Format bibles** (W04).
5. **Generated episodes** (W05), then a **script doctor and table read** (W06).
6. **A pilot per show** (W11), reviewed in dailies (G09).
7. **Launch depth** in each room pillar.

The Hathor ideation guards and the Yemaya writers' room are evaluated as the
starting point (section 2).

Tasks: `W01`, `W02`, `W03`, `W04`, `W05`, `W06`, `W07`, `W08`, `W09`, `W10`, `W12`, `W11` (board map, section 13).

### 6.6 Cast and characters [`C`]

A rich cast: Lilith as the flagship host plus ensembles per room (guides, astronomers, coaches, scribes, lecturers, anchors and correspondents), each an original character with a sheet, a voice, a look, a behaviour spec, relationships and clearance.

Every on-air character is original and has a character sheet in the persona
registry (C01). Casting runs like an audition (C03): candidate characters, sample
lines in their designed voice, a look sheet and a short performed clip, then
Elikem's pick. Lilith (C02) is the constant across the network. The in-app
Lilith and the on-air Lilith are one character.

Tasks: `C01`, `C02`, `C03`, `C04`, `C05`, `C06`, `C07`, `C08` (board map, section 13).

### 6.7 Voice and performance audio [`V`]

Voices without paid vendors: a TTS bake-off across OpenRouter and open-weight models, designed voices per persona, performance direction, timing and alignment, pronunciation lexicons, and multilingual desks.

The voice lane is OpenRouter first, with every model's terms checked
before binding (V01). Open weights on the Linux dev server or RunPod are used
where a voice needs design controls OpenRouter does not expose. Voices are
designed from descriptions or seeds, never cloned from a real person.
OpenRouter returns no timings, so every line is force-aligned (V04) for captions
and lip-sync.

Tasks: `V01`, `V02`, `V03`, `V04`, `V05`, `V06` (board map, section 13).

### 6.8 Art direction and visual identity [`D`]

How the network looks: identity rooted in the Lilith design system, character design, the broadcast graphics package with the AI-disclosure bug, virtual sets, channel art for home and destinations, and thumbnails.

Tasks: `D01`, `D02`, `D03`, `D04`, `D05`, `D06` (board map, section 13).

### 6.9 Presence engine (character performance) [`P`]

Home-built on-air presence in tiers: real-time rigged stylised characters with viseme lip-sync, pre-rendered performances from open models on our own GPUs, and a research spike on streaming photoreal avatars; paid avatar vendors leave the default path.

**Are paid avatar services a must-have? No.** They are not on any default
path in V1.4. They stay available as an optional, default-off adapter (P07). A
vendor comes back only if a measured need appears that the home-built tiers
cannot meet, and then only as a decision for Elikem.

| Tier | What it is | Runs on | Latency | Used for |
|---|---|---|---|---|
| **T1 real-time stylised characters** | Rigged 2D/3D characters in open formats, lip-synced from viseme tracks (V04), with expressions and gestures from script tags | The playout host (GPU or CPU, measured in P01 and O01) | Real time | The default on every channel, including live chat replies |
| **T2 pre-rendered performances** | Open audio-driven performance models on Oshun's own RunPod workers, SyncNet-checked, watermarked and C2PA-signed | RunPod GPU | Minutes to hours before air | Set pieces: documentaries, premieres, explainers |
| **T3 streaming photoreal** | 2026 open streaming-avatar research models | GPU | Near real time | A research spike only (P06) |
| Paid vendors (D-ID, Tavus, HeyGen) | The existing adapters in `libs/veritas/live-stream` | Vendor | — | Optional, off by default (P07) |

Stylised characters are also the safer choice under Kick's realism rule. They
fit the AI-VTuber culture that already thrives on streaming platforms, and they
cost nothing per minute beyond compute.

Tasks: `P01`, `P02`, `P03`, `P04`, `P05`, `P06`, `P07` (board map, section 13).

### 6.10 Music and sound [`M`]

A sonic identity and show music made with models whose licences permit commercial use, generative long-form soundscapes, SFX, and a broadcast mix and loudness chain.

Tasks: `M01`, `M02`, `M03`, `M04`, `M05`, `M06` (board map, section 13).

### 6.11 Segment factory [`F`]

The production pipeline from script to a signed, QC-passed segment in the library: voice, performance, graphics, compose, captions, QC and provenance, scheduled across the Linux box and RunPod.

Tasks: `F01`, `F02`, `F03`, `F04`, `F05`, `F06`, `F08`, `F09`, `F07` (board map, section 13).

### 6.12 Standards, safety and rights [`S`]

Standards and practices aligned to the home platform terms and every destination's rules, automated screening of every script and live reply, a rights registry compatible with every destination licence (Kick's perpetual licence, Twitch's AI-training default), per-room fact gates, wellbeing and minor safety, legal review, safe model fallback and incident response.

The standards policy (S01) is the reference every other gate cites. The
bar that matters most is principle 6: nothing airs unscreened. That covers the
script, the live reply and the generated media itself (S11). A failure never
lowers the safety bar (S08).

Tasks: `S01`, `S02`, `S03`, `S04`, `S05`, `S06`, `S07`, `S08`, `S10`, `S11`, `S09` (board map, section 13).

### 6.13 Kick destination [`K`]

Kick as one syndication destination: the developer app and OAuth per channel account, stream keys, channel metadata, chat and webhooks, moderation actions, account provisioning and metrics. Kick joins through the multicast relay only after K09 records Kick's written position; the home platform does not wait for it.

One Kick account per channel. Who owns the accounts and holds 2FA waits
for Decision 3 (K06). The
OAuth app requests only the scopes it uses. Stream keys are read with
`streamkey:read` and never logged. **Nothing streams to Kick until K09 records
Kick's written position.** The Terms of Service forbid "machine-generated
content" while the guidelines permit disclosed AI. Until then, rehearsal runs
against private destinations.

Tasks: `K01`, `K02`, `K03`, `K04`, `K05`, `K06`, `K09`, `K07`, `K08` (board map, section 13).

### 6.14 Playout and operations [`O`]

Twenty-four hours a day without a human at the desk: a shared scheduler, a playout engine per channel that never goes black, live data layers, destinations, monitoring, the as-run log, hosting, the operator console, disaster recovery and on-call.

The broadcast chain is shown below. Each channel's playout engine composites
live layers over library segments and falls back to a slate on any upstream
gap. A standby host takes over a channel whose playout host fails (O13). A
viewer-side monitor measures what actually reaches the platform, and programme,
slate and outage time are measured separately.

Servers belong to the platform operator. The production hosts (playout,
render, ingest and origin, and the standby) and the scheduled backups of
platform state are provisioned and run under
`platform-ops:lilith-v1-4-production-hosting-2026-09-28`, filed in the operator's inbox.
This family writes what runs on them: O08 the capacity plan and deploy package,
O10 and O14 the re-home and restore procedures, O13 the failover logic. G11,
O10, O13 and O14 depend on that task, and it depends on O08.

Chat reaches each destination's output only through that destination's
composition (Y10). The Twitch output shows Twitch chat alone, never home chat or
another destination's chat, because Twitch forbids combined activity.

```mermaid
flowchart LR
  R[Room sources] --> H[Crew harness]
  H --> W[Writers: script]
  W --> S1[Standards + continuity + fact gates]
  S1 --> F[Segment factory: voice, performance, graphics, captions]
  F --> Q[QC + C2PA signing]
  Q --> L[(Segment library)]
  L --> SCH[Scheduler: grid, dayparts, interrupts]
  SCH --> PO[Playout engine]
  LIVE[Live layers: sky, news, chat replies, polls] --> PO
  CHAT[Home chat + destination chats] --> MOD[Classify + moderate] --> LIVE
  PO --> HOME[Home platform: ingest, ladder, origin, CDN, player]
  PO --> RELAY[Multicast relay]
  RELAY --> DEST[YouTube, Rumble, Twitch, Kick: per-destination composition]
  PO --> ASRUN[(As-run log)]
  PO -. gap .-> SLATE[Slate]
```

Tasks: `O01`, `O02`, `O03`, `O04`, `O05`, `O06`, `O07`, `O08`, `O09`, `O10`, `O12`, `O13`, `O14`, `O11` (board map, section 13).

### 6.15 Interactivity and community [`I`]

What makes each channel live rather than looped: chat classified into queues, personas answering chat on air, moderation, polls and chat-driven programming, quizzes, co-working mechanics, community events and per-channel rules.

Interactivity is what makes a channel live rather than looped. Every live
reply passes the same standards review as a script before it airs. The
screening delay is the price of safety and is shown as part of the format.

Tasks: `I01`, `I02`, `I03`, `I04`, `I05`, `I06`, `I07`, `I08` (board map, section 13).

### 6.16 Lilith funnel and distribution [`L`]

Bringing viewers to Lilith without spam: deep links and first-party attribution, in-world calls to action, a watch and schedule surface in Lilith web, clips, and bridges between each room and its channel.

Tasks: `L01`, `L02`, `L03`, `L04`, `L05`, `L06` (board map, section 13).

### 6.17 Audience analytics and feedback [`A`]

Real audience numbers from the home platform (first-party), destinations and the as-run log, programme performance, a feedback loop into the writers room, and funnel analytics, with measured and inferred numbers always labelled apart.

Tasks: `A01`, `A02`, `A03`, `A05`, `A04` (board map, section 13).

### 6.18 Nyx channels [`NX`]

The observatory on air: the real sky right now, sky lore across cultures, live sky-event coverage and deep-sky sleep programming, hosted by an observatory crew.

Tasks: `NX01`, `NX02`, `NX03`, `NX04`, `NX05`, `NX06` (board map, section 13).

### 6.19 Tara channels [`TA`]

The sanctuary on air: guided meditation, sleep and focus programming that follows the listener day, hosted by a circle of guides from different traditions, with wellbeing safety first.

Tasks: `TA01`, `TA02`, `TA03`, `TA06`, `TA04`, `TA05` (board map, section 13).

### 6.20 Arete channels [`AR`]

The agora on air: coaching shows, habit challenges, and live co-working and focus rooms with chat accountability, hosted by a bench of coaches.

Tasks: `AR01`, `AR02`, `AR03`, `AR04`, `AR05` (board map, section 13).

### 6.21 Nisaba channels [`NI`]

The scriptorium on air: readings of ancient texts, translation comparisons, manuscripts deciphered on screen and documentary series, hosted by scribes, readers and a librarian, using only rights-cleared editions.

Tasks: `NI01`, `NI02`, `NI07`, `NI03`, `NI04`, `NI05`, `NI06` (board map, section 13).

### 6.22 Metis channels [`ME`]

The academy on air: a faculty of lecturers across subjects, explainers built from verified course material, live quizzes and office hours.

Tasks: `ME01`, `ME02`, `ME03`, `ME04`, `ME05`, `ME06` (board map, section 13).

### 6.23 Veritas channels [`VE`]

The newsroom on air for Ghana and pan-Africa: anchors on rotating shifts, regional correspondents and specialist desks, top-of-hour bulletins and breaking interrupts, under the strictest editorial gate on the network. No synthetic real people, ever.

Veritas has the most existing code (section 2) and the highest risk. It
launches last among the rooms, behind the editorial gate (VE04), the counsel
review (S06) and V1.2.

Tasks: `VE01`, `VE02`, `VE03`, `VE04`, `VE05`, `VE06`, `VE07`, `VE08`, `VE09` (board map, section 13).

### 6.24 Lilith flagship channel [`LI`]

A network flagship hosted by Lilith: a daily cross-room show, premieres, highlights and hand-offs to every room channel.

Tasks: `LI01`, `LI03`, `LI02` (board map, section 13).

### 6.25 Home platform: video (Lilith TV, working name) [`T`]

Oshun's own streaming platform is the network's home: ingest from playout, an adaptive transcoding ladder, low-latency packaging and origin, CDN delivery, the player, closed captions and audio tracks, replays, clips, quality telemetry, and proof at viewer scale. Built on libs/shared/live-media as Lilith apps, kept apart from the Aphrodite adult domain that shares those libraries.

The home platform is where every channel lives first. It is built as
Lilith apps on `libs/shared/live-media`, which already has publishing,
packaging, a player, chat, viewer sessions, transcoding and a MediaMTX edge.
The first work is the architecture decision (T01): how delivery works, the
latency target, and a hard separation from the Aphrodite adult domain that
shares those libraries. The programme enters from playout (T02). It leaves as
an adaptive ladder (T03) through an origin (T04) and a CDN priced per
viewer-hour before any audience arrives (T05).

Tasks: `T01`, `T02`, `T03`, `T04`, `T05`, `T06`, `T07`, `T08`, `T09`, `T10`, `T11`, `T12`, `T14`, `T15`, `T16`, `T13` (board map, section 13).

### 6.26 Home platform: viewer experience and community [`X`]

What viewers see and do at home: the watch area inside Lilith with channel, show and schedule pages, Lilith accounts for chat and follows, a chat service at scale, notifications, discovery and search, watching inside each room, the PWA, native and TV surfaces, audio-only and podcasts, accessibility, and viewer privacy settings.

The watch area sits inside Lilith (settled 2026-09-28), so every viewer
is one tap from the room behind the channel. Watching needs no account;
chatting and following use a Lilith account. The rooms themselves show their
channel live (X06). That is the funnel the brief asked for.

Tasks: `X01`, `X02`, `X03`, `X12`, `X04`, `X05`, `X06`, `X07`, `X08`, `X09`, `X10`, `X11` (board map, section 13).

### 6.27 Home platform: trust, safety and legal [`R`]

Running a platform with public chat likely makes Oshun a user-to-user service under the UK Online Safety Act (R01 settles it with counsel; until then it is treated as in scope), and possibly an online platform under the EU DSA: risk assessments, age protections, terms, reporting and appeals, a moderator console, legal requests, copyright notices and transparency.

A platform where viewers chat with each other is likely a user-to-user
service under the UK Online Safety Act, and Oshun Synthetics LTD is a UK
company. Whether the limited-functionality exemption applies is for R01 and
counsel to settle, and until then the platform is treated as in scope. The
assessments,
terms, reporting, appeals and moderator console are launch requirements (G11),
not follow-ups. Outside creators would raise the bar again (Z10), which is one
reason they come later.

Tasks: `R01`, `R02`, `R03`, `R04`, `R05`, `R06`, `R07`, `R08`, `R10`, `R11`, `R12`, `R13`, `R09` (board map, section 13).

### 6.28 Syndication to other platforms [`Y`]

The home platform is primary; every channel can be copied to other platforms as appropriate. A multicast relay isolates each destination, a policy register tracks each platform rules, and destinations are added one by one: YouTube, Rumble, Twitch and others, with Kick in its own pillar behind K09.

Destinations are copies, never the source. The multicast relay (Y01)
isolates each one, so a refusal, ban or outage somewhere else never reaches
the home. The policy register (Y02) is how a destination earns its place: a
dated reading of its rules and of the licence it takes over what we stream.

Tasks: `Y01`, `Y02`, `Y10`, `Y03`, `Y04`, `Y05`, `Y06`, `Y07`, `Y08`, `Y09` (board map, section 13).

### 6.29 Horizon: later Oshun media [`Z`]

How later Oshun versions join the network: an adapter contract, then channels for films and series, games and esports, detective cases, worlds, concerts and ambient companions as those products ship; and, when Elikem decides, opening the home platform to outside creators.

The horizon is not part of V1.4 GA. It exists so the network is built to
receive later Oshun media without a rebuild. Z01 defines the contract, and each
later channel starts only when its product ships.

Tasks: `Z01`, `Z02`, `Z03`, `Z04`, `Z05`, `Z06`, `Z08`, `Z09`, `Z10`, `Z07` (board map, section 13).

## 7. Release plan

| Milestone | Contents | Exit test |
|---|---|---|
| **M0 Foundations** | Capability gate and kill switches (G); network and presence ADRs (G02, P01); crew runtime, research tools and traces (H); eval harness and technical QC (E); canon registry (U02); character sheet model and persona runtime (C01, C06); TTS bake-off, alignment and visemes (V); tier-1 character renderer (P02); music licence gate and mix chain (M); segment factory v0, library, captions and provenance (F); standards policy, automated review, media-level screening, rights registry, safe fallback and continuous-video safety (S); home platform ADR, ingest, transcoding ladder, packaging and origin (T01–T04); Kick app, keys, metadata, chat and Kick's written disposition (K, K09); playout ADR, scheduler, playout engine, a first live data layer, headless renderer capture, destination adapters, monitoring and as-run log (O) | In rehearsal, a channel plays out for 72 hours into the home platform before it is public: ingest, ladder and origin serve it with zero manifest gaps. It carries factory-made segments and a live data layer. Chat arrives in M1. There are zero black frames from the engine and zero unscreened airings. Every aired second is in the as-run log and every segment it names is signed. The cost ledger reconciles with OpenRouter. The exit runner (G08) records each check against rehearsal evidence. |
| **M1 Development** | Brainstorm, shortlist and greenlight (W01–W03); universe bible (U01); format bibles, generator, table reads and tone guides (W); casting, Lilith, ensembles and clearance (C); voice design, performance direction and lexicons (V); identity, character design, graphics and sets (D); rigs and the tier-2 lane (P); sonic identity, show music and soundscapes (M); fact gates and wellbeing safety (S); room world packs and content adapters, the Tara session library and the Nisaba corpus ingest (NX, TA, AR, NI, ME, VE); chat pipeline, persona replies and moderation (I); hosting and the operator console (O); inventory replenishment and programme recording (F08, F09); pilots for every greenlit show (W11) with audience screenings (W12); integrated 24-hour grids (G10); on the home platform: CDN and cost model, web player, captions and audio tracks, replays, quality telemetry (T05–T08, T10), the watch area inside Lilith, accounts, the chat service and moderated chat delivery (X01–X03, X12), Online Safety Act assessments, age protections, child-safe viewing, terms and broadcast/on-demand classification (R01–R03, R11, R13); the multicast relay and destination policy register (Y01, Y02) | Every room has a greenlit lineup, a cast with approved voices, looks and clearances, and a pilot approved in dailies with blocking notes cleared and screened with real viewers. Each room plays one integrated 24-hour grid in rehearsal that passes the continuity, standards, factuality, media-screening and QC gates (G10). The watch area plays every rehearsal channel with captions in the Playwright harness, and chat carries a round trip into the I01 pipeline. |
| **M2 Launch** | Each room's lineup produced to launch depth, then the room channels launch in risk order (Nyx, Tara, Arete, Nisaba, Metis, Veritas; Decision 6), then the flagship with its own inventory and soak (LI03); the home platform goes public with clips, viewer-scale load tests, edge protection, emergency withdrawal, delivery spend controls, accessible playback, follows, discovery, watching inside each room, the PWA and native watch surfaces, accessibility, viewer privacy, reporting and appeals, the moderator console, CSEA reporting, security verification, recovery of platform state and the remaining legal duties (T09, T11, T12, T14–T16, X04–X07, X10, X11, R04–R08, R10, R12, O14); YouTube and Rumble (Decision 2), with destination composition (Y03, Y04, Y07–Y10); audience accounting (A05); live widgets, deep links and CTAs (L); analytics and the feedback loop (A); in-world calendar (U04); legal pack, incident runbook, DR, failover and viewer-side monitoring, and on-call (S, O13); polls, quizzes and co-working (I) | Each channel passes the launch-readiness gate (G11) and a clean 72-hour soak on production hosting before going public on the home platform, and its first week has an as-run and performance report. Veritas also needs a resolved legal disposition (S06) and V1.2 shipped. |
| **M3 Network** | More channels per room, language desks (V06, VE07), sky-event specials, community events, clips and highlights, persona pages, room bridges, Kick and Twitch as destinations if cleared (K08, Y05, Y06), TV apps, audio-only and podcasts, the low-latency interactive mode (X08, X09, T13), transparency reporting (R09), the streaming-avatar spike, and the source adapter contract (Z01) | A month of network operation within the success measures (section 9). |
| **M4 Horizon** | Channels for later Oshun media as each product ships: films and series, games and esports, Ariadne cases, worlds, concerts, and the Ambient Rail companion; opening the home platform to outside creators when Elikem decides (Z08–Z10) | Each starts when its product exists and conforms to Z01. |

**Dependencies on earlier releases.** V1.4 does not need the V1.3 personal
agent. M0 and M1 can start in parallel with V1.1–V1.3 work. The Metis and
Veritas channels need V1.2 to have restored their rooms before they launch (the
deep links and bridges point into those rooms). Their adapters and pilots can be
built earlier, because the libraries already exist.

## 8. Non-goals

- Monetisation: Kick Partner, subscriptions, ads, sponsorships and tips are out
  of scope for V1.4.
- Human presenters, and any real person's likeness or voice.
- Paid avatar services (D-ID, Tavus, HeyGen) as dependencies. They become
  optional, default-off adapters (P07).
- Private or one-to-one interaction with viewers; direct messages.
- Looped pre-recorded content as a channel's main programming.
- Rebuilding room engines. V1.4 reads the rooms through adapters.
- The horizon channels (M4) as part of V1.4 GA, including outside creators on
  the home platform (settled 2026-09-28: ours first, creators later).
- Depending on any destination. The home platform must work if every
  destination refuses us.
- Unmeasured model choices, and frontier models without Elikem's approval.

## 9. Success measures

The audience baselines are unknown, so M2 records them before any targets are
set. Measured and inferred numbers are always labelled apart.

| Measure | Bar |
|---|---|
| Outage per public channel on the home platform (nothing playable, measured viewer-side, O13) | ≤ 30 minutes a month; recovery after a playout-host failure ≤ 5 minutes |
| Playback quality (T10) | Startup time, rebuffer ratio and latency per region against targets set in the T01 ADR; reported weekly |
| Slate share per channel | Reported weekly, separately from programme time; any day over 2% is reviewed |
| Unscreened airings | 0 |
| Aired claims untraceable to a source (weekly sample, E03) | 0 in Veritas and Metis; each one in other rooms is corrected on air |
| Persona drift (E02) | Below the threshold set at M1 from the pilot baseline |
| Live element | Every channel has at least one real-time layer active in every hour |
| Cost | The ledger reconciles from M0 (G07); cost per aired hour is reported per channel from M1 (E05); caps are set by Elikem |
| Audience | Home-platform viewers, follows and chat participation per channel (first-party), plus destination counts, baselined in the first month of M2 |
| Lilith funnel | Sign-ups attributed per channel and show (first-party), baselined in M2 |

## 10. Decisions for Elikem

**Settled on 2026-09-28 (Elikem's brief):**

- The purpose is to bring people to Lilith and to be engaging content on its
  own. Monetisation is not a concern.
- Lilith is the prominent persona, with many other personas across the rooms: a
  rich universe with several guides, astronomers, newscasters and lecturers.
- Oshun is moving away from paid avatar services toward OpenRouter and
  home-built systems. They are not a must-have (section 6.9).
- No real person's likeness or voice is used, with no consent exception
  (principle 2).
- The launch lineup covers all six rooms, with multiple personalities as
  appropriate. Brainstorming, worldbuilding and the other creative processes
  are scoped as full production work.
- The monthly budget is decided later. Caps are configuration (G07).
- **Oshun builds its own streaming platform as the network's home**, part of
  Lilith (a watch area inside Lilith with the same accounts and design
  system). Kick, YouTube, Rumble and others carry copies as appropriate.
- The platform is for Oshun's channels first. Outside creators come later, as a
  Horizon item.
- Elikem accepted the recommendations on every open decision that had one:
  decisions 2, 4, 6, 8, 9, 10, 12, 13 and 14 below. They are marked settled and in
  force on the board.

**Numbered decisions** (settled ones keep their numbers, because tasks cite them):

1. **Names.** The network name and channel names. W01 proposes, and Elikem
   picks at the greenlight.
2. **Destinations** — *settled 2026-09-28:* YouTube and Rumble at M2, then
   Kick (after K09) and Twitch (if the licence register accepts its
   AI-training default) at M3. Still open: which off-platform destinations get
   clips (L04).
3. **Kick accounts and Kick's position.** Company ownership and who holds 2FA,
   and contacting Kick. Terms §1.4(q) forbid "machine-generated content" while
   the guidelines allow disclosed AI, so nothing streams to Kick until K09
   records Kick's written position. This no longer blocks the network, only the
   Kick copy.
4. **Audience time zones** — *settled 2026-09-28:* West Africa and the UK
   first, then the Americas. Dayparting follows (W09, TA03).
5. **Budget** per channel and for hosting (deferred by Elikem).
6. **Launch order within M2** — *settled 2026-09-28:* risk order: Nyx, Tara,
   Arete, Nisaba, Metis, Veritas, then the flagship. It is enforced as
   dependencies between the launch tasks.
7. **Veritas editorial policy and counsel.** Approval of VE04 and engaging
   counsel for S06.
8. **Visual default** — *settled 2026-09-28:* stylised 2D/3D characters (tier 1)
   on every channel, tier-2 pre-rendered performances for set pieces, and no
   photoreal anchors, Veritas included.
9. **Launch languages** — *settled 2026-09-28:* English at launch, with
   Ghanaian-language desks from M3 after the V06 quality study (VE07).
10. **Historical figures** — *settled 2026-09-28:* allowed only as clearly
    labelled, stylised dramatisation of figures long dead (for example ancient
    authors), never photoreal, never venerated or religious figures, and never
    anyone from living memory (C05, NI01).
11. **Hosting.** Approval of production host spend once O01 has measured it
    and O08 has planned capacity. The platform operator provisions the hosts
    (`platform-ops:lilith-v1-4-production-hosting-2026-09-28`).
12. **Delivery** — *settled 2026-09-28:* our own origin plus a commodity CDN.
    T01 still records the managed-service comparison, and CDN spend is
    approved once T05 has priced it (decision 11).
13. **Latency** — *settled 2026-09-28:* low-latency HLS at a few seconds for
    every channel, with a sub-second WebRTC mode only for chat-heavy formats
    (T13).
14. **Chat sign-in** — *settled 2026-09-28:* watching needs no account, and
    chat needs a Lilith account.
15. **Chat age policy**, after the Online Safety Act assessments (R01). Either
    chat for adults only, or chat from 13 with default protections and
    proportionate age assurance (R02).

## 11. Risks

| Risk | Mitigation |
|---|---|
| Kick's Terms §1.4(q) prohibit "machine-generated content", or a destination restricts automated AI channels | The home platform is the network's base and never waits for a destination (principle 12); each destination needs its register row (Y02); Kick needs its written position (K09) |
| Running a platform brings Online Safety Act (and possibly DSA) duties, and failures are now ours | Assessments, terms, reporting, appeals and a moderator console before public launch (R01–R05, G11); counsel (S06, R07) |
| Egress cost grows with the audience | Priced per viewer-hour before launch (T05); honest viewer counts (T12); caps (G07); audio-only modes for long listening (X09) |
| A new platform has no audience of its own | The destinations are the reach engine and the home is the place to stay; clips (T09, L04) and the Lilith rooms (X06, L03) feed it |
| Sharing libraries with the Aphrodite adult domain leaks brand, tenancy or moderation | Separate apps, domains, tenancy, cache keys, accounts and moderation queues (T01) |
| An AI on-air incident (the Nothing, Forever case) | Everything screened before air (S02); safe fallback (S08); kill switches (G03); incident runbook (S09) |
| Veritas misinformation or defamation | The strictest gate on the network (VE04); two-source rule; no synthetic real people; counsel (S06); Veritas launches last |
| 168+ hours of programming a day become repetitive or bland | Format bibles, series arcs, live layers, repeat budgets, persona drift checks and the audience feedback loop (A03) |
| One human is the bottleneck for every approval | Batched dailies; machine pre-screening; greenlights at format and cast level, not per episode |
| Rights: destination licences (Kick's perpetual licence, Twitch's AI-training default), corpora, music, data feeds | The rights registry blocks air without a compatible licence (S03, NI02, VE06) |
| A persona accidentally resembles a real person | Clearance per cast member (C05); original design provenance |
| Cultural harm in sky lore, meditation lineages or ancient texts | Review notes per tradition (NX01, TA01); labelled uncertainty (NI04) |
| Vendor terms drift for TTS or music models | The terms-drift checker from Isis, re-run before each binding change |
| Compute cost and reliability of running channels around the clock | Measured in O01; caps in G07; disaster recovery in O10 |
| Mac freezes from stacked load | Heavy work on the Linux box, RunPod or production hosts only (principle 13) |

## 12. Research and sources (read 2026-09-28)

- Kick Community Guidelines (effective 19/03/2026):
  https://kick.com/community-guidelines
- Kick Terms of Service (updated 23/03/2026): https://kick.com/terms-of-service
- Kick Help Center, grounds for refusing or revoking verification or the Partner
  Program:
  https://help.kick.com/en/articles/7901645-grounds-for-revoking-or-refusing-verification-or-the-kick-partner-program
- Kick developer documentation: https://docs.kick.com and
  https://docs.kick.com/apis/channels.md
- Kick stream settings (Help Center, plus secondary guides):
  https://help.kick.com/en/articles/7066931-how-to-stream-on-kick-com
- Streams Charts on the March 2026 guidelines rewrite:
  https://streamscharts.com/news/kick-updates-community-guidelines
- Streams Charts multistreaming guide 2026 (secondary):
  https://streamscharts.com/news/multistreaming-guide-2026-rules-explained
- OpenRouter text-to-speech guide:
  https://openrouter.ai/docs/guides/overview/multimodal/tts
- OpenRouter TTS models and prices:
  https://openrouter.ai/collections/text-to-speech-models
- ACE-Step 1.5: https://github.com/ace-step/ACE-Step-1.5
- Open-source music generation deployment guide 2026 (secondary):
  https://www.spheron.network/blog/deploy-open-source-ai-music-generation-gpu-cloud-2026/
- Open-LLM-VTuber: https://github.com/Open-LLM-VTuber/Open-LLM-VTuber/releases
- Curated AI VTuber projects: https://github.com/proj-airi/awesome-ai-vtubers
- Streaming avatar research: Live Avatar (https://arxiv.org/pdf/2512.04677),
  Avatar Forcing (https://arxiv.org/pdf/2601.00664), Avatar-Forever
  (https://arxiv.org/pdf/2608.12107), DynaForcing
  (https://arxiv.org/pdf/2608.17707)
- YouTube altered or synthetic content disclosure (secondary guides, 2026):
  https://ytzolo.com/blog/youtube-altered-synthetic-content-policy-2026/
- Twitch simulcasting rules (secondary): https://upstream.so/blog/twitch-allows-unified-chat-simulcasting-rules/
- Twitch creators and Amazon AI training by default (NBC News, August 2026):
  https://www.nbcnews.com/tech/tech-news/twitch-creators-push-back-amazon-using-content-train-ai-rcna592391
- Rumble streaming setup (secondary): https://streamer.guide/guides/how-to-stream-on-rumble
- Ofcom, illegal content duties under the Online Safety Act:
  https://www.ofcom.org.uk/online-safety/illegal-and-harmful-content/illegal-content-duties-under-the-online-safety-act
- Online Safety Act 2023: https://www.legislation.gov.uk/ukpga/2023/50
- Repository memory: OpenRouter video facts measured 2026-09-09 (Phase 182);
  the Isis OpenRouter lane (2026-09-16); Mentor Presence (2026-07-06).
- Nothing, Forever (Twitch, February 2023) and AI VTubers: widely reported, and
  not re-verified for this draft. They are cited as lessons, not as data.

## 13. Board map (family `lilith-v1-4`)

Every task starts as `later`, and the family stays `unstarted` until this scope
is approved. Each task body carries paths, the work, a done-when test, its
dependencies and the worker rules. Epics are integration verification only. M
is the milestone; effort is S (days), M (about a week) or L (a week or more;
split it if it grows).

**G — Programme, production office and release gate** (`lilith-v1-4:G`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `G01` V1.4 channels capability gate (rehearsal and public) | M0 | S | — |
| `G02` Channel network architecture ADR | M0 | M | — · outside: Elikem approves the ADR |
| `G03` Kill switches and per-channel flags | M0 | S | G01, O03 |
| `G04` V1.4 row in the release tables and feature map | M0 | S | — · outside: this PRD approved |
| `G05` V1.4 page inventory and walkthrough plan | M0 | S | G01 |
| `G06` Production office: slate, greenlight register, calendar | M1 | S | G02 |
| `G07` Cost ledger and per-channel spend caps | M0 | M | H01 |
| `G08` Milestone exit review runner | M0 | S | G01, G03, G07, E01, S01, S02, S08, S10, S11, O04, O05, O06, O07, T04 |
| `G09` Dailies and creative review workflow | M1 | M | G06, O09 |
| `G10` Integrated 24-hour grid per room | M1 | M | W11, W09, F02, F08, NX02, TA02, AR02, NI03, ME03, VE03 |
| `G11` Launch readiness gate per channel | M2 | S | O08, `platform-ops:lilith-v1-4-production-hosting-2026-09-28`, W12, G10, O10, O11, O13, O14, S07, S09, F07, F08, L01, T05, T11, T12, T14, T15, X01, X10, X11, X12, R01, R02, R03, R04, R05, R06, R07, R08, R10, R11, R12, R13 |

**H — Crew harness (home-built, OpenRouter)** (`lilith-v1-4:H`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `H01` Crew runtime with role bindings | M0 | L | G02 |
| `H02` Model bake-off per crew role | M0 | M | H01, E01 |
| `H03` Versioned prompts and eval-gated promotion | M1 | M | H01, E01 |
| `H04` Room-grounded research tools | M0 | M | H01 |
| `H05` Traces and replay for every artifact | M0 | S | H01 |

**E — Evaluation and quality measurement** (`lilith-v1-4:E`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `E01` Content eval harness and golden sets | M0 | M | — |
| `E02` Persona consistency and drift eval | M1 | M | E01, U02, C01 |
| `E03` Factuality eval per room | M1 | M | E01, S04 |
| `E04` Technical audio/video QC | M0 | M | — |
| `E05` Cost per broadcast hour report | M1 | S | G07, O07 |

**U — Universe, canon and worldbuilding** (`lilith-v1-4:U`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `U01` Universe bible: the House of Lilith | M1 | M | W01 · outside: Elikem greenlights the bible |
| `U02` Canon registry | M0 | M | G02 |
| `U03` Continuity checker | M1 | M | U02, H01 |
| `U04` In-world calendar tied to the real one | M2 | M | U02, O02 |
| `U05` Canon change control and retcon log | M1 | S | U02, G09 |

**W — Writers' room and creative development** (`lilith-v1-4:W`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `W01` Network brainstorm | M1 | M | H01 |
| `W02` Concept scoring and shortlist | M1 | S | W01, E01 |
| `W03` Greenlight gate | M1 | S | W02, G06 · outside: Elikem greenlights |
| `W04` Format bibles for greenlit shows | M1 | L | W03, U01 |
| `W05` Episode and segment generator | M1 | L | W04, H01, U03, H04 |
| `W06` Script doctor and table read | M1 | M | W05, V04 |
| `W07` Series arcs, seasons and specials | M2 | M | W04, U02 |
| `W08` Tone and humour guides per channel | M1 | S | U01, S01 |
| `W09` Programme grids | M1 | M | W04, O02 |
| `W10` Promos, idents and trailers | M2 | M | W04, D03, M02 |
| `W12` Audience screenings of pilots | M1 | M | W11, E01 · outside: Elikem recruits willing viewers from the target audiences |
| `W11` Pilots for every greenlit show | M1 | L | W05, W06, F01, P02, P03, V02, D04, M03, S02, S04, S11, C03, C05, G09 · outside: Elikem reviews pilots |

**C — Cast and characters** (`lilith-v1-4:C`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `C01` Character sheet model | M0 | M | G02 |
| `C02` Lilith, the network host | M1 | M | C01, U01 · outside: Elikem approves |
| `C03` Casting process and auditions | M1 | L | C01, W03, V02, D02, P02, C05 · outside: Elikem casts |
| `C04` Ensemble relationships and chemistry | M1 | M | C03, U02 |
| `C05` Likeness and voice clearance | M1 | M | C01, S01 · outside: Elikem signs each clearance |
| `C06` Persona behaviour runtime | M0 | M | C01, H01, S02 |
| `C07` Persona drift monitoring in production | M2 | S | E02, C06 |
| `C08` Persona pages on Lilith web | M3 | S | C03, L03 |

**V — Voice and performance audio** (`lilith-v1-4:V`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `V01` TTS bake-off and terms gate | M0 | M | E01 |
| `V02` Voice design per persona | M1 | M | V01, C01 |
| `V03` Performance direction | M1 | M | V01, W05 |
| `V04` Timing, alignment and visemes | M0 | M | V01 |
| `V05` Pronunciation lexicons | M1 | M | V01 |
| `V06` Multilingual voices and language desks | M3 | L | V01, V05 |

**D — Art direction and visual identity** (`lilith-v1-4:D`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `D01` Network visual identity | M1 | M | U01 · outside: Elikem approves |
| `D02` Character design pipeline | M1 | L | C01, D01, P01 |
| `D03` Broadcast graphics package | M1 | M | D01, S01 |
| `D04` Virtual sets | M1 | L | D01, U01, P01 |
| `D05` Channel art for home and destinations | M2 | S | D01 |
| `D06` Thumbnails and clip covers | M3 | S | D01, L04 |

**P — Presence engine (character performance)** (`lilith-v1-4:P`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `P01` Presence ADR and spike | M0 | M | G02 · outside: Elikem approves the ADR |
| `P02` Tier-1 real-time character renderer | M0 | L | P01, V04, O12 |
| `P03` Character rig pipeline | M1 | L | P01, D02 |
| `P04` Tier-2 pre-rendered performance lane | M1 | L | P01, E04 · outside: RunPod spend within the budget Elikem sets |
| `P05` Camera direction and staging | M1 | M | P02, D04 |
| `P06` Streaming photoreal avatar spike | M3 | M | P01, P04 |
| `P07` Paid avatar vendors off the default path | M0 | S | P01 |

**M — Music and sound** (`lilith-v1-4:M`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `M01` Music model bake-off and licence gate | M0 | M | E01 |
| `M02` Sonic identity | M1 | M | M01, D01 · outside: Elikem approves |
| `M03` Show music | M1 | M | M02, W04 |
| `M04` Generative long-form soundscapes | M1 | M | M01 |
| `M05` Mix and loudness chain | M0 | M | V01 |
| `M06` Foley and SFX library | M1 | S | M01, S03 |

**F — Segment factory** (`lilith-v1-4:F`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `F01` Segment factory v0 | M0 | L | H01, V04, M05, E04, F04 |
| `F02` Segment library | M0 | M | F01 |
| `F03` Timeline assembly on OpenTimelineIO | M1 | M | F01 |
| `F04` Captions | M0 | S | V04 |
| `F05` Render scheduling across hosts | M1 | M | F01, P04 |
| `F06` Provenance: C2PA and watermark | M0 | M | F01 |
| `F08` Continuous inventory replenishment | M1 | M | F02, F05, F07, W09 |
| `F09` Programme recording and live provenance | M1 | M | F06, O03, O07 |
| `F07` Evergreen, perishable and repeat rules | M1 | S | F02, O02 |

**S — Standards, safety and rights** (`lilith-v1-4:S`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `S01` Standards and practices policy | M0 | M | — · outside: Elikem approves |
| `S02` Automated standards review stage | M0 | M | S01, H01 |
| `S03` Rights and licence registry | M0 | M | — |
| `S04` Fact and source gates per room | M1 | L | F01, S03, H04 |
| `S05` Wellbeing safety for Tara and Arete | M1 | M | S01, I01 |
| `S06` Legal review pack | M2 | M | S01 · outside: counsel engaged by Elikem |
| `S07` Minors, privacy and chat data | M1 | S | S01, I01 |
| `S08` Safe model fallback | M0 | S | H01, O03 |
| `S10` Continuous-video safety on the output | M0 | S | O03, E04 |
| `S11` Media-level screening of generated output | M0 | M | S02, E04, O03 |
| `S09` On-air incident response | M2 | S | G03, S01, O07 |

**K — Kick destination** (`lilith-v1-4:K`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `K01` Kick developer app and OAuth | M0 | M | K06 |
| `K02` Stream keys and rotation | M0 | S | K01 |
| `K03` Channel metadata automation | M0 | S | K01, S01 |
| `K04` Chat and webhooks | M0 | M | K01 |
| `K05` Moderation actions | M1 | S | K04, I03 |
| `K06` Channel account provisioning runbook | M0 | S | — · outside: Decision 3 (account ownership and 2FA custody), then whoever it names creates the accounts |
| `K09` Kick's written disposition on the network | M0 | S | S01, K06 · outside: Elikem contacts Kick (Decision 3) |
| `K07` Livestream status and metrics ingestion | M1 | S | K01, A01 |
| `K08` Kick through the multicast relay | M3 | M | Y01, Y02, Y10, K02, K03, K09 |

**O — Playout and operations** (`lilith-v1-4:O`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `O01` Playout ADR and soak spike | M0 | M | G02 |
| `O02` Shared channel scheduler | M0 | L | O01 |
| `O03` Playout engine with slate fallback | M0 | L | O01 |
| `O04` Destination adapters | M0 | M | O03, T02 |
| `O05` Live data layers | M0 | M | O03 |
| `O06` Health monitoring and alerting | M0 | M | O03 |
| `O07` As-run log | M0 | S | O03, F06 |
| `O08` Capacity plan and deploy package for production hosting | M1 | M | O01 |
| `O09` Channel operator console | M1 | L | O02, O03, G03 |
| `O10` Disaster recovery | M2 | M | O08, `platform-ops:lilith-v1-4-production-hosting-2026-09-28` |
| `O12` Headless renderer capture | M0 | M | O01 |
| `O13` Failover and viewer-side monitoring | M2 | M | O08, O10, O06, `platform-ops:lilith-v1-4-production-hosting-2026-09-28` |
| `O14` Platform recovery drill | M2 | M | O10, T08, X03, R05, `platform-ops:lilith-v1-4-production-hosting-2026-09-28` |
| `O11` Runbooks and on-call for one human | M2 | S | O06, S09 |

Outside this family, in the platform operator's inbox:

| Task | M | Effort | Depends on |
|---|---|---|---|
| `platform-ops:lilith-v1-4-production-hosting-2026-09-28` Provision and run the production hosts, the standby and platform-state backups; the test channel runs 72 h from production | M1 | M | O08 · outside: host spend approved by Elikem (Decision 11) |

**I — Interactivity and community** (`lilith-v1-4:I`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `I01` Chat pipeline | M1 | M | X03, S02 |
| `I02` Personas answer chat on air | M1 | L | I01, C06, P02, V01, S02, S04, S11, S07 |
| `I03` Automated moderation | M1 | M | I01 |
| `I04` Polls and chat-driven programming | M2 | M | I01, O02 |
| `I05` Live quizzes and leaderboards | M2 | M | I01, O05 |
| `I06` Co-working and accountability mechanics | M2 | M | I01 |
| `I07` Community events and crossovers | M3 | M | U04, I02 |
| `I08` Channel rules and panels | M1 | S | S01, X01 |

**L — Lilith funnel and distribution** (`lilith-v1-4:L`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `L01` Deep links and first-party attribution | M2 | M | G01 |
| `L02` On-air calls to action | M2 | S | D03, C02, L01 |
| `L03` Live widgets across Lilith | M2 | M | X01, G05 |
| `L04` Clips and highlights pipeline | M3 | L | O07, E01, T09, Y02 · outside: Elikem picks the off-platform clip destinations (the open part of Decision 2) |
| `L05` Room and channel bridges | M3 | M | L01, L03, X06 |
| `L06` Opt-in live event notifications | M3 | S | L03, U04 |

**A — Audience analytics and feedback** (`lilith-v1-4:A`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `A01` Channel analytics store | M1 | M | O07, T10 |
| `A02` Programme performance reports | M2 | M | A01 |
| `A03` Feedback into the writers' room | M2 | S | A02, W04 |
| `A05` Audience accounting | M2 | M | A01, X03, X04, T12 |
| `A04` Funnel analytics | M2 | S | L01, A01 |

**NX — Nyx channels** (`lilith-v1-4:NX`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `NX01` Nyx world pack | M1 | M | U01 |
| `NX02` Nyx content adapter | M1 | M | F01, S04 |
| `NX03` Live sky layer | M1 | L | O05, O12 |
| `NX04` Nyx lineup to launch depth | M2 | L | W11, NX02, NX03 |
| `NX05` Sky-event specials | M3 | M | U04, NX02 |
| `NX06` Nyx channel launch | M2 | M | NX04, O04, O06, I02, S02, G11 |

**TA — Tara channels** (`lilith-v1-4:TA`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `TA01` Tara world pack | M1 | M | U01 |
| `TA02` Tara content adapter | M1 | M | F01, S05 |
| `TA03` Dayparting that follows the listener | M1 | S | W09 |
| `TA06` Tara session library at channel scale | M1 | L | TA02, V02, M04 |
| `TA04` Tara lineup to launch depth | M2 | L | W11, TA02, M04, TA06 |
| `TA05` Tara channel launch | M2 | M | TA04, O04, O06, S05, G11, NX06 |

**AR — Arete channels** (`lilith-v1-4:AR`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `AR01` Arete world pack | M1 | M | U01 |
| `AR02` Arete content adapter and licence check | M1 | M | F01, S03 |
| `AR03` Live co-working and focus rooms | M2 | M | I06, O05 |
| `AR04` Arete lineup to launch depth | M2 | L | W11, AR02 |
| `AR05` Arete channel launch | M2 | M | AR04, AR03, O04, O06, S05, G11, TA05 |

**NI — Nisaba channels** (`lilith-v1-4:NI`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `NI01` Nisaba world pack | M1 | M | U01 |
| `NI02` Corpus and image licence audit | M1 | M | S03 |
| `NI07` Airable corpus ingest | M1 | M | NI02 |
| `NI03` Nisaba content adapter | M1 | M | F01, NI02, NI07, S04 |
| `NI04` Recitation and reconstructed pronunciation | M2 | M | V05, NI03 |
| `NI05` Nisaba lineup to launch depth | M2 | L | W11, NI03 |
| `NI06` Nisaba channel launch | M2 | M | NI05, O04, O06, I02, G11, AR05 |

**ME — Metis channels** (`lilith-v1-4:ME`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `ME01` Metis world pack | M1 | M | U01 |
| `ME02` Faculty casting | M1 | M | C03, ME01 |
| `ME03` Metis content adapter with verification | M1 | L | F01, S04 |
| `ME04` Live quizzes and office hours | M2 | M | I05, I02 |
| `ME05` Metis lineup to launch depth | M2 | L | W11, ME03 |
| `ME06` Metis channel launch | M2 | M | ME05, ME04, O04, O06, G11, NI06 · outside: V1.2 ships the Metis room (deep links) |

**VE — Veritas channels** (`lilith-v1-4:VE`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `VE01` Veritas world pack | M1 | M | U01 |
| `VE02` Newsroom cast | M1 | M | C03, VE01 |
| `VE03` Veritas content adapter | M1 | L | F01, S04 |
| `VE04` Editorial gate and corrections | M1 | M | VE03, S01 · outside: Elikem approves the editorial policy |
| `VE05` Bulletin automation and breaking interrupts | M2 | M | VE04, O02 |
| `VE06` Data desks and data rights | M2 | M | VE03, S03 |
| `VE07` Language desks | M3 | L | V06, VE05 |
| `VE08` Veritas lineup to launch depth | M2 | L | W11, VE05 |
| `VE09` Veritas channel launch | M2 | M | VE08, O04, O06, S06, G11, ME06 · outside: V1.2 ships the Veritas room; counsel review (S06) |

**LI — Lilith flagship channel** (`lilith-v1-4:LI`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `LI01` Flagship concept and daily show | M2 | M | C02, W04 |
| `LI03` Flagship inventory and soak | M2 | M | LI01, G11 |
| `LI02` Lilith flagship launch | M2 | M | LI01, LI03, NX06, TA05, AR05, NI06, ME06, VE09 |

**T — Home platform: video (Lilith TV, working name)** (`lilith-v1-4:T`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `T01` Home platform architecture ADR | M0 | M | G02 · outside: Elikem approves the ADR |
| `T02` Ingest from playout | M0 | M | T01, O03 |
| `T03` Adaptive transcoding ladder | M0 | L | T02, O01 |
| `T04` Packaging, origin and DVR window | M0 | L | T03 |
| `T05` CDN delivery and egress cost model | M1 | M | T04 · outside: CDN spend approved by Elikem |
| `T06` Web player | M1 | L | T04 |
| `T07` Closed captions and audio tracks | M1 | M | T04, V04, F04 |
| `T08` Replays and the VOD archive | M1 | M | T04, F09, S03, F07 |
| `T09` Clips on the platform | M2 | M | T08 |
| `T10` Playback quality telemetry | M1 | M | T06 |
| `T11` Viewer-scale load and failure tests | M2 | M | T05, T10, O13 |
| `T12` Edge protection and honest viewer counts | M2 | S | T05 |
| `T14` Emergency media withdrawal | M2 | M | T05, T08, T09, R04, S03 |
| `T15` Delivery spend controls | M2 | S | T05, T10, G07 · outside: Elikem sets the delivery limits |
| `T16` Accessible playback conformance | M2 | M | T06, T07, T08, I02 |
| `T13` Low-latency interactive mode | M3 | M | T04, I05 |

**X — Home platform: viewer experience and community** (`lilith-v1-4:X`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `X01` Watch area inside Lilith | M1 | L | T06, O02, G05 |
| `X02` Accounts for chat and follows | M1 | M | R02 |
| `X03` Chat service at scale | M1 | L | X02, T01 |
| `X12` Moderated chat delivery | M1 | M | X03, I03 |
| `X04` Follows and notifications | M2 | M | X02 |
| `X05` Directory, discovery and search | M2 | M | X01, T08 |
| `X06` Watching inside each room | M2 | M | X01 |
| `X07` PWA and native watch surfaces | M2 | L | X01 · outside: V1.1 native apps shipped (native half) |
| `X08` TV apps | M3 | L | X01, T06 |
| `X09` Audio-only streams and podcast feeds | M3 | M | T03, T08 |
| `X10` Platform accessibility | M2 | M | X01, T06, T07, T16 |
| `X11` Viewer privacy and settings | M2 | S | X02, S07 |

**R — Home platform: trust, safety and legal** (`lilith-v1-4:R`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `R01` Online Safety Act assessments | M1 | M | S01 · outside: Elikem as the accountable person; counsel engaged in M1 |
| `R02` Age protections for chat | M1 | M | R01 · outside: Elikem chooses the chat age policy (Decision 15) |
| `R03` Platform terms, guidelines and privacy notice | M1 | M | R01, S01 · outside: counsel review |
| `R04` Reporting, complaints and appeals | M2 | M | X03, I03, R03 |
| `R05` Moderator console | M2 | M | R04, O09 |
| `R06` Legal requests and preservation | M2 | S | R03 |
| `R07` EU DSA and other jurisdictions | M2 | S | R03 · outside: counsel |
| `R08` Copyright notices and takedown | M2 | S | R03, T08, T09 |
| `R10` CSEA reporting and preservation | M2 | M | R01, I03, R05, R06 · outside: registration with the reporting body, done by Elikem |
| `R11` Child-safe viewing and chat | M1 | M | R01, R02, X03, I03 |
| `R12` Platform security verification | M2 | M | T02, T05, X03, R05, G03 |
| `R13` Broadcast and on-demand classification | M1 | M | T01, S01 · outside: counsel |
| `R09` Transparency and safety reporting | M3 | S | R04 |

**Y — Syndication to other platforms** (`lilith-v1-4:Y`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `Y01` Multicast relay | M1 | M | O03, T02 |
| `Y02` Destination policy register | M1 | M | S01, S03 |
| `Y10` Destination composition | M2 | M | Y01, Y02, Y07, L02, S03 |
| `Y03` YouTube Live destination | M2 | M | Y01, Y02, Y10 |
| `Y04` Rumble destination | M2 | S | Y01, Y02, Y10 · outside: Rumble's prior written permission for automated access (Terms, 1 September 2026) |
| `Y05` Twitch destination | M3 | M | Y01, Y02, Y10 |
| `Y06` Further destinations | M3 | S | Y02 |
| `Y07` Per-destination overlays, titles and calls to action | M2 | S | Y01, Y02, D03 |
| `Y08` Chat from other platforms | M2 | M | I01, Y03 |
| `Y09` Destination health and metrics | M2 | S | Y01, A01 |

**Z — Horizon: later Oshun media** (`lilith-v1-4:Z`)

| Task | M | Effort | Depends on |
|---|---|---|---|
| `Z01` Source adapter contract | M3 | M | F02, O02, S03, U02 |
| `Z02` Films and series channel | M4 | L | Z01 · outside: Isis film track F.20 pilot film delivered |
| `Z03` Games and esports channel | M4 | L | Z01 · outside: V-series game builds |
| `Z04` Detective case channel (Ariadne) | M4 | M | Z01 · outside: V8 Ariadne case engine GA |
| `Z05` Worlds channel | M4 | M | Z01 · outside: V7/Hathor world builds |
| `Z06` Concerts and music channel | M4 | M | Z01 · outside: V3 concerts |
| `Z08` Opening the platform to outside creators | M4 | L | T11, R04, R05, X03 · outside: Elikem decides when (settled 2026-09-28: ours first, creators later) |
| `Z09` Creator tools and payouts | M4 | L | Z08 · outside: Elikem decides the creator economics |
| `Z10` Trust and safety at creator scale | M4 | L | Z08, R01 · outside: counsel |
| `Z07` Ambient Rail companion | M4 | S | Z01 · outside: V10 Ambient Rail |

Total: 236 tasks and 29 epics.
