Skip to content

Deliver consistent-character, consistent-voice FableLoom production and hosted play #5377

Description

@atomantic

Goal

Deliver the production architecture described in docs/plans/2026-08-29-fableloom-character-voice-hosted-production.md: repeatable character identity and voice across full movies or episodic FableLoom stories, plus a two-device hosted experience where a viewer speaks to an off-screen protagonist over authored, pre-rendered video.

Why

PortOS already has a Universe Bible, character reference sheets and LoRAs, Kokoro/Piper synthesis, a branching FableLoom runtime, and local STT/TTS transport. The remaining work is to join those primitives into versioned character production packages, explicit playback assets, production provenance, and a safe half-duplex hosted session protocol.

Delivery slices

Child issues will cover:

  • approved Universe character production packages;
  • visual canon bindings and capability-aware conditioning;
  • machine-local voice profiles using existing engines;
  • Qwen3-TTS voice design, consented cloning, and optional fine-tuning;
  • entry, hold-loop, and transition playback assets;
  • scoped QR-hosted sessions with half-duplex character voice;
  • episodic production orchestration and continuity review; and
  • a non-blocking future investigation of diegetic FaceTime calls.

Program acceptance criteria

  • Canon-locked shots identify the exact character, approved identity assets, wardrobe, adapters, temporal source, and omitted inputs.
  • Offline dialogue and hosted replies resolve an approved character voice revision and reproducible mastering chain.
  • Missing local artifacts degrade visibly instead of silently substituting or appearing intentionally empty.
  • Hosted mode requires HTTPS, an off-screen protagonist, safe rendered hold loops, and ready STT/LLM/TTS routes.
  • Viewer and protagonist turns are half-duplex, and live character voice never overlaps rendered character dialogue.
  • All provider-heavy generation, training, and review remains explicitly user-triggered.

Out of scope

  • Real-time AI video or runtime lip-sync.
  • Internet relay or public exposure of a PortOS instance in the first hosted release.
  • Multi-audience sessions in the first release.
  • FaceTime integration as a dependency of browser-hosted mode.

Tracking

The browser-hosted path is the delivery target. #5385 is related future work
and does not block this epic's initial hosted release.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:mediaarea:story-builderStory Builder featurearea:voiceVoice stack: STT/TTS pipeline, proactive speech, voice tools, call bridgedecomposedEpic already split into per-slice child issuesepicUmbrella/tracking issue — shipped as per-slice children, never as one PRplanTracked by /do:replanplan-featureFeature plan filed by the plan-feature brainstorm

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions