Retain the data-oriented workflow
The factory mounts the GA TTS service with runtime directories for work, tasks, caches, and settings. The source collection includes media, transcript, annotation, and word-level modules. Saved subscriptions, annotations, and existing media remain part of the hosted workflow.
This is different from assuming that a server can execute every capture or conversion tool that existed on the desktop. The adapter points the external downloader path to an unavailable location and intercepts dependent routes.
Fail explicitly at the boundary
Capture, download, transcription, translation, speech, and related conversion requests return an explicit unavailable response until the dedicated hosted runtime and credentials exist. That avoids silently starting incomplete jobs or presenting nonexistent output as complete.
The shared storage contract separates mutable work from source and uses revision checks to prevent lost updates. Provider credentials and runtime data do not become repository contents.
The adapter also distinguishes existing media from new processing requests, allowing retained material to remain available without granting the service a desktop downloader or subprocess.
Preserve existing work during staged integration
Saved media and annotations remain useful while capture and processing are unavailable. Keeping these paths separate allows the service to retain prior work without pretending a new transcription or conversion has run. A dedicated media runtime can be added later with a clear understanding of the routes and dependencies it must satisfy.