This is not a detached story about content automation. This article is moving through the same loop it describes: brief, evidence, canon, channel versions, checks, publication.
Under the hood, the scheme is deliberately simple: chat writes, git stores the state, the server publishes. On a whiteboard, it looks obvious. In real work, this bus appeared only because I could no longer answer a basic operational question: what state is this text in, which versions are ready, and where does it go next?
This is an engineering diary: how separate channel writers turned into one unit with a manifest; why automatic publishing to personal social channels failed in a live run; and why orchestration had to be separated from writing. Without that last cut, this article would be lying about itself.
Continue reading “How the pipeline that generates the content you’re reading actually works”
