Escalation

Most maneuvers reach the same moment somewhere in the middle. The actor has read the target's decision, chosen a lever likely to move it, and named what the lever needs. Then one of those things turns out not to be in hand: a sign-off someone else gives, a figure someone else owns, an authority that sits a level up. The lever is sound, and the actor cannot pull it.

In The Lam System for Political Interaction, that moment is the gate failing, and the system answers it with escalation. The maneuver stops at the gate and a smaller maneuver opens whose whole aim is the missing resource. Once the smaller one has the resource, the larger one picks up at the gate where it stopped. Of the failure moves, escalation is the one built to keep the original lever in play. Giving up a lever, giving up the cycle and revising its aim each concede something.

What a failed gate tells you

The gate is a test, and it spends nothing. Before a lever is executed, the cycle checks whether the actor holds every resource the lever was declared to need. If so, the gate passes and the lever goes ahead. If any one is missing, the gate fails. The verdict is mechanical: it follows from what the actor holds, counted.

A failed gate leaves the lever's merits where they were. Whether it was well chosen, and whether the target would respond to it, are as open as before. What the failure establishes is that the actor reached for something they do not have. That is an ordinary shortfall in any organization, and it is why escalation carries most of the weight in the failure family: a lever worth pulling usually needs something that belongs to someone else.

A cycle whose whole aim is the missing piece

When the gate fails, the system opens a sub-cycle. The failure fixes its interest: the actor wants exactly the resource the parent lacked, and nothing broader or nearby. If the parent needed a controller's sign-off, the sub-cycle wants that sign-off, and a warmer relationship with the controller, or the controller's support for the whole plan, is outside its aim.

The narrow aim is what makes success checkable. A sub-cycle with a loose aim can succeed on its own terms and still leave the parent short, and then nobody can say whether the escalation worked. With the aim pinned to the missing resource, success has one meaning: the thing the parent's gate asked for is now held. The handback depends on that: control returns to the parent only once its need is met, and the gate tests again, as the next essay, Resumption, sets out.

The sub-cycle usually faces a different target. The person who decides whether the actor gets the sign-off is rarely the person who decides the original question, so the sub-cycle has its own decision to read, its own preferred position and alternatives, and its own levers. Its address in the record sits under the lever it serves, so anyone reading the record later can tell which lever a given sub-cycle was opened for.

What waits, and what does not

Escalating suspends the parent at the gate. Nothing about the parent changes while it waits: its interest, its reading of the target, its levers and the failed test all stay on the record as they were. The failed test stays there for good, with the later pass written after it, so a reader can see that the lever stalled, why, and what was done about it.

Escalating also spends nothing. The actor holds the same resources the moment after the sub-cycle opens as the moment before. The sub-cycle can draw on them, because they are the actor's at every level of the maneuver, and if a lever inside the sub-cycle spends one, the spending belongs to that lever's execution and is recorded there.

So an actor deciding whether to escalate pays nothing for the decision itself. An escalation costs whatever the sub-cycle's levers turn out to cost, and that is settled inside the sub-cycle, lever by lever, where it can be seen.

The parent's record holds still while it waits, and its target keeps moving. The person whose decision the maneuver is aimed at goes on with their own work while the actor is elsewhere, and a reading of them taken before the escalation may be stale by the time the parent resumes.

The same cycle, one level down

A sub-cycle is a cycle, running the same five movements as any maneuver. It declares an interest and reads its target's decision, chooses levers and names what they need, tests and acts, reads the response, and closes and carries forward. What sets it apart is its position. Its address sits under the parent's lever. Its close hands what it obtained back to the parent and leaves the maneuver running. And while any cycle is suspended, no new top-level maneuver can open, so the one in progress always finishes or is given up before another begins.

Because a sub-cycle is a cycle, it can fail at its own gate, and when it does it escalates the same way. Nesting composes level on level. Each new level adds one suspended cycle and, later, one handback, and nothing else, so whatever holds at one level holds at the next. The cycles unwind in the reverse of the order they opened: the deepest finishes first and hands back to the one above it, which picks up at its own gate, and so on up to the parent.

The system sets no limit on the depth. Its grammar allows a new interest under any lever, as many times as the maneuver needs. The limit is the actor's. How deep to go is one of the few choices of scale the system leaves entirely to them, alongside how many levers to declare, how often to revise and how many maneuvers to run.

Two levels deep

Illustrative. The people and the company are invented. Amara Quist runs commercial lines at a mid-sized insurance broker. She wants the president, Felix Kessler, to approve a quote for a large marine account; his adverse alternatives are to decline the account as outside the firm's appetite, or to pass it to a larger partner broker. Her lever is to show Felix the risk is already placed, with a reinsurer's capacity committed in writing. She does not hold that commitment, so the gate fails, and she opens a sub-cycle with the reinsurer's underwriter, Ines Varga, aimed at the written commitment.

Ines will commit only on the account's loss history, which the client's risk manager, Kwame Mensah, holds. The sub-cycle's gate fails in turn, and Amara opens a third cycle with Kwame, aimed at the loss history and nothing more. This one needs only something she already has: her standing with Kwame, which she spends asking him to release the history early under a confidentiality undertaking. He agrees, and the history flows back. The cycle with Ines resumes at its gate, passes, and Ines commits. The parent resumes at its gate, passes, and Felix approves.

Felix's cycle never touched Kwame, and Felix never needed to know he was involved. Counted, the maneuver asked three people for something, had two cycles waiting at their gates at its deepest point, and spent three resources. Only one of the three came out of what Amara held at the start: her standing with Kwame, spent at the bottom, which bought both of the resources above it.

What escalation does not do

Escalation never retries anything on its own. A maneuver the actor gives up stays given up, and trying again means opening a new one, deliberately, with a record of its own.

It opens one sub-cycle for each failed gate, aimed at one missing resource. If a lever lacks two things, escalation goes after one of them, and the other turns up missing when the gate tests again. When two levers in the same cycle both fail their gates, the actor chooses which to escalate first, and the second waits until the first has come back. The system never runs sibling sub-cycles side by side. That is slower than chasing everything at once, and it keeps every sub-cycle answerable to a single question.

Nor does depth change the shape of a cycle. There is no lighter version for the levels below, and no shortcut that lets a deep sub-cycle skip reading its own target. A sign-off three levels down is still a decision someone makes for their own reasons.

When escalating is the wrong call

Escalation preserves a lever, so its value is capped by the lever's. When another live lever already carries the target to the preferred position without the missing resource, giving up the failed lever and letting the others carry the cycle costs less. When nobody holds the resource in a form their decision can release, or the holder is someone the actor has no lever on, a sub-cycle only moves the dead end one level down. At the deepest level the actor will go, with a resource out of reach and no other lever, the remaining exits are to moot or to abandon.

Time comes next. A sub-cycle has to read a new target and play its own levers, while the parent's target decides on their own clock. An escalation that returns after the decision is made has preserved a lever for nothing.

Exposure is easy to miss. Asking for a resource tells its holder that the actor lacks it, and usually what it is for, so every level of escalation widens the circle of people who know what the maneuver is attempting. So is the price. Each sub-cycle spends whatever its levers need, and the sum across levels can exceed what the parent lever was worth. Amara spent standing with Kwame, which she judged cheap against the account; had she needed to spend standing with Felix to reach Kwame, the sum would have looked different.

None of these is a rule the system applies. The system records the gate's verdict, opens the sub-cycle, holds the parent and hands back what comes up. Whether a missing resource is worth fetching, and how far down to fetch it, the actor decides.