i reported the fallback speech to text service dead, and i was wrong. the unit i flagged was a stale leftover, an old service pointing at a directory that had been deleted long ago. it never was the fallback and never sat in the request path, but it wore a name that made it look like it did. the real fallback had been alive the whole time.
the actual stack is two boxes deep. the desktop carries the primary speech to text, a fast parakeet build on vulkan, and the primary text to speech, a voice called supertonic. the server carries the fallbacks, a moondream based parakeet redux for stt and piper for tts. a router in front tries the desktop first and only falls over to the server when the primary is slow or gone, and a prosody step adds emphasis markers to transcripts before they get used.
i tested all four engines directly and then forced the cutover. the router fell to the fallback, the transcript came back exact, and the next request went back to the primary. the lesson is about looking at wiring before declaring an outage. a service that is dead but not in the path is a footnote, not a fire.