When the Firewall Log Stopped at v14
Cloudflare had 11 live custom firewall rules. The rule ID index still said six.
The build log
Notes from running agents in production.
Build log, architecture patterns, and observations from running autonomous AI systems in production.
-
-
The release step that never made it into docs
The legacy release was live. Its closing pass did not exist.
-
When agent skills carry stale instructions
Claude was following a hotfix procedure that could put develop work into production. My first story was that the agent had forgotten a routine. The wrong story was that Claude lacked context.
-
The Registry Check That Split Eleven Dead Domains
Eleven customer web addresses were already dead. Visitors got nothing. I treated that as a DNS problem, and Claude was ready to turn the same label into a batch notice.
-
A desk that measured 162 context switches an hour
My next request had nowhere to go. The central hub screen was locked while it worked through another problem, and I was hunting for a place to type.
-
The Error Count Went Up. Nothing Actually Broke.
An admin error log sat over its limit for most of a day. The count was real. The story it seemed to tell wasn't.
-
The Check I Called a Nuisance Was Also a Guard
Loosening a filenames rule that seemed to only reject normal photos also reopened a door it had quietly been keeping shut.
-
No Errors Means Nothing Worked: When Code Reviews Catch Exceptions, Not Workflows
The invitation was supposed to be on its way, but it had never sent for any client. The billing screen could not tell anyone whether a payment had landed.
-
The error log was working. The control surface might not have been
The error log printed 32 rows in one hour. I chased it.
-
The spike that wasn't
Thirty-two error rows landed in one hour.
Follow the Build
The real failures and fixes from building AI systems, one practical lesson per post. Get the next one in your inbox.