Skip to content

Concepts and Architecture

This section explains the models and constraints used across Atlas task guides, feature guides, and reference material. Use it to understand why an entity, permission, or plugin behaves as it does.

Who this section is for

This section is for readers who need the terminology and models behind Atlas workflows. It covers:

  • how Atlas names and relates catalog entities;
  • how entity provenance and lifecycle states affect allowed changes;
  • how authentication, identity, ownership, and permissions connect; and
  • which runtime and plugin boundaries Atlas preserves.

Glossary

The Domain glossary defines Entity Kind, Facet, Contribution, Capability, Extension Point, Distribution, and other terms used throughout the site.

Reading order

  1. Domain glossary: shared vocabulary.
  2. Entity model: kinds, metadata, specs, and relationships.
  3. Entity references: reference identity and resolution.
  4. Life of an entity: provenance, claims, availability, removal, revival, and purge.
  5. Auth and identity, then Permissions: how a signed-in principal connects to ownership and policy evaluation.
  6. System shape, then Architectural principles: runtime composition, trust, and isolation boundaries.

Section boundary

Concept pages explain models. For procedures, see Using Atlas, Operating Atlas, and Plugin Development. Reference lists exact fields, identifiers, and API contracts.