manual_slop/conductor/tracks/mma_implementation_20260224/spec.md

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.