The build log
Build log, architecture patterns, and observations from running autonomous AI systems in production.
An internal admin screen that looked like a layout ticket required a trace of its real database work. The incident showed why query plans, scope, and user value matter more than the surface description of a slow page.
Closing a ticket exposed a silent assumption buried in our release workflow: git tags were the source of truth for hotfix version detection. They were not.
Inside a day of debugging an old web form, where a querystring namespace collision hid behind an upload bug and showed what AI-paired work in legacy code looks like.
A 414-prompt pairing day where the active model was never surfaced. Session continuity and model-identity continuity are different things, and a footer line fixes it.
After a single audit session burned 365,257 output tokens and 37,945,352 cache reads, we tested RTK, a proxy that compresses common command output before it reaches the model. The post is about why an IO-layer fix beats personal discipline once you are running parallel sessions.
The agent hit a missing skills index in the first minute and offered to build one. We told it to go ahead. That was the last straightforward decision of that day.
A complex event form improved after a product review reconsidered its container. Dialogs are not always wrong, but form scope, lifecycle, and mobile use should determine the interaction surface.
An AI-assisted UI rebuild looked plausible but missed design tokens, a title-alignment invariant, and a shell-level width constraint. Code review caught the gaps before release.
A stacked set of customer tickets became clearer once small, access-controlled diagnostics separated data-state problems from code regressions before remediation began.
A display-order field that appeared to save and then silently dropped its value. The investigation found that ADD and UPDATE had been writing different data shapes for years inside the same module save path.
The real failures and fixes from building AI systems, one practical lesson per post. Get the next one in your inbox.