Workflows

Workflow Triggers

Run workflows manually today and prepare them for richer trigger models later.

Overview

Workflows turn a good run into a repeatable one. Each step should point to real execution, store output, and fail honestly when the underlying run fails.

Operator Note

Overseer works best when each layer stays explicit: the orchestrator routes, supervisors execute, tools return evidence, and traces show what actually happened.

Getting Started

Begin with short workflows that mirror a conversation you have already tested manually.

Configuration

Define step order carefully, inspect each workflow run, and avoid burying multiple responsibilities in one step.

Examples

workflow.json

{
  "name": "release-review",
  "steps": [
    "summarize packaging changes",
    "inspect trace output",
    "publish a release summary"
  ],
  "failure_policy": "fail_fast"
}

Next Steps

Continue with Viewing Traces or head back to the documentation home.