Rhythm 2.0 Specifications

Appearance

ATS-PFM-LLM-010undefined

Markdown

ATS-PFM-LLM-010

undefined

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-LLM-010

Design

Executed by
TST-PFM-LLM-003, TST-PFM-LLM-009, TST-PFM-LLM-017, TST-PFM-LLM-044, TST-PFM-LLM-047, TST-PFM-LLM-048, TST-PFM-LLM-049, TST-PFM-LLM-054, TST-PFM-LLM-081, TST-PFM-LLM-082

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

Read atservices-platform ad3f6a65react-console baf6dae3

undefined ​

Coverage ​

The scenarios identify the rules or journey assertions they are intended to prove. A test binding names existing evidence; an unbound proposal remains work to verify.

ScenarioTitleLevelProvenance
ATS-PFM-LLM-010-01Unqualified callers cannot inspect system usageapitest
ATS-PFM-LLM-010-02Windows have preceding comparisonsapitest
ATS-PFM-LLM-010-03Live status follows capacity and accessunittest
ATS-PFM-LLM-010-04Utilisation handles excess and zero capacityunittest
ATS-PFM-LLM-010-05Trend folding preserves all small seriesapitest
ATS-PFM-LLM-010-06Daily rebuilding keeps classifications and organization boundariesapitest
ATS-PFM-LLM-010-07Progress resumes from unfinished changesapitest
ATS-PFM-LLM-010-08HQ cost formatting pairs dollars and creditsbrowsertest

The interaction register links concrete experiments with publish ai operation definitions and historical prices; admit ai work against the organization’s monthly allowance; recover interrupted requests and identify accounting drift; inspect an organization’s ai account and request history. Each experiment checks the outcome at the shared boundary; an unbound experiment remains proposed.

Unavailable-section rendering, independent live position reads during changes and unreadable-workspace reporting progress need feature-level proof. The browser probe verifies loading rather than accounting agreement.

Coverage

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

Test Scenarios

12 scenarios proving CAP-PFM-LLM-010; 11 bound to an existing test.

