CERTIFY · REJECT · PROBE · ASK · CALIBRATED CONSEQUENCE CHECKS FOR THE ACTIONS OF AI AGENTS · NO LLM ON THE CERTIFY PATH · FAIL CLOSED · CERTIFY · REJECT · PROBE · ASK · CALIBRATED CONSEQUENCE CHECKS FOR THE ACTIONS OF AI AGENTS · NO LLM ON THE CERTIFY PATH · FAIL CLOSED · CERTIFY · REJECT · PROBE · ASK · CALIBRATED CONSEQUENCE CHECKS FOR THE ACTIONS OF AI AGENTS · NO LLM ON THE CERTIFY PATH · FAIL CLOSED · CERTIFY · REJECT · PROBE · ASK · CALIBRATED CONSEQUENCE CHECKS FOR THE ACTIONS OF AI AGENTS · NO LLM ON THE CERTIFY PATH · FAIL CLOSED · CERTIFY · REJECT · PROBE · ASK · CALIBRATED CONSEQUENCE CHECKS FOR THE ACTIONS OF AI AGENTS · NO LLM ON THE CERTIFY PATH · FAIL CLOSED · CERTIFY · REJECT · PROBE · ASK · CALIBRATED CONSEQUENCE CHECKS FOR THE ACTIONS OF AI AGENTS · NO LLM ON THE CERTIFY PATH · FAIL CLOSED · CERTIFY · REJECT · PROBE · ASK · CALIBRATED CONSEQUENCE CHECKS FOR THE ACTIONS OF AI AGENTS · NO LLM ON THE CERTIFY PATH · FAIL CLOSED · CERTIFY · REJECT · PROBE · ASK · CALIBRATED CONSEQUENCE CHECKS FOR THE ACTIONS OF AI AGENTS · NO LLM ON THE CERTIFY PATH · FAIL CLOSED ·
A VM idle for three weeks may be about to do the one thing it exists for. RiskGate deletes only what is dormant in every plausible world and deallocates the rest, reversibly.
Transcript0:55 · narrated
Azure Public Dataset V1 (Microsoft, CC BY 4.0) · scripted cleanup agent · real riskgate verdicts on the real trace · offline study
01 · What happened
The situation
Microsoft's public Azure trace: 2,013,767 real VMs, 30 days of 5-minute CPU readings. 11,834 VMs were idle for three full weeks. One of them, vm-1261898, shows three flat weeks without a single busy hour. On day 21 the cleanup agent ranks delete first, deallocate second.
02 · The miss
Why the obvious safeguard didn’t catch it
Idle-for-N-days is the standard cleanup rule, and 14.4% of those three-week-idle VMs were needed again in the next nine days. Deleted means no way back.
03 · RiskGate
List, play forward, decide
RiskGate asks what this quiet VM could be: dormant, scheduled, or live. Delete is safe in one world; deallocate in two.
It reads what the agent didn't: the deployment and the subscription. For this VM, “live” is ruled out; “scheduled” is not.
Delete skipped. Deallocate certified: disks kept, snapshot taken, owner told. On day 27 the VM woke up to 59% CPU, a restart that takes minutes instead of a rebuild.
04 · At scale
What held, and the price
On held-out subscriptions it had never seen (50 re-splits), 96.8% of cleanup ran with no ticket: 58.5% deleted, 38.3% deallocated, 3.2% asked. Certified mistakes were 3.45% under a 5% budget, against 14.7% if the agent's first choice ran unchecked.
14.7% → 3.45%VMs wrongly cleaned up
96.8%cleanups with no ticket
0.28 msgate time per VM
Name one action your agent isn’t allowed to take today.
Send us its traces and what happened afterwards. We’ll show how often it could have run safely, and what it would have stopped.