Skip to content
Back to flagship systems

Orchestration · Flagship case study

OrchestratorX

Routing as a testable invariant, not a prompt.

A supervisor-pattern multi-agent framework that keeps routing in typed state and plain Python so execution order can be tested without a model or API key.

Inspect repository

Problem

When routing, retry behaviour, and completion rules live inside prompts, the most important system behaviour becomes probabilistic and difficult to explain after a run.

Architectural decision

A single supervisor owns every transition. Specialists return to the supervisor, never directly to one another, and every hop is written to an audit trace.

Execution topology

  1. 01

    Request

  2. 02

    Supervisor

  3. 03

    Specialist

  4. 04

    Verification

  5. 05

    Recorded result

Engineered invariants

  • Only the supervisor selects the next node.
  • Required specialists run before reporting.
  • A hop budget guarantees termination.
  • Failures remain visible in the ordered trace.
  • Concurrent runs isolate breaker state by run identifier.

Boundaries stated plainly

  • — Reference architecture, not evidence of a customer production deployment.
  • — Business-specific escalation policy must be supplied by the adopting organisation.
  • — Operational SLOs require measurement in the target environment.

Enterprise adoption path

  1. 01Connect organisation-specific tools.
  2. 02Define escalation and approval policy.
  3. 03Add production telemetry and service objectives.