Agents & Workflows
Agents & Workflows owns the definitions Merulan executes and the Runs they start. Agents define workers. Workflows link steps. Runs retain the work's state and result.
Boundary
Agents & Workflows owns execution, review gates, and recovery of stopped work. Work & Settings owns the Tasks and notices that help people coordinate it. Governance & Administration owns access and policy. A saved definition, an accepted launch, and a completed effect are separate facts. Choose the page that owns the fact you need to check.
Services
Agents & Workflows connects reusable definitions to readable execution. Start with the definition when deciding what may run. Start with the Run when deciding what happened.
| Service | Reader decision |
|---|---|
| Agents | Choose a worker's instructions, tool scope, and credential needs. |
| Workflows and blocks | Connect steps and understand their dependencies. |
| Runs and readback | Inspect the saved version, state, and result. |
| Reviews and repair | Decide waiting work or recover the stopped object. |
Start here
Use Build and launch work to take Agents & Workflows from a saved definition to a checked Run. The Console lists Agents at /workflows/agents, templates at /workflows/definitions, and Runs at /workflows/runs. Use Activity when the history crosses execution kinds.
The Agent creation contract owns exact creation fields. Use the API reference to check an HTTP call's permission, errors, and response. The Console guide explains how to reach the editors and work views.
Next steps
- Read Reviews and repair when Agents & Workflows has a waiting decision or stopped Run.
- Read Records & Lists for the Records an execution reads or changes.
- Read Labs & Modeling when a definition needs study against saved evidence.