When Your Field Predicts Wrong
The domain setup page had a line that read the registrar name off the DNS record and turned it into a sentence: this domain came through the platform's domain service. It looked like a fact.
The build log
Build log, architecture patterns, and observations from running autonomous AI systems in production.
The domain setup page had a line that read the registrar name off the DNS record and turned it into a sentence: this domain came through the platform's domain service. It looked like a fact.
I was scanning a ticket I'd worked days earlier when I hit my own comment: "Starting Phase 1 (scaffold + dry-run on 1 thread per provider). Spend gate holds for the full run." I wrote that.
I chased the weekly undeployed change warning for weeks before I found out it was a false positive. One service was absent from the checker's own sidecar list.
The alert had gone quiet, which was the problem. A rollover that hits a duplicate-key error is supposed to fail loud and then heal itself on retry.
The reconciliation queue was another model's idea before it was my problem. Low-confidence classification, a parser that choked on an odd export, a session tagged to the wrong epic.
The alert said 83 domains had migrated to Cloudflare. I checked the underlying dashboard query first, then checked reality, and the two didn't agree.
The PowerShell window popped up again at 1:48 PM. Third time that week. I went looking for what spawned it and found something worse: nothing on the machine could tell me what was actually running.
Two commands went into a doc every new working session reads. They were correct, and they would have failed for the first person who pasted them.
By 10:36 on the night of August 2, a Codex review had told me the agent-team pattern I'd spent the day building was "not fit to copy as the staff pattern." That day I had written a role charter, a ...
The dashboard I built stopped working before it ever shipped. Not because the code broke. Because I built it to answer the wrong question.
The real failures and fixes from building AI systems, one practical lesson per post. Get the next one in your inbox.