Why horizontal, not in-house
A reference embedded inside any one tool is unreachable to the others. The discipline has to sit above the stack.
The instinct, and why it fails
The instinct, when an organisation first recognises the dimensional gap, is to ask each of the existing tools to solve it locally. The warehouse team adds a values table. The catalogue team adds a controlled vocabulary feature. The semantic-layer team adds a dimension registry. Each solution is internally coherent. Together they produce the problem the discipline exists to eliminate.
Every system gets its own copy of the truth. The copies drift apart. The agent in the chat tool reads one canonical form for vendor. The model in the warehouse reads another. The dashboard tool, which still exists somewhere, reads a third. The configuration variance that the agent era introduces, where two configured systems produce structurally inconsistent output at machine speed, returns by a different door.
The architectural conclusion
Dimension management has to sit above the tools, not inside any one of them. The constraint is architectural, not aesthetic.
- A reference embedded in a warehouseis unreachable to an agent operating outside it.
- A reference inside a catalogueis decoupled from the systems that produce and consume values.
- A reference inside an MDM platforminherits the entity-centric assumptions that have limited those platforms from governing categorical values for thirty years.
What this requires
The reference has to be system-agnostic, API-first, and consumed by every layer: operational systems, ingestion pipelines, agents, semantic layer, governance tools. It has to be federated, so that different parts of the organisation can steward the dimensions they understand without going through a central choke point. It has to be versioned, so that records written under one definition remain interpretable when the definition changes.
And it has to be readable by software in the loop, not only by humans, because the consumers writing values are no longer only humans. This is the shape of the discipline described in the target state.
Where this leads
Dimension management starts as a transition enabler, the discipline that lets organisations move from dashboards to conversational analytics safely. It becomes permanent infrastructure, the categorical governance layer that every analytical and AI system in the organisation depends on.
The shift to conversational analytics is the trigger. The infrastructure that has to exist on the other side is what this module has been about. The next step is the Foundations module if the vocabulary in these eight pages needs grounding, or the target state for the operational specification of the discipline.