4 posts carrying this tag.
Agent runtimes got very good very fast. The thing that decides whether a change is correct across your other repositories did not get built at all. On cross repository blast radius, why AI code review misses it, and what a check actually needs.
A technical note on what 'verifiable' actually means in a verifiable code IR. Not a machine that rebuilds your code from a document, but a derived contract that every change gets checked against. Here is what a single verification check consists of, why round-trip is a signal and never a promise, and the honest boundary of what it can and cannot catch.
Specs and code drift apart the day after you write the PRD, because they are two separate documents that nobody keeps in sync. A verifiable context layer derives the spec a codebase actually implements and then continuously checks the code against it. Here is how spec-driven development works on a brownfield codebase, and why it needs a verifiable code IR that checks code against intent.
GraphRAG for codebases is a genuine step up from vector search. It follows real call edges instead of guessing at similarity, and it wins on architectural questions. But it breaks in three predictable places: cross-repo links that aren't call edges, the why behind the code, and anything that needs intent you can check changes against. Here is a clear-eyed map of what graph RAG for codebases solves, where it stops, and the verifiable context layer that sits above it.
