Federated Metadata: The Sequence Most Organisations Get Wrong
A four-part series: what most governance programmes are building on, and why it is not what they think
The first series on federated metadata argued that comprehensive cataloging collapses under its own weight, that federation is architecturally right but operationally demanding, and that the coordination taxes of distributed ownership require deliberate investment. That thinking was correct as far as it went. What it did not fully examine was the floor those arguments were standing on: whether the source systems beneath them were ever governed to be trustworthy, and where shared meaning actually comes from in organisations that have never fully agreed on it.
This second series goes deeper into that ground. It is written for the people who sit at the intersection of technical architecture, organisational authority, and strategic investment: those who have to make governance work rather than merely describe it. The argument running through all four essays is that governance is only as strong as the sequence beneath it.
Foundation, then translation, then the honest funding of coordination obligations, then governance architecture designed for the environment agents actually operate in. In that order, or not at all.
The Four Essays
The Foundation Decision — Most governance programmes are solving the wrong problem first
Source governance is an engineering release requirement, not a data quality policy. Most organisations treat it as a coordination problem and discover too late that they have built sophisticated governance architecture on foundations nobody controls. The cost has a name: authoritative incoherence, a system that is internally consistent, auditable, and wrong about what the business needs it to mean.
The Translation Investment — The hidden cost of domains that cannot agree on what words mean
Different domains hold legitimately different representations of the same reality, and no amount of enterprise ontology work resolves that. The goal is not a unified dictionary but a maintained translation layer. A platform is not a place where data lives. It is a logical construction of shared contracts and semantics that governs how data is used wherever it originates.
The Cost of Distribution — Distributed ownership hides its costs until the bill arrives
The expertise obligation, the versioning obligation, and the standards obligation tend to persist as federation matures rather than resolve. They are permanent design costs to be funded deliberately. Beneath all three runs a foundational tax: the price of building coordination infrastructure on sources that were never governed to be trustworthy.
The Accountability Decision — Agents do not fail loudly. That is precisely the problem.
When agents become the primary consumers of federated metadata, every coordination cost becomes an operational risk. Accountability must move from decisions to architecture: whoever designs the boundaries within which agents operate owns every decision those boundaries produce.
Where to Start
The essays can be read independently. Each one stands on its own argument. If you want to understand where this series began and what the first series established about cataloging, coordination, and the original costs of federation, the original three essays are the natural starting point before this one.
A Learning Journey
The original series published its third essay as explicit exploration rather than conclusion. This second series is where that iteration landed, with more confidence on the sequencing argument and more honesty about what remains open. The foundation argument does not fully resolve what minimum viable source governance looks like from a poorly governed baseline. The accountability argument names what the learning loop must do without fully specifying what it looks like in practice. These are not evasions. They are the questions where the thinking needs to keep developing. If you are working through any of them in your own organisation, I would genuinely like to hear what you are finding.
Additional Reading
The authority question: The Authority Crisis in Data Governance, The CIO Should Eat the CDO, The Logic Has to Stand on Something.
The platform and meaning arguments: The Data Platform Was Never a Place, Where Meaning Comes From.
The AI governance angle: The Governance Paradox: Human Oversight at Machine Speed.
The organisational cost of local optimisation exporting disorder to the broader system: The Entropy Tax: A New Law of Organizational Physics.
The original federated metadata series, When Everything Becomes Findable, The Metadata Coordination Problem, and What Federation Actually Costs, is where these arguments began. This series is where they became more certain.
An honest endnote
The sequencing argument this series makes, foundation before translation, translation before the honest funding of coordination obligations, all three before agents, is presented with more confidence than any individual organisation’s situation may warrant. The right starting point depends on where you are: an organisation with a poorly governed baseline faces a different set of first moves than one with stable source systems already in place. The essays argue for the sequence as a structural dependency, not as a universal implementation plan. What minimum viable looks like at each layer, and how to make progress when the foundation is still being established while the coordination layer is already in use, are questions the series identifies but does not fully resolve.
The series has also chosen to stay at the governance and organisational authority layer rather than the agentic architecture layer. Others are going considerably deeper into the operational design of agent networks. Eric Broda’s work on agentic mesh at agenticmesh.substack.com is worth reading for anyone who wants to follow that thread further. That is where the most important adjacent work is being done.
Thank you for the shout out!