In this section: Glossary

Capability Graph

Once a handful of capabilities have contracts, a natural question shows up: how do they depend on each other? The capability graph answers it. cdad graph walks every contract in the repo and renders the result as Mermaid, JSON, and Markdown, a directed map of what calls what.

The JSON adjacency list is the one worth building tooling against. It's intentionally stable and meant for agents to consume directly, not just for humans skimming a diagram during review.

A capability graph with large unlabeled gaps is really a map of where extractionstill needs to happen.