Review · For: dev

Agents need to know who owns code and which downstream symbols/tests are affected.

Ownership and blast radius make PR packs, batch runs and governance useful to the humans responsible for merge risk.

$ aindex ownership src/auth.ts --json && aindex blast-radius --files src/auth.ts --json

owners
affected_symbols
dependent_files
probable_tests

Command

Ownership & Blast Radius

Resolve owners and show what a change can break.

CLI

aindex ownership src/auth.ts --json && aindex blast-radius --files src/auth.ts --json

MCP

navigate action=blast-radius

Example output

What the Brain does automatically

Every risky change can name likely owners, downstream impact and the tests that protect it.

intent

When a pull request or diff needs review.

intent

When a task is classified as a refactor.

Not measuredProof

Not measuredNo public benchmark covers this workflow yet — the proof is the live command output above, not a positioning claim.

Source—

AvailableRuntime feature status · 0 evidence item(s). Metadata-only; no raw source included.

Required tier

Expands one changed file into callers, owners, blast radius and review routing.

Pro · €49/mo

Visible as a product workflow and pilot proof target; do not treat as fully shipped enterprise automation yet.

Buyer grade

Names the parity workflow and proof path without claiming full Sourcegraph-class depth.

Visible in

This workflow stays discoverable across setup, CLI, MCP status, docs, dashboard and pricing — never a hidden command.

Feature visibility checklist

This keeps grouped product names discoverable without claiming a separate maturity level from the underlying workflow.

OwnershipFoundation

Likely owners and affected tests are attached to risky changes.

Review

Owners per context item