The intro chapter recovered the vocabulary of storytelling. This chapter establishes the architectural moment at which an operation comes into being and the architectural moment at which it ceases. The two boundaries together define what an operation is as a unit, what role it plays, and what freedom that role grants the performer who inhabits it.
Instructions on Paper
Coordinated activity runs on instructions written down. A shopping list, a to-do list, a punch list. A shift handoff at the hospital, a standard operating procedure taped inside a cabinet door. A recipe, a training manual, a checklist for a surgeon or a pilot or a building inspector. A project plan, a design specification, a blueprint, an assignment memo. A contract, a request for proposal. A play script, a screenplay, a sheet of music, a keynote text on a lectern. A corporate mission statement, a code of conduct, a professional standard of practice. A constitution, a statute, a treaty between nations.
These are not a random assortment. They are members of a single family. Each is authored before the work begins. Each is handed off to the people who will perform against it. Each governs what happens next, within the latitude its author built into it. Each can be changed only by authoring another script — a rewrite, a revision, an amendment — and handing it off the same way the original was handed off. Each serves something larger than itself — the errand, the shift, the renovation, the surgery, the building, the performance, the company's purpose, the republic. What any given member contains varies with its work, but the content is drawn from a small set of universal categories — goals, rules, instructions, standards, examples, context, definitions, scope, conditions, schedules, roles, resources, and references. Every reader has encountered dozens of members of this family across their working and civic life, under dozens of different names. The family has no name in common use, because its universality made the name unnecessary. Everyone knew what these things were without needing a word for the category.
An input script is the architectural term for what every member of this family is. The term names the role these documents play, not any particular format or scale. A shopping list is an input script. A constitution is an input script. The range between them is continuous. What separates a shopping list from a constitution is the scale of the work governed, the stakes of the performance, and the formality of the authoring — not the architectural role the document plays.
A non-human performer capable of working from input scripts is a recent addition to the family. The architectural shape of the family did not change. What changed was the appearance of performers who are not human and who can still receive an authored script and act on it. The family expanded to include them; nothing about how the family works at the architectural level was disturbed.
The Input Boundary
Every input script crosses a boundary when it is passed from the author to the performer. Before the transfer, the document is being authored — drafted, revised, argued over. At the handoff, the document crosses out of the author's hands and into the performer's. What was transferred is what the operation will run against. The crossing is sharp. There is no partial handoff; the document is either across the boundary or it is not.
After the crossing, the author cannot reach into the operation and revise the document in place. The shopping list, once in the errand-runner's pocket, is not editable from the kitchen. The design specification, once handed to fabrication, is not editable from the engineer's desk. The constitution, once ratified, is not editable from the drafters' desks. The only way to change what governs the operation is to author another script — a rewrite, a revision, an amendment — and hand it off to the actor who will work from it. A rewrite is an input script. A revision is an input script. An amendment is an input script. Every change produces another script: producing a new version is itself an act of authoring, and what it produces is itself a member of the family, handed off the same way every other member is.
The input boundary appears anywhere authoring ends and performance begins. It is the one universal feature of every operation. Without an input, there is no operation — only authoring that never crossed the boundary.
The Output Boundary
Most operations produce something at the end. The errand-runner returns with the bag of groceries. The punch list comes back with everything checked. The fabrication shop delivers the as-built drawings. The contract is signed and exchanged. The committee submits its report. The bill passes and is filed. The verdict is returned. The defendant's case is heard, and the judgment is entered. Every reader recognizes these as completions in the ordinary sense — the work the script seeded, now done, handed off to whoever was waiting for it.
A completion is the architectural term for what every member of this family is. The crossing is delivery. Before delivery, the work is in progress; the performer is still doing it, still adjusting, still able to revise what has been produced. At delivery, what was produced crosses out of the performer's hands and into the world — into the orchestrator's hands, or the next performer's, or the public's. The crossing is as sharp as the input boundary's. A completion is delivered or it is not; there is no partial delivery, only work still in progress.
Not every operation produces a completion. A monitoring operation runs continuously, observing some condition, with no intent of ever delivering a finished thing. Its purpose is not to complete; its purpose is to be — to keep running, to keep watching, to remain available. A waiting operation holds until a condition is met and may terminate without delivering anything; the condition was not met before the operation was stopped, or the wait was itself the work, or the circumstances changed and the wait was no longer needed. A standing post, a vigil. These operations have an input boundary — they were initiated against some script — but no completion in the ordinary sense. They are bounded operations whose bound on the output side is termination rather than delivery.
The output boundary is the typical shape of an operation, not the universal one. The input boundary is universal because every operation begins. The output boundary is typical because most operations end by delivering something, but some end by simply stopping.
The Role
The two boundaries together establish what the performer is to be for the duration of the operation. The input script defines the role. When a role calls for a product, completion delivers it. Until the performance ends, the performer holds the role.
A role, in the recovered sense the intro chapter established, is not a job description. A role is what a performer takes on and inhabits — the character in the play, the position on the team, the office in the institution, the part in the mission. A role specifies what the performer is doing while they hold it, what they are responsible for, what latitude they have, what standards they will be judged against. A role is held for a duration; it begins when the performer takes it on and ends when the role is no longer being held. Every reader has held roles in this sense across their working life. The framework names what those roles have always been.
The input script is what defines the role for any given operation. It says what the performer is to do, what story the doing is in service of, what counts as the work being done well, what the performer is authorized to decide on their own authority and what requires escalation. A well-formed input script makes the role inhabitable; the performer can read it and know who they are to be for the operation's duration. A poorly formed one leaves the role ambiguous, and the performer either improvises a role from incomplete signal or escalates back to the author for clarification.
When a role calls for a product, the completion is what the role delivers — not what the performer happens to produce, but what the role required them to produce. The standards the input script specified are the bar the completion is judged against. A completion that meets the standards is a successful performance regardless of how the performer got there; a completion that misses them is a failed one regardless of how much work went in. The role is what makes the completion legible — without the role, the completion is just an artifact, with no basis for judging whether the work was done.
The role is what the boundaries establish together. The input script defines it. Until the performance ends, the role is what the performer holds.
The Freedom
Holding the role grants the performer a substantive freedom. Within the latitude the input script specified, the performer is free to do the work however they do the work. The orchestrator authored the input script; what happens during the performance is the performer's domain.
The freedom is not the absence of contract. It is what well-formed contracts produce. The input script has to carry the story, not just the instructions; otherwise the performer has nothing to orient by when conditions shift and the instructions no longer fit. The script has to specify the latitude granted; otherwise the performer cannot know what is theirs to decide. When a role calls for a product, the script has to specify what counts as the work done and the standards the product will be judged against; otherwise the performer cannot know when to deliver and the result cannot be evaluated. Without these, the freedom collapses — either into rigidity, where the performer cannot do anything the script did not anticipate, or into chaos, where the performer's work cannot be evaluated against any shared standard. The freedom is the freedom a well-defined role grants. It depends entirely on the input script being well-formed enough for the performer to inhabit the role.
Internal Orchestration
From outside, the role appears to be performed by an individual actor.
From the inside, the performer is itself an orchestrator. Whatever the performer does in the course of inhabiting the role, it does by composing sub-scripts and running sub-operations against them. There is no other mechanism. Every internal act is itself an operation, governed by the same boundary discipline as the operation it is happening inside.
This is what makes the input script immutable. The performer's only capability is to compose sub-scripts and run sub-operations against them. A sub-script is not a modification of the input script; it is a new script for a sub-operation, sitting beneath the input script in the operation's internal structure. The input script is what the performer is performing. The sub-scripts are the operations through which the performance unfolds.
The role the input script defines may itself be a role of orchestrating. Sometimes the input script asks the performer to answer a question, and the performer answers it through internal orchestration because the question is complex enough to require sub-operations. Sometimes the input script asks the performer to coordinate a network, and the performer's role is, by specification, to compose sub-scripts for sub-performers. The role's content varies; the mechanism does not.
The recursion has a floor. At some level, a sub-operation reaches a primitive — a single act by a single performer, working from a single input. The performer might be a human acting on an internally-composed brief, a non-human performer producing one act of output, or a deterministic performer carrying out one calculation. At that floor, there is no further inner orchestration. But for any non-primitive performer, what appears from outside as the performer's interior is in fact an internal network the performer is orchestrating.
This is what makes the role independent of what kind of performer fills it. A performer is defined by what it honors at its boundaries, not by what happens inside. What kind of thing inhabits the role does not change the role's architectural shape. The framework's commitments are at the boundaries.