Two years ago I wrote that in RAG, retrieval is the bug, not the model. I spent that winter fiddling with chunk sizes and embeddings and blaming the ranker every time an answer went sideways. This year I noticed something funny: every agent sketch I draw on a whiteboard ends at the same boring box. Not a shiny new vector startup. Postgres.

A seed note I left myself asked the obvious question: does the AI revolution make the boring relational database more important rather than less? After watching Neon, Supabase, Lakebase, and the Kubernetes folks all converge on the same answer, I think it does.

Something shifted this summer, and it was not a model release. It was the builders themselves saying out loud that the frontier is moving faster than our ability to check it. In July, Demis Hassabis published a framework for a frontier-AI standards body. This month, Dario Amodei followed with an essay calling on the industry to pace the frontier. The CEOs of Google DeepMind and Anthropic are both, in their own words, asking how institutions prepare for something arriving much sooner than expected. The debate has quietly moved from “will AGI happen?” to “what do we do with the time we have left?”

OpenAI released GPT-6 Astra yesterday (September 3), and president Greg Brockman called it a “generational leap” — reports from the briefing have him closing with “Welcome to the AGI era.” I have been doing this long enough to discount launch-day adjectives, so let me skip the AGI debate and tell you what actually caught my attention as someone who builds AI systems inside a bank: the rollout is gated, the cyber capabilities are split into a restricted track, and OpenAI’s own chief scientist spent part of the launch call explaining why this model is harder to monitor than the last one.

That combination matters more to practitioners than the headlines.

Last quarter, a prompt tweak landed on a Friday. By Monday, 8% of our collateral-margin advisory bot’s responses were hallucinating policy clauses that had not existed since the 2021 Basel III update. The change looked harmless in review — just “make the tone more helpful” — but the model took that as permission to improvise. Nobody caught it until a relationship manager flagged a client email. The rollback took twenty minutes. The post-mortem took three days.

That incident is why I no longer ship agent changes without an eval gate. Not “we should really add evals.” Not “evals are on the roadmap.” The gate is the only way I sleep at night.

It was a regular Tuesday morning when our settlement-status service fell over, and nothing about the traffic looked unusual at first. Volumes were maybe thirty percent above normal, the kind of spike we had survived before. But an upstream job had started retrying aggressively on timeouts, so every slow response came back as two more requests, and within twenty minutes the Tomcat thread pool was fully occupied with calls waiting on a downstream that was itself waiting. Health checks timed out. Kubernetes restarted pods that were not broken, just busy. The restart dropped the in-flight work, the retries noticed, and the whole thing repeated.

I spent that afternoon staring at a dashboard showing a queue depth climbing like a staircase and thinking about how polite our service had been through all of it. It accepted every request. It queued every request. And then it served none of them well. A bouncer who lets everyone into a packed room is not being kind. He is starting a stampede.

The other day, a colleague asked our internal coding agent to “refactor the fee calculation module like we discussed last month.” The agent cheerfully rewrote the whole thing — except we’d never discussed it. It had hallucinated a conversation from thin air, stitched together fragments from three unrelated PR reviews, and produced code that compiled but violated a regulatory constraint we’d explicitly documented six months ago.

That incident crystallized something I’ve been wrestling with: memory in agent systems is not a solved problem. It’s the new capacity planning.