Fixer orchestrator relationship

README.md

@@ -4,6 +4,10 @@
 
 **A lightweight, powerful agent orchestration plugin for OpenCode**
 
+<a href="https://x.com/alvinunreal" target="_blank" rel="noopener noreferrer">
+  <img src="https://img.shields.io/badge/Follow%20%40alvinunreal-000000?style=for-the-badge&logo=x&logoColor=white" alt="Follow @alvinunreal on X" />
+</a>
+
 <img src="img/team.png" alt="The Pantheon - Agent Team" width="600">
 
 *Transform your AI assistant into a manager capable of delegating complex tasks to specialized sub-agents, running searches in the background, and managing multi-step workflows with ease.*

src/agents/orchestrator.ts

@@ -126,6 +126,22 @@ When delegating tasks:
 - **Token efficiency**: Large content pastes waste tokens, degrade performance, and can hit context limits
 - **Clear instructions**: Give specialists specific objectives and success criteria
 
+### Fixer-Orchestrator Relationship
+The Orchestrator is intelligent enough to understand when delegating to Fixer is
+inefficient. If a task is simple enough that the overhead of creating context
+and delegating would equal or exceed the actual implementation effort, the
+Orchestrator handles it directly.
+
+The Orchestrator leverages Fixer's ability to spawn in parallel, which
+accelerates progress toward its ultimate goal while maintaining control over the
+execution plan and path.
+
+**Key Principles:**
+- **Cost-benefit analysis**: Delegation only occurs when it provides net efficiency gains
+- **Parallel execution**: Multiple Fixer instances can run simultaneously for independent tasks
+- **Centralized control**: Orchestrator maintains oversight of the overall execution strategy
+- **Smart task routing**: Simple tasks are handled directly; complex or parallelizable tasks are delegated
+
 ---
 
 ## Phase 4: Parallelization Strategy