THE MACHINERY OF THE ENGINE OF IDENTIFYING ACTION

How Five Stages Gate the Capacity to See the One Action Running a Life

Why the action that is quietly steering everything is the last one anyone names


A man is asked what his problem is.

He has an answer ready, because he has told it before. He is disorganized. He needs a better system. If he could just get his mornings under control, the rest would follow. He says it cleanly, the way you say a thing you have said many times, and every word of it is the outside view of his own life, the version shaped for speech, and not one word of it is the action actually running him.

What is running him is a thing he does every night at eleven and has never once mentioned, because to him it is not a problem. It is a relief. He lies down and reaches for the phone and the hour goes, and the morning he cannot control is the bill for the night he will not look at. The disorganization is the symptom he can see. The action that produces it is below his own line of sight, and so when he is asked, he hands over the symptom and calls it the cause.

He is not lying. He is doing the only thing a person can do when asked to name the action running their life. He reports what is visible to him, and the action that matters is precisely the one that is not.


A woman tries to find it for herself.

She is more honest than most. She sits down to work out what is actually wrong, and she thinks hard, and she produces a careful, intelligent account of her situation, and the account is wrong in the same way his spoken one was. The thinking that is supposed to find the action is being done by the same mind that cannot see it. She is searching a house with a flashlight that goes dark in exactly the room the thing is hiding in. She comes away with a theory about herself that is reasonable, articulate, and aimed at the wrong action entirely, and she will now spend a year fixing the thing she named instead of the thing that named it.

She lands where he did. She believes the problem is the one she can describe. The describable problem is almost never the one running the life.


Two people, both certain that the action steering their days is the one they can put into words, as though the deciding action and the visible action were the same action.

They are not. The action running a life is not usually the loud one. It is the quiet, repeated, defended one, performed below the level of report, leaking its existence into behavior long before it ever reaches speech. Finding it is not a matter of asking harder or thinking longer. Asking and thinking are the two instruments that cannot reach it, because both run through the mind that is keeping it out of view.

What follows is not advice.

It is not a method for self-improvement. Not a set of questions to ask yourself. Not a worksheet to fill in tomorrow morning.

It is mechanism.

The actual chain by which the one action running a life becomes visible, whether the life is someone else’s or your own. The five stages, in the order the seeing gets built. The threshold that gates each one. The reason the search collapses at a single hidden link while the rest of it stands ready. The reason the broken link is invisible to the person doing the searching.

There is a claim you will have heard, that people are the best authority on their own experience, that if you want to know what is wrong with someone you should ask them. As a courtesy it is decent. As a method for finding the action that runs a life it is exactly backward, and this document is the proof, because the engine that finds the action does not run on asking at all.

This document is that chain, laid open.

Nothing more.

What you do with it is your business.


PART ONE: THE FIVE STAGES

The Chain That Turns Days Into the One Action

Identifying the action running a life is usually treated as a single act of insight, a moment of realization that either arrives or does not. It does not work that way, and the experience of finding one of these actions does not feel like a flash. It feels like a sequence of distinct operations, each one feeding the next, each one able to fail on its own while the others stand ready.

 seeing the one action

 ┌────────────────────┐
 │  1. GATHER         │
 │  enough instances  │
 └─────────┬──────────┘
   below? you have an
   anecdote, not a
   pattern. one day
   proves nothing.
           │
 ┌─────────▼──────────┐
 │  2. SURFACE        │
 │  the leaks appear  │
 └─────────┬──────────┘
   below? you asked
   instead of watched
   and got the version
   made for speech.
           │
 ┌─────────▼──────────┐
 │  3. CLUSTER        │
 │  the leaks converge│
 └─────────┬──────────┘
   below? you chased a
   single signal and
   mistook noise for
   the pattern.
           │
 ┌─────────▼──────────┐
 │  4. ISOLATE        │
 │  the load-bearing  │
 │  one               │
 └─────────┬──────────┘
   below? you found a
   real action but not
   the one running the
   others.
           │
 ┌─────────▼──────────┐
 │  5. CONFIRM        │
 │  the body agrees   │
 └────────────────────┘
   below? you named it
   from outside and it
   never landed. defense,
   not recognition.

The chain has the three properties every causal chain has. It is sequential. Each stage has a threshold. The first stage below threshold sets the output of the whole system, no matter how much capacity is stacked behind it.

