--- id: FAS-PFM-LLM-07 title: Jazz AI Conversations acceptance feature: FEAT-PFM-LLM-07 product_area: platform module: llm revision: 1 status: proposed product_intent: proposed source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f rhythm-v2-docs: 9b95399181c8ec6670ce3d12d700e59643668692 capabilities: - CAP-PFM-LLM-019 - CAP-PFM-LLM-020 scenarios: - id: FAS-PFM-LLM-07-01 title: Conversation history follows scoped work kind: behaviour 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.' negative: false data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed 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 - id: FAS-PFM-LLM-07-02 title: Scoped chat cannot become detached general chat kind: interaction 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. negative: false data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed 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 - id: FAS-PFM-LLM-07-03 title: Project deletion retains scoped conversation lifecycle kind: lifecycle 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. negative: false data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed 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 - id: FAS-PFM-LLM-07-04 title: Prototype access exposes the sample-owner boundary kind: permission 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. negative: true data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed 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 - id: FAS-PFM-LLM-07-05 title: Unsupported directory changes retain existing filters kind: regression 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. negative: true data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed 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 evidence: - artifact: CAP-PFM-LLM-019 provenance: documented source: >- specs/platform/llm/planning/capabilities/CAP-PFM-LLM-019-converse-with-jazz-ai-and-keep-conversations-in-projects.md - artifact: CAP-PFM-LLM-020 provenance: documented source: >- specs/platform/llm/planning/capabilities/CAP-PFM-LLM-020-change-a-query-or-a-directory-s-filters-by-asking-jazz.md - provenance: documented source: 'rhythm-v2-docs:specs/CONVENTIONS.md#5.3 Feature Acceptance Suite' execution_gap: FND-PFM-LLM-081 --- # 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 | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish cumulative feature acceptance from the pinned capability and design baseline. |