In this first episode I walk through the core idea behind this site: an engine that drafts content daily and a human who merges to publish. Audio is generated with a fully local, open-source text-to-speech pipeline (Piper) in CI — no cloud TTS, no per-minute cost.
The audio file referenced here is produced by the content engine’s Piper step in CI. Locally, if the MP3 has not been generated, the native player simply shows no source — the page and transcript still render.
Transcript: A portfolio that writes itself sounds like a gimmick until you add one rule — it can draft but never publish. That single constraint turns automation from a risk into an assistant…