Architecture Graph

The artifact graph captures explicit relationships between ADRs and specs declared in YAML frontmatter (per ADR-0023 / SPEC-0018). Edges describe supersedes, extends, enables, governs, implements, requires, and related relationships between artifacts. The page below reflects the authored edges only; derived inverses (governed-by, implemented-by, etc.) are computed at query time by the /sdd:graph skill.

Stats

Metric	Count
ADRs	2
Specs	1
Authored edges	6
Derived edges (computed)	4
Orphan ADRs (no implementing spec)	0
Orphan specs (no governing ADR)	0

Full graph

Orphan ADRs

ADRs that no spec declares implements: against. Add an implements: [ADR-XXXX] line to a spec's frontmatter (or run /sdd:graph backfill) to remove an ADR from this list.

No orphan ADRs — every ADR has at least one implementing spec.

Orphan specs

Specs that no ADR declares governs: against. (For specs whose source-code coverage is the relevant orphan signal, use /sdd:graph orphans directly — that walks source files for governing comments and is not reflected in this static page.)

No orphan specs — every spec is governed by at least one ADR.

Querying the graph

The static view above is generated at docs-build time. For interactive queries:

/sdd:graph validate                  # full diagnostics
/sdd:graph impact ADR-XXXX           # what depends on this ADR
/sdd:graph ancestors SPEC-XXXX       # what this spec depends on
/sdd:graph chain SPEC-XXXX           # bidirectional view
/sdd:graph orphans                   # source files, specs, ADRs
/sdd:graph backfill                  # propose edges from prose

JSON output (--json) is the stable contract for any future MCP, IDE plugin, or dashboard.