chore(conductor): Setup file structure for MMA Orchestrator Integration track

conductor/tracks/mma_orchestrator_integration_20260226/index.md

@@ -0,0 +1,8 @@
+# MMA Orchestrator Integration
+
+This track implements the full hierarchical orchestration loop, connecting Tier 1 (PM) strategic planning with Tier 2 (Tech Lead) tactical ticket generation.
+
+### Navigation
+- [Specification](./spec.md)
+- [Implementation Plan](./plan.md)
+- [Previous Track: MMA Core Engine Implementation (Archived)](../../archive/mma_core_engine_20260224/index.md)

conductor/tracks/mma_orchestrator_integration_20260226/metadata.json

@@ -0,0 +1,6 @@
+{
+  "id": "mma_orchestrator_integration_20260226",
+  "title": "MMA Orchestrator Integration",
+  "status": "in-progress",
+  "created_at": "2026-02-26T22:04:00.000000"
+}

conductor/tracks/mma_orchestrator_integration_20260226/plan.md

@@ -0,0 +1,42 @@
+# Implementation Plan: MMA Orchestrator Integration
+
+## Phase 1: Tier 1 Strategic PM Implementation
+- [ ] Task: PM Planning Hook
+    - [ ] Create `orchestrator_pm.py` to handle the Tier 1 Strategic prompt.
+    - [ ] Implement the `generate_tracks(user_request, repo_map)` function.
+- [ ] Task: Project History Aggregation
+    - [ ] Summarize past track results to provide context for new epics.
+
+## Phase 2: Tier 2 Tactical Dispatcher Implementation
+- [ ] Task: Tech Lead Dispatcher Hook
+    - [ ] Create `conductor_tech_lead.py` to handle the Tier 2 Dispatcher prompt.
+    - [ ] Implement the `generate_tickets(track_brief, module_skeletons)` function.
+- [ ] Task: DAG Construction
+    - [ ] Build the topological dependency graph from the Tech Lead's ticket list.
+
+## Phase 3: Guided Planning UX & Interaction
+- [ ] Task: Strategic Planning View
+    - [ ] Implement a "Track Proposal" modal in `gui_2.py` for reviewing Tier 1's plans.
+    - [ ] Allow manual editing of track goals and acceptance criteria (Manual Curation).
+- [ ] Task: Tactical Dispatcher View
+    - [ ] Implement a "Ticket DAG" visualization or interactive list in the MMA Dashboard.
+    - [ ] Allow manual "Skip", "Retry", or "Re-assign" actions on individual tickets.
+- [ ] Task: The Orchestrator Main Loop
+    - [ ] Implement the async state machine in `gui_2.py` that moves from Planning -> Dispatching -> Execution.
+- [ ] Task: Project Metadata Serialization
+    - [ ] Persist the active epic, tracks, and tickets to `manual_slop.toml`.
+
+## Phase 4: Product Alignment & Refinement
+- [ ] Task: UX Differentiator Audit
+    - [ ] Ensure the UX prioritizes "Expert Oversight" over "Full Autonomy" (Manual Slop vs. Gemini CLI).
+    - [ ] Add detailed token metrics and Tier-specific latency indicators to the Dashboard.
+
+## Phase 5: Exhaustive Testing & Regression
+- [ ] Task: Headless Engine Verification
+    - [ ] Create `tests/test_orchestration_logic.py` to verify Tier 1 -> Tier 2 -> Tier 3 flow without a GUI.
+    - [ ] Verify DAG resolution and error handling (e.g., blocked tickets).
+- [ ] Task: Visual Verification Suite
+    - [ ] Create `tests/visual_orchestration_verification.py` using `ApiHookClient`.
+    - [ ] Simulate a full "Epic" lifecycle: User Prompt -> Track Review -> Ticket Generation -> Execution.
+- [ ] Task: Core Regression Suite
+    - [ ] Run all existing MMA, Conductor, and GUI tests to ensure no regressions.

conductor/tracks/mma_orchestrator_integration_20260226/spec.md

@@ -0,0 +1,21 @@
+# 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).