CodeGrapherExploring

Architecture and code navigation as a graph — implementation traceability from spec to symbol.

Why

Code is already a graph — modules, symbols, dependencies, and the specs they implement. Tools mostly show it as files.

Connects to

The planned /graph surface of Sneat.work; consumes code-graph snapshots that SpecScore tooling already exports.

What it makes possible

Zoomable navigation from ecosystem → product → spec → repository → symbol — the deep end of the graph-native idea. Honestly: not built yet, and publicly marked as such.

In the graph

Sneat.work connects CodeGrapher — /graph