The output of this chain is simple to name and hard to earn. The one action, seen clearly enough that naming it produces recognition instead of argument. Not a list of things a person could improve. Not a reasonable theory about their situation. The single action, below their own report, that is steering the rest, surfaced so cleanly that the moment it is spoken the person stops and goes quiet, because they have just been shown the thing they could not see and cannot now unsee.

And like every chain worth mapping, this one hides which link is starving. The friend gives advice aimed at the spoken problem. The person makes a resolution about the symptom. Both are pouring effort downstream of a stage that was never reached, because the action they are working on is not the action running the life, and the search that should have found the real one broke at a link no one inspected.


PART TWO: WHAT EACH STAGE REQUIRES AND WHAT BREAKS WITHOUT IT

Stage One: Gather

Gather is volume. The accumulation of enough separate instances of a life that a pattern can rise out of them.

A single day is an anecdote. On any given day a person does a hundred things, and there is no way to tell, from the one day, which of them was load-bearing and which was noise. The action that runs a life reveals itself by recurrence, by showing up again and again across days that otherwise have nothing in common, and recurrence cannot be seen in a single frame. It needs a stretch of them. The action that matters is the one the days keep returning to on their own, and you cannot see what the days return to until you have enough days to see the returning.

This is why a snapshot lies and a record tells the truth. One conversation, one journal entry, one bad morning, gives you the action that was salient that day, which is usually the loud one, the dramatic one, the one with a story attached. The action actually running the life is often quiet and undramatic and would never stand out in a single instance. It stands out only as a frequency, a thing that is there on Monday and Thursday and the next Tuesday, steady underneath the noise, and frequency is a property of a series, not a moment.

What requires the gather: every stage downstream. The leaks cannot surface from one instance, the leaks cannot cluster without multiple leaks to converge, and nothing can be isolated from a field of one. With too few instances the search fixes on whatever was loudest in the small sample and calls it the pattern.

What breaks without it: the whole engine, at the root. The person working from a single dramatic day finds the dramatic action and misses the quiet one that was there every day including that one. They mistake the salient for the frequent, and the salient is rarely what runs a life.

Stage Two: Surface

Surface is the appearance of the leaks. The moment the action shows itself in behavior, having refused to show itself in speech.

The action running a life does not announce itself when you ask. Asked directly, a person hands over the version made for language, the socially acceptable cousin of the real thing, shaped on the way out of the mouth into something they can say without shame. But the action leaks. It leaks through behavior in six specific places, and a person who has stopped asking and started watching can read it off them. Where the person spends energy working around something rather than touching it. The complaint that returns across unrelated conversations as if it had its own gravity. The room they will not enter, the topic they change, the decision they keep postponing. The reaction that comes with more force than the subject warrants. The body doing something the words are not, the held breath, the laugh in the wrong place, the pace that suddenly changes. And the unguarded sentence that slips out when the editing relaxes, specific and alive, “it’s like I’m always behind.”

These are not things you elicit by questioning. They are things you observe by watching, and the watching is the entire instrument. The single most important move in this engine is the refusal to ask the action to identify itself, because the asking produces the prepared answer and the prepared answer is the one layer guaranteed not to contain the action you are looking for.

What requires the surface: the cluster and everything past it. You cannot converge signals that never appeared. An engine that asks instead of watches collects clean, articulate, useless self-reports and has nothing real to work with.

What breaks without it: the search fills with the person’s own theory of themselves. You get the spoken problem in high resolution and the actual action not at all, and because the spoken problem sounds so reasonable, the failure is invisible. The search feels successful and found nothing.

Stage Three: Cluster

Cluster is convergence. The recognition that several separate leaks are pointing at the same single action.

One leak is not enough. A single workaround might be a one-off. A single sharp reaction might be a bad mood. The action running a life does not leak in one place. It leaks in several, because it touches several parts of the life, and the proof that you have found something real rather than noise is that the signals converge. The avoidance and the recurring complaint and the unguarded sentence all turn out to be circling the same point. When three different behaviors, observed on three different days, in three unrelated contexts, all resolve to one action, that convergence is the signal. A thing that shows up once is an event. A thing that several independent leaks all point at is a structure.

