The real reason enterprise AI is stuck: metaphors aren’t models.

06.10.2026

Author - Enrique Dans

Over the last two years, enterprise AI has become filled with human analogies. We talk about memory, reflection, planning, delegation, feedback, even sleep. Business Insider recently described Anthropic’s “dreaming” technique for AI agents, a telling example of how naturally the industry reaches for human metaphors when describing systems that are, in reality, computational architectures. 

The metaphors are useful. They make complex systems easier to understand. They help product teams explain what their systems do. They help executives believe they are buying something familiar, but it is a proper model what defines identity, state, relationships, permissions, constraints, and valid transitions. It creates invariants: properties the system guarantees regardless of who uses it or how often it runs.

Without invariants, every deployment becomes a custom interpretation, and when that’s the dominant mode of delivery, the result is not a platform: it is consulting.

This is exactly the trap enterprise AI is currently in. Every organization has its own data, workflows, vocabulary, policies, approvals, systems of record, exception paths, and political reality. Without a formal layer that can represent those things in a reusable way, each deployment becomes a translation exercise. The model may be general, but the company is not.

That layer will not be another chat interface. It will not be a longer prompt. It will not be a prettier copilot or a more anthropomorphic agent. It will be a formal layer. A layer that represents identity, state, permissions, constraints, provenance, workflows, outcomes, and business semantics in ways that are understandable both to machines and to humans.

A layer that creates invariants, that makes enterprise intelligence composable, governable, auditable, and repeatable.

That is when ecosystems emerge. That is when deployments become scalable. And that is when enterprise AI finally leaves its artisanal phase behind.

Every major software revolution follows the same pattern: first we imitate reality with metaphors, then we discover the abstraction that makes an industry possible.