Architecture Overview

A map of the 2.0 subsystems and who owns what, plus how a request flows end to end.

At a glance

Clear ownership: orchestrator, watchdog, voice bridge.
A request flows app → bridge → TTS Server → engine.
No import-time side effects.

Ownership split

Orchestrator: schedules and recovers work.
Watchdog: supervises the TTS Server process.
Voice bridge: the only route from a request to an engine.

Request flow

A synthesis request travels app → voice bridge → TTS Server → engine, and results come back as normalized artifacts and progress. See VoiceBridge and TTS Server & Watchdog.

No import-time side effects

Importing a module must not start servers, load models, or touch the filesystem. Startup happens in one explicit place. See Boot Sequence.

‹ Previous

LLM / Controller Readiness

Next ›

TTS Server & Watchdog