What's next · substrate · opening soon

The eight-substrate graph
Sentinel runs on.

Atlas indexes your codebase the way the people who wrote it would explain it: not as files, but as eight substrates joined by eight typed edges, snapshot-versioned, and kept current by a chokidar daemon. Sentinel uses Atlas as its evidence floor. We're opening Atlas as a standalone surface next.

Get the Atlas beta → Read the architecture
atlas-server.service · live snapshot #186
Nodes35,800
Edges39,800
Substrates8
Edge types8
Snapshots186
Repos watched3
Changes 24h678
Healthzactive
git 09b7b959 · chokidar · ~/.aria/atlas/atlas-server.sock
Eight substrates · one schema

Atlas does not have one model of your codebase. It has eight.

Each substrate runs its own extractor and produces nodes and edges into the same SQLite-backed graph (src/schema.sql). Cross-substrate queries are first-class. A finding in behavioral can join to its file in structural, the doctrine it violated in doctrinal, and the kernel compilation that handled it in cognitive. That join is what scanners cannot do.

01 · structural
Structural
Files, symbols, imports, exports, classes, functions, type declarations.
nodes32,560 edges6,810
02 · runtime
Runtime
Deploy topology — services, pods, statefulsets, daemons, systemd units, networking surface.
nodes285 edges12,185
03 · doctrinal
Doctrinal
Committed rules: doctrine memos, CLAUDE.md, MEMORY.md, hook guides, owner directives.
nodes811 edges3,607
04 · historical
Historical
Git commits, file evolution, who-changed-what, decay signals.
nodes500 edges2,724
05 · behavioral
Behavioral
What the system actually did at runtime — endpoint calls, tool invocations, gate fires.
nodes703 edges3,838
06 · cognitive
Cognitive
Loaded skills, cognition emissions, kernel compilations, Tadabbur and Qiyas runs.
nodes197 edges119
07 · conversational
Conversational
Owner turns, agent responses, claim/evidence pairs, doctrine triggers.
nodes318 edges3,882
08 · hive-state
Hive-state
Cross-session coordination — file leases, write claims, session lifecycle, sibling overlap.
nodes374 edges19
Eight edge relations

Typed edges. Cross-substrate joins.

Substrates are nothing without the edges between them. Eight relations tie the graph together. Counts below are live as of snapshot #186.

IMPLEMENTS
15,611 edges
MENTIONS
10,696 edges
DELEGATES_TO
6,883 edges
EVOLVED_FROM
2,485 edges
BOUND_BY
1,516 edges
BEHAVIORALLY_COUPLED
862 edges
DEPLOYED_AS
641 edges
GOVERNS
119 edges
The dossier query

A scanner sees a line.
Atlas hands you the blast radius.

Before any non-trivial edit, an agent calls atlas_dossier <target>.

What comes back is a pre-edit dossier for any symbol, file, doctrine memo, or Linear key: what it does, why it exists, what it preserves, who calls it, what it deploys as, what governs it, what gates protect it.

The agent then writes its code anchored to that dossier — and the gate at edit-time refuses if the cognition block doesn't cite dossier evidence. That is how Atlas turns from a passive graph into an active anti-drift mechanism.

Typical scanner
"eval() at line 32 — possibly unsafe."

Sentinel finding sealed against Atlas
Four linked findings · one composite · governing doctrine · deploying runtime · the session that last touched the file · the dossier of every consumer · the verification predicate that proves the fix.
finding · sealed against atlas atlas_dossier(contributions.js) 
finding_id:                2607
source:                    sentinel-composite
kind:                      compound_app_risk

evidence_anchor:           atlas_node:codebase/app/routes/contributions.js:32
atlas_dossier_url:         socket://atlas/dossier?target=app/routes/contributions.js
kernel_compilation_hash:   sha256:48566fb15ca5…

linked_findings: [
  dangerous_dynamic_execution,
  possible_command_injection,
  security_todo,
  wide_open_cors,
]

governing_doctrine:        codebase-kernel-review
runtime_deployment:        emr-realtime
last_session_to_touch:     aba649c5-fea  (claude-code, 2026-05-17T21:30Z)
MCP surface

Four queries. One Unix socket. One MCP server.

Atlas exposes four queries over the MCP server (bin/atlas-mcp), the Unix-socket HTTP API at ~/.aria/atlas/atlas-server.sock, and the CLI (node bin/atlas).

atlas_healthz
Daemon liveness, schema version, last snapshot id and status.
atlas_session_context
Compact (≤2KB) per-session orientation — freshness, active doctrines, recently-touched regions, live gate hooks, top Sentinel findings.
atlas_architecture
Top-down map — substrate-by-substrate counts, most-connected code units, most-mentioned doctrines, active gate hooks.
atlas_dossier <t>
Pre-edit blast radius for any symbol, file, doctrine memo, or Linear key. The query agents call before they touch anything.
Beta access · opening next

Get the Atlas beta when it ships.

Sentinel is shipping first. Atlas is opening next — as a standalone surface, usable by any tool that wants its findings sealed against a live, queryable, snapshot-versioned graph of code, runtime, doctrine, and history. One email, no marketing list, no follow-up sequence.