Rhythm 2.0 Specifications

Appearance

FAS-PFM-LLM-02AI Catalog and Pricing acceptance

Markdown

FAS-PFM-LLM-02

AI Catalog and Pricing acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-LLM-02
Capabilities
CAP-PFM-LLM-005, CAP-PFM-LLM-006

Product areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1

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

AI Catalog and Pricing acceptance ​

What the Feature Must Do as a Whole ​

Operation and price declarations are valid and test tiers use stub mode. Publish the catalog, resolve an operation and run its prepared script. The suite compares the feature outcome with its capability prerequisites and keeps partial proof visible.

Interactions Between Capabilities ​

A scripted request has settled at the old price. Publish a changed price and execute the same usage after fresh resolution. 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-02 as a whole.

01 Publication makes declared work callable behaviour proposed
Exercises
CAP-PFM-LLM-005 CAP-PFM-LLM-006
Relies on
ATS-PFM-LLM-005-02 ATS-PFM-LLM-006-01
Preconditions
Operation and price declarations are valid and test tiers use stub mode.
Steps
Publish the catalog, resolve an operation and run its prepared script.
Expected
The operation resolves to a published price, scripted usage is metered and no live model call occurs.
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-005-declare-and-publish-ai-operations-and-their-prices.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-006-prove-ai-features-without-spending.md
02 Changing prices changes scripted costs prospectively interaction proposed
Exercises
CAP-PFM-LLM-005 CAP-PFM-LLM-006
Relies on
ATS-PFM-LLM-005-05 ATS-PFM-LLM-006-02
Preconditions
A scripted request has settled at the old price.
Steps
Publish a changed price and execute the same usage after fresh resolution.
Expected
The new charge changes while earlier version history remains intact; the test cannot construct the live adapter.
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-005-declare-and-publish-ai-operations-and-their-prices.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-006-prove-ai-features-without-spending.md
03 Reversion appends rather than rewrites lifecycle proposed
Exercises
CAP-PFM-LLM-005 CAP-PFM-LLM-006
Relies on
ATS-PFM-LLM-005-03 ATS-PFM-LLM-005-04
Preconditions
A routing declaration is published, changed and then reverted.
Steps
Publish each declaration and inspect its historical versions under scripted verification.
Expected
Reversion creates a later historical version with the earlier digest; previous versions resist mutation.
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-005-declare-and-publish-ai-operations-and-their-prices.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-006-prove-ai-features-without-spending.md
04 Catalog inspection remains staff-only permissionnegative proposed
Exercises
CAP-PFM-LLM-005 CAP-PFM-LLM-006
Relies on
ATS-PFM-LLM-005-08 ATS-PFM-LLM-006-01
Preconditions
A support reader, customer administrator and unkeyed staff caller request catalog history.
Steps
Read the HQ catalog as each caller while test mode remains scripted.
Expected
Only the keyed staff reader receives the catalog and rates; denied reads never initiate model work.
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-005-declare-and-publish-ai-operations-and-their-prices.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-006-prove-ai-features-without-spending.md
05 Invalid publication preserves the working catalog regressionnegative proposed
Exercises
CAP-PFM-LLM-005 CAP-PFM-LLM-006
Relies on
ATS-PFM-LLM-005-02 ATS-PFM-LLM-006-02
Preconditions
A valid catalog is in force and a proposed publication routes an operation to an unpriced model.
Steps
Attempt publication, inspect version counts and run a script against the existing declaration.
Expected
Validation appends no versions and the existing published operation remains callable without live spending.
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-005-declare-and-publish-ai-operations-and-their-prices.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-006-prove-ai-features-without-spending.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