| Action | Rev. | Vis. | $/action | Users | $/user | Calls/day | Err % | Sev. | Blast / incident | Runaway blast | Blast / mo | w/ Cycles | Δ / mo | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ×11 | $2.8K | $275K | $82.5K | $82.5K | $0.00 | |||||||||
| ×11 | $550 | $55.0K | $49.5K | $49.5K | $0.00 | |||||||||
| ! | ×14 | $700K | $70M | $210K | $210K | $0.00 | ||||||||
| ×1 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | |||||||||
| Totals — worst incident · worst runaway · monthly | $700K | $70M | $342K | $342K | $0.00 | |||||||||
Blast radius is the magnitude of damage that could occur if the action fires when it should not — a measure of risk exposure, not a prediction. Blast / incident is that exposure: the damage of a single wrong fire (discrete, worst-case). Runaway blast is that incident times the runaway ceiling — one action looping N times before it is stopped (the runaway / tool-loop failure mode). Blast / mo is the expected monthly loss at the given error rate — and because the catastrophic classes usually fire rarely, the monthly figure under-states them, which is exactly why the per-incident and runaway radii sit next to it. Severity is an additive weight — reversibility (1 / 3 / 10) plus visibility (0 / 1 / 4) — that multiplies the direct impact ($/action + users × $/user). Examples: irreversible + customer-facing = ×11; irreversible + public = ×14 (the catastrophic class — flagged with !). Weights are illustrative defaults, not measured industry data — replace with figures from your own incident history. Containment is the share of incidents Cycles' runtime action authority would prevent before they fire; effectiveness depends on policy. For the full model, see the Risk & Blast Radius Reference.