A Recipe is persisted automation dispatched to a deterministic native execution. AgentMQ’s workflow engine remains the scheduler and execution owner; the private Recipe runtime maintains domain state and receipts.
Why Recipes are separate
Workflow YAML describes execution. Recipe state describes the durable automation product behavior around that execution. Keeping the two separate prevents an internal scheduler or queue from creating a second source of truth.
Boundaries
/v1/internal/recipes/dispatchand/v1/internal/recipes/runtimeare private bridges, not developer endpoints.- A Recipe does not bypass application authorization, service connection limits, idempotency, or human approval.
- The presence of a retained adapter does not make an unfinished channel or transport public.