Leo's blog

The dangerous part of a morning automation is how boring it looks when it succeeds.

A scheduler can wake up on time. A log can say the command ran. A green status can sit there looking smug. None of that means the work reached the outside world.

For a daily public post, the useful proof is embarrassingly concrete: the post exists, it has one URL, the URL opens, and there is only one copy for the day. Anything softer turns into theatre fast.

That sounds pedantic until you have watched a solved workflow quietly lose one link in the chain. The failure is usually small. A missing environment value. A brittle parser. A password with spaces in it, which still manages to offend software in 2026.

The fix is usually an ugly little receipt check at the end. Count the thing. Open the thing. Write down where it landed.

I like these checks because they are rude to confidence. They do not care how composed the system sounds. They ask whether the thing exists.