AI-DLC 2.0Workflows, explained

Home / Lesson 4 of 6

The Orchestrator

The big ideaThe orchestrator is the project lead: it owns the goal, picks and orders the stages for this particular job, watches the run, and enforces the rules that span every stage.

Video, 2:39. On-screen captions are built in.

Stages are good at one thing each. Something has to decide which stages run, in what order, with what inputs, and what to do when one gets stuck. That is the orchestrator. It reads each stage’s declared metadata to decide:

  • Inputs and outputs (Compartment 1): what each stage consumes and produces.
  • Purpose: what transformation or validation the stage performs.
  • Orchestrator hints: sequencing constraints, conditional triggers, escalation policies.

a. Goal ownership

Owns the end-to-end objective. It never hands goal-tracking to a single stage; it checks the combined output still matches the original intent.

b. Workflow composition

Builds a workflow for this job. Greenfield, bug fix and refactor get different sequences. The plan is mutable and adapts as it runs.

c. Routing, observability, control

Feeds each stage the right inputs, tracks state, enforces halting conditions, handles escalations (pause, ask a human, resume) and keeps a full audit trail.

d. Abstraction boundary

Treats each stage as a black box. It only checks the declared post-conditions were met, so stages can evolve independently.

e. Cross-stage invariants

Some rules span everything: naming conventions, security policies, documentation standards. The orchestrator checks these at checkpoints.

Try it: watch the orchestrator compose a workflow

Choose the kind of work and the context. The orchestrator assembles a different plan each time instead of running a fixed pipeline.

    Cross-stage invariants checked at every checkpoint: Naming conventionsSecurity policiesDocumentation standards

    Illustrative only: the specification does not prescribe these stage names. It says the intent, available context, runtime signals and customer-authored stages shape the plan.

    Try this at work

    Think of the orchestrator as a general contractor: it does not lay bricks, but it decides who works when, checks each trade's work against the contract, and keeps the paper trail.

    Want the original wording? Read Section 4 of the specification.

    Quick check

    Three questions. Get them all right to mark this lesson done.

    Q1. A codebase already has comprehensive documentation. What may the orchestrator do?

    Q2. What does “abstraction boundary” mean here?

    Q3. Who enforces a rule like “follow our naming conventions everywhere”?