ADW Orchestration
Merlino orchestration + Thorbit ADW

Your workforce directs.
ADW executes.

A visual map of how the score is written, approved, conducted, checked, improved, and delivered inside Codex.

Follow the work ↓

One connected orchestra loop

  1. Dan + domain leadswrite their score sections
  2. Oliverfinalizes the score
  3. Mikegives GO
  4. Carlosconducts the approved score only
  5. Accountable ownersimplement bounded work
  6. Queenowns output QA
  7. Peteyowns process QA every PDCA cycle
  8. Both verdicts pass?decision gate
No

Carlos routes findings to accountable owners → owners correct → Queen + Petey rerun

Yes

Dan final engineering review + POWD → Oliver delivers to Mike

1 · DirectionCompose before anyone plays

Dan and domain leads write the score

Dan and domain leads write the scoreCONTROLMIKE↓DOMAIN LEADS↓DAN: PRD↓OLIVER: CONFIRM

Dan writes the engineering section and each domain lead writes the section they own. Oliver reconciles those sections into one final score. Mike reviews that score and gives GO before execution begins.

  • Dan plus domain leads author their own sections.
  • Oliver finalizes one coherent score.
  • Mike gives GO on the finalized score.
Carlos does not write or finalize the score. Carlos conducts the approved score.
2 · ConductCarlos is conductor only

One approved score becomes bounded work

One approved score becomes bounded workCONTRACTCARLOS: CONTRACT↓BOUNDED TASKS↓IMPLEMENTERS↓EVIDENCE

After Mike gives GO, Carlos dispatches the approved score, coordinates dependencies, collects evidence, and sends findings back to accountable owners. Carlos never performs the implementation, fix, output QA, or process QA.

  • Required reads and mutation boundaries travel with each task.
  • Accountable owners implement and correct their sections.
  • Carlos coordinates dependencies and evidence only.
Every claim points to a file, symbol, route, check, or artifact.
3 · OrchestraConditional specialists are always considered

Keymaker and Architect scale to each score

Keymaker and Architect scale to each scoreSETTINGSconfig.toml↓developer instructions↓hooks.json↓STOP GATE

Every score lists Keymaker and Architect explicitly, then assigns N/A, Consulted, or Owner from the work actually depicted. Conditional means their responsibility level changes. It never means either specialist disappears from the orchestra.

  • Keymaker: N/A only with no credential or auth work; Consulted for existing credential mapping.
  • Keymaker owns new, missing, moved, validated, rotated, scoped, or injected credentials and API/MCP auth design.
  • Architect: N/A for an approved lane, Consulted for unresolved or cross-machine placement, Owner for topology, network, DNS, ports, Tailscale, proxy, or persistent-service changes.
The depicted protected Vercel lane consults Keymaker for existing SSO and deployment credential mapping.
4 · ConvergenceTwo independent verdicts, every cycle

Queen checks output. Petey checks process.

Queen checks output. Petey checks process.LOOPIMPLEMENT↓REVIEW + TRACE↓QUEEN QA↻PDCA + DEBT

In every PDCA cycle, Queen owns output QA and records expectations before observing results. Petey independently owns process QA, checking whether the score, prompts, skills, workflows, agents, validators, hooks, routing, or SOPs must improve. Carlos waits for both verdicts and conducts the next correction wave.

  • Queen returns the evidence-backed output verdict.
  • Petey returns PROCESS CLEAN or assigns process changes.
  • Carlos routes every finding to its accountable owner.
A PDCA cycle cannot close until both output and process verdicts pass.
5 · Learning + ProofDaily learning closes the loop

Hermes feeds Petey. Oliver delivers.

Hermes feeds Petey. Oliver delivers.DELIVERYGATES PASS↓DAN: POWD↓OLIVER: DELIVERY↓MIKE: RESULT

Matteo Jr owns the Hermes runtime. As a continuous daily side input, Hermes analyzes Queen, Petey, and Carlos artifacts and sends Petey a ranked improvement queue. It is not a sequential delivery stage. After both QA verdicts pass, Dan completes engineering review and proof, then Oliver confirms the approved score and delivers to Mike.

  • Matteo Jr owns Hermes runtime health and delivery.
  • Hermes supplies Petey a daily ranked queue.
  • Oliver confirms the result against the score and delivers.
Hermes recommends. Petey evaluates. Accountable owners change canonical sources.