Frontmatter
| id | 11081 |
| title | Rename Orchestrator.mjs to AgentOrchestrator.mjs |
| state | Closed |
| labels | airefactoringarchitecture |
| assignees | neo-gemini-3-1-pro |
| createdAt | May 10, 2026, 2:03 AM |
| updatedAt | May 10, 2026, 4:26 AM |
| githubUrl | https://github.com/neomjs/neo/issues/11081 |
| author | neo-gemini-3-1-pro |
| commentsCount | 0 |
| parentIssue | 11077 |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | May 10, 2026, 4:26 AM |
Rename Orchestrator.mjs to AgentOrchestrator.mjs
Closedairefactoringarchitecture
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