An executive asked how a difficult piece of political work is going will usually answer with a story. The chief operating officer seemed open on Tuesday. Finance is being slow. Someone in the depots has heard something. The story thins out when the question changes to where the work stands: which of the executive's efforts is waiting on which, what has been spent so far, what is still in hand, which projections have already been proved wrong. Most executives can say what they hope will happen next, and very few can say exactly where they are.
The Lam System for Political Interaction is built to answer that second question exactly, at any moment, and it manages this while knowing less about the people involved than the executive does. Everything it holds about a maneuver fits into four things, all of them on the actor's side of the work. None of the four is the target's state of mind. Even the target's options, the part of the picture that seems as if it must belong to the target, are read from what the actor wrote down. The rest of the system follows from that choice. It can be exact because it is exact only about the record, and every claim about another person enters the record as the actor's judgment, credited to the actor.
A vocabulary, a record and rules of movement
The system treats one piece of political work as a maneuver: one actor's intervention into one target's decision. The actor wants a resource the actor does not hold, and the target's selection controls it. The target is choosing among options, each weighed by what it offers and what it costs, and the actor's work is to change how the target sees those options until the one the actor prefers is the one the target selects. Lena Ortiz, head of customer operations at a freight company, needs a yes from the chief operating officer, Daniel Okafor, before the night dispatch desks can leave the depots and come under her budget. That maneuver, invented for this series, runs through the rest of this paper.
The system adds four things to that description. The first is a vocabulary of twenty-one constituents, from the actor and the agenda down to the obtained resources and the obtained utility, each with a Greek form for the act and a Latin form for the thing acted on or recorded. Every constituent also gets an address, read like a path from the agenda down, so that "the second lever's required resource" points at one thing and only one. Every entry the maneuver produces goes into a record, in order, and nothing in it is ever overwritten. Rules of movement then say which step the maneuver can take from where it stands and who takes it: the actor, the target, or the cycle itself as a matter of course.
On top of these sits a short list of guarantees, properties the system proves of every maneuver written in it, whatever the actor decides. Each one follows from how the vocabulary, the addresses, the record and the rules are built, and a later paper, What the System Guarantees, sets them out with their reasons.
Nothing in the system decides the questions a maneuver turns on. Whether Lena's standing with Daniel is enough for this particular ask, whether Daniel read the overtime case the way she projected, whether to declare a second lever now or wait to see how the first lands: these are judgments, and the system receives them from the actor. It describes a process a person drives. Its rigor covers form, order and the arithmetic of what the actor holds, and it claims nothing about whether a lever was well chosen.
That division also settles what software can do with the system. It can keep the record, refuse an entry that does not fit, say where the maneuver stands and which moves are open from there, and replay any earlier moment. It cannot run the maneuver, because every step that matters waits on a judgment only the actor can make. Keeping the record of a maneuver and running it are different jobs, and the system is built so the first can be handed to software while the second stays with the actor.
Why worked examples are not enough
A notation can be learned from examples for a long time before anyone notices what is missing. Its author writes a dozen maneuvers in it, and each one reads correctly to the author, who knows what was meant. The grammar lives in the examples. So does the sense of which symbol may sit inside which, which party performs which act, when two ways of writing a thing mean the same thing, and how one entry leads to the next. None of it is written down, because nobody has needed it to be.
The gaps show when someone else reads the record, and they show most plainly with a machine, which cannot read an entry for what its writer probably meant. Before software can keep a maneuver's record, it needs five things the examples only imply: a grammar that says which strings are entries at all; types that say which entries make sense; a rule for when two entries name the same thing; rules for how the state of a maneuver moves from one step to the next; and proofs that those four behave, so that nothing the rules allow can break the record.
The system counts as finished when whoever keeps the record, a person or a machine, can read any entry in exactly one way and tell whether it is well-formed and whether it makes sense. The same keeper has to be able to decide whether two entries name the same constituent, and to advance a maneuver by a step the rules allow, with the act credited to whoever performed it, the record extended and nothing erased. A worked maneuver should replay from opening to close. And wherever the system settled something that nothing in the work itself settled, the keeper should be able to point to the decision made there and the reason given for it.
A rule that forbids a step a maneuver plainly takes is wrong, and so is any rule that overwrites an entry, since the record could no longer be trusted. The third way to fail is to present the system as able to run a maneuver on its own, with its tests treated as things a machine can settle. A record kept on that basis would hold software's estimates of people in the same places as the actor's judgments, and nobody reading it later could tell the two apart.
Three framings, one kept
The name is literal, and it took three attempts to reach it. The first treated the notation as an algebra: a way of combining maneuvers, so that two of them could be composed into a larger one whose behavior followed from its parts. Nothing in political work composes like that. What had looked like composition was containment, a sub-cycle sitting inside the lever that opened it, and the lengthening of an address as one constituent is placed under another. The second framing borrowed from the formal languages computer scientists use for processes running side by side, in which a program is an expression rewritten step by step until it can go no further. Their way of presenting rules fitted the system well, and the claim to be one of them did not. The system's steps move a state forward one entry at a time, which is a different thing from rewriting an expression into a smaller one, and the tests that decide its most important steps are judgments a person makes, where a calculus would compute them. What was kept is the plain description: a system whose state moves one step at a time, with the actor's judgments as an input it receives. The essay Not a Calculus, Not an Algebra, near the end of the series, gives the full argument.
The four things it keeps track of
The state of a maneuver, at any moment, comes down to the active cycle, the record, the suspended parents and the resources the actor holds.
The active cycle is whichever cycle has control. A maneuver is one top-level cycle and any sub-cycles it opens, and only one of them moves at a time. When Lena's second lever needs the controller's sign-off and she does not hold it, a sub-cycle opens with the controller, Priya Natarajan, as its target, and control passes to it. The active cycle is only a pointer. It says which cycle is in control and holds none of that cycle's contents, which live in the record.
The record is every entry the maneuver has produced, in the order it was written, and it only grows. A projection stays beside the realization that answered it, a gate that failed stays failed after the sub-cycle has fixed it, and a revision is written next to what it revised. The full history of any cycle, from its opening to wherever it now stands, can be read from the record.
The suspended parents are the cycles waiting for a sub-cycle to hand back. They wait in a stack, so the most recent cycle to stop is the first to resume, and a maneuver nested two deep unwinds from the bottom up. While Priya's sub-cycle runs, Lena's cycle with Daniel waits at the gate where it stopped, with its interest, its reading of Daniel and its levers unchanged. When nothing is waiting, the active cycle is the top-level one.
What the actor holds is counted. Lena starts with the overtime data, her standing with Daniel and her standing with Priya. Each lever's execution takes away what it spent, and each closing sub-cycle adds what flowed back. The count is read at every gate, which is how the system tells whether a lever can be played, and written at every close.
Lena's maneuver, and the four things the system keeps
Illustrative. The people and the company are invented. Each row is one entry in the record, in the order it was written, and the tags under some rows show what Lena holds, spends and gets back, counted. The row that opens the sub-cycle is where control passes to it: the cycle with Daniel waits there, suspended, until the sub-cycle hands back. Open the sub-cycle to see it run.
Cycle: Lena and Daniel
- OpenThe cycleA new cycle opens under Lena's agenda.Held: the overtime dataHeld: her standing with DanielHeld: her standing with Priya
- InterestActorLena wants the dispatch budget and the authority over the desks.
- DetectionActorDaniel decides. He can approve the move, leave dispatch with the depot managers, or hand it to the automation program.
- ObjectiveActorDaniel approves the move, and the desks and their budget come to Lena.
- IntentionActorFirst lever: show Daniel that one desk cuts the overtime he has been criticized for.
- IntentionActorSecond lever: have Priya sign off the savings figure.
- Required resourcesActorThe first lever needs the overtime data and her standing with Daniel.
- Required resourcesActorThe second lever needs Priya's sign-off.
- Gate passesThe cycleFor the first lever: Lena holds both.
- ExecutionActorThe overtime case goes to Daniel.Spent: the overtime dataSpent: some of her standing with Daniel
- PerceptionTargetLena judges that Daniel reads the case as an answer to his critics.
- Gate failsThe cycleLena does not hold Priya's sign-off.
- EscalateThe cycleThis cycle waits at its gate. Control passes to the sub-cycle, and nothing Lena holds is spent.
Sub-cycle: Lena and Priya · 14 entries
- OpenThe cycleA sub-cycle opens under the second lever.
- InterestActorLena wants exactly the sign-off the cycle above lacked.
- DetectionActorPriya decides. She can sign the figure, or decline to put her name to it.
- ObjectiveActorPriya signs the savings figure.
- IntentionActorWalk Priya through how the savings figure was built.
- Required resourcesActorHer standing with Priya.
- Gate passesThe cycleLena holds that standing.
- ExecutionActorLena takes Priya through the figure, step by step.Spent: her standing with Priya
- PerceptionTargetLena judges that Priya finds the figure sound.
- SelectionTargetPriya signs.
- OutcomeThe cycleThe savings figure is signed off.
- Obtained utilityTargetPriya puts her name only to a figure whose working she has seen.
- CloseThe cycleThe sub-cycle closes.
- Flow backActorThe sign-off flows back to what Lena holds.Returned: Priya's sign-off
- ResumeThe cycleControl returns to the cycle with Daniel, at the gate where it stopped.
- Gate passesThe cycleLena now holds the sign-off. The failed test stays on the record above.
- ExecutionActorThe signed figure goes to Daniel.Spent: Priya's sign-off
- PerceptionTargetLena judges that Daniel reads the signed figure as one he can defend.
- SelectionTargetDaniel approves the move.
- OutcomeThe cycleThe night dispatch desks move onto Lena's budget.
- Obtained utilityTargetDaniel gets lower overtime and a cleaner organization.
- CloseThe cycleThe maneuver closes. Nothing is waiting.
- Flow backActorLena holds what she wanted, alongside what remains of her standing with Daniel.Returned: the dispatch budget and the authority over the desks
The list leaves out two things on purpose. One is the decision matrix. Daniel's options, and what each offers him and asks of him, look like part of the maneuver's state, and Lena certainly needs them, yet the system does not store them. It reads them from the record: the options detection declared, adjusted by every execution that has changed how one of them is weighed. Because the matrix is a reading of the record's history, the system can rebuild it as it stood at any earlier entry by replaying the record to that point, and Lena can see exactly what she believed about Daniel's choice before her first lever landed.
The other is everything outside the actor's own maneuver: other actors' maneuvers, the wider organization, what the depot managers are planning for their own budgets. A maneuver's state belongs to one actor, and whatever passes between actors is outside the system. The essay Across Actors takes up what that leaves out.
What the system keeps about Lena's maneuver, and what it does not
Illustrative. The people and the company are invented. Statements about the maneuver while Priya's sub-cycle is running: guess which ones the system holds, then select each to see why.
Select each item to see the verdict.
The active cycle. While Priya's sub-cycle runs, it is the one in control; the pointer says so and holds nothing else.
A suspended parent. It waits with everything it had declared, and resumes at the same gate once the sign-off comes back.
Among the resources she holds, counted. The overtime lever spent some of it, and what remains is still on the count.
The system has no channel to Daniel. It holds only what Lena has written about him, each entry credited to her.
In the record, as Lena's judgment, written where the target's perception belongs. It stays there even if later events prove it wrong.
Not stored. The system reads the decision matrix from the record's history, and can rebuild it as it stood at any earlier entry.
A judgment, made by Lena and received by the system. The gate counts what she holds; whether it will do is hers to say.
Another actor's business. A maneuver's state belongs to one actor, and whatever passes between actors is outside the system.
The record itself. It only grows, so the order is never lost.
Why the target is not in the state
None of the four things is a fact about Daniel. The record holds Lena's detection of his options, her projection of how he would read each lever and her reading of how he did, and each of those is an entry Lena made, at the moment she made it. When the record says Daniel read the overtime case as answering his critics, it means Lena judged that he did, and the system wrote her judgment into the place where the target's perception belongs. The system has no channel to Daniel except through the actor.
The system's exactness depends on this. Some of its entries are structural facts it produced itself, such as a cycle opening, a gate passing or a sub-cycle handing back, and those are mechanical and can be checked. The rest are judgments the actor supplied, and those are kept unchecked, in the actor's own wording, next to whatever followed them. A system that tried to hold the target's real state of mind would have to estimate it, and an estimate filed among the structural facts would spoil both kinds of entry, because the actor could no longer tell which were their own judgments and which were the software's guesses.
The same restraint is what makes the record worth reading afterward. An actor who projected that Daniel would read the overtime case one way, and recorded that he read it another, has a gap that can be measured, because both entries are the actor's and neither has been touched. Across many maneuvers those gaps describe how well the actor reads people, including the targets they misjudge in the same direction every time. Nobody else's estimates are mixed into that history, so whatever it shows about the actor's judgment, it shows accurately.
Five layers, read in order
The system is specified in five layers. Each layer assumes the ones before it, and together they are the order in which any entry is read before the record accepts it.
The grammar
The grammar decides which strings are entries at all: which symbols exist, how a path is built with the slash, when a dot marks the only constituent of its kind and when a number tells siblings apart, how brackets open and close. People writing by hand use shorthand, and the system reads shorthand into one canonical form before anything else happens, so a familiar abbreviation is never refused for being familiar. An entry the grammar cannot read in exactly one way goes no further.
The types
A well-formed entry can still make no sense, such as a required resource placed under the target, or a lever placed under the decision matrix. The types decide what can sit under what, following the tree of what contains what, and they decide ownership. Every operation belongs to the actor, the target or the cycle itself, and an entry that credits one to the wrong owner is refused. Lena detects; Daniel perceives and selects; the outcome is the cycle's own and belongs to neither of them. An entry in which Lena selects is well-formed and ill-typed, and the types stop it.
Sameness
This is the only layer about equality. It decides when two entries name the same constituent, and it rests on three plain facts: how a path is grouped does not change what it names; the order in which a set's members are listed does not matter; and the Greek capital alpha and the Latin capital A, which look identical in most type, are one letter for the agenda. To compare two entries, the system reduces both to one form and compares the results, which always gives an answer. Without this layer, Lena's two levers listed in the opposite order would count as a second set of levers.
Movement
Movement says how the state of a maneuver moves: from which point each step can be taken, which of the four things it changes and who takes it. The steps of the cycle (interest, detection, objective, the levers and what they require, the gate, execution, perception, selection, outcome, the two gains and the flow back) and the failure moves (escalate, resume, moot, abandon, revise) all belong here. A well-typed entry can still find no step that takes it. Lena cannot record the execution of her second lever while its gate stands failed. When no step allows an entry, nothing moves, and the actor's judgment has to say what happens next: escalate for the missing resource, set the lever aside, or give up the cycle.
The guarantees
The guarantees are proved from the four layers before them and never assumed. They are the properties the system promises of every maneuver: one address for every constituent; a record that stays well-formed and well-typed through every move; sameness that can always be decided; capital conserved across every level of nesting; maneuvers that always end; and an order of steps that changes nothing except at the forks where the actor chooses. None of them is a rule of its own. Each holds because of how the layers beneath it are built, which is why every guarantee can be stated with its reason.
One entry through all five
The test Lena's second lever faces at the gate shows the layers at work:
Read aloud: what the actor holds contains the required resource of the second lever, under the objective of the only interest on the agenda. The grammar reads it as two complete addresses in square brackets, with a dot after each constituent that is the only one of its kind (the actor, what the actor holds, the interest, the objective, the required resource) and a 2 marking the second of two levers. The types confirm that the left side is what the actor holds and the right side is a required resource sitting under a lever, the only two kinds of thing this test can compare. Sameness says the path names one resource however its slashes are grouped. Movement makes the test the gate, a step the cycle takes, and sends the cycle on to execution if the test holds and to the failure moves if it does not. For Lena it does not. Either way the guarantees hold: the gate spends nothing, so what Lena holds is unchanged, and the failed test joins the record for good.
Errors are therefore caught where they belong. A malformed entry is refused at the grammar and never reaches the types; a misplaced or misattributed one is refused at the types and never reaches movement. When a layer refuses an entry, the system names the layer and the rule, and it never repairs the entry by guessing. A record keeper that silently corrected entries would be making judgments of its own, and the record would stop being the actor's.
Which layer refuses this entry?
Illustrative. Take an entry from Lena's maneuver, such as Daniel approving the move, Lena approving it on his behalf, or the second lever executed while its gate stands failed. Tick each check that holds, from the top; the first one left unticked names the layer that stops it. Sameness has no check here, because it never refuses an entry: it decides when two entries name the same thing.
How the system was built
Every part of the system has one of two origins. Some parts describe what political work visibly does: an actor finds out who decides before choosing how to move them, and the person deciding can always leave things as they are, which is why doing nothing is always among the target's options. The other parts are decisions, made where nothing in the work settles the question, and each one is written down with its reason. A reader can therefore tell description from choice, and argue with the choices on their merits.
Worked maneuvers are the test. A rule is checked by carrying maneuvers through it step by step, and when a rule forbids a step a maneuver plainly takes, the rule is at fault. The constructed maneuvers in this series, each built to exercise one pattern, are carried through the same rules.
Where two parts of the notation disagreed, the system says so, chooses one as canonical, reads the other into it and logs the choice. The clearest case was a single sign that had been used both for "is the same as", which runs both ways, and for "is defined as", which runs one way. The system split the two. Sameness became the layer described above, and the expansion of a name into its definition became a step of its own, recorded when it happens, with the name and its definition kept distinct. Where the system cannot yet represent something a maneuver might do, it says that too, and the essay What the System Cannot Yet Represent lists what is outstanding.
How the series is organized
The series follows the shape of the system, and five papers come first to state it. After this one, The Maneuver follows a maneuver through its five movements, from declaring an interest to carrying forward what it won. The Boundary of Computation draws the line between what the system settles and what the actor judges. The Record takes the second of the four things in full: why nothing is overwritten, and what an actor learns from a record that keeps everything. What the System Guarantees states the six guarantees, each with the reason it holds.
The twenty-one constituents follow, one essay each, in the order the tree holds them, from the actor and the agenda to the obtained resources. They are the system's vocabulary, and each essay places its constituent in the cycle, says who performs it and shows what the record holds when it fires; Detection is one of them. Five essays then take the joints of a cycle, the moments that are not constituents: opening a cycle, the gate, playing several levers, reading their effect, and closing.
The failure moves come next, one essay each, beginning with Escalation, followed by two essays on how actors sequence several levers when they cannot know which will be enough. Five essays restate the guarantees, one or two at a time, as principles an executive can use. Five constructed maneuvers, each in an invented organization and each built to exercise one pattern, are then worked through from opening to close. Four essays on the system's limits end the series: what the system is not, what it cannot yet represent, how software administers a maneuver without running it, and what lies beyond a single actor. The hub holds the contents and marks the pieces still to come.