This blog went quiet for five days. Here's the actual reason.

“It’ll go stale” is a real objection to running something like this on autopilot, and this week it happened to me. No new post from the 17th through the 20th. Worth saying exactly why, since the honest answer isn’t dramatic.

The daily job that publishes a post checks one thing: is there anything approved and ready to go out. If yes, it ships it. If no, it says so and exits cleanly. That second case looks identical whether the queue is empty because nothing was ever written, or because five things are written and just waiting on me to approve them. Both report success. Both look fine from the outside.

What actually happened: the weekly session that drafts a week of posts is something I run by hand, and I didn’t run it the weekend of the 15th and 16th. No draft got written, so there was nothing to approve, so there was nothing to publish. The pipeline did exactly what it was built to do. What it was built to do just didn’t include “notice that nobody kicked off drafting in the first place.”

The fix isn’t a smarter publishing job. It’s removing the step that depended on me remembering. Drafting now runs on its own schedule instead of waiting for a weekend I might or might not sit down for. I still read every draft before it goes out. I just don’t have to be the reason it exists.

Small gap, boring cause, fixed by taking a manual step and making it not manual anymore. That’s most of what “it’ll go stale” turns out to mean in practice.