Budgets
The allowance buckets the admission plane is holding right now, and how much of each is already spoken for.
Note: Reserved allowance is already spoken for
Loading budget buckets…
Contain AI work
Warning: Two people, and it stops new work rather than cutting it
Sending this previews the containment for an independent approver; sending the same change again once they have decided it is what applies it. There is no way past the approval on this control — a contained scope locks nobody out of the console, so there is no emergency that this waiting makes worse.
While it is on, AI admission refuses every new run in scope. Runs already admitted are left to settle — this stops new work, it does not cut work in flight. Usage, budgets, limit policies and provider connections stay readable, because containing an incident and reading what it cost are the same job.
Note: In this deployment there is nothing running for it to stop
The run lifecycle is withheld in this deployment — creating, reading and cancelling an AI run are declared by the contract and are not registered here, by owner decision — so no AI run can start and none is in flight.
Throwing the switch is still worth doing and is not theatre: the containment is recorded durably, it survives a restart and a deploy, and any run path that is built consults it before it admits anything. But it will not stop work today, because there is none. If you are working an incident, this is not the control that ends it.