Rhythm 2.0 Specifications

Appearance

ATS-PFM-LLM-018Give people understandable AI refusal messages: Capability Test Specification

Markdown

ATS-PFM-LLM-018

Give people understandable AI refusal messages: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-LLM-018

Design

Executed by
TST-PFM-LLM-085

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

Read atservices-platform ad3f6a65react-console baf6dae3

Give people understandable AI refusal messages: Capability Test Specification ​

Coverage ​

RuleScenario
BR-CAP-PFM-LLM-018-01ATS-PFM-LLM-018-01
BR-CAP-PFM-LLM-018-02ATS-PFM-LLM-018-01
BR-CAP-PFM-LLM-018-03ATS-PFM-LLM-018-01
BR-CAP-PFM-LLM-018-04ATS-PFM-LLM-018-01
BR-CAP-PFM-LLM-018-06ATS-PFM-LLM-018-02
BR-CAP-PFM-LLM-018-08ATS-PFM-LLM-018-03

The interaction register links concrete experiments with run ai requests with consistent attribution and accounting; notify administrators at allowance thresholds; show administrators their organization’s ai allowance. Each experiment checks the outcome at the shared boundary; an unbound experiment remains proposed.

Customer wording at missing reset dates, internal server classifications and full notice-to-console agreement need complete interaction proof beyond individual sentence helpers.

Coverage

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

Test Scenarios

3 scenarios proving CAP-PFM-LLM-018; 2 bound to an existing test.

01 Customer refusal vocabulary preserves next stepsruleunittest
Proves
BR-CAP-PFM-LLM-018-01 BR-CAP-PFM-LLM-018-02 BR-CAP-PFM-LLM-018-03 BR-CAP-PFM-LLM-018-04
Preconditions
Supported customer refusals and operator-only faults are represented.
Steps
Obtain each customer sentence.
Expected
Supported cases receive their defined retry, support or renewal guidance, and operator faults have no dedicated sentence.
Data
Fixtures representing supported customer refusals and operator-only faults are represented.
Bound to
Source
services-platform:modules/llm/tests/unit/services/usage/usage-sentences.spec.ts#tells an organization that has used its allowance when it resumes
02 Vocabulary keeps internal terminology out of customer copyinvariantunittest
Proves
BR-CAP-PFM-LLM-018-06
Preconditions
All generated customer sentences are available.
Steps
Scan the sentences for prohibited internal words.
Expected
Only organization-facing terminology remains, without money, model, provider or override detail.
Data
Fixtures representing all generated customer sentences are available.
Bound to
Source
services-platform:modules/llm/tests/unit/services/usage/usage-sentences.spec.ts#is declared for a population of sentences, so the rule below is not vacuous
03 Pause notice and customer helper share wordinginteractionbrowsernegativeproposed
Proves
BR-CAP-PFM-LLM-018-08
Preconditions
The same exhausted allowance supplies notice and console-helper content.
Steps
Generate both messages.
Expected
The pause explanation matches apart from the organization name versus direct address.
Data
Fixtures representing the same exhausted allowance supplies notice and console-helper content.
Source
react-console:lib/api/generate-query.ts:allowanceMessage

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