01 / THE WORK
What we admire
GitNexus explores code knowledge graphs that an agent can query for relationships and flows. It was a useful comparison while we decided how much of our graph should be an owned local engine.
02 / THE LESSON
The principle that stayed
The graph’s runtime and parser versions affect reproducibility. An optional external adapter can be useful, but the canonical evidence path should remain available offline.
03 / OUR BOUNDARY
Where CodeVetter stands
The graph decision keeps CodeVetter’s Tree-sitter index in Rust and treats a GitNexus subprocess as optional secondary research. It is not required by the product.