Home / Context Model

Enterprise Context Model

Five context layers — four core plus Governance cutting across all of them. This is the map of what the Enterprise Brain connects: every kind of knowledge your organization holds, and where it lives today.

5 layers 51 topics 100+ source systems

Principle: Category = nature of content, not the source system.

The model at a glance

Four kinds of enterprise knowledge, one governance layer cutting across them all — feeding a single governed intelligence layer. Click any layer to explore its full contents below.

Knowledge at rest
Knowledge in motion
{{ col.short }}
{{ chip }}
Governance — cuts across all four CROSS-CUTTING
{{ chip }}
▼
Enterprise Brain
▼
Governed answers & decisions

From your systems to answers you can sign off on

The Brain connects your sources, builds governed knowledge from them, and serves it to any AI — search, copilots, or autonomous agents.

01
Connect
Point the Brain at your systems — databases, warehouses, documents, code, policies. It runs inside your environment.
→
02
Build
Pipelines ingest and transform each source into governed knowledge — what things mean, how they relate, the rules that apply.
→
03
Govern
Every definition is versioned, owned, and access-controlled. Each answer carries its evidence and a tamper-evident record.
→
04
Use
RAG and agents answer questions and run workflows over the same governed knowledge — with a full audit trail every time.

Structured data, documents, code, and live systems — one governed layer, built once and used everywhere.

BUILT FOR REGULATED ENVIRONMENTS

Your data never leaves your environment

The entire Brain runs inside your trust boundary — your cloud account, your datacenter, or fully air-gapped. Ingestion, transformation, storage, and model inference all happen within your walls. Nothing is sent to an outside service, and no model provider ever sees your data.

The knowledge graph holds meaning and pointers — your definitions, relationships, and the map of where everything lives. Your bulk records aren't duplicated into it; they're queried where they already sit, under your own access controls.

Inside your boundary
VPC, on-prem, or air-gapped — one deployment
Self-hosted inference
Your GPUs run the models; no external API
Not copied into the graph
Records stay in your warehouse and lake
Access-controlled at query time
Your existing policies gate every read

AutoSemantica connects your internal systems inside one enterprise — it does not move data across organizational or legal boundaries.

Inside each layer

One layer at a time — every category, topic, and the systems where that knowledge lives today.

{{ tree.short }}
{{ tree.topicsLabel }} {{ tree.sourcesLabel }}
{{ cat.name }}
{{ topic.name }}
{{ topic.desc }}
{{ src.name }}

The model: Domain, Data, Technical = knowledge at rest. Operational = knowledge in motion. Governance = the control plane that cuts across all four. Real agent work never stays within one layer — every meaningful task pulls context from 4–5 layers, and the interactions happen at the component level, not the category level.

See how these components combine in real situations

Explore the Scenario Library →