KindCue is a studio side project: six-to-nine-second looping health reminders — “Water. Now, not later.” — rendered as kinetic typography, one sourced micro-fact per video, published across six platforms. It launched in a single overnight session on July 10. By July 19 it was publishing itself.
The renderer is deterministic Remotion: same props and seed produce an identical mp4, which makes a 25-tip content bank batch-renderable and reviewable. Distribution went through three versions fast. v0 was manual posting — and manual posting is where consistency goes to die; four posts in, a stressful week produced a five-day gap. The conclusion wasn’t “try harder”, it was architectural: the flaky component was the human operator layer, so automate distribution now rather than at the growth gate. v1 bulk-scheduled through native platform schedulers. v2 wired a posting API with a verified queue — thirty-six posts, six platforms, six days, scheduled in one session.
Day one of the automated queue delivered the lesson that justified the whole build. Three platforms published clean at 09:00. The entire Meta trio failed together — one vendor cluster, not three separate bugs. Recovery was same-morning retries, and the monitoring gap closed the same day: an evening watchdog now verifies same-day delivery and retries approved content exactly once, then reports. One retry, then report — automation that retries forever is automation that hides failures.
The spine is content-agnostic on purpose. If this format fails its gate, the content swaps; the pipeline stays. That’s the studio thesis in miniature: build the system, let the work flow through it, measure honestly at gates.