Skip to content
Atlas docs

Atlas docs

Ask a question, read the evidence, track it as a case. When the answer is code, Studio builds the plan, emits the scaffolds, and runs the gates.
Run your first investigation How Atlas reasons
Atlas docs · v0.1

You probably arrived here with one of four jobs. The sidebar mirrors them; pick the one closest to yours.

Investigate a conversion
Natural-language queries against the Keystone knowledge graph, with full evidence on every answer.
Track work as a case
Cases own the state: pinned findings, corpus freshness, release diffs, governance scorecard — one URL per migration thread.
Build in Studio
Classify a task, generate CDS and ABAP scaffolds, read gate results — five Studio stations after task capture, six stages end-to-end.
Understand a decision
Explanation pages for the questions that start with why — evidence tiers, plan lifecycle, the VDM, the gate model.

What Atlas actually does

Section titled “What Atlas actually does”
The Studio pipeline Task one-sentence description Classify analytics · RAP extension · migration Plan dependency graph + gates Generate CDS · ABAP metadata Validate gate passes tests Transport TR + deploy Six stages. Every transition is a gate. No gate is bypassable.
Studio pipeline — Atlas turns a task description into a transported CDS view through six gated stages.

A task description enters on the left. Six gated stages later, an annotated CDS bundle is ready for the customer’s transport landscape; once the release manager moves the TR through, Atlas records the activation and advances the plan to Transported. Every stage leaves evidence behind, which is the point — the trail that comes out the right side is only trustworthy if every step is reviewable.

The docs are organized in the four Diátaxis modes, strictly separated. Tutorials teach; how-to guides solve specific problems; reference is factual; explanation answers why. If a page feels like it belongs in two modes, it is probably doing its job badly.