Rhythm 2.0 Specifications

Appearance

FAS-PFM-LLM-04Rhythm HQ AI Usage Oversight acceptance

Markdown

FAS-PFM-LLM-04

Rhythm HQ AI Usage Oversight acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-LLM-04
Capabilities
CAP-PFM-LLM-010, CAP-PFM-LLM-011, CAP-PFM-LLM-012
Executed by
TST-PFM-LLM-006, TST-PFM-LLM-009

Product areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1

Read atservices-platform ad3f6a65react-console baf6dae3rhythm-v2-docs 9b953991

Rhythm HQ AI Usage Oversight acceptance ​

What the Feature Must Do as a Whole ​

A staff reader can access an organization with a refused request. Navigate from reporting to its account, request directory, detail and explanation. The suite compares the feature outcome with its capability prerequisites and keeps partial proof visible.

Interactions Between Capabilities ​

A stored refusal precedes a grant that restores live capacity. Read HQ live status and explain the same request before and after the grant. The interaction scenario checks what changes across that shared boundary. Lifecycle, permission and regression scenarios preserve the wider feature obligations.

Regression Record ​

RevisionChangeScenarioWhy
1initialallEstablish cumulative feature acceptance from the pinned capability and design baseline.

Scenarios

5 scenarios proving FEAT-PFM-LLM-04 as a whole.

01 Support follows usage to a refusal explanation behaviour proposed
Exercises
CAP-PFM-LLM-010 CAP-PFM-LLM-011 CAP-PFM-LLM-012
Relies on
ATS-PFM-LLM-010-01 ATS-PFM-LLM-011-02 ATS-PFM-LLM-012-07
Preconditions
A staff reader can access an organization with a refused request.
Steps
Navigate from reporting to its account, request directory, detail and explanation.
Expected
The selected organization and request stay consistent, with retained decision figures separated from current affordability.
Data
An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks.
Source
rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-010-see-ai-usage-and-spend-across-every-organization.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-011-inspect-one-organization-s-ai-usage-and-requests.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-012-explain-why-an-ai-request-was-refused-or-failed.md
02 Added capacity changes present explanation interaction proposed
Exercises
CAP-PFM-LLM-010 CAP-PFM-LLM-011 CAP-PFM-LLM-012
Relies on
ATS-PFM-LLM-010-03 ATS-PFM-LLM-012-04
Preconditions
A stored refusal precedes a grant that restores live capacity.
Steps
Read HQ live status and explain the same request before and after the grant.
Expected
Present status and affordability improve while the original refusal arithmetic remains unchanged and explanation takes no hold.
Data
An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks.
Source
rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-010-see-ai-usage-and-spend-across-every-organization.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-011-inspect-one-organization-s-ai-usage-and-requests.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-012-explain-why-an-ai-request-was-refused-or-failed.md
03 Late settlement updates history and task inspection lifecycle proposed
Exercises
CAP-PFM-LLM-010 CAP-PFM-LLM-011 CAP-PFM-LLM-012
Relies on
ATS-PFM-LLM-010-06 ATS-PFM-LLM-011-03
Preconditions
A request closes after its start day and its enclosing task has already closed.
Steps
Rebuild the affected day and inspect request and task histories.
Expected
History uses request start day and retained settlement figures; healthy requests remain ineligible for refusal explanation.
Data
An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks.
Source
rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-010-see-ai-usage-and-spend-across-every-organization.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-011-inspect-one-organization-s-ai-usage-and-requests.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-012-explain-why-an-ai-request-was-refused-or-failed.md
04 Customer keys cannot open staff investigations permissionnegative test
Exercises
CAP-PFM-LLM-010 CAP-PFM-LLM-011 CAP-PFM-LLM-012
Relies on
ATS-PFM-LLM-010-01 ATS-PFM-LLM-011-01 ATS-PFM-LLM-012-01
Preconditions
A customer administrator holds broad customer authority.
Steps
Attempt the system report, own organization’s HQ account and its explanation.
Expected
All staff-only surfaces refuse the customer; no diagnostic content is exposed.
Data
An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks.
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,services-platform:modules/llm/tests/e2e/llm-usage.e2e.spec.js#refuses a customer’s administrator a tenant’s usage even in their own tenant,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
05 An unavailable section remains distinguishable regressionnegative proposed
Exercises
CAP-PFM-LLM-010 CAP-PFM-LLM-011 CAP-PFM-LLM-012
Relies on
ATS-PFM-LLM-011-03 ATS-PFM-LLM-012-06
Preconditions
One account subsection is unreadable while other reads remain available.
Steps
Read the overview and request a missing explanation.
Expected
Available sections remain usable, the failed section reports unavailable and the missing request remains not found.
Data
An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks.
Source
rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-010-see-ai-usage-and-spend-across-every-organization.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-011-inspect-one-organization-s-ai-usage-and-requests.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-012-explain-why-an-ai-request-was-refused-or-failed.md

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