What is an orchestrant?
An orchestrant is the person who understands the agents behind the agents: an advisory and service role that sets up and reads the vendor chains an organisation's work runs on, several specialised subcontractors deep, and keeps every link in them accountable.
Today an enterprise architect sets up the toolchains an organisation works with, and a procurement buyer decides which vendors get in. An orchestrant is both roles one layer deeper, for the time when every role and every domain works through AI. Each vendor's agents run on other vendors' agents, with specialised subcontractors several layers down, so the question is no longer which tool a team uses but what is actually doing the work behind it. The orchestrant maps those chains, checks what a vendor's guarantees really cover, and notices where responsibility changes hands before anyone finds out the hard way. It is an advisory and service role, like a developer or a designer: the orchestrant sets the ensemble up and reads it, and the deliberators who own the judgment decide. The deeper the chains run, the more a deliberator's judgment rests on the orchestrant's map of what is behind it.
As in
"Our orchestrant found two more subcontractors behind the translation agent, so the quote went up, and honestly I felt better about it."
The closest thing today
The nearest things today are enterprise architecture and procurement, which set up a company's toolchains and vet its vendors, and the platform teams that have started issuing AI agents identities and permissions of their own. None of them yet reads what runs behind a contracted agent, vendor by vendor.
