Trace a dependency

The dependency model

Every member declares its edges in its atlas.json, and atlas assembles them into topology/constellation.json. Edges are typed: build (the strongest coupling), contract (a published interface), runtime (a deployment relation).

Steps

1. Read the graph on the site — /systems/<name> shows what a system depends on and what depends on it, each edge typed and (where declared) deep-linked to the target's docs. The interactive view and the stack show the whole shape.

2. Compute the blast radius of a change with the CLI:

   node bin/atlas.mjs impact --repo ontos --symbol V
   

   It reports which members and edges a change touches across the constellation.

3. Verify cross-repo doc links resolve:

   node bin/atlas.mjs crosslinks docs .
   

Notes

• The substance systems form a single vertical stack the dependency graph alone can't derive — see the architecture for why ontos sits at the floor and arche at the top.
• design and atlas are orthogonal infrastructure: every system reads them, but they sit under the stack, not in it.