RFC: Orchestrator

[jmatejcz]

Is your feature request related to a problem? Please describe.
Orchestrator that will listen to ros topics (for example user topic) for new tasks. When new task comes, it will be added to task queue.

Task can be interuppted (agent should be chekpointed? ) and new agent should start new task with higher prio.
Then previous agent can be brought back to continue previous task.

Every task is executed by new agent.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[rachwalk]

I am appending some diagrams which were prepared some time ago (back at RAI1) so they may be a little out-of-date, but serve as a certain useful point to attempt to understand what interfaces and behaviours are expected for the Orchestrator.

The class diagrams regarding what informations should be included in tasks.... I think at this point Atomic Execution Unit can be considered equivalent to a Tool Call

What follows are simple flow diagrams regarding the execution patterns expected to be able to be orchestrated:

And some architectural diagrams and more class definitions

As I've mentioned these may be partially out of date, however still interesting to be considered.

Additionally I think that given RAI 2.0 everything-is-agent ideology, I think it would be beneficial to make the Orchestrator fulfill the Agent API. This would allow it to use Connectors, and that way connect with everything else.