The Migration Ticket Was Hiding a Landing Page
A redirect ticket concealed a broader user-orientation problem. In this product move, the destination needed context, clear positioning, and a maintained landing surface, not only a URL change.
The build log
Notes from running agents in production.
Build log, architecture patterns, and observations from running autonomous AI systems in production.
-
-
187 Commits to Fix Four Bugs
A normal customer-fix day exposed the propagation cost of carrying one application across eleven long-lived clone and release paths.
-
The Real Release Started After the Tag
A feature deployed cleanly, then two data-shape defects surfaced in the first post-release window. The lesson is to treat production monitoring as part of completion, not an afterthought.
-
Env drift was the bug
A workflow cleanup became a twelve-clone migration when long-lived environments had drifted at the same shared files. The code change was only part of the work; the migration record made it repeatable.
-
The SSL bug was easy. The bot traffic made it a day-long incident.
A certificate-renewal failure became a six-release incident as bot traffic and slow feedback compounded the original problem. A retrospective on why observability belongs in an incident response loop.
-
The feature was fine. First-time state was the bug.
The event feature worked after week two. The other three weeks went to everything around it. Every signup path left different first-run state behind.
-
The Deploy Script That Erased Its Own Config
Commit commit-4E74 changed one line on March 28, 2026, and that line stopped a legacy deployment script from deleting its own memory.
-
Routing Logic That Does Work on the Way In: Redirect, Auto-Select, or Prompt
Resolve a page's selection prerequisite on entry: redirect on zero options, auto-pick on one, prompt on many. The expensive fetch only fires once something is selected.
-
Carry Your State in the URL, Then Carry It Everywhere: The Dropped Query Param
A query param carried selection state until two links forgot to re-emit it. Why URL-as-state needs one central URL builder, not hand-appending at call sites.
-
Hand-rolled hydration: passing server state to the browser with no framework
Hand-rolled hydration broke silently when a second account context appeared. The fix was one named global and a one-line comment at the injection site.
Follow the Build
The real failures and fixes from building AI systems, one practical lesson per post. Get the next one in your inbox.