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

# Atlas primitives

> The small set of concepts behind Atlas decision intelligence.

Atlas is organized around primitives rather than isolated features. Each primitive supplies a stable contract that products, analytics, integrations, and agents can share.

| Primitive | Responsibility |
| - | - |
| Objects | Durable records for operational entities and Atlas artifacts |
| Identities | External and alternate keys that resolve to an object |
| Relationships | Typed connections between objects |
| Data surfaces | Governed access to operational records and projections |
| Metrics | Reusable measurements with defined grain and lineage |
| Analyses | Decision-oriented interpretation of metrics and evidence |
| Lists | Governed collections of object records |
| Cycles | Operating cadence, stages, and transition history |
| Semantic layer | Shared definitions for fields, metrics, filters, and lineage |
| Decision layer | Governed practices, policies, rules, guidance, and outcomes |
| Planner, execution, and audit | Governed movement from intent to accountable action |

## From signal to action

Data enters Atlas through governed data surfaces. Atlas resolves records to objects, applies semantic meaning, evaluates the relevant operating context, and makes the result available to people, workflows, and agents.

This separation matters: a provider payload can change without changing the business identity of an object, and a workflow can change without rewriting the object it contains.

> **[Objects](https://docs.aioncx.com/concepts/objects.md)**
>
> Understand the canonical record spine.

> **[Semantic layer](https://docs.aioncx.com/concepts/semantic-layer.md)**
>
> See how Atlas gives operational data shared meaning.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.