Conductor delegations

During a Conductor thread, the agent may delegate to a specialist — deeper authoring in the Definition or Study builder — then return control when the step is done.

You stay in charge. Delegation is not silent autopilot.

How delegation works

1. Conductor recognizes a step needs the full builder (complex code, heavy edits)

2. You see a delegation card — what will open, what the specialist will try

3. Accept to open the Definition Builder or study builder with context loaded

4. Specialist works — you can edit alongside

5. Signal I’m finished (or equivalent) to hand back to Conductor

I’m finished

When the builder work is done:

• Confirm I’m finished on the delegation card

• Conductor resumes — next collect, study, or pin proposal

• Saved changes are on the Definition/Study in your library

Skip the button if you already returned via the Conductor thread — follow the in-thread prompt.

Take over manually

Close delegation anytime. The artifact remains under Definitions or Studies. Continue solo or reopen Conductor later.

What good looks like

Conductor drafts an ORB definition, delegates a volume-filter fix you adjust in code, you click finished, Conductor queues collect without losing thread context.

Important distinctions

Delegation = temporary specialist mode inside Conductor.

Solo builder = you opened New definition without Conductor — no delegation card.

Terminal trading = not a delegation target.

Next

1. Conductor overview — start a thread

2. Example journeys — full loop stories

3. Definition Builder — where delegations open