The enemy is not failure. Failure is a verdict. The enemy is non-executability.
The Question
“What should I do?” is a question almost everyone asks and almost no framework answers honestly. The standard responses are either too large or too small. Too large: find your purpose, discover your passion, align with cosmic meaning. Too small: optimize your habits, track your metrics, increase your output. The large answers are overspecified — they demand a five-role existential architecture from a target that supplies one life. The small answers are underspecified — they flatten a being capable of criterion revision into a set of behaviors to be tuned.
The framework developed in the earlier essays offers a different kind of answer. Not a moral commandment. Not a productivity system. A structural one.
The Structural Answer
If the primitive is self-sustaining process, and carry-through is an achievement rather than a default, and there is a non-arbitrary asymmetry between sound running and unsound running, then the question “what should I do?” has a structural shape:
Do things whose carry-through you can sustain.
That is not a motivational slogan. It is a constraint derived from the framework’s own terms. If value is structural — if the difference between holding and collapsing is real and intrinsic — then a life oriented toward things that carry through is structurally different from a life oriented toward things that cycle, collapse, or never ground out. The difference is not aesthetic. It is not a matter of taste. It is the same asymmetry identified in Value Is Structural, applied to conduct.
What Carries Through
A thing carries through when it satisfies the conditions the framework identifies at each level of explicitness.
At the level of persistence: does it hold? Is the thing you are building, making, or sustaining structurally capable of continuing without constant emergency intervention? A project that collapses the moment you stop propping it up is not carrying through. It is being carried. A friendship that survives only because one person absorbs all the maintenance is being carried. A business model that depends on never being examined closely is being carried. The difference matters because one is sustainable and the other is not, and the framework says that difference is real.
At the level of distinction: is there a real difference between what you are doing and not doing it? Some activities produce no observable partition. They leave the world structurally identical to how it was before the effort. Effort that produces no external verdict is persistence without distinction. It loops. A thing that carries through produces a difference that holds — a structure, a relationship, a built object, a changed condition.
At the level of selection: are you operating under criteria you can own? Selection without owned criteria is drift. You are still selecting — the framework says selection is always happening once three roles are explicit — but the criteria may be inherited, unexamined, or structurally incoherent. A life that selects under criteria it has never inspected is not failing to select. It is selecting badly. The verdicts are real but the criteria behind them are noise.
The Enemy
The enemy is not failure. Failure is a verdict. It is arity 3. It is selection working as intended. A thing that fails has been evaluated against a criterion and found not to hold. That is the process functioning. Failure carries information. Failure feeds back. Failure is part of sound running.
The enemy is non-executability.
Non-executability in a life looks like this: asking questions your situation cannot ground. Demanding verdicts from criteria you cannot sustain. Cycling through options without ever producing a verdict. Building dependency structures that route through themselves without anchor. Holding yourself to a standard imported from a context that does not apply to yours.
“Why haven’t I achieved X by age Y?” is a five-role question aimed at a one-role target. It imports a foil (people who achieved X by Y), a criterion (timeline-indexed success), a justificatory demand (what went wrong?), and a modal space (a world in which you could have done it differently) — none of which the target supplies. The target is your actual life, running as it runs. The question exceeds it. The felt depth of the dissatisfaction is the question’s structural complexity, mistaken for depth in the subject.
“Should I pursue A or B?” is an arity-2 question that may be aimed at a richer target. If the real situation has more internal structure than a binary — if A and B are not exhaustive, if the criteria for choosing between them are multiple and independent, if the relevant dimensions of your life do not collapse into one axis — then the question is underspecified. The sense of being stuck is the question failing to represent the target’s actual structure.
The diagnostic works on life questions the same way it works on philosophical ones. When the question’s demanded structure exceeds or falls short of its target’s, the result is predictable: overspecification produces phantom depth (existential dread that is really structural mismatch), underspecification produces false dichotomy (feeling trapped between options that do not exhaust the space).
What This Looks Like in Practice
Match your questions to your targets. If the question you are asking yourself generates more roles than your situation can fill, the question is the problem. Reformulate it at the arity your life actually supports.
Select under criteria you can own. Not criteria inherited from a context that does not apply. Not criteria absorbed from people whose situations differ from yours. Criteria that you have inspected, that ground out in your actual conditions, that produce verdicts you can endorse when you see them clearly.
Build things that carry through. Things whose persistence is structurally sound, not propped up. Things that produce real distinction — observable differences between the world with them and the world without them. Things that can survive contact with selection and return a verdict you can feed back into further action.
Let failure do its work. A verdict of “this did not hold” is not a catastrophe. It is the system functioning. The catastrophe is never producing a verdict at all — cycling through planning and deliberation and option-weighing without ever committing to a selection that could fail. The catastrophe is endless self-blocking: planning, weighing, revising, and reframing until nothing executable ever reaches action.
What This Does Not Say
This is not a command to be productive. Productivity frameworks optimize for output volume. This framework does not care about volume. It cares about whether what you do carries through — whether the running is sound, not whether the running is fast.
This is not a command to be stoic. The framework does not say “accept collapse without feeling.” Collapse is real. Loss is real. The asymmetry between carrying through and falling apart is felt, not just observed. The claim is that the asymmetry is structural, not that it is painless.
This is not a command to persist at all costs. Pathological persistence — sustaining a process past the point where its criteria still ground — is the structural equivalent of an ungrounded dependency cycle. The validators catch exactly this in formal systems. In life, the equivalent is staying in an arrangement whose carry-through depends on criteria that no longer hold, or that never held. Knowing when to stop is itself a verdict. It is selection working, not selection failing.
This is not a system for eliminating uncertainty. Uncertainty is not non-executability. A well-formed question can have an uncertain answer. An executable process can produce a verdict you did not predict. The framework does not promise clarity. It promises structural soundness — that the questions you ask can be grounded by the targets you have, and that the selections you make are under criteria you can own.
The Directive
Given that there is running, what should be carried through?
Not everything. Not anything. The things whose persistence is earned rather than forced. The things whose distinctions are real rather than fabricated. The things whose selections ground out in verdicts you can endorse and feed back into further conduct.
A finite being capable of explicit selection is not merely carried by process. It participates in the criteria by which its own running is shaped. That participation is not optional once selection is explicit. You are already selecting. The only question is whether the selection is owned.
Author
Tom Passarelli
License
CC0. This work is in the public domain.