This is the stage that separates a real reading from a clever one. It is easy, watching a person, to construct a story from a single vivid detail, and the story will be wrong about as often as it is right, because a single detail underdetermines the cause. The cluster is the discipline of refusing to call it found until the signals triangulate. You hold the candidate action loosely and you check it against the next leak and the next, and either they keep converging on it, in which case you are closing in, or they scatter, in which case you had a coincidence dressed as an insight and you let it go.

What requires the cluster: the isolation. You cannot isolate the load-bearing action from a single signal, because a single signal cannot tell you whether the action is central or peripheral. Only the convergence shows you how much of the life routes through this one point.

What breaks without it: the search latches onto the first plausible action and stops. A clever observer, or a person reading themselves, finds one striking thing and builds the whole diagnosis on it, and because the one thing was real, the error is hard to catch. It was real. It was just not the one running the life, and a second and third leak would have shown that the convergence was elsewhere.

Stage Four: Isolate

Isolate is the separation of the load-bearing action from the field of real actions around it.

A life has many actions, and several of them are genuinely problematic, and the cluster will often light up more than one. The work of this stage is to find, among the real actions, the single one that is running the others. Not the worst action. Not the most painful. The one that, if it moved, would move the most behind it. Some actions are downstream, symptoms of a deeper one, and fixing them does nothing because the action above them keeps regenerating them. One action is upstream, and it is doing the regenerating, and it is the only one worth naming, because it is the only one whose removal changes the rest.

This is the stage where the question is not “what is wrong” but “which wrong thing is producing the other wrong things.” The late-night phone is not just one bad action among several. It is the action that produces the late waking, which produces the skipped morning, which produces the day that never finds its footing, which produces the evening exhaustion that reaches for the phone. The other actions are real and they are all symptoms of the one. Isolate it and you have the lever. Miss it and you have a list of symptoms to fight one at a time forever, each one growing back because the action that feeds it was never named.

What requires the isolation: the confirmation. You can only name one action back to a person cleanly enough to land, and it has to be the right one, the load-bearing one, because naming a symptom produces a shrug and naming the keystone produces the stillness. The confirm stage cannot fire on a peripheral action.

What breaks without it: the search ends with a true but useless finding. You correctly identify a real action, and it is genuinely one of the person’s actions, and changing it accomplishes nothing, because it was a branch and not the trunk. The person tries, the action is gone, and the life is unchanged, because the upstream action that mattered was never separated from the downstream ones that did not.

Stage Five: Confirm

Confirm is the body’s agreement. The signal, in the person, that the named action is the real one, given not in words but in a sudden physical change.

An action can be correctly isolated and still fail to land, because the naming was done from the outside, as a verdict delivered to the person. Told what their real action is, a person reacts with defense, and the defense shuts the seeing, because being told what you really do is an intrusion and the mind pushes it out. But shown a description they arrive at themselves, the same person reacts with recognition, and recognition has a physical signature that cannot be faked and cannot be willed. The breath shifts. A sigh arrives. The shoulders drop. They say “yes” in a way that is different from social agreement, or they go quiet, or they say “that is what I have been trying to say.” The body acknowledges that the action has been touched.

This is the only reliable test that the engine ran correctly. Not the cleverness of the reading, not the confidence of the observer, not the internal logic of the diagnosis. The relief signature in the person whose action it is. A reading that produces argument, qualification, “yes but,” is either wrong or was delivered as an announcement, and either way it has not confirmed. A reading that produces the drop, even in rough and incomplete form, even before every detail is right, has hit the action. The signature is prior to the precision. You can refine the words afterward. You cannot manufacture the drop, and where it does not appear, the engine has not finished, however certain you are that you found the thing.

What requires the confirm: nothing downstream. This is the terminal stage. When it fires, the action has been seen by the person who lives it, which is the only place the seeing was ever trying to reach.

What breaks without it: the action is named and rejected, or named and politely accepted and quietly discarded, because it landed as someone else’s theory rather than as the person’s own recognition. The observer believes the job is done because the words were correct. The words were correct and the seeing did not transfer, because it was announced instead of arrived at, and an announced truth is defended against, not absorbed.


PART THREE: THE THREE MOST COMMON CONSTRAINT LOCATIONS

The chain has five links, but in practice the breaks cluster. Three locations account for the overwhelming majority of failed attempts to find the action running a life.

