Every other vendor ships automation armed on day one and asks you to trust a confidence score they chose. In AEROSS the rung an automation sits on is a fact about its own record on your estate, and the arithmetic that moves it is arithmetic rather than a model.
It begins by watching: when its event appears the match is written down as what it would have done, and nothing runs. To move to asking a person first, its record must clear the thresholds you set — by default a fix rate above ninety in a hundred, a clear margin over the measured self-healing rate, across at least ten real runs. Running without asking is the last rung, and any automation can be capped at a rung it may never pass.
While an automation watches, the same events are followed with nothing done to them. How often they recover on their own is the control the automation must beat. Some events fix themselves, so a runbook that only ever ran alongside a recovery it did not cause will not pass the bar — which stops automation taking credit for outcomes it did not produce.
No. Spend and capacity figures can be set and are recorded with the action, but they are not gates today. The limits that genuinely refuse are the off switch, the pause and the per-agent ceiling, each of which is a refusal where actions are checked rather than a warning read afterwards.