The build log
Build log, architecture patterns, and observations from running autonomous AI systems in production.
The host warned they can't promise replacement parts for our dedicated boxes. The fix everyone expects is a rewrite. The fix that pays the bills is decoupling: DNS to the edge first, hardware second, stack unchanged.
Everyone has a story about AI making their team faster. I audited mine: commits per person per year, tickets resolved, review comments. The team doubled its output in six months, and every person's gain landed in a different currency.
The technical part of an edge migration took days. The human part, moving a long tail of customer-managed DNS without breaking anyone's website, is the part that's still going. Canary batches, a migration board, deadline emails, and a relay with a tested restore.
At 9:59 AM, I deleted a ticket built around 13 supposed production duplicates and restored a test-site domain row, domainID 1368, that the cleanup had removed.
At 6:33 AM, the daily sweep logged one line and moved on: vault drop failed, my home server unreachable over Tailscale, DNS resolution failing. The obvious read was that my PC was off.
The oldest SSH tab dropped first whenever an agent spent several minutes thinking.
On June 30, I changed 40 lines in src/content.config.ts, added 33, removed 7, and stopped requiring voice, tone, and style before a post could publish.
The wrench dialog said the competition and find-a-team filters should be showing. On the live test site, they weren't.
On June 27, a close guard rejected a legitimate item because it had found the wrong bundle.
The filter fix looked correct for about 90 seconds. Then I noticed I had changed the dropdown builder, not the display loop that was actually suppressing the control.
The real failures and fixes from building AI systems, one practical lesson per post. Get the next one in your inbox.