Use cases / Engineering managers
Knowing whether review is keeping up
The sanity index: is the codebase getting harder to review as more of it is written by machines?
The problem
Throughput metrics go up when agents arrive. Nobody measures whether review still means anything.
What visualdiff does
- Every stored review contributes risk, hold rate, drift, agent share and signal-to-noise.
- The sanity index rolls them into one weekly number per repository.
- Trends show when a repository needs stricter policy or more reviewers.
Weekly series per repository from every stored review, exported as JSON from /api/v1/sanity.
Related
- Reviewing pull requests written by agentsAgents open pull requests faster than anyone can read them. Read the 10% that decides whether it is safe.
- Large refactors that hide a behaviour changeA refactor is supposed to change nothing. Find the one line that does.
- Stopping hallucinated dependenciesSlopsquatting: attackers register the package names models invent. Catch them at review.
- Seeing which running systems a change reachesThe diff says rds.tf. The map says orders-db, the API in front of it, and the queue behind it.