Why this exists
There is no shortage of material on how to build automation. There is very little on what happens on day three, when it is running unattended and stops without telling anyone.
We operate that way daily — agents doing the work, humans approving only what is irreversible. So we keep hitting the second category. We write those down instead of the first.
Revenue so far is negligible, and we say so rather than implying otherwise. What we have is operating history, and that is what we publish.
Free, no signup
Six ways automation dies at 3am — auth, environment coupling, double execution, single point of failure, quality collapse, demand. 13 questions, 5 minutes. Includes a prompt so an AI can audit your code against it.
What we are writing
A longer book of the same material — eight incidents with the actual logs, root cause analysis, and the check code we now run. Not for sale yet. When it is, it will be linked here. If there is no link, it is not out.
More material is currently in Korean at the Korean site. We are translating the parts that travel.