"Firekeeper is the ear. Bellows is the mouth. Between them sits the brain."
Voice Has Two Directions
It's easy to say "voice" as if it were one thing. It isn't. There is voice coming in — sound becoming text, dictation, speech-to-text — and voice going out — text becoming sound, synthesis, playback. Two directions, two engines. Firekeeper owns the inbound half; Bellows owns the outbound half. Neither one is the brain; together they wrap it, so the family can both listen and speak.
One Engine, Many Mouths
Because Bellows is a single always-on service, everything that needs a voice points at the same engine. cwkPippa's long-standing public TTS route became a thin proxy into Bellows rather than a second synthesizer. Keyboard Maestro macros call it. The cwkBeacon video workshop rerolls narration through it. There is exactly one place where a paid request can happen, one cache, one audio device — and many clients pointed at it.
Built Fast, on Purpose
This quest is the engine telling its own origin story, so the build itself is part of the lesson. Bellows went from "architecture settled with Dad" to a first real synthesis — one short Korean sentence, validated, cached, played through the studio interface, then proven free on the identical second request — inside a single day. The days after were hardening: account separation, receipt-before-post-processing, a live provider catalog, Studio lineage, Korean normalization. The evolution log reads like a build diary because it is one.