In From Cocoa to Chocolate, agents are specialists left to use their judgement. Some work cannot be left to judgement. This piece covers the Business Process Studio, the factory’s fixed recipe: the place where a process is laid out once and then runs the same way every time.
Judgement, or a fixed recipe
Some work should be left to an agent’s judgement: a question that could be asked a hundred ways, an answer that depends on what the person needs. Other work must happen the same way every time, in the same order, with the same checks.
A factory does not leave that second kind of work to whoever is on shift. It uses a fixed recipe. Chocolate Factory uses the Business Process Studio.
One of the ways an agent goes wrong is by skipping a rule. Instructions can ask an agent to follow a business rule, but a rule written as a step in a process is followed because the process cannot continue without it. Where a rule must never be skipped, it belongs in the recipe.
Left to an agent
Flexible work
- The agent decides how to answer
- Steps can vary with each request
- Tuned through its instructions, knowledge and tools
Laid out in the Studio
Fixed work
- The same steps, in the same order, every time
- The same checks on every run
- Changed only by saving a new version
Lay a process out once
In the Studio, a process is drawn as a flowchart: a trigger that starts it, then agents, tools and decisions, each step with its own inputs.
- Trigger
- Agent step
- Tool call
- Decision
- Response
Paths can split on conditions, and each connection says when it is followed: always, on success, or on failure. A failure is not an accident the process stumbles into. It is a path someone drew in advance.
The Studio offers nine kinds of step, from triggers and agent steps to tool calls, thinking steps, branches, responses and outputs. Together they cover the shapes a business process actually takes.
Draw it, or describe it
A team can name a workflow and build it step by step on an empty canvas. Or it can describe in words what the workflow should do and let AI write the first draft, using the business’s connected apps. The draft opens straight into the editor for people to refine.
Because the draft uses the business’s connected apps, it can include the steps that reach the systems the process actually runs on. Either way, people decide what the finished process looks like. An AI draft is a starting point, and like any other version it does not run until someone decides it should.
People where the risk is real
A workflow can stop for a person. Steps that carry risk are routed to a named approver before the process continues, while routine paths run on their own. The business decides where that line sits.
This is the factory’s quality assurance stage: human approval on the steps that carry risk. Not every step needs a person. The ones that do are named, and so is the person.
Risky steps wait for a named approver. Routine paths run on their own. The business draws the line between them.
Every save kept, nothing runs until you say so
Each saved change becomes a version, and the earlier versions are kept. A new version does not run until someone decides it should, so a process can be changed with confidence and traced back if needed.
AI is never finished, and neither are the processes around it. Rules shift, and a process has to shift with them. Versions mean a change is a decision someone made, at a point that can be found again, rather than an edit nobody can trace.
Agents can use it as a tool
A workflow is not only something people trigger. An agent can call it as a tool, so a flexible conversation can hand off to a fixed, approved process at exactly the point where the steps must not vary.
That joins the two kinds of work. The agent handles the conversation. The workflow handles the part that has to be done by the recipe.
It also means a process is written once and reused. Every agent that needs that process calls the same approved workflow, rather than each one being asked to follow the steps from its own instructions. When the process changes, it changes in one place, as a new version.
A complete record of every run
Every run is recorded step by step, and any run can be replayed and walked through in order.
What every run records
- What went into each step
- What came out of each step
- How long each step took
- Which version of the workflow ran
- Whether the run finished
When something goes wrong, the record shows the step responsible. The team changes that step, and the change becomes a new workflow version that runs only when the team says so. Nothing has to be rebuilt.
What it changes
Business teams decide which steps need a person, and lay out the processes they understand best. Risk, security and compliance get control they can point to: risky workflow steps wait for a named approver, every change is a kept version, and every run has a full record.
The recipe card is written once, followed every time, and changed only on purpose. The full feature set is on the Workflows page.
The short version
- A process is drawn once as a flowchart, by hand or from an AI draft.
- Steps that carry risk wait for a named approver.
- Every save is kept as a version, and nothing runs until someone decides it should.
- Agents can call a workflow as a tool, and every run is recorded and can be replayed.



