Context layer
A context layer is the governed layer that makes your existing data understandable and usable by AI at runtime. It's not where you move your data. Three ideas define how it works:
- Start with one domain, not the whole catalog. That's the shortest path to a working system.
- MCP is the delivery mechanism, not the context itself. The context is the metadata, lineage, glossary, and governance that Atlan exposes through that interface.
- Context improves through use. Every failed agent answer shows you a missing definition, relationship, or governance signal to fix at the source.
At enterprise scale
The enterprise context layer sits between two layers most data platforms already have: a data layer (warehouses, lakes, BI tools) and an AI layer (models, agents, copilots). The gap between them is decision-grade context—definitions, lineage, policy, and ownership—that doesn't ship through data pipelines and isn't encoded in model weights. Without it, agents produce confident answers grounded in incomplete meaning.
At enterprise scale, three properties separate this layer from a single-team build:
- Multi-domain federation. Each domain owns its definitions but contributes to one graph. Conflicts get arbitrated, not duplicated.
- Compliance overlay. Access controls, versioned certification, and audit logs support enterprise audit requirements.
- Compounding learning. Teams evaluate, correct, and redeploy context so the shared repositories improve over time.
Single-team vs. enterprise
| Dimension | Single-team (one domain) | Enterprise (multi-domain) |
|---|---|---|
| Scope | One domain, one team | Multiple domains, federated ownership |
| Asset scale | Hundreds to low thousands | Large, multi-domain estate |
| Glossary scale | Tens of terms | Hundreds to thousands of terms |
| Governance | Lightweight RBAC | Domain-federated, audit-trailed |
| Compliance overlay | Optional | Required (for example, GDPR, SOX, CCPA) |
| Owner | Data or AI engineer | CDO, CIO, or platform lead |
| Time to first production agent | Days to weeks | Plan for one priority domain first |
| Estate-wide rollout | Not applicable | Multi-quarter program |
| Failure mode | Definitions diverge across agents | Definitions drift across domains, compliance gaps |