Execution safety, control 6 of 9
S-06 Enforce budgets, limits and cancellation
P0Hard gateNeeds your evidence
Autonomous work must operate within explicit cost, request, duration and scope budgets. Missing pricing data is not permission for unbounded spending.
- Priority
- Gate. A FAIL stops publish or launch.
- Hard gate
- Yes. A FAIL stops publication, whatever the score.
- Change class
- READ_ONLY: Inspect authorised evidence.
- Quality bucket
- Not scored: hard gate only
Evidence to review
- Budget ledger, cancellation state and limit-exhaustion tests.
How to implement
- Set per-run and per-site limits before execution.
- Count retries and subagents against the same parent budget.
- Stop or degrade to safe read-only work when limits are reached.
- Check cancellation before every queued consequential action.
- Count parent plans, subagents, retries and separate batches against externally maintained URL and revision/action budgets; do not reset scope by renaming a job.
How UltimateSEO checks this
Needs your evidence. No automated check covers this control, so it stays UNKNOWN until evidence is supplied.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.