Verification Engine direction

Roadmap · after v1.0

Blast radius

In plain terms: if you change or remove something, what else is affected? Pre-computed dependency closure across services, files, and features — graph math, not model imagination.

Verification Engine

PR-wide blast radius on roadmap — v1.0 includes quality map and governance findings in chat. Sub-10-second impact queries across the full service graph ship with the Verification Engine. Features in v1.0.

What blast radius means

Borrowed from incident response: the blast radius of a change is everything that could break downstream. ContextMint builds this from imports, service dependencies, and feature links in your engineering graph — — so reviewers see impact before opening a 2,000-line diff.

< 10 secTarget query latency
Index-timeClosure pre-computed
EvidenceDependency path cited
What breaks if Payments API is removed?
Payments API
├─► Checkout Service (direct)
├─► Billing Worker (direct)
├─► Subscription Service (transitive)
└─► 14 more downstream nodes…
⚠ ADR-12 event-sourcing boundary touched

Built for PR review

Every changed file expands to affected features, teams, and services before reviewers open the diff.

MCP & API (planned)

Expose get_blast_radius to agents with the same deterministic graph humans trust — see MCP server.

See ContextMint on your codebase

A local AI coding assistant for a solo developer. The same product adds a shared server and human approval for a small company or enterprise. Coming soon.

Book a Demo Trust & Security