Put the gate before a risky migration.
Start with the piece that is proven today: an agent-proposed migration gets parsed statement by statement, then graded on blast radius before it can run.
The demo reproduces the real analyzer: five additive statements pass, one data-loss statement needs approval, one unknown statement fails closed, and one catastrophic table drop blocks.
Local proof path
Run the blast-radius gate
1. Install the package
cd packages/novyx-blast-radius
python -m venv .venv
source .venv/bin/activate
pip install -e .2. Run the canonical demo
PYTHONPATH=. python examples/demo.py3. Use the analyzer in the gate
from novyx_blast_radius import BlastRadiusAnalyzer
report = BlastRadiusAnalyzer(probe).analyze(migration_sql)
report.verdict # block
report.flagged # 3 dangerous statements
report.explanation # plain-English blast-radius reasonA practical first rollout
Start with migrations
The proven wedge is schema migration review: parse every statement and grade it on reversibility and live data impact.
Run the gate before execution
Let additive statements pass, require review for irreversible data loss, and block catastrophic changes.
Record the verdict
Use the verdict and explanation as the evidence your approval or deployment workflow consumes.
Expand carefully
After the migration gate is trusted, apply the same effect-governance model to more production-changing actions.
Do not boil the agent platform first.
Prove one gate on one dangerous class of change. Once the team trusts the verdicts, wire the same effect-governance model into broader production workflows.
Good first action
An agent-proposed schema migration with real data-loss risk.
Bad first action
A broad rewrite of every agent integration before proving one gate.
Success signal
The gate produces a readable verdict that reviewers can trust before execution.
Next step
Connect the verdict to approval, audit, and deployment workflows.