Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
i.1Wiki
Agentic AI Atlas · Process and Governance
processa5c.ai
Search the atlas/
Wiki · section map

Trail and section pages

I.In this sectionpp. 1 - 1
v6 Ontology-Driven Development Process — Master DesignDebt-Driven LoopCascade RuleGovernanceGap Tracker
I.
Wiki article

process

Reading · 1 min

Process and Governance guide

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.

Page nodewiki/process/README.mdSection pages · 5Documents · 0

Pages in this section

Start with the section hub, then move sideways into adjacent pages when you need more detail.

v6 Ontology-Driven Development Process — Master Design

Page

The agent-catalog graph is the single source of truth for the v6 domain. Every other artifact — node-kind specs, validation rules, generated documentation, the wiki, generator code, the SDK, and user-facing interfaces — is a projection of the graph, never authored independently.

wiki/process/00-process-design.md

Debt-Driven Loop

Page

The debt loop is the engine that keeps the v6 ecosystem in alignment after the forward phases (1–5) have laid down the initial artifacts. It detects, prioritizes, and closes drift between what is true in the world and what every projection of the graph claims is true. Levels are ordered by priority — lower level numbers always win — because a finding at Level N invalidates every derivation at Levels N+1..7.

wiki/process/01-debt-loop.md

Cascade Rule

Page

When closing a gap at Level N, propagate the change down through Levels N+1..7 BEFORE picking up generic gaps at higher levels. Track each propagated change as an entry in the gap node's propagationStatus field; the gap is not closed until every applicable level reads done or not-applicable (with a one-line reason).

wiki/process/02-cascade-rule.md

Governance

Page

Every phase and every debt-loop level has a named owner. Owners are represented as Authority nodes in the graph and referenced from the owner field on Gap nodes (and on Claim, EvidenceSource per the evidence model).

wiki/process/03-governance.md

Gap Tracker

Page

Human-readable form of every tracked gap. Each file in this directory mirrors a Gap node in the graph (see graph/02-node-kinds/catalog-meta.md, NodeKind Gap).

wiki/process/gaps/README.md

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

PageWhy 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.

Trail

Wiki

Process and Governance

In this section

v6 Ontology-Driven Development Process — Master Design
Debt-Driven Loop
Cascade Rule
Governance
Gap Tracker

Page record

Open node ledger

wiki/process/README.md

Documents

No documented graph nodes on this page.