Rhythm 2.0 Specifications

Appearance

FAS-PFM-LLM-03Monthly AI Allowance and Notices acceptance

Markdown

FAS-PFM-LLM-03

Monthly AI Allowance and Notices acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-LLM-03
Capabilities
CAP-PFM-LLM-007, CAP-PFM-LLM-008, CAP-PFM-LLM-009

Product areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1

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

Monthly AI Allowance and Notices acceptance ​

What the Feature Must Do as a Whole ​

A small allowance has two active administrators and other staff. Run scripted requests across both charged thresholds, submit one more request and perform recovery within the live window. The suite compares the feature outcome with its capability prerequisites and keeps partial proof visible.

Interactions Between Capabilities ​

Stale held work is eligible for estimated recovery and an enclosing transaction defers delivery. Recover the request, commit and run the owed-notice retry. 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-03 as a whole.

01 Allowance consumption progresses to refusal behaviour proposed
Exercises
CAP-PFM-LLM-007 CAP-PFM-LLM-008 CAP-PFM-LLM-009
Relies on
ATS-PFM-LLM-007-03 ATS-PFM-LLM-008-03 ATS-PFM-LLM-009-02
Preconditions
A small allowance has two active administrators and other staff.
Steps
Run scripted requests across both charged thresholds, submit one more request and perform recovery within the live window.
Expected
Administrator notices reflect each crossing, the last request is refused without spending and recent work is not recovered.
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-007-hold-each-organization-to-its-monthly-ai-allowance.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-008-warn-an-organization-s-administrators-at-80-and-100.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-009-recover-what-an-interrupted-ai-request-left-behind.md
02 Recovered work can leave an owed notice interaction proposed
Exercises
CAP-PFM-LLM-007 CAP-PFM-LLM-008 CAP-PFM-LLM-009
Relies on
ATS-PFM-LLM-009-01 ATS-PFM-LLM-008-06
Preconditions
Stale held work is eligible for estimated recovery and an enclosing transaction defers delivery.
Steps
Recover the request, commit and run the owed-notice retry.
Expected
The recorded hold is released, estimated charge remains visible and the committed crossing can be delivered afterward.
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-007-hold-each-organization-to-its-monthly-ai-allowance.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-008-warn-an-organization-s-administrators-at-80-and-100.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-009-recover-what-an-interrupted-ai-request-left-behind.md
03 Local month renewal opens a separate account lifecycle proposed
Exercises
CAP-PFM-LLM-007 CAP-PFM-LLM-008 CAP-PFM-LLM-009
Relies on
ATS-PFM-LLM-007-01 ATS-PFM-LLM-009-02
Preconditions
A used local month has retained crossings and the next local month has no account yet.
Steps
Advance past local month start and request admission, then inspect both months.
Expected
The new account starts independently; prior charges and notice history remain in the earlier month and fresh work is not swept.
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-007-hold-each-organization-to-its-monthly-ai-allowance.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-008-warn-an-organization-s-administrators-at-80-and-100.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-009-recover-what-an-interrupted-ai-request-left-behind.md
04 Notice recipients follow local administrator eligibility permissionnegative proposed
Exercises
CAP-PFM-LLM-007 CAP-PFM-LLM-008
Relies on
ATS-PFM-LLM-008-03 ATS-PFM-LLM-007-03
Preconditions
Eligible local administrators, a suspended administrator, another role and a foreign administrator exist.
Steps
Settle through a charged threshold and inspect recipients and refused-request effects.
Expected
Only active local administrators receive the crossing message and a later refusal produces no additional mail.
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-007-hold-each-organization-to-its-monthly-ai-allowance.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-008-warn-an-organization-s-administrators-at-80-and-100.md
05 Repeated recovery neither charges nor alerts twice regressionnegative proposed
Exercises
CAP-PFM-LLM-007 CAP-PFM-LLM-008 CAP-PFM-LLM-009
Relies on
ATS-PFM-LLM-009-03 ATS-PFM-LLM-008-05
Preconditions
An eligible stale request and one retryable threshold notice exist.
Steps
Repeat successful reconciliation and inspect period charge, alerts and crossing delivery.
Expected
The request receives one recovery charge and one alert; an already completed crossing is not sent again.
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-007-hold-each-organization-to-its-monthly-ai-allowance.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-008-warn-an-organization-s-administrators-at-80-and-100.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-009-recover-what-an-interrupted-ai-request-left-behind.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