conductor(checkpoint): Phase 1: Setup and Architecture complete

conductor/workflow.md

@@ -365,6 +365,9 @@ To emulate the 4-Tier MMA Architecture within the standard Conductor extension w
 
 ### 1. Active Model Switching (Simulating the 4 Tiers)
 - **Activate MMA Orchestrator Skill:** To enforce the 4-Tier token firewall explicitly, invoke `/activate_skill mma-orchestrator` (or use the `activate_skill` tool) when planning or executing new tracks.
+- **Tiered Delegation (MMA Protocol):**
+    - **Tier 3 Worker (Implementation):** For significant code modifications (e.g., refactoring large scripts, implementing complex classes), delegate to a stateless sub-agent via `.\scripts\run_subagent.ps1 -Prompt "Modify [FILE] to implement [SPEC]..."`. Avoid performing heavy implementation directly in the primary context.
+    - **Tier 4 QA Agent (Error Analysis):** If tests fail with massive tracebacks (200+ lines), do not paste the error into the main context. Use `.\scripts\run_subagent.ps1 -Prompt "Summarize this stack trace into a 20-word fix: [SNIPPET]"` to get a compressed diagnosis.
 - **Phase Planning & Macro Merges (Tier 1):** Use high-reasoning models (e.g., Gemini 1.5 Pro or Claude 3.5 Sonnet) when running `/conductor:setup` or when reviewing a major phase checkpoint.
 - **Track Delegation & Implementation (Tier 2/3):** The MMA Orchestrator skill autonomously dispatches Tier 3 (Heads-Down Coding) tasks to secondary stateless instances of Gemini CLI (via `.\scripts\run_subagent.ps1 -Prompt "..."`) rather than performing heavy coding directly in the main thread.
 - **QA/Fixing (Tier 4):** If a test fails with a massive traceback, **DO NOT** paste the traceback into the main conductor thread. Instead, the MMA Orchestrator skill instructs you to spawn a fast/cheap model sub-agent (via a shell command) to compress the error trace into a 20-word fix, keeping the main context clean.
@@ -372,3 +375,4 @@ To emulate the 4-Tier MMA Architecture within the standard Conductor extension w
 ### 2. Context Checkpoints (The Token Firewall)
 - The **Phase Completion Verification and Checkpointing Protocol** is the project's primary defense against token bloat.
 - When a Phase is marked complete and a checkpoint commit is created, the AI Agent must actively interpret this as a **"Context Wipe"** signal. It should summarize the outcome in its git notes and move forward treating the checkpoint as absolute truth, deliberately dropping earlier conversational history and trial-and-error logs to preserve token bandwidth for the next phase.
+- **MMA Phase Memory Wipe:** After completing a major Phase, use the Tier 1/2 Orchestrator's perspective to consolidate state into Git Notes and then disregard previous trial-and-error histories.