Enterprise AI has produced a lot of noise about models, GPUs, vector databases, and agent frameworks. Those conversations matter. But the shift that will decide whether enterprise AI works is happening underneath the models.
For decades, metadata meant documentation. Teams built catalogs so people could find data sets, governance programs recorded definitions and ownership, and lineage helped reconstruct what broke, after it broke.
Metadata described the business. AI expects metadata to run it. That gap is bigger than it sounds.
An AI system doesn’t inherit the years of institutional knowledge a senior analyst holds in their head. It doesn’t know that finance’s definition of revenue excludes returns while sales’ definition includes them. It doesn’t know a customer ID became unreliable after a migration three years ago. It doesn’t know churn got redefined last quarter.
People pick that up over time, usually by getting burned once. AI simply answers using whatever definition it happens to land on, with no burned-once memory to fall back on. That’s what turns metadata from documentation into infrastructure.
Business meaning is now infrastructure
Infrastructure is anything every application depends on without thinking about it: the network, identity, storage. Every application assumes it exists. Business meaning belongs on that list now too.
Every AI application depends on the same definitions of customer, revenue, product, contract, and risk holding steady across systems. When they don’t, AI scales the inconsistency faster than any team of humans ever could.
BI showed us this problem first. Two dashboards would return two different numbers because two tools implemented the same metric two different ways. Most organizations learned to live with it: reconciliation meetings, spreadsheet showdowns, a standing argument about whose report is right.
AI broke the tolerance for semantic inconsistency. A wrong number on a dashboard gets caught by someone in the room. A wrong number an agent acts on can move through automated workflows before anyone notices.
The model reasons against whatever business context it’s handed. Fragmented context produces a confidently wrong answer, and that’s worse than an obviously wrong one. Without governed context, an AI agent is just a fast, well-spoken guesser.
That’s an architecture problem. No amount of model scale changes it. The fix is ensuring every AI system reasons from governed business definitions that stay consistent across the enterprise, regardless of which platform consumes them.
Governance has a new job
Enterprise governance has spent 20 years answering one question: who can access this data That question still matters. AI raises a second question that’s becoming just as important: what does this data actually mean?
Two analysts with identical access can produce two different numbers if they calculate the same metric two different ways. Most governance platforms document definitions and stop there. Enforcing them is a separate job, and usually a missing one.
Most enterprises got here by combining multiple metadata tools into an assembled solution: the right tool bought for each symptom, at a different point in time. A lineage tool to reconstruct what broke. A catalog for discovery. A governance platform for policy. A semantic layer for BI. None of them were designed on a shared foundation.
Each purchase solved its own slice and kept its own copy of what things mean. Four tools later, the work is funded in four places, owned in none, and measured nowhere, and the enterprise is still asking the question it started with.
AI makes that gap harder to ignore. A model uses whichever definition it finds first and sounds equally confident either way, blind to the conflict between them. Confidence is a property of the model, independent of whatever business logic sits underneath it.
Governance needs to reach past access control. It needs to connect business definitions to the systems that implement them, with ownership, version history, and lineage attached. A glossary entry and the system enforcing that definition should never drift apart.
When the documented definition of a metric differs from the one the applications actually execute, governance becomes an administrative exercise instead of an operational capability. AI simply exposes that gap faster than any previous technology, making it impossible to ignore.
Vendor neutrality just became a strategic call
Something else is shifting at the platform level. Every major cloud vendor now ships some version of governance, metric definitions, or AI context natively. That’s genuine progress, and enterprises should expect it.
Almost no enterprise lives inside one vendor’s perimeter though. Most run multiple clouds, a stack of legacy applications, SaaS tools, several BI platforms, and AI services from more than one provider. Each platform optimizes for its own world.
Business definitions must be able to travel across all of them. If every platform keeps its own version of what things mean, organizations rebuild the same fragmentation, only now it sits further inside AI workflows, where it’s harder to catch.
A vendor-neutral metadata architecture solves a different problem than any single vendor’s platform does. When business definitions can move with the enterprise rather than remain trapped inside individual platforms, organizations gain strategic flexibility instead of accumulating another form of lock-in.
Ownership stays with the enterprise, independent of which technology happens to consume those definitions. That means never having to redefine the business every time the infrastructure changes.
As AI ecosystems keep shifting, holding onto ownership of business meaning matters as much as holding onto ownership of the data itself.
Where this goes over the next five years
Metadata management is entering its second generation.
The first generation was about discovery: find the data sets, document who owns them, build the catalog. Necessary work, still running in most enterprises today. It’s no longer enough on its own.
The second generation is about execution. Metadata will shape how AI systems reason, how analytics platforms calculate metrics, how governance policy is applied, and how organizations prove the provenance behind a decision a machine made on their behalf.
That takes a different design: lineage, cataloging, governance, and business definitions all drawing from one shared metadata foundation. Business context becomes one operational model that every consuming system reads from directly.
Business definitions will start looking a lot more like software too. Version-controlled. Moved through development pipelines. Impact-tested before deployment, the same way a code change gets tested before it ships. AI agents, analytics platforms, databases, and applications will all read the same governed definitions.
The discipline has a name, MetadataOps, and a role to go with it. A MetadataOps engineer owns the path a business definition takes to production the way a platform engineer owns the path code takes. The role sits upstream of context engineering: context engineering decides what reaches an agent’s window, and MetadataOps decides what exists to be retrieved in the first place.
Enterprises build and maintain business meaning as an engineered asset, with the same discipline as everything else running in production. The real breakthrough here is enterprises finally giving context the same engineering discipline they’ve spent years giving code, infrastructure, and security.
For two decades, metadata explained the enterprise after the fact. The next decade will depend on metadata guiding it before decisions are made.
—
New Tech Forum provides a venue for technology leaders—including vendors and other outside contributors—to explore and discuss emerging enterprise technology in unprecedented depth and breadth. The selection is subjective, based on our pick of the technologies we believe to be important and of greatest interest to InfoWorld readers. InfoWorld does not accept marketing collateral for publication and reserves the right to edit all contributed content. Send all inquiries to doug_dineley@foundryco.com.