Run your first check
Install Enola, record a baseline, make one change, and inspect the result.
01 · Start
New to Enola
Learn the terms
Snapshots, facts, findings, constraints, receipts, and partial verdicts.
Understand the pipeline
How source files become a graph and how two snapshots produce a check result.
Understand the graph
What is in a snapshot, how repositories are linked, and which files are a stable contract.
02 · Use
Four ways to use it
All four read the same graph.
On your own
Pin the graph, change the code or pull, and see what came in. No agent and no AI needed.
In CI
The same check on every pull request with enola-action: annotations on the lines that introduced a finding, and the architecture delta in the job summary.
With your coding agent
Over MCP, the agent asks what depends on the code before it edits. Hooks run the check when it stops. Setup is in the quickstart.
As a foundation
A snapshot is plain files in a documented format. Run Enola as a subprocess and load them into your own tools.
03 · Tasks
Find the guide for your task
Explore and plan
Orient in a codebase, trace dependencies, and estimate change impact.
Interpret a result
Read status, evidence, exit codes, receipts, coverage, and JSON.
Check a change
Baselines, policy categories, hooks, target scope, and spillover.
Run Enola in CI
Pull-request checks, failure policy, reproducibility, and annotations.
Declare architecture intent
State expected services, seams, layers, and external dependencies.
Enforce constraints
Define components, rules, modes, exemptions, and recipes.
Configure a repository
Set repository scope, ignores, extractors, providers, and output.
Analyze multiple repositories
Compose repositories and inspect resolved cross-repository edges.
04 · Help and reference
Resolve a problem or look up behavior
Troubleshooting
Installation, MCP, snapshot, comparison, hook, and constraint problems.
MCP and CLI reference
MCP tool catalogue, shell commands, and links to complete contracts.
Language coverage
Detected inputs, extractor capabilities, and static-analysis limits.
Detailed CLI, schema, integration, provider, and architecture references are grouped under Advanced reference in the documentation menu and open on GitHub.