II.
Page reference
Reading · 1 minpage:process
Process and Governance reference
This section explains how the Atlas graph is maintained, reviewed, corrected, and carried through downstream docs and tooling. Read it when you want the operating model behind the catalog rather than a single domain fact.
Process and Governance
This section explains how the Atlas graph is maintained, reviewed, corrected, and carried through downstream docs and tooling. Read it when you want the operating model behind the catalog rather than a single domain fact.
Start with these pages
| Page | Why it matters |
|---|---|
| `00-process-design.md` | The master design for the ontology-driven workflow. |
| `01-debt-loop.md` | The recurring loop for surfacing and retiring graph debt. |
| `02-cascade-rule.md` | The rule that prevents half-fixes from stopping at one projection layer. |
| `03-governance.md` | Owners, approval boundaries, and arbitration paths. |
| `gaps` | The live gap tracker and the readable form of current issues. |
When to read this section
- You need to understand how a graph correction is supposed to propagate.
- You are deciding whether a problem belongs to schema, graph data, docs, generators, or QA.
- You want to understand how gaps are tracked and closed.
- You are onboarding to Atlas maintenance work.