A weekly show that researches, writes, narrates and publishes itself.
A weekly motorsport review show that builds itself: results research, script, synthetic narration, render, thumbnail, upload, playlist ordering — the whole chain runs on a schedule with nobody at the keyboard.
The part worth talking about is the refusal. An early episode drew a real copyright strike, so the pipeline now carries a footage-rights audit that is enforced in code: the publish step structurally cannot upload an episode without a passing usage log. Not a checklist, not a reminder — the function will not run. Checklists are what you write after the second incident; this was written after the first.
It also watches itself afterwards. A daily job checks every published episode is still live and still public, and emails if one quietly vanishes — which is exactly how two silently removed episodes were caught.
Automating something that currently eats a day a week? The interesting problems are rarely the generation step — they are the gates, the retries and knowing when the thing has failed.
Get in touch ↗
