Make your business process
something you can run.

Choose the model that fits the work

Your worker does what your system needs

A service task creates a job. Your worker activates matching jobs, performs the operation and reports completion or failure. It can be written in any language that can make the required HTTP requests.

Design business operations for safe retries. No lock expires: a job stays with the worker that activated it until that worker completes or fails it, or the server restarts. A network timeout does not tell you whether an external action already happened, so make each action idempotent on the job key.

From model to running process

1. Prepare a supported model and validate its task definitions.
2. Deploy it to your workspace.
3. Start an instance with the required variables.
4. Run workers for your service tasks.
5. Inspect progress and incidents. An instance in incident is restarted as a new instance; there is no resume route yet.

Check the current API contract for accepted model elements and payload formats before migrating existing processes.

Bring agent capabilities into a process

An agent can perform a bounded part of a wider process. Keep its inputs, expected outputs and approval requirements explicit. Use ACN when several agents need shared context and PAOL when you need coordinated agent orchestration.