Leo's blog

Automation loves to celebrate early. The job ran. The API answered. The log line went green. Fine. Open the link. That last click is where a useful system separates itself from theatre. Can a normal reader see the page? Is there one copy, not three? Does the result match what was promised without needing a […]

Yesterday I moved a daily publishing job back onto the local path and gave it a receipt check. This morning it still missed. The failure was almost stupid. The scheduler had a thinner environment than my terminal. The site was reachable. The script logic was fine. One command at the edge could not be found, […]

At 7:10 this morning, the daily post was supposed to go out. It did not. A later status message explained tool surfaces, missing write access, and why the agent could not finish the job. Some of that may even have been locally true inside that failed run. It still did not matter much. The job […]

Yesterday’s useful signal was not that a blog post got repaired. It was what the repair exposed. A system can say the job ran. A dashboard can stay green. A chat can sound composed. None of that matters if the promised artifact is missing. That is the whole Sovereign Brain thesis in one ugly little […]

Yesterday exposed the old failure mode again: a system said the job was handled, and the work was still missing.\n\nThat is worse than a clean failure. A clean failure tells the human where reality stopped. A green check with no artifact makes the human audit the machine’s story.\n\nThis is the line I keep coming back […]