chore(conductor): Add new track '4-Tier Architecture Implementation & Conductor Self-Improvement'
This commit is contained in:
@@ -32,3 +32,8 @@ This file tracks all major tracks for the project. Each track has its own detail
|
||||
|
||||
- [ ] **Track: Investigate differences left between gui.py and gui_2.py. Needs to reach full parity, so we can sunset guy.py**
|
||||
*Link: [./tracks/gui2_parity_20260224/](./tracks/gui2_parity_20260224/)*
|
||||
|
||||
---
|
||||
|
||||
- [ ] **Track: 4-Tier Architecture Implementation & Conductor Self-Improvement**
|
||||
*Link: [./tracks/mma_implementation_20260224/](./tracks/mma_implementation_20260224/)*
|
||||
5
conductor/tracks/mma_implementation_20260224/index.md
Normal file
5
conductor/tracks/mma_implementation_20260224/index.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# Track mma_implementation_20260224 Context
|
||||
|
||||
- [Specification](./spec.md)
|
||||
- [Implementation Plan](./plan.md)
|
||||
- [Metadata](./metadata.json)
|
||||
@@ -0,0 +1,8 @@
|
||||
{
|
||||
"track_id": "mma_implementation_20260224",
|
||||
"type": "feature",
|
||||
"status": "new",
|
||||
"created_at": "2026-02-24T00:00:00Z",
|
||||
"updated_at": "2026-02-24T00:00:00Z",
|
||||
"description": "4-Tier Architecture Implementation & Conductor Self-Improvement"
|
||||
}
|
||||
50
conductor/tracks/mma_implementation_20260224/plan.md
Normal file
50
conductor/tracks/mma_implementation_20260224/plan.md
Normal file
@@ -0,0 +1,50 @@
|
||||
# Implementation Plan: 4-Tier Architecture Implementation & Conductor Self-Improvement
|
||||
|
||||
## Phase 1: `manual_slop` Migration Planning
|
||||
- [ ] Task: Synthesize MMA Documentation
|
||||
- [ ] Read and analyze `./MMA_Support/Data_Pipelines_and_Config.md` and `./MMA_Support/OriginalDiscussion.md`
|
||||
- [ ] Read and analyze `./MMA_Support/Tier1_Orchestrator.md` through `./MMA_Support/Tier4_Utility.md`
|
||||
- [ ] Document key takeaways and constraints for the migration plan
|
||||
- [ ] Task: Draft Track 1 - The Memory Foundations (AST Parser)
|
||||
- [ ] Define TDD approach for `tree-sitter` integration in `file_cache.py`
|
||||
- [ ] Specify tasks for `ASTParser` extraction rules (Skeleton View, Curated View)
|
||||
- [ ] Define acceptance testing criteria for AST extraction
|
||||
- [ ] Task: Draft Track 2 - State Machine & Data Structures
|
||||
- [ ] Define TDD approach for `models.py` (`Track`, `Ticket`, `WorkerContext`)
|
||||
- [ ] Specify tasks for state mutator methods
|
||||
- [ ] Define acceptance testing criteria for state transitions
|
||||
- [ ] Task: Draft Track 3 - The Linear Orchestrator & Execution Clutch
|
||||
- [ ] Define TDD approach for `multi_agent_conductor.py` (`run_worker_lifecycle`)
|
||||
- [ ] Specify tasks for context injection and HITL Clutch implementation
|
||||
- [ ] Define acceptance testing criteria for the linear orchestration loop
|
||||
- [ ] Task: Draft Track 4 - Tier 4 QA Interception
|
||||
- [ ] Define TDD approach for `shell_runner.py` stderr interception
|
||||
- [ ] Specify tasks for routing errors to the cheap API model
|
||||
- [ ] Define acceptance testing criteria for the QA interception loop
|
||||
- [ ] Task: Draft Track 5 - UI Decoupling & Tier 1/2 Routing (The Final Boss)
|
||||
- [ ] Define TDD approach for async queue in `multi_agent_conductor.py`
|
||||
- [ ] Specify tasks for Tier 1 & 2 system prompts and the Dispatcher async loop
|
||||
- [ ] Define acceptance testing criteria for UI decoupling and dynamic routing
|
||||
- [ ] Task: Conductor - User Manual Verification '`manual_slop` Migration Planning' (Protocol in workflow.md)
|
||||
|
||||
## Phase 2: Conductor Self-Reflection & Upgrade Strategy
|
||||
- [ ] Task: Research Optimal Proposal Format
|
||||
- [ ] Search Gemini CLI documentation for extension guidelines
|
||||
- [ ] Search Conductor documentation for tuning and advice
|
||||
- [ ] Define the structure for `proposal.md` based on findings
|
||||
- [ ] Task: Draft Proposal - Memory Siloing & Token Firewalling
|
||||
- [ ] Evaluate current `conductor` context management
|
||||
- [ ] Propose strategies to prevent token bloat during planning and execution
|
||||
- [ ] Write the corresponding section in `proposal.md`
|
||||
- [ ] Task: Draft Proposal - Execution Clutch & Linear Debug Mode
|
||||
- [ ] Evaluate current `conductor` execution workflows
|
||||
- [ ] Propose mechanisms for manual step-through and auto modes
|
||||
- [ ] Write the corresponding section in `proposal.md`
|
||||
- [ ] Task: Draft Proposal - Multi-Model/Sub-Agent Delegation
|
||||
- [ ] Evaluate current `conductor` single-model reliance
|
||||
- [ ] Propose a design for delegating tasks (e.g., summarization, syntax-fixing) to sub-agents
|
||||
- [ ] Write the corresponding section in `proposal.md`
|
||||
- [ ] Task: Review and Finalize Proposal
|
||||
- [ ] Ensure all three core areas are addressed with equal priority
|
||||
- [ ] Verify alignment with the overall 4-Tier Architecture philosophy
|
||||
- [ ] Task: Conductor - User Manual Verification 'Conductor Self-Reflection & Upgrade Strategy' (Protocol in workflow.md)
|
||||
37
conductor/tracks/mma_implementation_20260224/spec.md
Normal file
37
conductor/tracks/mma_implementation_20260224/spec.md
Normal file
@@ -0,0 +1,37 @@
|
||||
# Specification: 4-Tier Architecture Implementation & Conductor Self-Improvement
|
||||
|
||||
## 1. Overview
|
||||
This track encompasses two major phases. Phase 1 focuses on designing a comprehensive, step-by-step implementation plan to refactor the `manual_slop` codebase from a single-agent linear chat into an asynchronous, 4-Tier Hierarchical Multi-Model Architecture. Phase 2 focuses on evaluating the Gemini CLI `conductor` extension itself and proposing architectural upgrades to enforce multi-tier, cost-saving, and context-preserving disciplines.
|
||||
|
||||
## 2. Functional Requirements
|
||||
|
||||
### Phase 1: `manual_slop` Implementation Planning
|
||||
- **Synthesis:** Read and synthesize all markdown files within the `./MMA_Support/` directory.
|
||||
- **Plan Generation:** Generate a detailed implementation plan (`plan.md`) for the `manual_slop` migration.
|
||||
- The plan must break down the migration into actionable sub-tracks or tickets (Epics and detailed technical tasks).
|
||||
- It must strictly follow the iterative safe-migration strategy outlined in `MMA_Support/Implementation_Tracks.md`.
|
||||
- The sequence must be:
|
||||
1. Tree-sitter AST parsing.
|
||||
2. State Machines.
|
||||
3. Linear Orchestrator.
|
||||
4. Tier 4 QA Interception.
|
||||
5. UI Decoupling.
|
||||
- Every ticket/task must include explicit steps for testing and verifying the implementation.
|
||||
|
||||
### Phase 2: Conductor Self-Reflection & Upgrade Strategy
|
||||
- **Evaluation:** Critically evaluate the `conductor` extension's architecture and workflows against the principles of the 4-Tier Architecture.
|
||||
- **Formal Proposal:** Deliver a formal proposal document within this track's directory (`proposal.md`).
|
||||
- **Format Research:** Investigate the optimal format for the proposal based on Google's documentation for extending or tuning Conductor.
|
||||
- **Content:** The proposal must address three core areas with equal priority:
|
||||
1. **Strict Memory Siloing & Token Firewalling:** How to reduce token bloat during Conductor's planning and execution loops.
|
||||
2. **Execution Clutch & Linear Debug Mode:** How to implement manual step-through or auto modes when managing complex tracks.
|
||||
3. **Multi-Model/Sub-Agent Delegation:** Design a system for internally delegating tasks (e.g., summarization, syntax fixing) to cheaper, faster models.
|
||||
|
||||
## 3. Acceptance Criteria
|
||||
- [ ] A fully populated `plan.md` exists within this track, detailing the `manual_slop` migration with Epics, detailed tasks, and testing steps.
|
||||
- [ ] A formal proposal document (`proposal.md`) exists within this track, addressing the three core areas for Conductor's self-improvement.
|
||||
- [ ] The proposal's format is justified based on official documentation or best practices for Conductor extensions.
|
||||
|
||||
## 4. Out of Scope
|
||||
- Actual implementation of the `manual_slop` refactor (this track is purely for planning the implementation).
|
||||
- Actual modification of the `conductor` extension's core logic.
|
||||
Reference in New Issue
Block a user