The Database Was in Sydney
Dashboard screens took one and a half to nearly three seconds to paint because each made eight to ten database reads, in sequence, across the Pacific. Cutting the round trips first and then moving the functions beside the database brought most screens under seven hundred milliseconds.
Two Spellings of One Instant
A claim token written as a JavaScript timestamp ending in Z came back from Postgres ending in +00:00. The run compared them as strings, decided the claim was stale, and exited. Every time. The tests passed because they used tidy fake tokens.
Searching for the Word Yes
Every message over ten characters was embedded and searched as typed, so "yes, go with the second one" went to the vector store as a query. A small deterministic classifier now searches on the subject of the turn, and treats corrections with particular care.
The Cache That Never Hit
Measured across two weeks of real traffic, the prompt cache marker on conversation history had never produced a hit. Content that changed every turn sat in front of it, and the history window slid by one message per turn.
An Unordered Limit Is a Lottery
A scheduled job ran green every thirty minutes for a week and did almost nothing, because its query had a LIMIT and no ORDER BY. An audit found the same shape in nine other jobs, two of them already starving real work.
A Stylesheet Is Not a Palette
Brand colours read from CSS included states nobody ever sees, browser defaults nobody chose, and one red that was only ever an error message. Reading the rendered page, and checking the reader with an independent instrument, fixed the palette at its source.
Sent Is a Claim
Failed recipients were logged and forgotten, so a campaign the provider refused entirely still read as sent. Failures are now data, the final status is earned, and energy is reserved at approval and settled against what was delivered.
A Timeout Is Not a Cancellation
Tool calls had a time budget enforced by racing a timer. When the timer won, the system reported failure while the work carried on and sometimes completed. Now the work can be cancelled, and when it cannot be, the outcome is reported as unknown.
The Limit That Ran Before My Code
Photo uploads above four and a half megabytes vanished without a word. My code allowed fifty, but the hosting platform refused the request before my code ever ran. Sending bytes straight to storage removed the cap from the path.
The Row That Never Finished
Activity rows left as running by processes that died were counted by a concurrency gate forever. Two of them made every image wait a full minute and then carry on, which is why nothing ever reported it.
Everyone Is Not a Default
The code that chose an email's recipients fell through to the whole list when nothing else was set. That made a deliberate broadcast and a forgotten audience look identical. Now a broadcast is a recorded choice, and the approver sees the count before anything goes out.
One Image, Every Turn
A wide, highly compressed image passed the byte limit and broke the vision API's dimension limit. Because history is resent on every turn, one upload would have failed every message that followed. Inputs that persist need stricter gates.