> ## Documentation Index
> Fetch the complete documentation index at: https://developers.klarity.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Intelligence layers

> Klarity organizes operational intelligence into two layers. The MCP gives you query access to both.

Klarity organizes operational intelligence into two layers — **Process Index (aka Process Context Graph)** and **Artifacts**. Each maps to a distinct set of MCP tools and is best for a different kind of question.

| Layer                                                                | What it contains                                                                     | Example questions                                                                    |
| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ |
| [Process Index](/concepts/process-index) (aka Process Context Graph) | Hierarchy, versions, steps, policies, dependencies, observations, activity timelines | "How does our vendor onboarding work?" "What changed in our close cycle last month?" |
| [Artifacts](/concepts/artifacts)                                     | Documents, videos, screenshots, session timelines                                    | "Find the latest SOX compliance checklist."                                          |

## How they fit together

The Process Index is Klarity's context graph — the primary query surface for almost every question. It's where processes, their versions, their dependencies, and the observations captured against them live, all linked into one navigable structure. Artifacts are the underlying source documents and recordings the workspace has captured.

The most useful answers chain across both layers in a single session:

> "Give me the full picture on month-end close — process hierarchy, recent observations, and the most relevant docs."

That single prompt fans out into a process search, hierarchy traversal, observation reads, activity timeline drills, and artifact lookups. Ten-plus tool calls, orchestrated automatically, answered with grounded evidence.

## When to start at each layer

* **Start at the Process Index** when the user names a workflow, team, system, or business outcome — this is the default for almost every question.
* **Start at Artifacts** when the user names a document, screenshot, or recording.

The [Tool reference overview](/tools/overview) maps each entry path to the specific tools that begin the chain.