The Orchestrator

Every organization needs a visible path from technical novice to independent orchestrator, and the model that works is a residency under a senior orchestrator. A resident engineer is not a cheap programmer assigned to an agent; a resident engineer is somebody learning to understand and operate a delegated system, with a named senior orchestrator, a bounded system, a training plan, and a record of demonstrated capabilities.

The name is borrowed from medicine on purpose. Before anyone practices medicine independently, they go through a fairly arduous residency in a teaching hospital — supervised, on real patients, with attending physicians responsible for what the resident does. There is an honest debate about its abuses, the long hours above all: in 1984 an eighteen-year-old patient named Libby Zion died at New York Hospital, hours after being admitted through the emergency room, under the care of residents deep into a thirty-six-hour shift, and the investigation of her death produced the Bell Commission and, eventually, the eighty-hour weekly limits that now govern American residency programs.⁵ The lesson is not to import the hazing. It is that medicine stopped allowing independent practice without a long period of supervised real work — the one-year internship that once sufficed for general practice gave way to multi-year residencies — because the alternative was letting untested judgment loose on real patients.⁶ Something like that has to exist for orchestrators, because otherwise organizations have no way to develop people who can both orchestrate and maintain some level of objective independence from the tools making it all possible.

6.3.1 Months 0–2: technical foundation

The resident learns the system’s repository, services, APIs, data stores, deployment pipeline, permissions, dashboards, and runbooks, working read-only at first while tracing real requests, reading incident reports, inspecting pull requests, and reproducing failures in a test environment. By the end they should be able to answer, for their own system, the questions Marcus answered in section 12.2.2. What comes out is a system map and a list of unanswered questions, because nobody receives production authority merely for completing lessons.

6.3.2 Months 3–6: supervised operation

Now the resident starts observing production behavior alongside a senior orchestrator — investigating alerts, inspecting traces, comparing expected against actual outcomes, preparing proposed changes, and sitting in the review where a change is accepted or rejected. They can make reversible changes in a sandbox and then along a controlled production path, practicing how to change a prompt or instruction, add an evaluation case, narrow a tool permission, adjust a handoff, and roll back a release.

Throughout, the senior orchestrator asks the resident to explain the evidence before anyone discusses a solution, which is how the resident learns that a system can be wrong even when its JSON parses, its API returned 200, and its dashboard looks perfectly healthy.

6.3.3 Months 6–12: bounded authority

The resident now receives authority over a narrow workflow with the permission envelope written down: they can approve some changes, prepare others for a human, and must escalate anything involving new data, new permissions, new customer promises, or a newly regulated process.

They also run a weekly system review covering goals, incidents, unresolved questions, evaluation results, changes in context, authority requests, and the system’s own proposed improvements, while the senior orchestrator challenges their interpretation and checks whether the evidence actually supports the proposed action. Before the period ends, the resident must complete at least one improvement, one rollback, one incident analysis, and one handoff to another resident or specialist.

6.3.4 Months 12–24: qualification for independent orchestration

After a year some residents are ready for independent orchestration and others need longer, since the duration depends on the system’s risk, domain, and authority rather than on a universal clock.

The candidate presents a portfolio containing a system map, a goal and measurement plan, a delegation contract, an evaluation set, a decision record, an incident analysis, a rollback plan, and a handoff — and they have to demonstrate that they can narrow or stop a system rather than only expand one.

6.3.5 How senior orchestrators train residents

A senior orchestrator should not hand a resident nothing but easy tickets. The job is to give progressively larger responsibility while keeping a safe boundary around it, and at each step the senior orchestrator asks:

• What did the system assume?
• What should it have asked before proceeding?
• What information would change the decision?
• Which action is reversible?
• Which permission is broader than the goal requires?
• What would we see if this went wrong?
• Who is responsible for the consequence?

That is how a resident learns to improve the system’s questions rather than merely answer them.

6.3.6 Training for system improvement

The resident also has to learn how to help a system improve itself without ever letting the system grant itself authority. The improvement loop runs:

system observes a problem
→ system proposes a question or change
→ resident checks the evidence
→ specialist reviews the consequence
→ authorized person approves the boundary
→ system tests the change
→ resident monitors the result
→ the organization decides whether to keep it

The system contributes ideas and evidence. People retain authority over goals, permissions, and consequences.

---

5. Libby Zion, eighteen, was admitted to New York Hospital through the emergency room on the night of March 4, 1984, and died on the ward early the next morning while under the care of residents working extended shifts; the Bell Commission recommendations that followed (adopted by New York State in 1989) limited residents to eighty hours per week and twenty-four consecutive hours on duty, and the ACGME adopted similar limits nationally in July 2003. AHRQ PSNet, “Duty Hours and Patient Safety,” https://psnet.ahrq.gov/primer/duty-hours-and-patient-safety.↩︎

6. Through the mid-twentieth century most American general practitioners entered independent practice after medical school and a one-year rotating internship; specialty residencies displaced that path after World War II, and family medicine was approved as a specialty with three-year residencies in 1969. See “Where Have the Generalists Gone? They Became Specialists, Then Sub-Specialists,” The American Journal of Medicine blog, https://amjmed.org/where-have-the-generalists-gone-they-became-specialists-then-sub-specialists/. Cited to keep the medical analogy honest: supervised residency became the norm; it was not always the rule.↩︎