Supervisor Concepts

Supervisors are where Overseer turns routing decisions into controlled execution.

Why Supervisors Exist

The orchestrator decides where work should go. The supervisor owns what happens next. It is responsible for domain-specific execution, tool use, and returning a structured result instead of ambiguous assistant prose.

Supervisor Contract

A healthy supervisor returns status, summary, evidence, artifacts, and failure details. That contract is what lets Overseer distinguish verified work from plausible-sounding work.

{
  "status": "completed",
  "summary": "Generated the requested chart from provided data.",
  "evidence": ["chart SVG produced", "input series parsed successfully"],
  "artifacts": ["chart.svg"],
  "verified": true,
  "error": null
}

Evidence Over Prose

If a supervisor cannot prove the work happened, it should return an unverified or failed result. This is one of the core anti-hallucination rules in Overseer.

Domain Shape

Supervisors should map to real domains such as research, workflow analysis, or desktop execution. Keep them stable enough that the orchestrator can route confidently.

Next Steps

Continue with Creating Supervisorsand then review Delegation Patterns.