Agents do not just need context. They need context that holds together while they act.
Third in a series. Prior articles: “The Artist Already Knew” and “The AI Data Layer.“
Models respond. Agents act.
That is a small sentence with consequences, and it is the shift this article is about. The AI landscape is no longer only chat interfaces and question-and-answer flows. Gemini executes checkouts inside search. ChatGPT’s Operator capability opens browsers and fills carts. Anthropic’s Model Context Protocol lets Claude read and write to external systems. Google’s Universal Commerce Protocol standardizes how any agent can transact with any merchant. Salesforce reports that twenty percent of the 2025 holiday retail season was already influenced by AI agents. The era of the agent is not coming. It is here, it is growing quickly, and it changes what the infrastructure underneath it has to do.
Across this series, I have argued that context is the defining variable in applied AI, and that the contextual infrastructure feeding modern AI systems is a genuine next-generation data layer — the AI Data Layer — continuing a trajectory that runs from the early Analytics Data Layer through the Universal Data Layer and the Customer Data Layer that the industry now calls the CDP. In each of those transitions, Tealium has been the company building the category-defining layer. The transition to agents is the one where the stakes of that infrastructure get materially higher, because the consequences of wrong context are no longer a strange output but a strange action — a booking made, a refund issued, a preference updated, a negotiation completed.
Four shifts define what the contextual infrastructure has to do now. They build on each other, and together they describe what it means for context to keep up with an agent’s work.
The first shift is that context becomes continuous. A model answering a question receives a context window, produces an output, and the next call starts roughly fresh. An agent does not work that way. An agent operates across a session — sometimes across minutes, sometimes across days, sometimes across a long-running process that coordinates many smaller decisions — and the context it holds at step seventeen is partly a function of what it decided at steps one through sixteen. The CDP era optimized for the correctness of a profile at the moment it was read. The agent era asks for something harder: the profile has to remain coherent across the full arc of an agent’s work, update as the world changes underneath it, and deliver the right slice of that evolving picture to the agent at each step. Continuous context is not a faster version of point-in-time context. It is a different engineering problem.
The second shift is that agents generate signal, and that signal has to come home. When an agent books a flight, submits a return, updates a preference, or negotiates with another agent on a customer’s behalf, that action is itself a customer event. It has to flow back into the profile, because the next decision — whether by the same agent or a different one — depends on knowing that it happened. Agent-generated signal also carries different provenance than customer-generated signal, and the infrastructure has to capture the distinction. An action a customer took is not architecturally identical to an action an agent took on a customer’s behalf, even when the outcome is the same. Done well, this creates a virtuous loop: every agent action enriches the context that makes the next agent action better. Done poorly, it creates compounding noise. The architecture decides which of those you get.
The third shift is that permission itself becomes context that has to move. When a customer asks an agent to “book me a flight,” what they authorized is not a fixed fact stored once at the start of the session. It is a condition that applies to some actions and not others, for some data and not others, for some duration and not others. As the agent works, the permissions that govern its next action have to travel with it — available at every step, evaluable in real time, revocable the moment the customer’s intent changes. Consent in the agent era is not a flag on a record. It is a living signal that moves alongside the customer and the agent, and the AI Data Layer is what keeps it moving. Organizations that treat permission as static will find their agents making authorized decisions in one moment and unauthorized ones in the next. Organizations that treat permission as context will find that trust becomes the most durable asset their brand owns.
The fourth shift is that the architectural pattern from the last article — customer, contextual layer, AI, action — has to close into a loop. In the responsive-AI world, that pattern is roughly linear: context flows into the model, an answer flows out, and the cycle completes. In the agent world, the action the AI takes produces new state in the real world, which has to be observed, ingested, governed, and made available to the next decision. The AI Data Layer stops being a pipeline and becomes a closed loop. The pieces are mostly already there in any organization that built a CDP seriously. What changes is what the layer is for, how tightly the loop has to close, and how continuously the whole system has to keep the context current.
This is the work Tealium has been building toward across three generations of data layer. We built the Universal Data Layer and made it the standard by which a vendor-neutral description of a digital event was carried across the stack. We built the Customer Data Layer and made real-time, identity-resolved, consented customer profiles the operating foundation for a decade of marketing and experience technology. The AI Data Layer we are building now brings continuous context, bidirectional agent signal, living permission, and closed-loop architecture into one layer — and we have already stood up the connective tissue that lets agent ecosystems reach it, including a managed Model Context Protocol server that gives agents a standardized, consented way to access the customer context they need to act responsibly.
I want to be honest that no single vendor, including Tealium, has fully solved every piece of the agent context problem. What I can tell you is that the organizations we work with who are furthest along share a pattern. They treated customer data infrastructure as strategic before the agent era made it urgent. They invested in identity, consent, and orchestration when those capabilities were useful mostly for better marketing. They are now discovering that the same investments are exactly what agents need, with relatively little new work to adapt them. Three generations of data layer turn out to be a single architectural trajectory, and the organizations that walked it deliberately are the ones best positioned for what is arriving now.
Every article in this series so far has been about infrastructure — what it is, why it matters, what it has to do. Infrastructure is the prerequisite. It is not the destination.
In the final article of this series, I want to spend time on what becomes possible once the infrastructure is in place. Customer representations so complete and so live that organizations can simulate a journey before committing to it. Agents coordinating with other agents on a customer’s behalf in ways that feel, from the customer’s point of view, like a single seamless experience. A shift from managing customer records to maintaining customer representations that grow more useful with every interaction. Some of it is already starting. Some of it is further out. All of it is closer than most people think.
That is the article I want to write next.
