# MMA Hierarchical Delegation: Recommended Architecture

## 1. Overview
The Multi-Model Architecture (MMA) utilizes a 4-Tier hierarchy to ensure token efficiency and structural integrity. The primary agent (Conductor) acts as the Tier 2 Tech Lead, delegating specific, stateless tasks to Tier 3 (Workers) and Tier 4 (Utility) agents.

## 2. Agent Roles & Responsibilities

### Tier 2: The Conductor (Tech Lead)
- **Role:** Orchestrator of the project lifecycle via the Conductor framework.
- **Context:** High-reasoning, long-term memory of project goals and specifications.
- **Key Tool:** `mma-orchestrator` skill (Strategy).
- **Delegation Logic:** Identifies tasks that would bloat the primary context (large code blocks, massive error traces) and spawns sub-agents.

### Tier 3: The Worker (Contributor)
- **Role:** Stateless code generator.
- **Context:** Isolated. Sees only the target file and the specific ticket.
- **Protocol:** Receives a "Worker" system prompt. Outputs clean code or diffs.
- **Invocation:** `.\scripts
un_subagent.ps1 -Role Worker -Prompt "..."`

### Tier 4: The Utility (QA/Compressor)
- **Role:** Stateless translator and summarizer.
- **Context:** Minimal. Sees only the error trace or snippet.
- **Protocol:** Receives a "QA" system prompt. Outputs compressed findings (max 50 tokens).
- **Invocation:** `.\scripts
un_subagent.ps1 -Role QA -Prompt "..."`

## 3. Invocation Protocol

### Step 1: Detection
Tier 2 detects a delegation trigger:
- Coding task > 50 lines.
- Error trace > 100 lines.

### Step 2: Spawning
Tier 2 calls the delegation script:
```powershell
.\scripts
un_subagent.ps1 -Role <Worker|QA> -Prompt "Specific instructions..."
```

### Step 3: Integration
Tier 2 receives the sub-agent's response.
- **If Worker:** Tier 2 applies the code changes (using `replace` or `write_file`) and verifies.
- **If QA:** Tier 2 uses the compressed error to inform the next fix attempt or passes it to a Worker.

## 4. System Prompt Management
The `run_subagent.ps1` script should be updated to maintain a library of role-specific system prompts, ensuring that Tier 3/4 agents remain focused and tool-free (to prevent nested complexity).