Approval gates are a design decision, not a safety net
Where you put the human changes what the process can be trusted to do unattended.
Writing
What we're learning as we build the platform and put the first processes live. Technical where it needs to be.
Featured · Engineering · 9 min
A single agent holding an entire workflow in its context is easy to demo and hard to operate. Breaking the process into named phases gives you somewhere to put an approval gate, a retry policy and a cost measurement.
Where you put the human changes what the process can be trusted to do unattended.
One model for the whole process is a cost decision disguised as a simplicity decision.
The questions are older than the technology, and the answers have to be in the logs.
Anything else can be made to look good in a pilot that never reaches production scale.
The handoff is the interesting part, and most of the failure modes live in it.
The processes were already written down. Nothing would follow them faithfully.
New writing and platform notes. No drip campaign.