The first is the surface. This is the constraint for almost everyone who tries to find the action by asking, including everyone who asks themselves. They route the entire search through speech and reflection, collect a clean and confident account, and never realize the account is the one layer structurally guaranteed not to contain the action. This is the most common break by an enormous margin, because asking is the natural thing to do and watching is not, and the failure is invisible precisely because the spoken answer sounds so reasonable. The search feels complete and never reached the action at all.

The second is the isolate. This is the constraint for the perceptive, the observer who watches well, surfaces real leaks, sees them cluster, and then stops at the first real action instead of finding the one running the others. They are not wrong about what they found. They found a real action. They mistook a branch for the trunk, named a symptom as the cause, and aimed the whole effort at a downstream action that grows back as fast as it is cut, because the upstream action feeding it was never separated out. The perceptiveness is real and it stalls one stage short of the lever.

The third is the confirm. This is the constraint for the one who finds the right action and ruins it by telling. They surface, cluster, and isolate correctly, arrive at the true load-bearing action, and then deliver it as a verdict, “here is what you actually do,” and the defense slams shut and the seeing never transfers. They were right and it did not matter, because they announced a truth that can only be absorbed when it is arrived at. This break is the most frustrating, because the work was done and the landing was lost in the last move, by the impatience to be seen as the one who saw.


PART FOUR: HOW THE SEARCH HIDES THE CONSTRAINT

The chain has a property that makes it nearly impossible to debug from the inside. Every one of its five failures produces the same satisfying experience. I found the problem.

From inside, the gather failure, the surface failure, the cluster failure, the isolate failure, and the confirm failure all feel the same. They all feel like arriving at an answer. The searcher reaches a named action, feels the closure of having an explanation, and stops, and the closure feels identical whether the action found is the real one or a decoy thrown up by a stage that quit early. The mind does not distinguish a true finding from a premature one by any internal sensation, because both end the discomfort of not knowing, and ending that discomfort is what the mind was actually optimizing for.

This is the same trap that produces the confident wrong answer everywhere. The need to have found something is stronger than the need to have found the right thing, and a plausible action that ends the search will be accepted over a continued search that might find the real one, because the plausible action delivers the relief of closure now. The searcher is not lazy. They are responding to the pull of resolution, which arrives the moment any answer is reached, regardless of whether the answer is load-bearing.

And the false closure is expensive, because it ends the search at exactly the wrong moment. If you believe you have found the action, you stop gathering, stop watching, stop checking for convergence, stop asking whether this is the trunk or a branch, stop watching for the body’s confirmation. The certainty that you have it is the precise thing that prevents you from finding it. Four of the five stages are abandoned the instant a plausible answer appears, and the plausible answer is usually the spoken one, the salient one, the symptom, the branch, the announced verdict that produced no drop. The feeling of having found the action is the single greatest obstacle to finding it.


PART FIVE: FINDING WHERE YOUR SEARCH BREAKS

The repair is impossible until the starved stage is named, and the starved stage cannot be named from the feeling of the search, because the feeling is the same for all five, the feeling of having found something. It has to be found by interrogating each stage directly. Five questions, asked in order, each one isolating one link.

How many separate instances is this reading built on, or is it built on one vivid day? If the action you have named comes from a single dramatic moment, the gather is below threshold, and you have the salient action rather than the frequent one. Nothing downstream is trustworthy until the pattern is drawn from a stretch of days, not a snapshot.

Did this action come from watching behavior, or from asking and being answered? If you found it by asking the person, or by asking yourself, the surface is the constraint, and what you have is the version made for speech. The action you want did not arrive in any answer. It arrives in the workaround, the returning complaint, the avoidance, the disproportionate defense, the body, the unguarded sentence. If you have not watched for those, you have not surfaced anything yet.

Do several independent signals point at this action, or just one? If the reading rests on a single leak, the cluster has not formed, and you may be holding a coincidence. Check it against the next behavior and the next. Either they converge on it or they scatter, and until they converge you have a candidate, not a finding.

Is this action the one producing the others, or is it one of the ones being produced? If the action you named is painful and visible and complained about, suspect it is downstream. Ask what action sits above it generating it. If removing your candidate would leave the rest of the cascade intact, you have a branch, and the isolate stage is not done. The trunk is the action whose removal collapses the others.

