chore(conductor): Add new tracks for 'Session Context Snapshots' and 'Discussion Takes'
This commit is contained in:
@@ -0,0 +1,5 @@
|
||||
# Track discussion_takes_branching_20260311 Context
|
||||
|
||||
- [Specification](./spec.md)
|
||||
- [Implementation Plan](./plan.md)
|
||||
- [Metadata](./metadata.json)
|
||||
@@ -0,0 +1,8 @@
|
||||
{
|
||||
"track_id": "discussion_takes_branching_20260311",
|
||||
"type": "feature",
|
||||
"status": "new",
|
||||
"created_at": "2026-03-11T19:30:00Z",
|
||||
"updated_at": "2026-03-11T19:30:00Z",
|
||||
"description": "Discussion Takes & Timeline Branching: Tabbed interface for multi-timeline takes, message branching, and synthesis generation workflows."
|
||||
}
|
||||
25
conductor/tracks/discussion_takes_branching_20260311/plan.md
Normal file
25
conductor/tracks/discussion_takes_branching_20260311/plan.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Implementation Plan: Discussion Takes & Timeline Branching
|
||||
|
||||
## Phase 1: Backend Support for Timeline Branching
|
||||
- [ ] Task: Write failing tests for extending the session state model to support branching (tree-like history or parallel linear "takes" with a shared ancestor).
|
||||
- [ ] Task: Implement backend logic to branch a session history at a specific message index into a new take ID.
|
||||
- [ ] Task: Implement backend logic to promote a specific take ID into an independent, top-level session.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 1: Backend Support for Timeline Branching' (Protocol in workflow.md)
|
||||
|
||||
## Phase 2: GUI Implementation for Tabbed Takes
|
||||
- [ ] Task: Write GUI tests verifying the rendering and navigation of multiple tabs for a single session.
|
||||
- [ ] Task: Implement a tabbed interface within the Discussion window to switch between different takes of the active session.
|
||||
- [ ] Task: Add a "Split/Branch from here" action to individual message entries in the discussion history.
|
||||
- [ ] Task: Add a UI button/action to promote the currently active take to a new separate session.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 2: GUI Implementation for Tabbed Takes' (Protocol in workflow.md)
|
||||
|
||||
## Phase 3: Synthesis Workflow Formatting
|
||||
- [ ] Task: Write tests for a new text formatting utility that takes multiple history sequences and generates a compressed, diff-like text representation.
|
||||
- [ ] Task: Implement the sequence differencing and compression logic to clearly highlight variances between takes.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 3: Synthesis Workflow Formatting' (Protocol in workflow.md)
|
||||
|
||||
## Phase 4: Synthesis UI & Agent Integration
|
||||
- [ ] Task: Write GUI tests for the multi-take selection interface and synthesis action.
|
||||
- [ ] Task: Implement a UI mechanism allowing users to select multiple takes and provide a synthesis prompt.
|
||||
- [ ] Task: Implement the execution pipeline to feed the compressed differences and user prompt to an AI agent, and route the generated synthesis to a new "take" tab.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 4: Synthesis UI & Agent Integration' (Protocol in workflow.md)
|
||||
23
conductor/tracks/discussion_takes_branching_20260311/spec.md
Normal file
23
conductor/tracks/discussion_takes_branching_20260311/spec.md
Normal file
@@ -0,0 +1,23 @@
|
||||
# Specification: Discussion Takes & Timeline Branching
|
||||
|
||||
## 1. Overview
|
||||
This track introduces non-linear discussion timelines, allowing users to create multiple "takes" (branches) from a shared point in a conversation. It includes UI for managing these parallel timelines within a single discussion window and features a specialized synthesis workflow to merge ideas from multiple takes.
|
||||
|
||||
## 2. Functional Requirements
|
||||
|
||||
### 2.1 Timeline Branching (Takes)
|
||||
- **Message Branching:** Add a "Split/Branch from here" action on individual discussion messages.
|
||||
- **Tabbed Interface:** Branching creates a new "take," represented visually as a new tab within the same discussion session. The new tab shares the timeline history up to the split point.
|
||||
- **Take Promotion:** Allow users to promote any specific take into an entirely new, standalone discussion session.
|
||||
|
||||
### 2.2 Take Synthesis Workflow
|
||||
- **Multi-Take Selection:** Provide a UI to select multiple takes from a shared split point for comparison and synthesis.
|
||||
- **Diff/Compressed Representation:** Develop a formatted representation (e.g., compressed diffs or parallel sequence summaries) that clearly highlights the differences between the selected takes.
|
||||
- **Synthesis Generation:** Feed the compressed representation of the differences to an AI agent along with a user prompt (e.g., "I liked aspects of both, do C with these caveats") to generate a new, synthesized take.
|
||||
|
||||
## 3. Acceptance Criteria
|
||||
- [ ] Users can split a discussion from any message to create a new "take".
|
||||
- [ ] Takes are navigable via a tabbed interface within the discussion window.
|
||||
- [ ] A take can be promoted to a standalone discussion session.
|
||||
- [ ] Multiple takes can be selected and formatted into a compressed difference view.
|
||||
- [ ] An AI agent can successfully process the compressed take view to generate a synthesized continuation.
|
||||
Reference in New Issue
Block a user