01must proveProposed | The sensitive HQ AI usage manage key is required to preview or change limits; read-only staff and customer administrators are refused. | permission | api | test |
02must proveProposed | A replacement supplies the AI switch, base allowance or default, disabled operations, concurrency cap or default and note, with omitted optional cap and note reset. | validation | api, service | observed |
03must proveProposed | Limit validation accepts a default allowance or a whole credit amount from zero to ten million, a default or positive whole concurrency cap, and declared disabled operations stored once in sorted order. Notes are trimmed and limited to one thousand characters; reasons are trimmed to one through five hundred characters. Invalid input leaves state unchanged. | validation | api, service | observed |
04must proveProposed | A changed save requires the inspected limits version, using zero for defaults, and missing or stale versions are rejected. | validation | api, service | test |
05must proveProposed | Values identical to stored limits return unchanged without a write, new version or audit entry, even with an older supplied version. | policy | service | observed |
06must proveProposed | A limits save atomically updates the current month’s base allowance and audit event without rewriting charges, holds, grants or past periods; later periods use the new base when created. | lifecycle | service, database | observed |
07must proveProposed | The audit event includes before and after values, reason and actor and marks allowance increases, AI re-enablement or operation re-enablement as widening. | policy | service | observed |
08must proveProposed | Preview reports proposed allowance, committed and remaining credits, limiting reason and effective-ceiling pressure without writing limits or audit events. | calculation | service | observed |
09must proveProposed | Disabled AI rejects every operation; an active operation exemption can bypass an operation switch but never the global AI switch, and refusal records the disabled-feature reason without a hold. | policy | service | test |
10Proposed | The reason belongs in the audit event and is distinct from the explanatory note retained with limits. | policy | service | documented |
11Proposed | Only usage managers see the console’s Edit Limits control, which remains disabled with an unavailable label. | permission | console | observed |