Book 3 · The Orchestrated OrganizationChapter 3

What Comes Next

This chapter runs deeper into protocol detail than any other in this volume, and an executive reader should know what to do with it. You do not need to evaluate the wire formats. You need three things from the material: the vocabulary to ask a vendor which of these mechanisms their product supports, the ability to recognize which team owns the handoff question when two systems meet, and the judgment to fund the work — because the failure mode this chapter describes is not technical, it is organizational, and the fix is a budget line. Skim the formats; read the failure modes.

Connect a development system to an operations system today and look at what actually crosses the wire. On the sending side, the development fleet has opened the pull request, run the tests, and produced a release candidate with a trace behind every change and a named person who approved the merge. On the receiving side is a different vendor’s product, with its own agents, its own identity provider, and its own owner. What passes between them, in the integrations I have seen so far, is a webhook: a task identifier, a commit SHA, and a bearer token that says the caller is allowed to call. Everything the sending system knows about why the release may go out — who approved it, what it may touch, when the approval expires, what evidence has to come back — stays behind, because the webhook has no field for any of it. The receiving system deploys on the strength of the token.

Most days nothing goes wrong. The problem is the day something does. The operations system cannot show that the instruction it followed was one the sender was entitled to give. The development system cannot show what was done with its instruction. And the person whose name is on the merge learns from the incident channel that a deployment happened under their approval, on a system they have never logged into, for reasons neither system recorded. The gap is a task that crosses a system boundary while the authority behind it stays home. Nothing on the market closes it for general work. One industry has closed it for one kind of work, and the way it did so is the most useful evidence there is about what everyone else is still missing.