Skip to content

CAP-PFM-LLM-013Set an organization’s AI access and recurring limits

Markdown

CAP-PFM-LLM-013

Set an organization’s AI access and recurring limits

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationPartially observed

KindCapabilityProduct areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
Configured allowance and switches apply to new admissions.Ceiling and version checks reject invalid or stale updates.Control audits retain the change, actor and reason.
Surfaces
apiconsole
Preconditions
An existing organization is selected.
Postconditions
The limits update synchronizes the current period and audit.
Constraints
The console limit controls are incomplete.
Intent sources
services-platform:docs/proposals/llm-observability/11-decisions.md#D-3

Controls

22 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-IAM-003 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-005 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

KeyChecked atScope
hq.llm-usage.manageapiglobal
hq.llm-usage.manageconsoleglobal

Business Rules

11 rules, 9 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

IdRuleKindEnforced atProvenance
01must prove
Proposed
The sensitive HQ AI usage manage key is required to preview or change limits; read-only staff and customer administrators are refused.
permissionapitest
services-platform:modules/llm/tests/e2e/llm-limits.e2e.spec.js#is refused the write before a handler runs, whatever the customer’s scope grants
02must prove
Proposed
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.
validationapi, serviceobserved
03must prove
Proposed
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.
validationapi, serviceobserved
04must prove
Proposed
A changed save requires the inspected limits version, using zero for defaults, and missing or stale versions are rejected.
validationapi, servicetest
05must prove
Proposed
Values identical to stored limits return unchanged without a write, new version or audit entry, even with an older supplied version.
policyserviceobserved
06must prove
Proposed
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.
lifecycleservice, databaseobserved
07must prove
Proposed
The audit event includes before and after values, reason and actor and marks allowance increases, AI re-enablement or operation re-enablement as widening.
policyserviceobserved
08must prove
Proposed
Preview reports proposed allowance, committed and remaining credits, limiting reason and effective-ceiling pressure without writing limits or audit events.
calculationserviceobserved
09must prove
Proposed
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.
policyservicetest
10
Proposed
The reason belongs in the audit event and is distinct from the explanatory note retained with limits.
policyservicedocumented
11
Proposed
Only usage managers see the console’s Edit Limits control, which remains disabled with an unavailable label.
permissionconsoleobserved

Scenarios

IdGivenWhenThenProvenance
01An organization uses default limits at version zero.An administrator submits a reasoned allowance increase.The update advances the version, synchronizes the current period and records widening.test
services-platform:modules/llm/tests/e2e/llm-limits.e2e.spec.js#syncs this month’s period to the new allowance
02Two administrators use the same limit version.The second update arrives after the first.The stale update changes nothing.test

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.