Rhythm 2.0 Specifications

Appearance

ATS-PFM-LLM-012Explain an AI refusal or unsuccessful conversation: Capability Test Specification

Markdown

ATS-PFM-LLM-012

Explain an AI refusal or unsuccessful conversation: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-LLM-012

Design

Executed by
TST-PFM-LLM-006, TST-PFM-LLM-025, TST-PFM-LLM-074

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

Read atservices-platform ad3f6a65react-console baf6dae3

Explain an AI refusal or unsuccessful conversation: Capability Test Specification ​

Coverage ​

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

The interaction register links concrete experiments with bound ai conversations and handle recoverable failures; admit ai work against the organization’s monthly allowance; inspect an organization’s ai account and request history; provide temporary ai capacity and revoke it. Each experiment checks the outcome at the shared boundary; an unbound experiment remains proposed.

Concurrent changes while the present-position blocks are assembled and snapshot-free or truncated explanations need combined boundary proof. A complete support journey remains unexecuted.

Coverage

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

Test Scenarios

9 scenarios proving CAP-PFM-LLM-012; 7 bound to an existing test.

01 Customer authority cannot open HQ explanationspermissionapinegativetest
Proves
BR-CAP-PFM-LLM-012-01
Preconditions
A customer administrator is authenticated.
Steps
Request a problem explanation.
Expected
The HQ route refuses access.
Data
Fixtures representing a customer administrator is authenticated.
Bound to
Source
services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#is refused 403 for a customer’s administrator, because the route is system
02 Original refusal arithmetic does not changeruleapitest
Proves
BR-CAP-PFM-LLM-012-02
Preconditions
A refusal is followed by an additional capacity grant.
Steps
Explain the same refusal before and after the grant.
Expected
Policy and decision-time arithmetic remain unchanged.
Data
Fixtures representing a refusal is followed by an additional capacity grant.
Bound to
Source
services-platform:modules/llm/tests/integration/services/explain/explain-invocation.integration.spec.js#reproduces the snapshot’s state as block 2, with the arithmetic as a sentence
03 Missing grant references remain explicitedgeapitest
Proves
BR-CAP-PFM-LLM-012-03
Preconditions
A snapshot references an existing grant and an unreadable grant.
Steps
Open its explanation.
Expected
The readable grant includes its window and the other remains listed as not found.
Data
Fixtures representing a snapshot references an existing grant and an unreadable grant.
Bound to
Source
services-platform:modules/llm/tests/integration/services/explain/explain-invocation.integration.spec.js#reads an override then in force back by id, with its window
04 Current admission check observes later capacityruleapitest
Proves
BR-CAP-PFM-LLM-012-04
Preconditions
A refused estimate becomes affordable after a grant.
Steps
Explain it before and after that grant.
Expected
The present check changes from refusal to admission, lists later grants and takes no hold.
Data
Fixtures representing a refused estimate becomes affordable after a grant.
Bound to
Source
services-platform:modules/llm/tests/integration/services/explain/explain-invocation.integration.spec.js#says the same request would still be refused now, before the grant
05 Failure histories disclose retries and truncationfailureapitest
Proves
BR-CAP-PFM-LLM-012-06
Preconditions
Failed work has several attempts and an incomplete retained history.
Steps
Open its failure explanation.
Expected
Classification, outcome and attempt verdicts appear with an incomplete-history indication.
Data
Fixtures representing failed work has several attempts and an incomplete retained history.
Bound to
Source
services-platform:modules/llm/tests/integration/services/explain/explain-invocation.integration.spec.js#lists the attempts in order with their status codes and the verdict on each
06 Healthy or foreign requests do not explainvalidationapinegativetest
Proves
BR-CAP-PFM-LLM-012-08
Preconditions
Healthy settled, nonexistent and foreign problem requests are represented.
Steps
Request explanations for all three.
Expected
Healthy work returns nothing-to-explain while missing and foreign work returns not found.
Data
Fixtures representing healthy settled, nonexistent and foreign problem requests are represented.
Bound to
Source
services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#says 409 IllegalOperation for a request that settled without error
07 Support follows a refusal from overview to explanationinteractionbrowserproposed
Proves
AS-JNY-PFM-LLM-002-01 AS-JNY-PFM-LLM-002-02 AS-JNY-PFM-LLM-002-03
Preconditions
An organization has a refused request.
Steps
Open its overview, request directory, request detail and explanation.
Expected
Displayed account figures agree and the explanation distinguishes the original refusal from present admission without showing captured content.
Data
Fixtures representing an organization has a refused request.
Source
FND-PFM-LLM-027
08 Later capacity changes only present admissioninteractionapiproposed
Proves
BR-CAP-PFM-LLM-012-04 BR-CAP-PFM-LLM-014-07
Preconditions
A refusal snapshot precedes a capacity grant.
Steps
Explain before granting, after granting and after revocation.
Expected
The present affordability check follows the grant while retained policy and decision-time arithmetic remain unchanged.
Data
An isolated workspace with the records, clock instants and caller authority stated in the preconditions.
Source
services-platform:modules/llm/services/explain/explain-invocation.ts,services-platform:modules/llm/services/overrides/allowance-overrides.ts
09 Explanation keeps retry verdicts readablefailureunitnegativetest
Proves
BR-CAP-PFM-LLM-012-06
Preconditions
The suite owns isolated fixtures representing the valid control and the contrasting case described by its steps.
Steps
Derive explanation verdicts for retryable and terminal attempt classifications.
Expected
The verdict distinguishes temporary retry guidance from outcomes that another attempt cannot repair.
Data
Suite-owned fixtures, with a fixed clock where dates or grant windows matter.
Bound to
Source
services-platform:modules/llm/tests/unit/services/explain/explain.spec.ts#is retries_spent for the last failure of a retryable status

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