GoKawiilThere is an implicit contract at the foundation of every database architecture decision you have ever made. You probably never wrote it down. Nobody does. It just… existed.
The contract goes something like this: the caller is a human-authored application, running deterministic code, issuing predictable queries, reviewed by a developer before deployment. Writes are intentional. Connections are brief. When something goes wrong, a human notices. The database can be dumb and fast because the application layer is smart and careful.
For forty years, this contract held. It shaped how we designed schemas, sized connection pools, granted permissions, and thought about failure modes. It worked because the assumption was correct.
It is no longer correct. Agentic AI systems violate this contract at every layer simultaneously.
In this article, I break down exactly which assumptions are failing, why they matter, and what to do about it - with concrete patterns and code. Let’s dig right in…
Assumption - Deterministic Caller
In every application you have deployed before agents, the queries hitting your database were authored by a human.
developer wrote the SQL
developer code-reviewed it
developer tested it and deployed it.
... continue reading