We Assumed We Were Letting AI Crawlers In. We'd Been Blocking Them for Months.
The alert fired on a rule we'd never named: 200 events in 24 hours through the verified-bot skip lane, and not one of them was the thing we'd come to document.
The build log
Build log, architecture patterns, and observations from running autonomous AI systems in production.
The alert fired on a rule we'd never named: 200 events in 24 hours through the verified-bot skip lane, and not one of them was the thing we'd come to document.
The alert I was chasing had nothing to do with what I found. I was in the codebase for an unrelated ticket, tracing how staff sessions get verified on an internal admin tool, when I hit a line that...
Between 10 and 20 percent of our signup codes and password resets to Yahoo, AOL and Gmail had been hard-rejected for about ten days, and nothing in our code had changed in that time.
A staff login check had one carve-out for the login page itself. The carve-out read a value the caller controlled, not one the server had already resolved.
One filter button sat in the wrong place on mobile and in the right place on desktop, and the stylesheet that positioned it looked fine in the editor.
Four reviewers ran in parallel over a finished diff, and one of them flagged a preview render that would be written into the production page cache and served to real visitors.
51 of 55. That is how many of the "already cleared" verdicts an adversarial audit refuted after I fanned a backlog review out to sub-sessions and got back 45 tidy files, each one confident.
One of my AI agents called me escapist. I fired back a task asking it to prove it with my own data. It retracted the claim within the hour.
A maintenance window ran exactly once, against a real production box, and the written plan turned out wrong in four separate places.
The alert wasn't an alert. It was a number: 82 tickets, 382 comments, and nobody had read all of them. I opened the epic planning to work through it top to bottom and closed it inside a minute.
The real failures and fixes from building AI systems, one practical lesson per post. Get the next one in your inbox.