01 Unqualified callers cannot inspect system usagepermissionapinegativetest
Proves
BR-CAP-PFM-LLM-010-01
Preconditions
Customer authority, an unrelated staff key and absent security context are represented.
Steps
Request system usage as each caller.
Expected
Every caller is refused.
Data
Authorized and unauthorized fixtures for the scenario, with controlled request and usage records.
Bound to
Source
services-platform:modules/llm/tests/e2e/llm-usage.e2e.spec.js#refuses a customer’s administrator, whatever they hold at their customer’s scope
02 Windows have preceding comparisonsvalidationapitest
Proves
BR-CAP-PFM-LLM-010-02
Preconditions
Usage spans current and preceding reporting periods.
Steps
Read supported windows and submit an unsupported window.
Expected
Supported reports include their preceding comparison and invalid windows return a named input error.
Data
Fixtures representing usage spans current and preceding reporting periods.
Bound to
Source
services-platform:modules/llm/tests/integration/services/usage-reports/platform-usage.integration.spec.js#is available, with the window it covers and the window before it
03 Live status follows capacity and accesstransitionunittest
Proves
BR-CAP-PFM-LLM-010-03 INV-DOM-PFM-LLM-004-08
Preconditions
Balances represent below-warning, warning, full, excess and zero allowance, disabled AI and organization, and newly added capacity.
Steps
Derive each status.
Expected
States follow committed capacity and access; new capacity can restore a previously constrained position.
Data
Fixtures representing balances represent below-warning, warning, full, excess and zero allowance, disabled AI and organization, and newly added capacity.
Bound to
Source
services-platform:modules/llm/tests/unit/services/usage-reports/usage-status.spec.ts#is warned at exactly eighty percent
04 Utilisation handles excess and zero capacityboundaryunittest
Proves
BR-CAP-PFM-LLM-010-04
Preconditions
Normal, over-allowance and zero-allowance positions exist.
Steps
Calculate the percentages.
Expected
Values round to one decimal, exceed 100% when applicable and remain empty for zero allowance.
Data
Fixtures representing normal, over-allowance and zero-allowance positions exist.
Bound to
Source
services-platform:modules/llm/tests/unit/services/usage-reports/usage-status.spec.ts#is the committed share of the allowance to one decimal
05 Trend folding preserves all small seriesruleapitest
Proves
BR-CAP-PFM-LLM-010-05
Preconditions
More than ten dimensions have reported usage.
Steps
Read the grouped trend.
Expected
The ten largest remain separate, Other exactly sums the rest and empty dates are absent.
Data
Fixtures representing more than ten dimensions have reported usage.
Bound to
Source
services-platform:modules/llm/tests/integration/services/usage-reports/platform-usage.integration.spec.js#keeps the ten largest series and folds the rest into one called other
06 Daily rebuilding keeps classifications and organization boundariesruleapitest
Proves
BR-CAP-PFM-LLM-010-08 INV-DOM-PFM-LLM-004-01 INV-DOM-PFM-LLM-004-02
Preconditions
Closed, refused, failed, released and running work spans two organizations and UTC dates, with a late settlement.
Steps
Rebuild before and after the late settlement.
Expected
Closed classifications and applicable costs remain in their start-date cells, running work is excluded and only the late settlement’s pair rebuilds.
Data
Fixtures representing closed, refused, failed, released and running work spans two organizations and UTC dates, with a late settlement.
Bound to
Source
services-platform:modules/llm/tests/integration/services/reconciliation/rollup-settled-invocations.integration.spec.js#counts a call on the day it started even when it settled on the next
07 Progress resumes from unfinished changesinvariantapitest
Proves
BR-CAP-PFM-LLM-010-09 INV-DOM-PFM-LLM-004-03
Preconditions
A rebuild has insufficient time for all changed pairs.
Steps
Run a bounded pass followed by a completing pass.
Expected
The watermark stops at the earliest unfinished change then advances on completion without regression.
Data
Fixtures representing a rebuild has insufficient time for all changed pairs.
Bound to
Source
services-platform:modules/llm/tests/integration/services/reconciliation/rollup-settled-invocations.integration.spec.js#advances the watermark to the run start less the settlement margin
08 HQ cost formatting pairs dollars and creditsrulebrowsertest
Proves
BR-CAP-PFM-LLM-010-10
Preconditions
A credit-and-cent cost pair is available.
Steps
Format it for HQ.
Expected
The result presents dollars together with credits.
Data
Fixtures representing a credit-and-cent cost pair is available.
Bound to
Source
react-console:lib/hq/ai-usage-format.test.ts#shows cents as dollars beside the credits
09 HQ navigation preserves organization selectioninteractionbrowserproposed
Proves
BR-CAP-PFM-LLM-010-01 BR-CAP-PFM-LLM-011-02
Preconditions
HQ reporting lists an organization with request history.
Steps
Open its organization card and use View Requests.
Expected
The directory opens with that organization already selected and subsequent details remain scoped to it.
Data
An isolated workspace with the records, clock instants and caller authority stated in the preconditions.
Source
services-platform:modules/llm/tests/e2e/llm-usage.e2e.spec.js#refuses a customer’s administrator, whatever they hold at their customer’s scope,services-platform:modules/llm/tests/e2e/llm-usage.e2e.spec.js#answers 404 for a request of another tenant, the tenant policy binding the read
10 Daily cells have a unique reporting identityinvariantapitest
Proves
BR-CAP-PFM-LLM-010-08
Preconditions
The suite owns isolated fixtures representing the valid control and the contrasting case described by its steps.
Steps
Insert two cells with the same day, workspace, dimensions and rate version.
Expected
The second cell is refused rather than adding another copy of the charge.
Data
Suite-owned fixtures, with a fixed clock where dates or grant windows matter.
Bound to
Source
services-platform:modules/llm/tests/integration/db/llm-usage-daily.table.integration.spec.js#refuses a second cell with the same day, organization, dimensions and rate version
11 Reporting progress cannot move backwardinvariantapitest
Proves
BR-CAP-PFM-LLM-010-09
Preconditions
The suite owns isolated fixtures representing the valid control and the contrasting case described by its steps.
Steps
Write a progress instant and then attempt to write an earlier instant.
Expected
The retained watermark remains at the later instant.
Data
Suite-owned fixtures, with a fixed clock where dates or grant windows matter.
Bound to
Source
services-platform:modules/llm/tests/integration/services/persistence/usage-rollups.queries.integration.spec.js#never moves backwards
12 Execution leaders disclose unreadable workspacesedgeapitest
Proves
BR-CAP-PFM-LLM-010-07
Preconditions
The suite owns isolated fixtures representing the valid control and the contrasting case described by its steps.
Steps
Collect closed task leaders with one workspace read made to fail.
Expected
Available leaders remain usable and the response separately identifies the unreadable workspace.
Data
Suite-owned fixtures, with a fixed clock where dates or grant windows matter.
Bound to
Source
services-platform:modules/llm/tests/integration/services/usage-reports/execution-leaders.integration.spec.js#names a tenant whose read failed and still answers the others

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.

Rhythm Software