Enterprise Knowledge gives AI business understanding — not just more information.
It is an enabling pillar of AI Fabrix. Enterprise Knowledge supplies business context; Operational Trust applies boundaries; Role Assistants perform governed work; Evidence Fabrix proves the outcome.
Describe the business once. Reuse entities, metadata, and relationships across Role Assistants. Existing applications remain the systems of record.
Enterprise Knowledge is not only a data catalog or search index. It is the business model AI uses to understand what exists, how it connects, what it means, who may use it, and what work can be requested.
Business Context Map
AI Fabrix automatically creates a Business Context Map from the approved business entities and relationships defined across connected enterprise systems.
The Business Context Map is the governed, reusable map of how business information connects across systems. A Customer can connect to Contacts, Deals, Contracts, Cases, Projects and Documents; an Employee can connect to a Manager, Team, Role and Assignments. Existing systems remain authoritative for their records.
Without this shared map, each AI solution has to reconstruct the same business navigation through orchestration, workflows, prompts, tool calls or model reasoning. With it, Role Assistants can start from reusable business context instead of rediscovering how the business fits together for every task.
Operational Trust still determines which connected information and capabilities the active person and Business Role may use. Connected does not mean permitted.
The first AI use case builds business context. The next one reuses it.
Give AI understanding — not only retrieval
Enterprise information does not have equal meaning or authority. A regulation is different from a company policy. A current agreement is different from an obsolete document. Customer, contract, project, and product information may be related even when they live in different systems.
Traditional RAG can retrieve semantically similar content. That alone does not tell AI which business context applies, which source is authoritative, which version is current, or which information the user may receive.
Smart RAG with business metadata
Smart RAG combines semantic relevance, business metadata, and permission-aware filtering.
Metadata can describe the active customer, contract, project, or case; source authority; relationships; classification; ownership; permissions; version and validity. Role Assistants use this metadata to narrow retrieval to the active role and outcome before content is supplied to AI.
At retrieval time, Operational Trust limits which Enterprise Knowledge capabilities and content are available for the active user and case. Relevant is not the same as permitted — see Dimensions and protection.
Smart RAG is one Enterprise Knowledge capability. It complements structured business data and governed operations; it does not replace them. Practice detail: Records search and AI context.
A zero or low-confidence result has two distinct possible causes — policy/scope exclusion, or the business data itself being incomplete (honest completeness) — see Records search and AI context for both.
Viewpoints: certified business pictures
Some work needs a predefined business picture rather than more documents or a list of individual records.
A Viewpoint gives a Role Assistant a certified, read-only perspective — for example revenue by customer, pipeline by stage, or actual cost by cost centre. It is calculated when used under Operational Trust, while systems of record remain authoritative. It is not a second reporting warehouse.
Smart RAG retrieves permitted content; a Viewpoint provides an approved business picture for the current decision. See Viewpoints and joined business context.
Enterprise Knowledge helps AI retrieve the right information — and understand why it applies.
What Enterprise Knowledge owns (and does not)
| Concern | Owner |
|---|---|
| Business meaning, metadata, relationships, Business Context Map, governed search context, sync freshness for connected systems | Enterprise Knowledge |
| Current authorized business facts (“what is true now”) | Enterprise Reality |
| Certified reusable business proof | Evidence Fabrix |
| Policy, identity, dimensions, certification gates, capability admission | Operational Trust |
| Decision Engine orchestration and continuation | Architecture / Runtime |
Source systems remain authoritative for live records. Enterprise Knowledge organizes and exposes governed business context from certified integrations — it does not replace Reality, certify Evidence, or execute Role Assistant work.
Organization documents and uploads usually enter as document storage / Knowledge first. Approving document metadata for search is not the same as certifying Evidence. See Evidence Fabrix and Document approval and governance.
Why it matters
AI cannot perform useful enterprise work when it sees disconnected system objects. Traditional platforms expose CRM accounts, file paths, and ticket IDs. AI Fabrix creates reusable business meaning through the Business Context Map:
Customer
├── contacts
├── deals
├── contracts
├── documents
├── support cases
├── owners
└── available work
That is the difference between connecting systems and giving AI business understanding. Prefer a minimal set of business entities and metadata — quality over quantity — then extend when the business needs a new entity. See Business entities and resource types.
Business metadata
Business metadata explains what data means in business language — not only how a vendor stores it. Resource types (customer, contract, document, task) define the business entity before system structure. Detail: Business metadata.
Cross-system relationships
Cross-system relationships link business entities across systems so no single application has to hold the full story. AI Fabrix uses approved relationships to create the reusable Business Context Map. Detail: Cross-system relationships.
How it works
Systems of record (authoritative)
↓
Business metadata and resource types
↓
Cross-system relationships
↓
Business Context Map (Enterprise Knowledge)
↓
Smart RAG / Viewpoints / governed capabilities
↓
Operational Trust at use (permitted for this person and case)
Datasources sync external records into governed business entities. Dimensions and protection from Operational Trust apply so context stays within policy. Uncertified or out-of-scope data does not become assistant context.
When several Connected Systems share one business object, write and list authority declares preferred mutations and authoritative lists from metadata — without custom multi-write glue.
Governed capabilities from business context
Enterprise Knowledge defines what AI can request through governed business capabilities — not raw API calls. AI requests the capability; AI Fabrix handles system-specific execution under Operational Trust. Admission is fail-closed. See Governed capabilities.
The AI-facing contract speaks in business operations — customer.search, deal.reviewPipeline — never in vendor endpoint names, raw table names, or test/internal field labels. Business metadata is what makes that translation possible: see Business metadata. This is the same governed-content distinction described in Business meaning as governed content.
Enterprise MCP
Enterprise MCP is the governed AI interface to Enterprise Knowledge — business language, not raw vendor APIs. It is compiled after publish and certification — not a separate product beside Role Assistants. Detail: Enterprise MCP.
Example
A customer review may require CRM accounts and deals, signed contracts, open support cases, project documents, and owner information. The Business Context Map already describes how those approved entities relate. Enterprise Knowledge resolves that reusable business context; Smart RAG and Viewpoints supply the right shape of knowledge; Operational Trust keeps it within role and dimension scope before a Role Assistant acts.
Business value
Enterprise Knowledge helps organisations stop rebuilding the same business context and navigation inside every AI solution, reduce unnecessary runtime discovery across tools, reuse definitions and relationships across Role Assistants, and keep systems of record authoritative.
One-line summary
Enterprise Knowledge creates the reusable Business Context Map AI uses to understand how the business connects — under Operational Trust.