Rhythm 2.0 Specifications

Appearance

ATS-PFM-LLM-019Use Jazz AI conversations and project folders: Capability Test Specification

Markdown

ATS-PFM-LLM-019

Use Jazz AI conversations and project folders: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-LLM-019

KindAcceptance test setProduct areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision2

Read atservices-platform ad3f6a65react-console baf6dae3

Use Jazz AI conversations and project folders: Capability Test Specification ​

Coverage ​

RuleScenario
BR-CAP-PFM-LLM-019-01ATS-PFM-LLM-019-01
BR-CAP-PFM-LLM-019-02ATS-PFM-LLM-019-02
BR-CAP-PFM-LLM-019-05ATS-PFM-LLM-019-03
BR-CAP-PFM-LLM-019-07ATS-PFM-LLM-019-04
BR-CAP-PFM-LLM-019-08ATS-PFM-LLM-019-05
BR-CAP-PFM-LLM-019-09ATS-PFM-LLM-019-06
BR-CAP-PFM-LLM-019-10ATS-PFM-LLM-019-07

The interaction register links concrete experiments with run ai requests with consistent attribution and accounting; refine queries and directory filters with jazz ai. Each experiment checks the outcome at the shared boundary; an unbound experiment remains proposed.

All empty and archived conversation transitions, restart loss, simultaneous sends and deletion during generation lack executable coverage. Prototype entry and sample-owner sharing do not prove customer isolation.

Coverage

  • Rule gap: FND-PFM-LLM-078
  • Transition gap: FND-PFM-LLM-078
  • Validation covered
  • Permission covered
  • Edge gap: FND-PFM-LLM-078
  • Failure gap: FND-PFM-LLM-078
  • Boundary covered
  • Concurrency gap: FND-PFM-LLM-078
  • Invariant gap: FND-PFM-LLM-078
  • Interaction covered

Test Scenarios

8 scenarios proving CAP-PFM-LLM-019; 0 bound to an existing test.

01 Prototype Jazz AI has no feature gatingpermissionbrowserproposed
Proves
BR-CAP-PFM-LLM-019-01
Preconditions
A signed-in user lacks AI-specific keys and the organization AI switch is off.
Steps
Open the teammate page and header panel.
Expected
The prototype still opens; product gating remains an unresolved choice.
Data
Fixtures representing a signed-in user lacks AI-specific keys and the organization AI switch is off.
Source
react-console:components/console/nav-config.ts:unlistedNav
02 General chat bypasses Platform accountingruleapiproposed
Proves
BR-CAP-PFM-LLM-019-02
Preconditions
An organization has little allowance remaining.
Steps
Ask Jazz AI a general question.
Expected
The console produces a reply without a Platform request or credit hold.
Data
Fixtures representing an organization has little allowance remaining.
Source
react-console:app/api/agent/conversations/[id]/messages/route.ts:MODEL
03 Conversation input schemas bound lengthsvalidationapinegativeproposed
Proves
BR-CAP-PFM-LLM-019-05
Preconditions
Agent input schemas accept direct questions and project edits.
Steps
Send blank or oversized direct questions and missing or oversized project names.
Expected
The invalid examples receive input refusals.
Data
Fixtures representing agent input schemas accept direct questions and project edits.
Source
react-console:lib/agent/schemas.ts
04 Prototype conversations share the sample ownerboundarybrowsernegativeproposed
Proves
BR-CAP-PFM-LLM-019-07 INV-DOM-PFM-LLM-005-02
Preconditions
Two users in different workspaces reach the same console process.
Steps
Create and list conversations from both sessions.
Expected
The sample-owner history is shared; the product should isolate real users before release.
Data
Fixtures representing two users in different workspaces reach the same console process.
Source
react-console:lib/agent/store.ts:owned
05 Project deletion retains its conversationstransitionbrowserproposed
Proves
BR-CAP-PFM-LLM-019-08 INV-DOM-PFM-LLM-005-04
Preconditions
A project holds two conversations.
Steps
Delete the project folder.
Expected
Both exchanges remain and become unfiled.
Data
Fixtures representing a project holds two conversations.
Source
react-console:lib/agent/store.ts:deleteProject
06 Archive retains a restorable exchangetransitionbrowserproposed
Proves
BR-CAP-PFM-LLM-019-09 INV-DOM-PFM-LLM-005-06
Preconditions
A conversation is currently open.
Steps
Archive it and restore it from the archive list.
Expected
It leaves active lists, another conversation opens and restoration makes the original available again.
Data
Fixtures representing a conversation is currently open.
Source
react-console:components/agent/conversation-browser.tsx:onArchive
07 Confirmed deletion removes the exchangetransitionbrowsernegativeproposed
Proves
BR-CAP-PFM-LLM-019-10
Preconditions
A conversation exists in the browser.
Steps
Choose deletion and confirm the dialog.
Expected
The confirmation precedes removal and the conversation no longer appears in active or archived lists.
Data
Fixtures representing a conversation exists in the browser.
Source
react-console:components/agent/conversation-browser.tsx
08 Scoped history survives navigation and undointeractionbrowserproposed
Proves
BR-CAP-PFM-LLM-019-09 BR-CAP-PFM-LLM-020-03
Preconditions
A staff person refines an unsaved query with an existing scoped conversation.
Steps
Apply a supported edit, undo it, archive its conversation, leave and reopen assistance.
Expected
Undo restores the query; reopening restores the same conversation and preserves the exchange without saving the query.
Data
An isolated workspace with the records, clock instants and caller authority stated in the preconditions.
Source
react-console:components/agent/conversation-browser.tsx:onArchive,react-console:components/console/agent-chat.tsx:undo

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