Orchestrator is a roadmap entry with no implementation and no repository behind it. It is listed here because the ecosystem does have a real coordination problem — work is dispatched to agents through Munera, executed by the Arcanada Agent System runtime, and routed to models through Model Connector, with no single layer that owns the hand-offs between them.
That layer is the concept. Until it is built, the honest description is that the pieces it would coordinate are the products that exist: Munera holds the tasks, the Agent System runs the agents, Model Connector routes the calls. If you are looking for something you can use today, those three are it.
- Status
- Planned — concept only
- Autonomy (AAL)
- L0 → L3
- Implementation
- None
- Repository
- None
Planned capabilities
Status not stated
- Concept only: no implementation, no repository
Current autonomy level
Weakest link
Nothing ships under this name. Munera holds the tasks, the Arcanada Agent System runs the agents and Model Connector routes the calls; the layer that would own the hand-offs between them does not exist yet.
Roadmap to L3
- Decide whether this belongs as a product or as a capability of an existing one.
- If it stays a product, give it an owner and a repository.
Next step
Review the plan and future launch gates
PLANNING does not mean availability or active development. The roadmap above is the next reference; no launch date is claimed.
Review the path to the target level