# Track Specification: MMA Orchestrator Integration

## Overview
Implement the full hierarchical orchestration loop, connecting Tier 1 (PM) strategic planning with Tier 2 (Tech Lead) tactical ticket generation. This track will enable the GUI to autonomously break down high-level user 'Epics' into actionable tracks and tickets, and manage their execution through the multi-agent system.

## Goals
1. **Tier 1 Epic Planning:** Implement the logic for the Orchestrator to analyze project state and user requests to generate Implementation Tracks.
2. **Tier 2 Ticket Dispatcher:** Enable the Tech Lead to take a Track Brief and generate a Directed Acyclic Graph (DAG) of worker tickets.
3. **GUI Orchestrator Loop:** Create the 'main thinking loop' in gui_2.py that manages the transition between planning and execution.
4. **Project History Integration:** Ensure that completed tracks and tickets are properly summarized and stored in the project's persistent memory.

## Technical Scope
- **Prompt Engineering:** Finalize and integrate the Tier 1 and Tier 2 system prompts from mma_prompts.py.
- **Backend Plumbing:** Extend multi_agent_conductor.py to handle track generation and ticket dispatching.
- **UI Interaction:** Connect the 'New Project/Epic' button to the Tier 1 generator and the 'Start Track' button to the Tier 2 dispatcher.
- **State Management:** Implement the transition logic between 'Strategic Planning', 'Tactical Dispatching', and 'Worker Execution' states.

## Constraints
- **Hierarchy Enforcement:** All planning must flow from Tier 1 to Tier 2, and all execution from Tier 2 to Tiers 3/4.
- **Token Firewalling:** Use scripts/mma_exec.py for all tiered sub-agent calls.
- **HITL Verification:** Maintain Step Mode capabilities for each transition (Planning -> Dispatching -> Execution).