the map · under development · v1.0.4
The questions a grep cannot answer.
The code intelligence layer. Two jobs a text search physically cannot do: deterministic blast-radius, and the stable semantic map.
every edge banded by how it is known
01the query vocabulary
What you can ask it.
Text search answers one question: where does this string appear. RepoGraph answers the ones it physically cannot, the questions about what depends on what. Each query returns an auditable answer instead of a guess.
blast-radiusWhat breaks if I change this?
Every caller that transitively reaches the module you are about to touch. The query you run before you edit shared code, not after the incident.
reflexionWhere did the architecture drift?
The design you declared, compared against the edges the code actually has. The divergence is the finding, on a method with thirty years behind it.
why-coupledWhy do these always change together?
The hidden dependency behind two modules that co-move in every release. The seam that never showed up inside a single file.
dead-codeWhat is unreachable?
Nodes no entrypoint can reach, confirmed against the graph rather than guessed. Safe to delete becomes a query result, not a hunch.
map --domainWhere are the seams?
Domain boundaries, ownership, and layering across the whole repository. You cannot grep for a seam; you can only read it off the map.
Navigation, where is this function, you already own: grep does it natively, and a fresh grep beats a stale index every time. RepoGraph owns only the questions grep cannot reach.
02epistemic honesty
Every edge, banded by how it is known.
Most code graphs hand you a confident, incomplete answer and call it exhaustive. RepoGraph labels the certainty of every edge, so a blast radius can say precisely where it is proven, where it is inferred, and where it simply cannot see.
Compiler-grade facts from a language server or a SCIP index. The call actually resolves. Solid edges, drawn with certainty, the same the security world has always trusted.
STATIC · LSP / SCIPThe dynamic dispatch static analysis cannot see, recovered from co-change history and, sparingly, an LLM resolving one specific edge. Dashed, and labeled as inference, never dressed up as fact.
DYNAMIC · co-changeThe graph names what it could not prove instead of guessing. Confirmed missing is a finding, not a blank. The map never claims more certainty than it has.
BOUNDED · no bluffing03what we hold
The rules the map never breaks.
All of it is under active development. These are the positions it does not trade away, whatever the release.
Every edge is banded: observed, inferred, or absent. Never a confident blank.
Blast-radius is reverse-transitive and auditable, never a model that is pretty sure.
The map names what it cannot prove, instead of bluffing past it.
It rides the audit's single ingestion pass. No new service, no Neo4j.
04how it is built
A byproduct, not a platform.
No new service, no Neo4j. RepoGraph is adjacency on the Postgres the audit already runs on, with pgvector alongside. Its edges are fed by a language server for what is provable and by commit history for what is not, and the whole thing rides the single ingestion pass that produces the audit. It ships in-repo behind a typed client boundary, and extracts to its own service only when a second real consumer appears.
05the map that does not go stale
Declare the architecture. Measure the drift.
The stable semantic map has a construction method with thirty years behind it, the software reflexion model: declare the architecture you meant to build, compare it against what the code actually does, and treat the divergence as the finding. Convergence, divergence, and absence map onto the same three evidence bands.
RepoGraph converges into the audit you are already adopting. It is a measured Tier-1 slice: one recipe, proven complete on the kernel's own repository against a hand-audited ground truth, before a single line of breadth is built. The map is honest, and the honesty is the product.
Read the thesis behind it →Answers you can audit.
See the blast-radius and the semantic map on your own repository, every edge banded by evidence, under NDA.
The map never claims more certainty than it has.