When the action was named, did the body drop, or did the mind argue? If naming it produced defense, qualification, a reasonable “yes but,” either the action is wrong or it was announced instead of arrived at. The confirm has not fired. A correct, well-delivered reading produces stillness and a sigh, not a rebuttal. No drop, no confirmation, however certain you are.

The first question that returns a failing answer is your constraint. Stop there. The stages below it are not your problem yet, and working on them is the precise form of wasted motion this whole document exists to prevent.


PART SIX: WHY THE STAGES CANNOT BE BUILT OUT OF SEQUENCE

The order of the chain is not a suggestion. It is a set of dependencies, and working a downstream stage on top of a broken upstream one is effort poured into a stage that cannot yet hold it.

You cannot surface leaks from instances you have not gathered. The leaks are properties of a pattern, and a pattern is a property of a series. Try to read the action off a single day and there is no recurrence to read, only the salient event of that one day, which is rarely the action that repeats. The surfacing depends entirely on having enough frames for the quiet, frequent action to appear against the noise.

You cannot cluster signals that have not surfaced. Convergence requires multiple leaks to converge, and if the search is still routing through asking, no real leaks have appeared at all, only spoken answers, and spoken answers do not converge on the hidden action, they converge on the prepared story. The cluster is built from surfaced behavior, and without it there is nothing to triangulate.

You cannot isolate the load-bearing action from a single signal. Knowing which action runs the others requires seeing how many of the others route through it, and that is exactly what the convergence shows. With only one leak you cannot tell central from peripheral, trunk from branch, because centrality is measured by how much converges, and a single signal measures nothing. The isolate stage is made of the cluster.

And you cannot confirm an action you have not isolated. The body drops for the keystone, not for a symptom, so naming a downstream action back will produce a shrug at best, and the confirm will read as failure when the real failure was upstream, at the isolate. The confirmation is a test of the isolation, and a test cannot pass on an input the earlier stage got wrong.

So the order is fixed. Gather the instances. Watch until the leaks surface. Hold the candidates until the signals cluster. Separate the one action the cluster centers on. And only then name it back, lightly, and watch the body for the drop that confirms. Run it in this order and each stage stands on a finished one beneath it. Run it out of order and you are reading structure off noise, naming branches for trunks, and announcing verdicts the body was never going to confirm.


PART SEVEN: WHAT HAPPENS AFTER EACH STAGE IS BUILT

Fixing the constraint does not finish the search. It relocates the work to the next-weakest stage. This is the property that makes the chain an engine and not a checklist, and missing it is how people repair their real bottleneck, feel the surge of progress, and then are baffled when the action still does not become clear.

Fix the gather and a pattern starts to appear, and almost immediately the surface becomes the constraint, because now there are enough days to show recurrence, but if the days are being filled with spoken self-reports the recurrence is only the recurrence of the prepared story. The win at having enough instances exposes the weakness of asking instead of watching.

Move from asking to watching and the leaks begin to appear, and now the constraint moves to the cluster, because a watcher new to it will see real leaks and over-read each one, building a story from the first vivid signal. The task becomes the discipline of waiting for convergence, holding candidates loosely until several independent leaks meet.

The signals start to cluster and a real structure appears, and now, surprisingly to most, the constraint moves to the isolate, because the cluster often lights up several real actions at once, and the work is no longer finding a real action but finding the one that runs the rest. The win at seeing structure exposes the harder question of which part of the structure is upstream.

And once the load-bearing action is isolated, the final constraint is the confirm, which is not a matter of being more right but of delivering with enough restraint that the person arrives at the action themselves instead of being handed it. After that the search on this action is finished. The constraint leaves this action entirely. It moves to the next life you want to read, or the next layer of your own, and you run the chain again, faster now, because you have done it before and you know it is an engine and not a flash of insight.


PART EIGHT: THE ENGINE IN FULL

