Atlas Documentation

Status: Proof of Concept (Alpha). APIs may change.

Atlas is a semantic registry for software architecture: describe your system's components, functions, and relationships as compound identities (sets of semantic aspects), then query, validate, and visualize your architecture as a single queryable graph.

Start here

Doc	What
Getting Started	5-minute tutorial
Core Concepts	Compound identities, tiers, data flow
API Reference	Function reference
Examples	Annotated example registries

Guides

Doc	What
Authoring Guide	Building entity definitions interactively
Sources	Registry in EDN files, plain defns with ^{:atlas.source/id …}, bb source, Emacs hover (experimental)
Compound-ID Refactoring	Reviewing/improving compound-ids to avoid drift
Dependency Traversal	Forward/reverse recursive dependency analysis
Semantic Aggregation	Rolling aspects up the dependency graph
Declared Dispatch	The Atlas execution pattern
Source Tracker	Correlating registry entities with git history
Upgrade Check	What a new atlas version changes for your project: registry and tool answers, before and after (experimental)

Semantic-Driven Development

Doc	What
Semantic-Driven Development	The SDD vision
LLM-IDE Guide	For LLMs: the registry model and atlas.llm-ide tools
Lens Design	The lens abstraction

Tooling

Doc	What
Emacs Integration	IDE support via CIDER
Keybindings	Emacs keybindings reference
Visual Explorer	Browser-based graph UI (v1/v2)
UI v3	SSE-driven semantic browser (experimental)
atlas-dev module	Dev-tooling library
Overarch Adapter	Export to C4/UML/GraphViz diagrams (experimental)
YAML-LD / JSON-LD Adapter	Export to W3C linked data / RDF (experimental)

Modules

Atlas is a monorepo of independently-publishable libraries:

• core/ — atlas — the production library (registry, query, invariants, datalog)
• dev-tools/ — atlas-dev — source tracking and dev tooling
• ui/ — atlas-ui — the browser-based visual explorer
• emacs/ — CIDER-driven IDE integration

The cloud service (team sync, versioning, branches) and its docs live in a separate repo.

---

Internal design notes and working documents live in internal/ (not part of the published documentation set).