Rhythm 2.0 Specifications

Appearance

FAS-PFM-LLM-05Rhythm HQ AI Controls acceptance

Markdown

FAS-PFM-LLM-05

Rhythm HQ AI Controls acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-LLM-05
Capabilities
CAP-PFM-LLM-013, CAP-PFM-LLM-014, CAP-PFM-LLM-015, CAP-PFM-LLM-016

Product areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1

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

Rhythm HQ AI Controls acceptance ​

What the Feature Must Do as a Whole ​

A manager changes limits, creates capacity and corrects a charge; a sensitive reader holds an eligible access grant. Commit each valid control and read captured content, then inspect the organization’s AI audit history. The suite compares the feature outcome with its capability prerequisites and keeps partial proof visible.

Interactions Between Capabilities ​

An operation exemption is active and organization-wide AI is enabled. Disable global AI, check access, re-enable it and revoke the exemption. 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-05 as a whole.

01 Reasoned controls retain a joined audit history behaviour proposed
Exercises
CAP-PFM-LLM-013 CAP-PFM-LLM-014 CAP-PFM-LLM-015 CAP-PFM-LLM-016
Relies on
ATS-PFM-LLM-013-07 ATS-PFM-LLM-014-06 ATS-PFM-LLM-015-06 ATS-PFM-LLM-016-02
Preconditions
A manager changes limits, creates capacity and corrects a charge; a sensitive reader holds an eligible access grant.
Steps
Commit each valid control and read captured content, then inspect the organization’s AI audit history.
Expected
Each accepted control retains actor and reason, successful content access has its own content-free audit and charges remain traceable.
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-013-set-what-ai-an-organization-may-use-and-how-much.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-014-grant-and-revoke-temporary-ai-capacity.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-015-correct-what-an-organization-was-charged-for-ai.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-016-read-a-captured-prompt-or-response-under-an-access-grant.md
02 Temporary capacity does not override global AI disablement interaction proposed
Exercises
CAP-PFM-LLM-013 CAP-PFM-LLM-014
Relies on
ATS-PFM-LLM-013-09 ATS-PFM-LLM-014-07
Preconditions
An operation exemption is active and organization-wide AI is enabled.
Steps
Disable global AI, check access, re-enable it and revoke the exemption.
Expected
Global disablement prevents access despite the exemption; re-enablement restores operation-only evaluation and revocation ends the exemption.
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-013-set-what-ai-an-organization-may-use-and-how-much.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-014-grant-and-revoke-temporary-ai-capacity.md
03 Capacity can be scheduled and revoked before start lifecycle proposed
Exercises
CAP-PFM-LLM-013 CAP-PFM-LLM-014 CAP-PFM-LLM-015
Relies on
ATS-PFM-LLM-014-03 ATS-PFM-LLM-014-07 ATS-PFM-LLM-015-06
Preconditions
A future capacity window follows a reasoned base-limit change and correction.
Steps
Create the scheduled grant, revoke it before start and inspect limits, corrections and capacity at the start instant.
Expected
The revoked grant contributes no capacity; original grant details, base configuration and signed correction remain separately inspectable.
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-013-set-what-ai-an-organization-may-use-and-how-much.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-014-grant-and-revoke-temporary-ai-capacity.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-015-correct-what-an-organization-was-charged-for-ai.md
04 Control authority and content authority remain distinct permissionnegative proposed
Exercises
CAP-PFM-LLM-013 CAP-PFM-LLM-014 CAP-PFM-LLM-015 CAP-PFM-LLM-016
Relies on
ATS-PFM-LLM-013-01 ATS-PFM-LLM-014-01 ATS-PFM-LLM-015-01 ATS-PFM-LLM-016-05
Preconditions
Support, a customer administrator, a usage manager and a sensitive reader have distinct authorities.
Steps
Attempt limit, grant, correction and content operations as each relevant caller, with and without an eligible access grant.
Expected
Read-only and customer authority cannot mutate controls; management authority alone cannot open content and content authority still needs a live eligible grant.
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-013-set-what-ai-an-organization-may-use-and-how-much.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-014-grant-and-revoke-temporary-ai-capacity.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-015-correct-what-an-organization-was-charged-for-ai.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-016-read-a-captured-prompt-or-response-under-an-access-grant.md
05 Repeated creates remain visible as separate facts regressionnegative proposed
Exercises
CAP-PFM-LLM-013 CAP-PFM-LLM-014 CAP-PFM-LLM-015
Relies on
ATS-PFM-LLM-013-05 ATS-PFM-LLM-014-06 ATS-PFM-LLM-015-06
Preconditions
Limits are saved and grant and correction payloads are valid.
Steps
Replay unchanged limits, then submit each create payload twice and inspect history.
Expected
Limits add no new audit while repeated grants and corrections remain separate audited records; the suite exposes their lack of replay protection.
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-013-set-what-ai-an-organization-may-use-and-how-much.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-014-grant-and-revoke-temporary-ai-capacity.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-015-correct-what-an-organization-was-charged-for-ai.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