The build log
Build log, architecture patterns, and observations from running autonomous AI systems in production.
A staff tool for moving a customer account to a different configuration shipped in two patches and came back in one revert. The rebuild that held added nothing new to the page.
A 59% week-over-week signup jump looked like proof an SEO fix had worked, until the referral data showed most signups weren't being attributed to anything at all.
Exit code 4 came back on the first run where the meter was actually allowed to say no.
The branch was cut as a HOTFIX. By the time it merged, JIRA said staging task. Nobody had touched the type field on purpose.
The staff plan page showed no payment history for a customer account that had a first payment. The staff preview of the plan page was hardcoded to show none.
A session message blamed the wrong account. Tracing it found an open redirect. My first fix missed a second copy.
The drift check ran on 2026-08-31 and said live 31 vs doc 27, four behind. It was correct. It was also the only thing it looked at.
The payment cleared at 18:16:03 UTC. Stripe fired paymentintent.succeeded, invoice.paymentsucceeded, checkout.session.completed, all three, on schedule.
A deleted line in a colleague's branch would have wiped a team's Stripe keys the next time they saved their payment options. Not flagged by CI. Not flagged by a linter.
The number that stuck with me was 8. Out of 3,673 session rows scattered across six endpoints that each answered "what's running right now" differently, only 8 rows were the ones that mattered: the...
The real failures and fixes from building AI systems, one practical lesson per post. Get the next one in your inbox.