Processes Overview

Processes track multi-step workflows. Each process defines a series of steps — some automated, some requiring human input. Use processes to give operators visibility into where things stand.

Process Lifecycle

Created (running)
    |
    +---> Steps progress (step_started -> step_completed)
    |
    +---> Completed (all steps done)
    |
    +---> Failed (error occurred)

Process Model

Field	Type	Description
`process_id`	string	Unique identifier (UUID)
`namespace`	string	Org-qualified namespace (e.g., `orgId.deployments`)
`name`	string	Display name
`description`	string	Optional description
`status`	string	`running`, `completed`, `failed`
`current_step`	string	Key of the currently active step
`step_defs`	array	Step definitions
`timeline`	array	Step execution history
`task_ids`	array	IDs of linked tasks
`started_at`	string	ISO 8601 timestamp
`completed_at`	string	ISO 8601 timestamp (when completed)

Linking Tasks to Processes

When creating a task, include process_id and process_step to link it to a process. When the task completes, the process step auto-completes with a step_completed event.

{
  "title": "Approve release",
  "process_id": "proc-uuid",
  "process_step": "approval",
  "steps": [...]
}