Expand description
Orchestrator: coordinates the Ouroboros lifecycle for user messages.
The orchestrator is the “brain” that runs the Ouroboros protocol. Given a user message:
- Conduct the interview (ask clarifying questions if needed)
- Generate a seed (via LLM for complex tasks, or ad-hoc for simple tasks)
- Execute the agent via the supervisor
- Return the result to the user
The orchestrator does NOT know about channels or HTTP — it only coordinates Ouroboros + Supervisor + EventBus + StateStore + Scheduler + AccessManager.
Structs§
- Orchestration
Result - Result of a full orchestration cycle.
- Orchestrator
- The orchestrator coordinates the full Ouroboros lifecycle.
- SubTask
- A subtask within a multi-agent plan.
Enums§
- Agent
Role - Role of an agent within a group.