Skip to content

ATS-PFM-LLM-017Show administrators their organization’s AI allowance: Capability Test Specification

Markdown

ATS-PFM-LLM-017

Show administrators their organization’s AI allowance: Capability Test Specification

Markdown
  • DocumentProposed

KindAcceptance test setProduct areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision2

Read atservices-platform ad3f6a65react-console baf6dae3

Coverage

  • Rule gap: FND-PFM-LLM-076
  • Transition gap: FND-PFM-LLM-076
  • Validation gap: FND-PFM-LLM-076
  • Permission covered
  • Edge covered
  • Failure gap: FND-PFM-LLM-076
  • Boundary covered
  • Concurrency gap: FND-PFM-LLM-076
  • Invariant covered
  • Interaction covered

Test Scenarios

13 scenarios proving CAP-PFM-LLM-017; 9 bound to an existing test.

01 Organization summary requires local console authoritypermissionapinegativetest
Proves
BR-CAP-PFM-LLM-017-01
Preconditions
Local administrator, unkeyed user, foreign administrator, anonymous and HQ-only contexts are available.
Steps
Read the local summary under each context.
Expected
Only the appropriately authorized local administrator succeeds.
Data
Fixtures representing local administrator, unkeyed user, foreign administrator, anonymous and HQ-only contexts are available.
Bound to
Source
services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#answers the summary to the organization’s administrator
02 Summary states usage and local renewalruleapitest
Proves
BR-CAP-PFM-LLM-017-02
Preconditions
An organization is at 85%, another unused and another disabled.
Steps
Read their summaries.
Expected
Balances, warning message, local reset and history reflect each position, including unused and disabled states.
Data
Fixtures representing an organization is at 85%, another unused and another disabled.
Bound to
Source
services-platform:modules/llm/tests/integration/services/usage/organization-usage.integration.spec.js#states the allowance, what is used and what remains, from the live period
03 Customer summary excludes internal commercial detailinvariantapitest
Proves
BR-CAP-PFM-LLM-017-03 INV-DOM-PFM-LLM-004-06
Preconditions
Usage includes grants and custom limits.
Steps
Read the customer summary.
Expected
Neither keys nor text disclose money, provider, model, operation identity, grants or internal limits.
Data
Fixtures representing usage includes grants and custom limits.
Bound to
Source
services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#carries no key naming money, a provider, a model, an override or a limit on the summary
04 Features explain current restrictionruleapitest
Proves
BR-CAP-PFM-LLM-017-04
Preconditions
An operation is enabled with capacity, then disabled.
Steps
Read the feature list before and after disablement.
Expected
Availability changes to restriction with its disabled-feature explanation.
Data
Fixtures representing an operation is enabled with capacity, then disabled.
Bound to
Source
services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#answers the features, available while the organization has credits
05 Active exemptions expose a feature-list mismatchedgeapiproposed
Proves
BR-CAP-PFM-LLM-017-05
Preconditions
The only feature operation is disabled but has an active exemption.
Steps
Read availability and request operation admission.
Expected
Admission allows it while the feature list still says restricted.
Data
Fixtures representing the only feature operation is disabled but has an active exemption.
Source
services-platform:docs/milestones/PLAT-M3-ai-usage-organization-page.md#State found on 2026-10-19 (re-inspected)
06 Unknown historical operations have an Other groupruleapitest
Proves
BR-CAP-PFM-LLM-017-06
Preconditions
Both declared and no-longer-declared operations have usage.
Steps
Read usage by feature.
Expected
Declared usage appears in its feature and the remainder in Other AI features.
Data
Fixtures representing both declared and no-longer-declared operations have usage.
Bound to
Source
services-platform:modules/llm/tests/integration/services/usage/organization-usage.integration.spec.js#sums the period’s requests and credits by feature and groups an undeclared operation as other
07 Customer periods stay organization-scopedboundaryapitest
Proves
BR-CAP-PFM-LLM-017-07 INV-DOM-PFM-LLM-001-11
Preconditions
Two organizations have usage in the same month.
Steps
Read one customer summary.
Expected
All reported figures belong to that organization.
Data
Fixtures representing two organizations have usage in the same month.
Bound to
Source
services-platform:modules/llm/tests/integration/services/usage/organization-usage.integration.spec.js#does not read another organization’s period
08 Reporting datasets exclude diagnostic contentinvariantapitest
Proves
BR-CAP-PFM-LLM-017-08
Preconditions
Two organizations contain requests.
Steps
Query the request dataset under each organization reader.
Expected
Each reader receives only local records and no body, storage, snapshot, raw usage or version columns.
Data
Fixtures representing two organizations contain requests.
Bound to
Source
services-platform:modules/llm/tests/integration/db/llm-invocations-query.view.integration.spec.js#answers the tenant’s own two requests to the query reader, newest last, and not the other tenant’s
09 Planned customer dashboard remains a delivery obligationrulebrowserproposed
Proves
BR-CAP-PFM-LLM-017-09
Preconditions
An organization administrator has usage to review.
Steps
Open the intended Tools and Dashboards AI Usage page.
Expected
The product should show credit position, renewal, feature states, recent monthly trend, pause wording and request navigation without money.
Data
Fixtures representing an organization administrator has usage to review.
Source
services-platform:docs/milestones/PLAT-M3-ai-usage-organization-page.md#Scope in one paragraph
10 Customer review agrees with HQinteractionapiproposed
Proves
AS-JNY-PFM-LLM-004-01 AS-JNY-PFM-LLM-004-02
Preconditions
Usage and a disabled feature exist for one organization.
Steps
Follow the administrator review journey and compare its results with HQ.
Expected
Credit position agrees across the two views and the feature explains its restriction.
Data
Fixtures representing usage and a disabled feature exist for one organization.
Source
FND-PFM-LLM-027
11 Customer summary uses the refusal vocabularyinteractionapiproposed
Proves
BR-CAP-PFM-LLM-017-02 BR-CAP-PFM-LLM-018-01
Preconditions
The organization has exhausted its allowance and has a known reset date.
Steps
Read the summary and derive the allowance-refusal sentence at that reset.
Expected
The summary and sentence share renewal guidance and exclude internal money, model and provider wording.
Data
An isolated workspace with the records, clock instants and caller authority stated in the preconditions.
Source
services-platform:modules/llm/services/usage/organization-usage.ts,services-platform:modules/llm/tests/unit/services/usage/usage-sentences.spec.ts#tells an organization that has used its allowance when it resumes
12 Customer mapping withholds internal commercial fieldsruleunittest
Proves
BR-CAP-PFM-LLM-017-03
Preconditions
The suite owns isolated fixtures representing the valid control and the contrasting case described by its steps.
Steps
Map a period containing credits and internal money and model detail to the customer summary.
Expected
Only customer-facing credit and percentage details are retained.
Data
Suite-owned fixtures, with a fixed clock where dates or grant windows matter.
Bound to
Source
services-platform:modules/llm/tests/unit/services/usage/organization-usage.spec.ts#has no key naming money, a provider, a model, an override or a limit on the summary
13 Every declared feature has readable descriptionsruleunittest
Proves
BR-CAP-PFM-LLM-017-04
Preconditions
The suite owns isolated fixtures representing the valid control and the contrasting case described by its steps.
Steps
Read catalog features with their declared labels and descriptions.
Expected
Every declared feature has a label and explanatory line rather than exposing only an internal key.
Data
Suite-owned fixtures, with a fixed clock where dates or grant windows matter.
Bound to
Source
services-platform:modules/llm/tests/unit/services/usage/usage-features.spec.ts#describes every feature the catalog declares, with a label and a line

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.