The landscape maps for AI agents have become almost comically dense. Every major lab ships a framework. Thousands of MCP servers proliferate. Orchestration, memory, evaluation, governance: each concern has spawned multiple competing implementations, most less than a year old. A thriving ecosystem, evidence the category is real.

Everything blooming at once looks different if the frost hasn't come yet.

Building a prototype agent is genuinely cheap. Inference costs have fallen roughly 10x annually. A competent team can have something demonstrable in days. Operating that agent reliably, at production scale, with the governance and failure handling that enterprise deployment demands, remains stubbornly, qualitatively harder. Deloitte's 2025 survey found 38% of organizations piloting agentic solutions but only 11% in production. McKinsey's numbers tell a similar story from a different angle: 23% of organizations say they're scaling an agent somewhere in the business, but in any individual function, that figure drops to 10%. The intent is broad. The depth, so far, is thin. And over a third of organizations Deloitte surveyed have no formal agentic strategy at all.

That cost asymmetry drives the proliferation. KPMG found that system complexity has overtaken all other challenges as organizations try to move from pilot to production. The jump from single-agent to multi-agent is where orchestration logic, shared memory, failure handling between agents, and evaluation frameworks compound into something qualitatively harder than the prototype suggested.

The most honest document in the ecosystem right now might be the MCP roadmap itself. The protocol has crossed 97 million monthly downloads. Every major provider has adopted it. And its own 2026 roadmap reads less like a victory lap than a gap analysis. The four enterprise-readiness items it identifies — audit trails, SSO-integrated auth, gateway behavior, configuration portability — are classified as pre-RFC, still needing clear problem statements and directional proposals. The lead maintainer wrote directly that a dedicated enterprise working group does not yet exist. Meanwhile, production teams are stitching together custom logging, bolting on their own trace identifiers, reconstructing request chains after the fact. The dominant connective tissue of the agent ecosystem, adopted at extraordinary scale, openly acknowledges that the infrastructure enterprises need to operate it responsibly hasn't been specified yet.

The adoption curve and the readiness curve are diverging. That tension holds only as long as most deployments remain pilots. And the emerging consensus from every serious survey points the same direction: infrastructure, not models, is where things are stuck. Model capability has outrun the operational scaffolding. Can organizations run agents with the observability and governance that production requires?

We've watched this before. The container orchestration landscape of 2014–2017 had at least five serious competitors. The simpler options worked fine for testing. When cloud vendors endorsed Kubernetes and production requirements imposed real selection pressure, the field consolidated dramatically. By 2023, 87% of container-using organizations ran Kubernetes. The whole cycle took six years. The agent ecosystem is more layered, so the parallel is illustrative rather than predictive. But the structural logic holds: selection pressure comes from operating requirements, and operating requirements only surface at scale.

None of this has matured yet. The constraints that will determine what survives haven't fully arrived. Everything grows. That's the tell.