Every product you ship is underspecified. Not a flaw — a fact. No spec survives contact with every ambiguous case, every channel contradiction, every path nobody meant to allow.
For years that gap stayed invisible, because someone filled it for free.
Four things happened, silently, every time a human used your systems:
→ They resolved ambiguity locally. Interpreted what you meant, not just what you wrote.
→ They reconciled contradictions across channels. One page said one thing, another said something else — they picked whichever made sense and moved on without telling you either one was wrong.
→ They stayed inside the path you designed, even when the system let them wander further. Not because your rules stopped them. Habit did, or courtesy, or boredom.
→ When none of that worked, they complained. That complaint was the only real sensor you had on your own quality.
Each one looks minor on its own. Together, they were the reason your system’s actual behavior stayed close to what you designed, instead of drifting toward everything it technically allowed.
None of it was ever diagrammed. Nobody owned it, versioned it, or wrote an SLA against it. The human user was an undeclared dependency in your architecture — the only one that never showed up in a design doc.
An agent inherits none of these four services. It doesn’t infer intent. It won’t notice a contradiction unless told to check. It has no habit keeping it on the happy path. And when it fails, it doesn’t complain — it just tries something else, somewhere else, and you never find out.
Companies aren’t facing a new technology. They’re losing a subsidy they never knew they were receiving.
The fix isn’t a new team or a new budget for AI readiness. It’s writing down, finally, what that dependency was quietly doing for you — because you can’t govern a dependency you never declared, and you can’t declare one you never named.