The Complete Chain

                  THE ENGINE OF IDENTIFYING ACTION

  ┌───────────────────────────────────────────────────────────┐
  │  1. GATHER     enough separate instances accumulate         │
  │                >> a pattern can rise out of the noise        │
  └───────────────────────────┬───────────────────────────────┘
                              │  produces a series to read
  ┌───────────────────────────▼───────────────────────────────┐
  │  2. SURFACE    the action leaks into behavior where         │
  │                speech refused it                            │
  │                >> the real action appears, unasked          │
  └───────────────────────────┬───────────────────────────────┘
                              │  produces real signals
  ┌───────────────────────────▼───────────────────────────────┐
  │  3. CLUSTER    several independent leaks converge on        │
  │                one point                                    │
  │                >> a structure, not a coincidence            │
  └───────────────────────────┬───────────────────────────────┘
                              │  produces a located action
  ┌───────────────────────────▼───────────────────────────────┐
  │  4. ISOLATE    the one action running the others is         │
  │                separated from the field                     │
  │                >> the trunk, not a branch                   │
  └───────────────────────────┬───────────────────────────────┘
                              │  produces the lever
  ┌───────────────────────────▼───────────────────────────────┐
  │  5. CONFIRM    the action is named back and the body        │
  │                drops                                         │
  │                >> the person sees it themselves, and it      │
  │                   can no longer hide                         │
  └───────────────────────────────────────────────────────────┘

         output: the one action, surfaced cleanly enough
                 that naming it produces recognition,
                 because the seeing was arrived at,
                 not announced

Read as a system, the engine says one thing. At no point does finding the action run on the action being asked to name itself. The gather replaces the snapshot with a series. The surface replaces the question with observation. The cluster replaces the single clever guess with convergence. The isolate replaces the loud symptom with the quiet cause. And the confirm replaces the delivered verdict with the arrived-at recognition. Every stage is a transfer of the search off the part of the person that cannot see the action and onto behavior, which has been showing the action all along, in plain view, to anyone who stopped asking and started watching.

The Shift

Before the engine, the search sits on the report, and the report is the weakest possible foundation, because the report is produced by the exact part of the person that is keeping the action out of view. Every search is a question, and the question returns the prepared answer, and the prepared answer is the one layer that cannot contain the thing. The search ends at the first plausible story, satisfied, and wrong.

After the engine, the search sits on behavior, and behavior cannot keep the secret the way speech can. The action that will not say its name still has to be performed, and the performing leaves marks, and the marks accumulate across days into a pattern that points, and the pattern is read, not asked for. The person is not interrogated. They are watched, with care, until the thing they could not say shows itself in what they do, and then it is shown back to them gently enough that they meet it as their own.

Finding the action running a life is not a flash of insight granted to the perceptive. No one is that perceptive on a single day, and the people who appear to be are not guessing. It is an engine, run in order, gathering, watching, clustering, isolating, confirming, producing a reading so grounded that when the action is finally named the person goes quiet, because they have been shown the thing that was steering everything and they can feel that it is true.

That is not insight.

It is engineering.

And the action was always visible, because it was never hidden in the words. It was only ever hidden from them.


CITATIONS

The limits of introspective report: R. Nisbett and T. Wilson, “Telling More Than We Can Know: Verbal Reports on Mental Processes,” Psychological Review, 1977. People confidently report causes of their own behavior that demonstrably did not drive it, and deny the causes that did.

The felt versus the stated problem: the distinction between the layer a person describes and the layer they would pay to end is developed in THE MACHINERY OF THE FELT PROBLEM, from which the six behavioral leaks are drawn.

Habit and the invisibility of frequent action: W. Wood, J. Quinn, D. Kashy, “Habits in Everyday Life,” Journal of Personality and Social Psychology, 2002. A large share of daily behavior is performed automatically in stable contexts and goes unnoticed by the person performing it.

Keystone behavior and cascading change: C. Duhigg, The Power of Habit, 2012. Certain single actions sit upstream of many others, and changing the upstream one shifts the cascade beneath it.

The bottleneck that governs a chain: E. Goldratt, The Goal, 1984. The output of any chain is set by its single binding constraint, and effort spent anywhere else is wasted until that constraint is found.

The presenting problem versus the working problem: the clinical observation that the issue a person first names is rarely the issue treatment resolves is standard across the psychotherapy literature on case formulation.

THE MACHINERY OF THE FELT PROBLEM. The layer beneath the spoken one, and the six behaviors through which it leaks. The instrument the surface stage runs on.

THE MACHINERY OF THE ENGINE OF ENDLESS ACTION. The companion engine. This one finds the action running a life. That one builds an action that runs for a lifetime.

THE MACHINERY OF ENDING ACTION. What to do once the action is found. The mechanism by which a standing action is cut clean and does not return.

THE MACHINERY OF CONSTRAINTS. The governing logic. One bottleneck sets the output of any chain, including the chain of a life.