Rhythm 2.0 Specifications

Appearance

FAS-PFM-LLM-01Metered AI Requests acceptance

Markdown

FAS-PFM-LLM-01

Metered AI Requests acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-LLM-01
Capabilities
CAP-PFM-LLM-001, CAP-PFM-LLM-002, CAP-PFM-LLM-003, CAP-PFM-LLM-004

Product areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1

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

Metered AI Requests acceptance ​

What the Feature Must Do as a Whole ​

A declared task has three scripted requests and a configured capture store. Complete the task and compare request charges, task totals, monthly accounting and capture states. The suite compares the feature outcome with its capability prerequisites and keeps partial proof visible.

Interactions Between Capabilities ​

A task request first returns a rejected final answer and then a valid repair. Reject the first answer through the consumer judge, accept the repair and inspect attempts and settlement. 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-01 as a whole.

01 One task accounts for its model conversations behaviour proposed
Exercises
CAP-PFM-LLM-001 CAP-PFM-LLM-002 CAP-PFM-LLM-003 CAP-PFM-LLM-004
Relies on
ATS-PFM-LLM-001-03 ATS-PFM-LLM-003-05 ATS-PFM-LLM-004-01
Preconditions
A declared task has three scripted requests and a configured capture store.
Steps
Complete the task and compare request charges, task totals, monthly accounting and capture states.
Expected
The returned result, task totals and monthly charge agree with the settled requests, whose redacted evidence is retained.
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-001-make-every-ai-request-through-one-metered-path.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-002-keep-an-ai-conversation-within-its-limits.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-003-account-for-a-multi-step-ai-task-as-one-execution.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-004-keep-redacted-evidence-of-every-ai-request.md
02 A repaired answer remains one metered request interaction proposed
Exercises
CAP-PFM-LLM-001 CAP-PFM-LLM-002 CAP-PFM-LLM-003
Relies on
ATS-PFM-LLM-002-08 ATS-PFM-LLM-003-05
Preconditions
A task request first returns a rejected final answer and then a valid repair.
Steps
Reject the first answer through the consumer judge, accept the repair and inspect attempts and settlement.
Expected
Both turns belong to one request and one task; usage includes the repair and the rejected call consumes tool budget.
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-001-make-every-ai-request-through-one-metered-path.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-002-keep-an-ai-conversation-within-its-limits.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-003-account-for-a-multi-step-ai-task-as-one-execution.md
03 A failed task retains completed request accounts lifecycle proposed
Exercises
CAP-PFM-LLM-001 CAP-PFM-LLM-003 CAP-PFM-LLM-004
Relies on
ATS-PFM-LLM-003-01 ATS-PFM-LLM-004-01
Preconditions
A task completes two requests before its body throws.
Steps
Let the body fail and inspect the task, associated requests and evidence.
Expected
The task closes failed with timing while earlier settled costs and capture references remain investigable.
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-001-make-every-ai-request-through-one-metered-path.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-003-account-for-a-multi-step-ai-task-as-one-execution.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-004-keep-redacted-evidence-of-every-ai-request.md
04 Workspace removal respects the diagnostic boundary permissionnegative proposed
Exercises
CAP-PFM-LLM-001 CAP-PFM-LLM-004
Relies on
ATS-PFM-LLM-004-04
Preconditions
Two workspaces have model records and captured content.
Steps
Remove the first workspace’s AI records and inspect both workspaces through scoped readers.
Expected
The removed workspace has no surviving dependent AI records or evidence versions; the other workspace remains unchanged.
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-001-make-every-ai-request-through-one-metered-path.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-004-keep-redacted-evidence-of-every-ai-request.md
05 Unknown usage keeps an explicit estimate regressionnegative proposed
Exercises
CAP-PFM-LLM-001 CAP-PFM-LLM-002 CAP-PFM-LLM-003
Relies on
ATS-PFM-LLM-001-03 ATS-PFM-LLM-003-05
Preconditions
A task’s scripted model completes successfully without usage figures.
Steps
Settle the request and compare request, task and period costs.
Expected
The reservation estimate is charged with unknown cents and the hold is released; the task retains that accounting distinction.
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-001-make-every-ai-request-through-one-metered-path.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-002-keep-an-ai-conversation-within-its-limits.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-003-account-for-a-multi-step-ai-task-as-one-execution.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