Context
The ai/agent/Orchestrator.mjs is colliding conceptually and nominally with the daemon orchestrator (ai/daemons/Orchestrator.mjs).
The Problem
Namespace collision creates confusion between the agent-side coordination layer and the daemon-side maintenance supervisor, especially as we elevate the daemon orchestrator in Epic #11077.
The Architectural Reality
The agent-side orchestrator manages agent lifecycle and routing, while the daemon-side manages background tasks. They exist in different substrates (ai/agent/ vs ai/daemons/).
The Fix
Rename ai/agent/Orchestrator.mjs to ai/agent/AgentOrchestrator.mjs. Update all references, imports, and tests accordingly.
Acceptance Criteria
Out of Scope
- Refactoring the internal logic of
AgentOrchestrator.
Related
Context
The
ai/agent/Orchestrator.mjsis colliding conceptually and nominally with the daemon orchestrator (ai/daemons/Orchestrator.mjs).The Problem
Namespace collision creates confusion between the agent-side coordination layer and the daemon-side maintenance supervisor, especially as we elevate the daemon orchestrator in Epic #11077.
The Architectural Reality
The agent-side orchestrator manages agent lifecycle and routing, while the daemon-side manages background tasks. They exist in different substrates (
ai/agent/vsai/daemons/).The Fix
Rename
ai/agent/Orchestrator.mjstoai/agent/AgentOrchestrator.mjs. Update all references, imports, and tests accordingly.Acceptance Criteria
ai/agent/Orchestrator.mjsrenamed toAgentOrchestrator.mjs.Out of Scope
AgentOrchestrator.Related