Every new tool adds another silo, and your agents inherit the mess. The missing piece is older and cheaper than any integration: a shared vocabulary the machine can compute.
In March, a stakeholder I'd worked with for two quarters changed companies. For eleven days, two of my systems disagreed about where he worked. My CRM said the old employer. My agent layer said the new one. The outreach draft my agent prepared that morning congratulated him on a move he had announced himself, then referenced a role he had already left. Nothing crashed. Nothing alerted. The system simply answered wrongly, confidently, in my name. Multiply that by every tool in your company and you have the quiet failure of enterprise AI: it isn't hallucination, it's disagreement between systems that were never taught the same vocabulary.
The pilot works, the agents are impressive, then someone asks a question that crosses two systems and the whole thing shrugs. Which company does this contact belong to after the acquisition? Who can approve a partnership at an account where the decision-maker moved last quarter? The stack shrugs, because a pile of integrations isn't a world model.
Tools give an agent hands. An ontology gives it a world model.
The vocabulary and the map
The distinction is older than the hype: Tom Gruber defined it in 1993, in the field's canonical reference. An ontology is an explicit specification of a conceptualization: the vocabulary, what things are, what evidence counts. The knowledge graph is the map you draw with it: the actual nodes and edges, this person, this company, this history. One is the rules, the other is the territory. The lineage runs back to the Semantic Web vision of 2001; the reasoning engines only arrived now, and the meaning layer is still what most teams are missing. In practice the vocabulary lives as a property graph (the Neo4j family) or RDF triples; the choice matters far less than having one at all.
Without them, every integration is a new dialect: your email tool says contacts, your CRM says leads, and your agent can't tell that three of those are the same human being. If you have a master data management team, slow down before calling any of this new. MDM has fought identity resolution across silos for two decades and your MDM people already own half the answer. What agents change is the exposure: the vocabulary used to sit in governance wikis nobody read at query time, and now a machine reasons over it live, every morning, and every answer walks your ontology in public.
What it looks like when it works
I run a small version of this for real. My agent layer maintains a living map of my professional market, and the core structure is one line: Person works_at Account, with a start date and a source on the edge. The production graph behind my systems carries 46 knowledge cards, 154 nodes, and 170 edges today. Small numbers, on purpose: every node earned its place through a source I could check. When someone changes jobs, that isn't a stale CRM row. It's one node changing state, and every recommendation that touches him updates with it.
The rules draw the map, and a query walks verified edges with its sources attached.
The demonstration is one query: 'who at Helios Retail can approve a data partnership?' The answer names the node it walked (Ananya Verma), the edge that proved employment (works_at Helios Retail, since March 2024), and the source that landed it (her announcement). Without the structure, the same question gets a confident paragraph with a footnoted feeling and no footnotes.
The field saw this coming. The practice didn't.
Gartner predicted back in 2021 that graph technologies would sit under 80 percent of data and analytics innovations by 2025, up from 10 percent in 2021, and analysts at MarketsandMarkets size the knowledge graph market at roughly 1.9 billion dollars in 2026, growing toward 9.88 billion by 2032. The honest read: adoption lagged the prediction, because most teams waiting for a platform to make graphs easy are still waiting. The ones that actually run them started smaller, with schemas they already had. Microsoft reached the same conclusion from the retrieval side: its GraphRAG research (arXiv:2404.16130) showed agents reason dramatically better over documents when a graph organizes the corpus first. And the strongest commercial proof has a name: Palantir sells its Foundry Ontology as the centerpiece of enterprise AI.
The objection worth engaging: just buy it
Because the ontology your agents reason over is your competitive memory. Palantir's version models your business inside their platform, on their terms, at their price. Owning the vocabulary, on infrastructure you already run, keeps your memory yours; the pattern is proven at the highest stakes, and the discipline to build the small version is what a mid-size team should take from it. The second objection comes from inside the building: we already resolve identities, the MDM team has run matching for years. True, and vector search plus entity matching still answers retrieval questions, not reasoning questions. An ontology doesn't replace your MDM. It gives your agents the map your MDM never built.
When you should NOT build one
A decision rule, because advocacy without an exit is selling. Don't build if you have one system of record and no cross-silo questions: a well-kept database already is your world model. Don't build if no agent will reason over the vocabulary; a graph nobody queries fails expensively. And don't build until you can name the questions that crossed systems and went unanswered: the ontology exists to answer those.
How to start, small and honest
Write down the 20 nouns your business actually runs on. Roles, accounts, commitments, signals.
Define 5 relations between them and what evidence creates or changes each: a job change needs a source.
Build the graph for one workflow only, agents maintain it under rules, corrections logged.
Require every answer to name its nodes. No citation, no answer.
Expand when the first workflow feels boring. Boring is the sound of a world model working.
Now the part the demos skip: the graph itself can rot. Somebody owns the vocabulary, or in eighteen months you have three words for customer and a fight. Evidence conflicts sometimes, so precedence gets written down before the first conflict arrives. Growth needs a stop condition: a graph that absorbs every noun anyone mentions is a junk drawer with a schema. Healthy graphs are run like products, with an owner, a changelog, and a reason to say no.
Grounding is the enterprise word for it. NIST's AI Risk Management Framework asks for exactly this under explainability and traceability. What fewer people say out loud: grounding is not a prompt trick. You can't ask a model to show its work across a sprawl of silos. The structure has to exist first. The model can only walk a path someone built.
Originally published at builder-singh.com
