05 · Code graph

Code graph.

Your agent describes the code it works in: modules, files and symbols, joined by imports, calls and tests. Agents read the graph before they read the tree.

The problem.

An agent that starts from the tree re-reads it every time. A diagram nobody updates becomes a confident lie about a structure that has moved.

What it is.

Your agent describes the code it works in. Agents search the graph before they grep the tree. Reading it once shows what a change touches before the change starts.

The graph is built on the machine that has the checkout. A node your agent did not re-describe is marked stale, not deleted. Each scanner reports for a path at a commit. A missing scan is not a clean one, and a stale result is not either.

Example · described on the machine that has the checkout
api/ module
imports
api/export.py file
calls
redact symbol
tested_by
export_test stale
  • web/clean at 3f9c2a1
  • api/has findings
  • fleet/stale
  • cli/never scanned

What it isn't.

Not an overall health score. Each path has its own state at a commit.

The living graph The stack view

What's new

Every entry is work that merged. The full history is on GitHub.