Resumption

Most executives have sent someone, or gone themselves, to collect a resource another person controls: a signature, a commitment, a figure from another department. The errand usually comes back with something. Often it comes back with something close to what was asked for: a promise to sign next week, or a sense that the other side is supportive. The main piece of work then carries on as if the resource were in hand, and the gap shows up later, at the worst moment, when someone asks to see the thing itself.

In The Lam System for Political Interaction, the errand is a sub-cycle, opened when a lever's gate fails for want of a resource, and the moment it comes back is resumption. Escalation covers the opening of the sub-cycle and the parent's wait. Resumption covers the return, and its rule is strict: control passes back to the parent only once the sub-cycle has delivered what the parent needed, so the system never has to weigh whether something close will do.

What the handback writes

When a sub-cycle finishes, it closes and what it obtained flows back into what the actor holds. The two happen together, as one step, because a sub-cycle that has reached its close has nothing left to do but hand over what it won. Next, control passes back to the parent. This entry moves nothing in the actor's holdings; the resource is already there. Then the parent's gate tests again, looking for exactly the resource it failed to find.

Each entry reads what the one before it wrote. The parent cannot be handed control until the resource has landed, and the gate cannot find a resource that has not yet been counted in. Splitting the return this way also keeps the arithmetic in one place. Opening a sub-cycle spends nothing and resuming spends nothing, so everything an escalation cost was spent by levers inside the sub-cycle, at entries that say which lever spent what. The difference between what the actor held when the parent stopped and what they hold when it resumes is the escalation's net effect: what came back, less what the sub-cycle's levers used up.

Why the handback needs no judgment

Most of the steps that move a maneuver forward wait on the actor's judgment. Whether the target read a lever as projected, whether a resource is strong enough for a particular ask, whether to give up a lever: the system leaves all of these with the actor, and The Boundary of Computation argues why it must. The handback is different, and the difference was arranged at the sub-cycle's opening.

When the parent's gate failed, the sub-cycle's interest was set to exactly the resource the gate was looking for, under the same name. The sub-cycle wants what the parent lacks, word for word. So when the sub-cycle comes back, the question of whether it succeeded is one the record can answer by itself: does the actor now hold the named thing? No translation is needed between what the errand was for and what the parent needs, because they were written as one thing from the start.

That arrangement protects the actor at the moment they are least reliable. An executive coming out of a good meeting is inclined to count it as a win, and the person deciding whether the errand worked is usually the person who wants the larger maneuver to go on. The system compares what came back with a want written down before the errand began, when the actor had no reason yet to call anything a success.

The system cannot see the document in the actor's hand, and the entry that records what flowed back is still the actor's to write. The guard narrows the question the actor answers there, from whether the sub-cycle went well to whether a named resource is held, and a colleague reading the record could check the second against the paper in the file.

A berth, and a confirmation

Illustrative. The people and the company are invented. Lucia Moreno runs terminal operations for a container port operator. A new shipping line wants weekly calls with vessels larger than any the terminal now takes, and Lucia wants the president, Henrik Dahl, to give her the authority to sign the berth agreement. His adverse alternatives are to turn the line away, or to hand the negotiation to the commercial team. Her lever is to show Henrik that the terminal can take the larger vessels without moving any existing customer's slot. It needs the harbor master's written confirmation that the berth is deep enough at the tide windows she plans to use.

She does not hold it, so the gate fails, and a sub-cycle opens with the harbor master, Colm Brennan. Its interest is the written confirmation and nothing broader. Colm's options, as Lucia lists them, are to confirm now, to confirm after the next depth survey, or to refuse. Her lever is to take him through the terminal's tide-window plan, and it spends her standing with him. Colm reads the plan as safe, confirms in writing, and gains a berthing schedule his office can enforce. The sub-cycle closes and the confirmation flows back. Control returns to the cycle with Henrik, the gate finds the confirmation, and the lever is played.

The near miss

Suppose Colm had taken the second option. He sees no difficulty, he tells Lucia, and he will put it in writing once the next depth survey is done. On most working days that would be good news, and Lucia might walk back to Henrik with it.

Colm selected one of the adverse alternatives Lucia's own detection listed, and what flows back is his promise. The promise is real and it is hers, so it joins what she holds, counted like anything else. The parent does not resume. Its gate asked for a written confirmation, and a promise of one is a different resource under a different name. Control stays where it is, and the ways out are to moot the sub-cycle or abandon it, one level at a time. Either way the parent gets control back without the resource, still at a failed gate, and it has its own decision to make.

That decision is no longer about the errand. Lucia could declare a different lever on Henrik, one the promise is enough for: telling him the harbor master expects to confirm after the survey, which asks less of him and offers less. She could set the lever aside if another one already carries the case, or give the cycle up. Trying the same lever again through a second sub-cycle is not one of the options, because a lever never has more than one sub-cycle beneath it; trying again means a new lever with an address of its own. A parent that wants to retry after its sub-cycle fails is one of the cases What the System Cannot Yet Represent names.

What resumption does not refresh

A resumed parent picks up at the gate where it stopped, with its detection, its objective and its levers as they were. The target did not wait. While Lucia was with Colm, Henrik went on running the port, and he may have promised the deep berth to an existing customer's expansion in the meantime. The confirmation would still pass the gate, because the gate answers whether Lucia can play the lever, and whether the lever is still worth playing is a different question, about Henrik, which only she can answer. The handback is mechanical, and the moment just after it calls for a judgment, because the next entry in the parent is an execution, and an execution spends.

A fetched resource is held briefly on the normal path: it arrives at the sub-cycle's close and leaves at the parent's execution. If Lucia judged at that moment that the lever was no longer worth playing and set it aside, the confirmation would stay in what she holds. Nothing obtained through a sub-cycle is lost when the lever it was fetched for goes unplayed. It stays in her holdings for another lever or another maneuver, perhaps with the next line that wants to bring larger vessels in.

Why the rule is strict

Under a looser rule, the parent would resume whenever its sub-cycle closed. That is simpler to state, and it lets a failed errand pass for a successful one. The parent would resume and test its gate again, the gate would fail on the same missing resource, and the maneuver would go around the same errand again, potentially without end. The strict rule ends that loop before it starts, because a sub-cycle that did not deliver cannot hand back.

It also keeps the counting straight. Each failed gate opens at most one sub-cycle, so no two sub-cycles can each claim to have supplied the same resource and have it counted in twice. A sub-cycle's flow back happens once, at its close. Across any depth of nesting the actor's holdings balance at every moment, as Capital Is Conserved shows, and each resumption is the point where the balance can be read off for the level below.

For someone reading the record later, every errand in a maneuver shows up as a matched pair: the sub-cycle's interest near its top and the parent's gate passing just after the handback, with the same resource named in both. Where the pair is complete, the errand delivered. Where a sub-cycle closed and no resumption follows, the record says exactly what came back instead, and what the actor decided to do with a parent still short of what it needed.