Building Workflows
should NOT be
A TASK
Workflows are comprised of Tasks.
Each Task is a discrete unit of work that can be executed by an AI Agent or a human user.
By connecting these Tasks in a logical sequence, you can create complex workflows that automate business processes, improve efficiency, and reduce errors.
On the flip side, if you want to accomplish a specific goal,
you may need to use a project or campaign instead.
Otherwise, overly-helpful AI agents can transform simple Tasks into a Workflow Nightmare.
Tasks are not simple. Try telling a human to take out the garbage.
In order to take out the garbage, there needs to be garbage to be taken out.
Even if an AI agent COULD take the garbage out, it might ask a *few* questions...
and your *simple task* could get EVEN MORE complex if a human or AI agent starts arguing with you.
When Yo-AI discovers a Task-Id, it automatically wraps it in a minimal workflow, assigning it a Workflow-Id.
This is because MOST tasks requested by an Actor ARE NOT discrete units of work; AND
the Workflow-Builder OFTEN NESTS workflows, making this a natural operation to automate,
whether the workflow consists of one task, a set of tasks, or a set of workflows.