manual_slop/conductor/tracks/mma_dashboard_visualization_overhaul/spec.md

Track Specification: MMA Dashboard Visualization Overhaul

Overview

Make the invisible backend operations visible and interactive. The current GUI is too barebones to effectively manage a multi-agent system. This track overhauls the MMA Dashboard to provide real-time insights into tracks, task dependencies, and agent streams.

Goals

1. Track Browser: Create a dedicated panel to view all tracks, their statuses, and overall progress metrics.
2. DAG Visualizer: Implement a visual representation (hierarchical list or node graph) of the current Track's tasks, clearly indicating status and blockers.
3. Live Output Streams: Ensure the GUI text boxes stream the output of Tier 1 (Planning), Tier 2 (Directing), and Tiers 3/4 (Executing) in real-time, tied precisely to their respective tasks.

Constraints

• Must be built natively using DearPyGui capabilities (e.g., node editor or nested tree nodes).
• Must be performant and not block the main rendering loop when updating live text streams.

Context & Origins

This track was born from the "Human Verification" phase of the initial MMA Orchestrator prototype (mma_orchestrator_integration_20260226). We realized that while the backend API plumbing for the hierarchical MMA tiers (Tiers 1-4) was technically functional, the product lacked the necessary state management, UX visualization, and human-in-the-loop security gates to be usable.

Key Takeaways from the Prototype Phase:

• The Tier 2 (Tech Lead) needs its own track-scoped discussion history, rather than polluting the global project history.
• Tasks within a track require a DAG (Directed Acyclic Graph) engine to manage complex dependencies and blocking states.
• The GUI must visualize this DAG and stream the output of individual workers directly to their associated tasks.
• We must enforce tiered context subsetting so that Tier 3/4 workers don't receive the massive global context blob, and we need a pre-spawn approval modal so the user can intercept, review, and modify worker prompts/contexts before they execute.

Instructions for the Implementing Agent: As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their spec.md files before concluding your run.

Execution Order & Dependencies

This is a multi-track phase. To ensure architectural integrity, these tracks MUST be executed in the following strict order:

1. MMA Data Architecture & DAG Engine: (Builds the state and execution foundation)
2. Tiered Context Scoping & HITL Approval: (Builds the security and context subsetting on top of the state)
3. [CURRENT] MMA Dashboard Visualization Overhaul: (Builds the UI to visualize the state and subsets)
4. Robust Live Simulation Verification: (Builds the tests to verify the UI and state)

Prerequisites for this track: Tiered Context Scoping & HITL Approval MUST be completed ([x]) before starting this track.