Skip to content

JNY-PFM-LLM-002Support investigates an AI refusal

Markdown

JNY-PFM-LLM-002

Support investigates an AI refusal

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

KindJourneyProduct areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1End-to-endRequired

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.

Goal
Explain an AI refusal to a customer and establish whether the request can proceed now.
Screens
/hq/aiUsage/hq/tenants/{id}/hq/aiUsage/requests/hq/aiUsage/requests/{tenantId}/{invocationId}

Steps

#SurfaceActionCapabilityExpectedProvenance
1/hq/aiUsageFind the organization on the AI Usage page.CAP-PFM-LLM-010The list supplies its usage position, cost and status.test
react-console:e2e/mock/hq-ai-usage.mock.spec.ts#shows the tiles, the trend, who needs attention and the organizations with their states
2/hq/tenants/{id}Open the organization’s AI Usage card.CAP-PFM-LLM-011The card supplies allowance figures, reset information, limits and recent history.test
react-console:e2e/mock/hq-ai-usage.mock.spec.ts#reads the limited organization: the warning band, the limits, the history and the refusals
3/hq/aiUsage/requestsOpen View Requests and select refused requests.CAP-PFM-LLM-011The directory filters to that organization without displaying captured bodies.test
react-console:e2e/mock/hq-ai-usage.mock.spec.ts#asks for an organization first, then filters its requests without ever showing prompt text
4/hq/aiUsage/requests/{tenantId}/{invocationId}Open a refused request.CAP-PFM-LLM-011The detail supplies request metadata, attempts and its refusal snapshot.test
services-platform:modules/llm/tests/e2e/llm-usage.e2e.spec.js#answers one invocation with its attempts and the refusal snapshot of a refused one
5/hq/aiUsage/requests/{tenantId}/{invocationId}Read the explanation.CAP-PFM-LLM-012The panel presents the recorded reason, admission arithmetic and a current comparison.test
react-console:e2e/mock/hq-ai-usage.mock.spec.ts#a refused request explains itself in three blocks, and shows evidence statuses without content

Alternate and Failure Paths

PathFrom stepConditionPath takenOutcomeProvenance
alternate4The request failed after dispatch.Read the attempt timeline and verdicts.Support can distinguish a provider failure from an admission refusal.test
react-console:e2e/mock/hq-ai-usage.mock.spec.ts#a failed request shows its attempts as a timeline
failure1A usage section cannot load.That section presents its unavailable state independently.Support can continue with information that loaded.observed
failure1A customer administrator tries an HQ read.HQ authorization rejects the request.The customer receives no HQ usage data.test
services-platform:modules/llm/tests/e2e/llm-usage.e2e.spec.js#refuses a customer’s administrator, whatever they hold at their customer’s scope

Assertions

IdStatementProvenance
01Agreement between the overview, organization card and request directory remains unproved.unknown
02The directory excludes captured request and response bodies.test
react-console:e2e/mock/hq-ai-usage.mock.spec.ts#asks for an organization first, then filters its requests without ever showing prompt text
03The explanation presents refusal figures and a current admission comparison.test
react-console:e2e/mock/hq-ai-usage.mock.spec.ts#a refused request explains itself in three blocks, and shows evidence statuses without content

End-to-end policy: required: This path depends on agreement between several HQ screens. Mock browser coverage establishes their presentation; the live browser check does not compare their figures.

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.