II.
Page reference
Reading · 2 minpage:index
Agentic AI Atlas Wiki reference
Welcome to the readable side of the Atlas graph. This wiki is the easiest way to move between narrative docs, generated reference pages, and the underlying graph records without having to know the schema first.
Agentic AI Atlas Wiki
Welcome to the readable side of the Atlas graph. This wiki is the easiest way to move between narrative docs, generated reference pages, and the underlying graph records without having to know the schema first.
Start here
- New to Atlas? Open `agent-generate/universal-agentic-stack` for the big-picture map.
- Looking for process and governance? Start at `process`.
- Checking delivery, testing, or release discipline? Go to `qa`.
- Want to understand how pages are produced? Open `generators`.
- Want graph-backed visual templates? Open `views`.
- Need the implementation details of the wiki itself? See `00-wiki-architecture.md` and `01-derivation-mapping.md`.
Ways to browse
| Path | When to use it |
|---|---|
| `/wiki` | Stay in prose and follow section hubs. |
| `/search` | Jump directly to a page, node, or topic by name. |
| Node ledgers | Open any documented record to inspect attributes and edges directly. |
| `/graph` | Move visually through neighborhoods when you do not know the exact node yet. |
Main sections
| Section | What it contains |
|---|---|
| `process` | The ontology-driven workflow, debt loop, cascade rule, governance, and tracked gaps. |
| `qa` | Quality gates, CI/CD, coverage, evidence freshness, and delivery policy. |
| `generators` | The derivation layer that turns graph data into docs, types, diagrams, and other artifacts. |
| `agent-generate` | Generated references and landscape maps derived from graph data. |
| `views` | Reusable graph-backed UI templates such as the Service Tower projection. |
| `00-wiki-architecture.md` | How the wiki is structured, navigated, and published. |
| `01-derivation-mapping.md` | Which graph queries and generators are responsible for which page types. |
What this wiki is for
- Give readers a welcoming way into the graph before they drop into raw node ledgers.
- Keep section hubs, reference pages, and graph records linked tightly enough that navigation stays easy.
- Make it obvious where to continue next from any page.
- Preserve the rule that graph-backed truth lives in the catalog, while the wiki provides the reading experience around it.