The Semantic Control Plane for Enterprise AI.
Give your AI one authoritative understanding of your business. VISEON for Enterprise connects existing systems, definitions, relationships, business rules and evidence into one governed canonical context. People access it through VISEON Ask; compatible AI agents access it through MCP. Both resolve meaning against the same sources, subject to their permissions and context.
1
canonical graph of your organisation, defined once and referenced everywhere.
Edge
serving for fast, deterministic graph retrieval; measure end-to-end latency per use case.
0
access policies rewritten. Your existing permissions still decide who sees what.
8-week
target pilot for an agreed function or location, subject to scope and source access.
The problem
Your systems know your business. Does your AI know which to believe?
Your data platform has a semantic model. So do your warehouse, your BI tool, your metrics layer and your data catalog. Each is right within its own boundary, and each describes the same customers, products, contracts and policies slightly differently.
Your procedures, SLAs and approval chains mostly live in none of them. They sit in documents and wikis. Without an explicit source of semantic authority, each AI agent may reconcile these definitions differently. That can produce persuasive but inconsistent answers, outdated interpretations and decisions based on the wrong business rule.
Illustration: one entity, five definitions
What VISEON: Enterprise does about it
It establishes canonical entity definitions and identifiers, maps each system’s representation to those entities, and relates applicable rules and supporting evidence. Existing source data stays in its systems; VISEON maintains governed semantic metadata and references. Answers can expose their supporting entities and sources, or identify when the available evidence is insufficient.
The ontology
The canonical context behind your Semantic Control Plane
Structured and unstructured knowledge in one graph: the facts in your systems and the rules in your documents, tied to the same entities.
Entities
Your organisation, business units, products, services, customers, suppliers, sites, systems and people, each with one identifier.
Relationships
Who owns what, what depends on what, which contract covers which service, which system is the source for which figure.
Rules
Policies, SLA thresholds, approval requirements and semantic constraints represented for machine interpretation. Source systems still enforce permissions and authorisation.
Evidence and provenance
The documents, wikis and records behind each fact, linked to the entities they describe, so grounded answers can cite the evidence they actually use.
Expressed using open representations including Schema.org, JSON-LD and RDF-compatible identifiers, with MCP interfaces for compatible agents. Enterprise meaning is designed to be inspectable, reusable and portable; integrations and execution runtimes remain separate concerns.
Semantic authority
Semantic Contracts define what an agent can rely on.
A knowledge graph represents business meaning. A semantic contract makes that meaning operational: which definition applies, which source is authoritative, what evidence is required and what to do when the evidence is incomplete or conflicting.
Define authority
Agree canonical definitions, entity identities, source precedence, effective dates and the evidence required for a reliable answer.
Resolve meaning
Apply semantic constraints to route exact graph lookups, evidence retrieval and bounded explanations, rather than asking a language model to invent authority.
Respect the boundary
Flag unresolved or insufficient evidence. VISEON governs interpretation, not user authentication or access rights; the connected systems authorise data access and actions.
The Semantic Firewall
Think of the Semantic Firewall as the boundary between an agent’s question and the enterprise’s authoritative meaning. It evaluates semantic scope, source authority and evidence requirements; the Semantic Behaviour Tree supplies governed routing and execution. Neither substitutes for the security controls of the systems providing the data.
Your existing investments
Keep every platform. Give them one ontology.
Platform semantic models, metrics layers and catalogs each describe part of the business well. VISEON: Enterprise federates them: each becomes a source for, and an endpoint of, the canonical entity map.
Names are examples of common platforms, not integrations VISEON claims with each.
Portable by default
Open by design
An enterprise ontology should be an enduring organisational asset, not merely a configuration inside one application. Definitions need to remain understandable and reusable as tools, models and vendors change.
VISEON for Enterprise represents canonical meaning using open standards, making definitions inspectable and reusable beyond any one consuming AI application. And because it is built from the same vocabulary the web uses, the graph that governs your internal agents can also publish, deliberately and selectively, to your website, AI search and agentic commerce.
Designed for change
Your AI Operating System needs an authoritative understanding of your enterprise.
AI operating systems coordinate agents, analytical models, decisions and workflows. Those components need a common understanding of the business. VISEON provides canonical semantic context for them to consume—not a replacement for operational execution, analytics or human decision rights.
As your LLMs, agent frameworks and systems evolve, your organisation can maintain consistent entity definitions, relationships and evidence boundaries. Source systems continue to supply data, calculations, permissions and authorised actions.
Example: Can we approve this supplier contract?
- Resolve the canonical supplier, contract and responsible business unit.
- Retrieve the applicable procurement policy, effective date and financial threshold.
- Identify the required approval chain and reference the supporting sources.
- Return a grounded explanation or identify missing evidence; existing procurement systems and authorised people decide and execute.
One graph, two interfaces
VISEON Ask for people. MCP for agents.
VISEON Ask is the human interface to the graph: plain-English questions, answered from governed data. Compatible AI agents, whether in Claude, ChatGPT, Copilot or your own applications, can query its MCP interface. Both interfaces use the same canonical definitions and evidence; the answer remains subject to the agent’s context and the source systems’ permissions.
- Who approves a supplier contract over £250k?
- Which services does this SLA cover?
- What is our definition of an active customer?
- Which systems hold this product’s price?
- Exact answers first. A Semantic Behaviour Tree routes each question: a direct graph answer where one exists, evidence retrieval where it does not, and a language model only to phrase what the evidence supports.
- Provenance with every answer. Grounded responses expose supporting entities and sources, and identify missing or insufficient evidence.
- Your permissions, unchanged. VISEON is authentication-agnostic. Connected source systems and services retain responsibility for enforcing RBAC, ABAC and other access controls.
- Answers from the edge. The graph is served at the edge, with low-latency exact retrieval. End-to-end response time depends on the query, source access, network and model use.
- Context that carries over. A stateful conversation keeps the subject and the evidence already established, so follow-up questions are not fresh guesses.
Inside and outside
The graph that runs your agents can also represent you to the world.
Internal ontologies usually stop at the firewall, and public structured data is usually maintained separately, by a different team, from different definitions. VISEON uses one vocabulary for both.
You choose what is published. The public part of the graph describes your organisation, products and services to AI search engines and to other companies’ agents; the private part governs your own. Where they overlap, they are a shared canonical identity, with private and public publication boundaries.
Read: the enterprise semantic layer, internal and external context
Private
Operations, policies, SLAs and approval chains, served to your own people and agents over MCP, inside your permissions.
Public
Organisation, products, services and expertise, published as structured data for discovery, discussion and agentic commerce.
Proof, in public
This website runs on the same infrastructure.
VISEON.IO is built as a knowledge graph first: every page, product, service, person, glossary term and FAQ is an entity with one identifier. That graph is served to people through VISEON Ask and to agents through MCP and NLWeb, exactly as it would be inside your organisation.
Try it. Ask it who founded Differentia Consulting, or whether VISEON Data Assurance moves your data, and look at where the answer comes from.
150+
pages, each with its own governed graph.
145
glossary terms, each a defined entity.
75
questions, each with its own page and answer.
0
unresolved references across the site.
The data underneath
An ontology is only as trustworthy as the data it points to.
VISEON Data Assurance scores every row of the data behind the graph, where it lives, against the nine DAMA quality dimensions. These quality signals help an agent assess the fitness of the underlying data; answer trust also depends on source authority, recency, evidence and the semantic contract.
Deployment
One function first: an eight-week pilot target
Begin with an agreed use case, accessible sources and measurable acceptance tests; then extend the same canonical context across functions.
Audit
Weeks 1–2
Map the entities, rules, approval chains and sources for one pilot function, and where their definitions conflict.
Model
Weeks 3–4
Establish canonical definitions and identifiers, encode the rules, and document semantic boundaries and the source systems responsible for permissions.
Connect
Weeks 5–8
Deploy the MCP endpoint and VISEON Ask, connect the first agents, and test answers against known cases.
Govern
Ongoing
Detect drift as systems and procedures change, and keep the graph aligned with how the business actually works.
Questions
What architects ask first
How is this different from a data catalog or a semantic layer?
A catalog inventories data assets; a semantic layer defines metrics for analytics. VISEON: Enterprise models the business itself: its entities, their relationships, the rules that govern them and the documents that explain them. Catalogs and semantic layers become sources for that model, not replacements for it.
We already have an ontology in our data platform. Why add another?
You would not be adding a competing one. A platform’s ontology describes the data inside that platform. VISEON federates it with the definitions in your other systems and documents, so there is one canonical identifier per entity across all of them. The platform ontology keeps working and is linked, not replaced.
How does VISEON for Enterprise compare with Palantir?
Both model the enterprise as an ontology across structured and unstructured data, and both can work with data where it lives. VISEON emphasises canonical definitions expressed in open representations (Schema.org, JSON-LD and RDF-compatible identifiers), independent reuse across agent interfaces and selective publication to external AI discovery. Buyers should compare not just ontology formats but also rule portability, execution, integration depth and operational governance.
Does our data move?
No. Operational source data normally stays in its existing systems. VISEON holds or references canonical definitions, relationships, rules and evidence metadata. Connected systems remain responsible for authorising access to their data.
What is the difference between VISEON Ask and the VISEON MCP endpoint?
VISEON Ask is MCP for people. VISEON Ask is the common interface: plain English, links to the sources behind each answer, and context kept for follow-up questions, whichever product it sits in front of. Behind it, a worker tailored to the need, such as the VISEON for Web MCP or the Enterprise Ask MCP, reads the governed knowledge graph, and that worker’s MCP endpoint lets compatible AI assistants and agents call the tools directly. A person and an AI agent therefore resolve meaning against the same governed definitions and provenance. Relevant context and source-system access permissions may change what either can see and the answer they receive.
Which standards is it built on?
Schema.org and JSON-LD for the entities and relationships, RDF-compatible identifiers, the Model Context Protocol for agent access, and NLWeb for natural-language access to published content. Metric definitions can align with the Open Semantic Interchange specification.
Give every AI agent a governed understanding of your business
Start with an architecture review of one function: which definitions require authority, what your agents must be able to substantiate, and what a scoped eight-week pilot could demonstrate.
Or email [email protected] · Built by Differentia Consulting, enterprise data specialists since 2002.

