Problem
There is no interface for how to define a Workflow. Currently, all agents are actually workflows: Do start, Do LLM, Do Stop. This is not flexible and requires doing some strange things to make all workflows work, and doesn't allow dynamic invocation of Task Agents
Proposed solution
A workflow should be a known sequence of tasks that are scheduled and executed.
The Workflow Task itself keeps track of the current state, handles retries (via a script task), schedules the tasks and sets up dependencies between them.
This will likely require extending the task source interface to understand dependencies between tasks, so that we can have the Workflow Agent call "SetDependency" when scheduling the tasks, as well as understand "draft" vs "live" states. Remember this should be separated Bifrost itself, as it is only one of potentially many task sources that implements the interface
Alternatives considered
No response
Area
Orchestrator
Additional context
No response
Blocked
Problem
There is no interface for how to define a Workflow. Currently, all agents are actually workflows: Do start, Do LLM, Do Stop. This is not flexible and requires doing some strange things to make all workflows work, and doesn't allow dynamic invocation of Task Agents
Proposed solution
A workflow should be a known sequence of tasks that are scheduled and executed.
The Workflow Task itself keeps track of the current state, handles retries (via a script task), schedules the tasks and sets up dependencies between them.
This will likely require extending the task source interface to understand dependencies between tasks, so that we can have the Workflow Agent call "SetDependency" when scheduling the tasks, as well as understand "draft" vs "live" states. Remember this should be separated Bifrost itself, as it is only one of potentially many task sources that implements the interface
Alternatives considered
No response
Area
Orchestrator
Additional context
No response
Blocked