The report got the architecture right. It got the owner wrong.
The new martech map is right about where everything is going. It is quiet on the one layer you have to own, and in Australia that layer is about to become the law.
In March, Scott Brinker published the clearest map I have read of where martech is going. The stack of boxes is dissolving into what he calls a composable canvas: one data foundation, with custom agents built on top as the real edge. I do not have a quarrel with any of it. We have been building on that premise for years. The data stays where it lives, the intelligence sits next to it, and the advantage goes to whoever can shape it to their own business.
He is right, and the market has caught up to him fast. Databricks now calls the warehouse the CDP. Gartner's latest quadrant rewards warehouse-native and agentic. The CDP Institute's own numbers show the composable vendors growing several times faster than the rest of the field. The direction is no longer in question. So I am not going to spend a thousand words agreeing. I want to talk about the one thing the report names and then walks straight past.
Of the data classes Brinker lays out, the one that decides who actually owns the system is the record of why. He calls it the context graph: the decision traces, the approvals, the reasoning behind what the machine did. He treats it as architecture, a useful thing to capture on the way to real-time everything. It is not architecture. It is governance. The "what" lives in any system you care to name. The "why" is what a board, a regulator, or a customer asks for when a decision goes wrong, and it is the thing almost nobody is keeping on purpose.
In Australia, that gap now has a date on it. Brinker's report calls the context graph the keeper of the "why". Australian law is about to make that "why" mandatory. From December 2026, businesses have to be able to explain how their automated decisions are made. The Privacy Act reforms tighten what consent even means. The Consumer Data Right keeps widening. The penalties for getting it wrong run into the tens of millions. The report describes a best practice. I am describing a legal requirement, and the only safe place to keep that record is infrastructure you own. A document written for a global audience, and sponsored by a data platform, was never going to lead with that. It is not their deadline.
Here is where the architecture and the ownership part ways. You can assemble a composable canvas out of rented parts and it will run beautifully, right up until someone asks you to explain a decision. At that point the answer matters more than the speed, and the answer lives wherever the parts live. If the explanation sits in a supplier's account, you do not own it. You can request it. You can pay to keep querying it. You cannot put your name to it without trusting someone else's. A decision you cannot explain on your own terms is a decision you are renting, and renting your own audit trail is an odd place to be standing when the regulator is on the phone.
I want to be honest about what we do and do not do, because the report's end state is enormous. We are not the firm that builds your whole canvas. That is a multi-year, whole-of-business programme, and there are much bigger firms for it. What we do is narrower, and I think more useful right now. We build the pieces that have to be owned, and we hand them over with the keys. The consolidated data. The shared definitions, so "high-value customer" means one thing in marketing and the same thing in finance. The first agents that act on it. And the record of why, written in your environment, in your name, ready before anyone has to ask. You do not have to own the whole canvas this year. You can own the first piece this quarter.
So I read Brinker's report as good news, mostly. It is the best argument yet that the thing we have been quietly building is where the whole market is heading. But validation cuts both ways. When the architecture is something everyone can buy, from the same handful of platforms, assembled the same way, the architecture stops being the edge. Within a year, composable is table stakes. The edge is the part you cannot buy off a shelf and cannot rent back: the layer that has to explain itself, kept somewhere you control.
Everyone is about to own the same composable canvas. The only edge left is owning the layer that has to explain itself.
The first piece is the one you own.
NTWRK builds the foundational pieces that have to be owned, the record of why included, and hands them over with the keys.