You describe the process
Two sentences is enough. A person reads it.
A teardown is our written review of one of your processes. We measure its volume and exception rate, and say whether an agent is worth building. You keep the document, even if the work stops there.
Your deployment would run on Gatehouse, our control plane.
Two sentences is enough. A person reads it.
On one call, we check the process against scope, role, limits, review and seal. We mark what an agent would do, what a person keeps, and where the agent must stop and ask.
A written map of the scope, the limits, and who decides when the agent stops. It ends with a verdict, which can be that this process is not worth automating yet.