Change & Impact

Nobody knows what an AI change breaks. Now you do.

An AI assistant changes a shared entity and you find out three days later when the payment flow breaks in staging. Blast radius is computed by deterministic graph traversal — not an LLM estimate. Change an entity, an endpoint, or a guard rule and get the exact set of files, services, tests, and spec nodes that are affected, sized XS through XL, with coupling risk scores. Before you write a single line.

Blast Radius · Interactive Demo

Select a node above →

PRAETOR / BLAST-RADIUS

Source Node

Select a node to see its full downstream blast radius — every file, service, and test that changes if this changes.

Dependency Rings

●

Source

Direct

Transitive

Peripheral

Node Types

EntityFunctionTableEndpointTestService

How it works

Blast radius is computed by deterministic graph traversal — not an LLM estimate. Every affected node is traced through typed data-flow and control-dependency edges. Zero false positives. <1ms response time.

< 1s

to compute full blast radius via graph traversal

LLM guesses — pure deterministic graph traversal

XS–XL

change sizing with coupling risk score

edge types traversed for full dependency coverage

Blast radius — deterministic, not guessed

Graph traversal computes exact affected nodes. No confidence scores. No hallucinated dependencies. A provable answer derived from the dependency edges in the Blueprint.

Upstream blast radius

What depends on the node you are about to change? Every file, endpoint, test, guard rule, and spec node that references it — traced through all 73 edge types in the graph.

Downstream blast radius

What does the node you are changing depend on? Every spec node, utility, and service it imports — so you know the full dependency chain and what breaks if that dependency changes.

Cross-service impact

Changes that cross service boundaries: frontend ↔ API ↔ worker ↔ database. The WIRING layer tracks frontend-to-backend call edges so cross-service impact is explicit, not inferred.

Code-level blast radius

For brownfield projects, CPG analysis extends blast radius to the code graph — tracking which functions call the changed function, which modules import the changed module, and which test suites cover the changed code.

Change sizing and risk scoring

Not just what breaks — how big the change is and how risky it is to make.

Change sizing (XS–XL)

Affected files, endpoints, and tests counted and categorized XS through XL. Size estimates before you commit let you scope changes honestly — and price them accurately.

Coupling and centrality risk

Every node in the Blueprint has a centrality score — how many nodes depend on it. High centrality means high change risk. The graph surfaces this score before you touch the node.

Spec-level conflict detection

Two parallel AI sessions modifying the same spec node? The graph detects the conflict at the Blueprint level — before either session writes code — and surfaces it as a gap_conflict_unresolved node.

See your project's blast radius in under a second.

Start for free Read the docs

Nobody knows what an AI change breaks. Now you do.

Blast radius — deterministic, not guessed

Change sizing and risk scoring

See your project's blast radius in under a second.

Command Palette