Rhythm 2.0 Specifications

Appearance

FAS-PFM-LLM-07Jazz AI Conversations acceptance

Markdown

FAS-PFM-LLM-07

Jazz AI Conversations acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-LLM-07
Capabilities
CAP-PFM-LLM-019, CAP-PFM-LLM-020

Product areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1

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

Jazz AI Conversations acceptance ​

What the Feature Must Do as a Whole ​

A person has a query with chosen columns and an existing scoped conversation. Refine the query, undo, navigate away and reopen assistance. The suite compares the feature outcome with its capability prerequisites and keeps partial proof visible.

Interactions Between Capabilities ​

A conversation belongs to a saved query. Open its history on the general page, attempt a general reply and reopen from the query. 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-07 as a whole.

01 Conversation history follows scoped work behaviour proposed
Exercises
CAP-PFM-LLM-019 CAP-PFM-LLM-020
Relies on
ATS-PFM-LLM-019-06 ATS-PFM-LLM-020-06
Preconditions
A person has a query with chosen columns and an existing scoped conversation.
Steps
Refine the query, undo, navigate away and reopen assistance.
Expected
The same exchange reopens, undo preserves the original query and the changes remain unsaved.
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-019-converse-with-jazz-ai-and-keep-conversations-in-projects.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-020-change-a-query-or-a-directory-s-filters-by-asking-jazz.md
02 Scoped chat cannot become detached general chat interaction proposed
Exercises
CAP-PFM-LLM-019 CAP-PFM-LLM-020
Relies on
ATS-PFM-LLM-020-05 ATS-PFM-LLM-020-01
Preconditions
A conversation belongs to a saved query.
Steps
Open its history on the general page, attempt a general reply and reopen from the query.
Expected
Detached sending refuses with the originating-work instruction and assistance resumes on the same scope.
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-019-converse-with-jazz-ai-and-keep-conversations-in-projects.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-020-change-a-query-or-a-directory-s-filters-by-asking-jazz.md
03 Project deletion retains scoped conversation lifecycle lifecycle proposed
Exercises
CAP-PFM-LLM-019 CAP-PFM-LLM-020
Relies on
ATS-PFM-LLM-019-05 ATS-PFM-LLM-019-06 ATS-PFM-LLM-020-01
Preconditions
A project contains an archived query conversation.
Steps
Delete the project and reopen query assistance, then archive and restore its conversation.
Expected
The conversation becomes unfiled, scope reopening restores it and its messages survive archive and restoration.
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-019-converse-with-jazz-ai-and-keep-conversations-in-projects.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-020-change-a-query-or-a-directory-s-filters-by-asking-jazz.md
04 Prototype access exposes the sample-owner boundary permissionnegative proposed
Exercises
CAP-PFM-LLM-019 CAP-PFM-LLM-020
Relies on
ATS-PFM-LLM-019-01 ATS-PFM-LLM-019-04 ATS-PFM-LLM-020-01
Preconditions
Two signed-in users in different workspaces reach the same process with AI disabled.
Steps
Open Jazz AI and inspect shared conversations and scoped history from both sessions.
Expected
The prototype entry remains ungated and uses the shared sample owner; this is a release gap rather than proof of customer isolation.
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-019-converse-with-jazz-ai-and-keep-conversations-in-projects.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-020-change-a-query-or-a-directory-s-filters-by-asking-jazz.md
05 Unsupported directory changes retain existing filters regressionnegative proposed
Exercises
CAP-PFM-LLM-019 CAP-PFM-LLM-020
Relies on
ATS-PFM-LLM-020-04 ATS-PFM-LLM-020-06
Preconditions
A directory has deliberate filters and a scoped exchange.
Steps
Ask an unsupported change, leave and return to its assistance.
Expected
Filters remain unchanged and the explanation stays in the existing conversation without implying a live model interpretation.
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-019-converse-with-jazz-ai-and-keep-conversations-in-projects.md,rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-020-change-a-query-or-a-directory-s-filters-by-asking-jazz.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