AI Technology20-10-20266 min read

The Coordination Layer: What to Build When Models Converge

Models are converging and getting cheaper to swap, so the durable engineering in enterprise AI is moving somewhere else: the layer that decides who may act, what is remembered, when a human takes over and what gets evidenced. A build guide for the part of your AI stack you'll still own in five years.

Paul Coerkamp
Paul Coerkamp
CEO & Co-Founder
The Coordination Layer: What to Build When Models Converge

Here is a useful question for any enterprise AI team: if your model provider retired your model tomorrow, what would you have to rebuild?

A year or two ago the answer was often "almost everything." Today it should be "one configuration entry." For three years, enterprise AI strategy meant model strategy: which model, which vendor, which benchmark. That question matters less every quarter, because the leading models are converging and switching between them is increasingly a configuration change. What does not converge, and cannot be swapped in ten seconds, is everything around the model: the layer that coordinates people, agents and systems.

In this article I'll make that layer concrete: what it contains, why your engineering budget belongs there, and a checklist to test whether a team is building it or demoing around it.

Treat the model as a dependency and the coordination layer as the asset.

Why the difficult work moved

Three independent sources point the same way. Forrester's 2026 agentic AI assessment lands on a structural diagnosis: "a long running agent doesn't behave like a chatbot: it behaves like a distributed system, and distributed systems demand orchestration, identity, and context discipline that most companies have never built." Anthropic's 2026 State of AI Agents report finds that nearly half of organizations, 46 percent, cite integration with existing systems as a primary obstacle to deploying agents, ahead of any concern about model capability. And Gartner now predicts that by 2030, more than 60 percent of early agentic orchestration implementations will fail to meet performance or cost expectations, because enterprises underestimate the integration, governance and talent requirements of making digital workforces reliable.

Taken together, they say that organizations rarely fail on the model anymore; they fail on everything the model plugs into. Or, as Linas Beliūnas put it in his newsletter this month: "Coordination between humans and agents is the scarce layer once models converge." Len covered the unit of work half of this argument two weeks ago: sessions versus cases. This piece is about the machinery that makes case running work possible at all.

The four components

Across every regulated agent build we've delivered, the same four components keep being the actual work. The newsletter reports specialist teams spending 80 percent of engineering on compliance and integration infrastructure; our own ratio is in the same neighborhood, and it divides into these four.

Where the defensible layer sits

The permission model

Authentication only tells you who the user is. A permission model says which action requires which authority, per product, per amount and per jurisdiction. An agent that can read a balance, freeze a card and draft a settlement holds three very different powers, and each needs its own gate: some actions the agent takes alone, some need step up authentication from the customer, some need a named employee's approval. A common mistake is to encode all of this in the prompt, which the model treats as a suggestion. The permission model has to be enforced outside the model, where a confused agent cannot talk its way past it.

Case state

Case state is memory that survives sessions, shifts and systems. It records what has happened in the case, what is pending, what was decided and by whom, and it lives in a database with a schema rather than in a context window. This is also where the clock lives: deadlines, waiting periods, retry schedules, escalation timers. The test Len proposed is the right one, so I'll repeat it: your agent should be able to act on day eight of a case in which nobody has typed anything since day one.

Handing over, and handing back

A person takes over from the agent and later hands the case back, with full context in both directions. When confidence drops or authority requires it, a person takes over and sees the whole case, not a transcript dump. When the person resolves their part, the agent resumes the routine follow up. Most builds get the first half right and forget the second: the human closes their task and the case silently dies, because nothing resumes it. A handover is a two way door, and both directions carry state.

Evidence generation

The fourth component makes every automated step logged, attributable and reconstructable: which data was read, which model version answered, which check passed, who approved. That evidence is generated while the case runs. An export bolted on afterwards turns "show me how this decision happened" into a forensic project, whereas here it is a query. This is where governance stops being policy and becomes code, and it's the part your auditor, and increasingly your regulator, will judge you on.

Why this layer is the defensible one

Everything below the coordination layer is commoditizing: models converge, get swapped and get repriced. Everything above it, the channels, changes with fashion: web chat today, WhatsApp tomorrow, voice next year. The layer in between is the only part that compounds. It encodes your products, your authority structure, your compliance requirements and your integrations, none of which a competitor can download.

This has a practical consequence for build versus buy. Whatever platform or vendor you look at, ask to see the permission model, the case state, the handover protocol and the evidence trail, and spend less time on how good the model is. A vendor that answers with a benchmark chart is selling you the layer that's converging. That is also how we built our own platform: the four components are part of the platform itself, so a new use case starts with them in place instead of rebuilding them per project.

The checklist

Five checks that tell you within an hour whether a team is building the coordination layer or a demo:

  1. Kill the process and restart it. The case should resume where it was. If state lived in the context window, it is gone.
  2. Ask for the permission table. You want to see which actions the agent can take alone and where that is enforced. "It's in the system prompt" is a failing answer.
  3. Trigger a handover and come back. Check whether the human sees the case or a transcript, and whether the agent resumes after they finish or the case dies in a queue.
  4. Pick a closed case and ask how the decision happened. If reconstructing it takes engineering time, evidence generation doesn't exist.
  5. Swap the model. If anything other than a configuration entry changes, the model was carrying responsibilities it should never have had.

A team that passes all five can survive a model deprecation, an audit and a regulator visit in the same quarter. A team that fails three of them has built an impressive conversation, and will find out the difference in production.

Models will keep converging. The coordination layer is the part you own. If you'd like to see how we have built ours, with the permission tables, the case state and the evidence trail on real use cases, we'd be glad to walk your team through it. You can reach us here.

Paul Coerkamp
Paul Coerkamp
CEO & Co-Founder
Writes about Business Strategy, Enterprise Sales, AI Implementation, Startup M&A
Paul Coerkamp on LinkedIn
Published on 20-10-2026

Related Articles

9 Things I Really Hate About AI
AI Technology12-05-2025

9 Things I Really Hate About AI

I think it's great that technology is so embedded in our daily lives. It helps us get knowledge faster, finish tasks more efficiently, gives us inspiration, and occasionally scares the hell out of us with those crazy (fake) videos. I help a lot of companies implement AI, so in the end it pays my bills. But after spending a ridiculous amount of time with all these new technologies, it's time to write down the things I really hate about AI.

Read More →
A Conversation Is Not a Case
AI Technology06-10-2026

A Conversation Is Not a Case

The 95 percent pilot failure stat is making the rounds again, this time with a diagnosis I actually agree with: chatbots automate sessions, but a bank runs cases. Why the unit of work decides whether your AI survives production, and the day eight test that shows which one you built.

Read More →
Agentic AI Languages and Dialects: Why Voice Quality Is Still the Hard Part
AI Technology10-04-2026

Agentic AI Languages and Dialects: Why Voice Quality Is Still the Hard Part

Agentic systems promise autonomous workflows, but speech and dialect quality fail first. Why Arabic, Turkish, Chinese and more run into the same gap.

Read More →

Stay Updated

New posts on conversational AI, enterprise automation and customer experience, sent to your inbox when they go live

No spam, unsubscribe at any time