A note before reading. This is a practice tool, not an introduction to the framework. It assumes you already know what the pipeline is, what Move 3 means, and why "I" is treated as a thought rather than an entity. If you haven't read the
Pipeline, the
Analogy, or the book first, the diagrams below will read as opaque jargon. Start there. Come back here when you want a structural reminder for catching the pipeline as it runs.
Trigger I
Rumination
When the mind replays past events
Master · When Rumination Starts
Three checkpoints. Run them in order.
Stop at the first that fires.
CHECKPOINT 1
Is this image repair disguised as analysis?
The loop is not seeking resolution. It is looking for a version where the image survives.
↓
CHECKPOINT 2
Where is the "I" in this thought?
Look directly. Only more thoughts return. The entity is not there — only its name keeps appearing.
↓
CHECKPOINT 3
What is the event, stripped of the identity claim?
Two layers: descriptive event (can be true) and identity claim (structurally void). Register the first. Reject the second.
Fail Mode 1 · Treating Thoughts as Entities (Move 3)
thought
content on the screen
→
entity with capacity
system-level property
A thought cannot possess intelligence — only describe it.
Capacity belongs to the system. The thought describes; it does not possess.
Fail Mode 2 · The Recursive Trap (Framework as Identity)
"I see through the pipeline"
— identity reinstalls →
"I am someone who sees through the pipeline"
The seeing was real. The "I saw" is the new material.
The pipeline is content-agnostic — including its own dismantling.
Fail Mode 3 · Counter-Identity Defense (Replayed)
THEM (in memory)
"you are X"
Having ⊢ Being
⇆
YOU (rehearsing)
"I should have said Y"
Having ⊢ Being
The replay is rehearsing a defense built on the same rule that hurt you.
"What I should have said" is the pipeline running on the memory, looking for a counter-identity that holds.
Fail Mode 4 · Capacity Conflated with Expression
capacity
dispositional · system property
=
expression
occurrent · time-bound event
Having had an expression is not being the capacity.
One performance is not a fixed property. Expression and capacity are different ontological categories.
Trigger II
External Judgment
When someone says something about you
Master · The Comment Lands
Three checkpoints. Run them in order.
Stop at the first that fires.
CHECKPOINT 1
Whose pipeline produced that comment?
Their machinery using you as raw material for their image construction. The comment is doing a job for them. Information about their state, not a verdict on yours.
↓
CHECKPOINT 2
What two layers does the comment carry?
Descriptive (the behavior, the event) — can be true. Identity (the entity claim) — structurally void. Register the first. Reject the second.
↓
CHECKPOINT 3
Who is the "I" the comment landed on?
Look. Only thoughts return. The comment reaches an address with no one home. The verdict has no subject to land on.
Fail Mode 1 · Counter-Identity Defense
THEM
"you are X"
Having ⊢ Being
⇆
YOU (defending)
"I am not X, I am Y"
Having ⊢ Being
Same rule. Opposite outputs. Defending with counter-identity uses the rule that hurt you.
The speed of the defense reveals the rule was already running in you.
Fail Mode 2 · Resisting the Occurrence
Resistance fights an event already in the past. Suffering is the held mobilization, not the event.
Letting the event stand ≠ accepting its content. You can respond to behavior without inheriting the verdict.
Fail Mode 3 · The Reinterpretation Door
"you are stupid"
if "I" = entity
→
structurally true
if "I" = thought
The "I"-thought has no capacities. So "you are stupid" is literally accurate at the thought level.
Apply consistently — to positive judgments too. Selective application puts you back in the pipeline.
Trigger III
Comparison
When you notice someone else's capacity, status, or success
Master · The Comparison Fires
Three checkpoints. Run them in order.
Stop at the first that fires.
CHECKPOINT 1
What is actually being compared?
Two systems differing on a dimension. Their capacities under those conditions vs yours under these. That is the descriptive fact. Nothing about a self has been said yet.
↓
CHECKPOINT 2
Where did "I am less" enter?
Capacity gap → identity claim → ranking of fictional selves. Three errors stacked. The feeling of "less than" is the output of the stack, not data about worth.
↓
CHECKPOINT 3
Can the information be used without the suffering?
Functional use: register the gap, learn, adjust strategy. Identity use: convert the gap into self-evaluation. Same data, two operations. Use the first. Drop the second.
Fail Mode 1 · Capacity Becomes Entity
REAL
"their system
processes faster"
→
CONVERSION
"they are
smarter"
→
Three moves: capacity → identity → ranking. Each is a category error compounded.
The suffering enters at the conversion. Watch where the slide happens.
Fail Mode 2 · The Egalitarian Residue
CAPACITY
unequal
empirical · varies across systems and conditions
+
ENTITY-STATUS
equal
structural · zero entity behind any system
Systems vary in capacity. Selves do not vary in significance — because they don't exist.
Neither pride nor inferiority has anything to attach to.
Fail Mode 3 · The Hidden Childhood Pattern
CONDITIONING
comparative position
secured belonging
→
PRESENT
ranking feels
like safety
→
FICTION
pipeline runs
on old data
The need to rank is not really about the rank. It is the body still treating relative position as relative safety.
The original conditions are gone. The pattern continues to fire.
Trigger IV
Self-Evaluation
When something went well or badly
Master · The Verdict Forms
Three checkpoints. Run them in order.
Stop at the first that fires.
CHECKPOINT 1
Is this pride or shame? Same machinery.
Positive and negative self-evaluations are the same pipeline producing different outputs. If you accept one direction, the other will eventually run on you. Apply the lens consistently.
↓
CHECKPOINT 2
Did the system perform, or did the "I" perform?
Capacity is system-level. The "I" claims credit for what the body, the conditioning, the conditions produced. The narrator takes ownership of work it did not do.
↓
CHECKPOINT 3
Watch the asymmetry. Where does it show?
"I figured it out" vs "the conditions were bad." The "I" claims authorship for favorable outcomes and deflects to conditions for unfavorable ones. The selective claim itself proves the "I" was never the source.
Fail Mode 1 · Pride and Shame as the Same Output
SUCCESS
"I am brilliant"
Having ⊢ Being
(positive valence)
≡
FAILURE
"I am useless"
Having ⊢ Being
(negative valence)
Both are Move 3 outputs. Same rule, opposite valences.
Accepting pride installs the structure that produces shame. Apply the framework to both equally.
Fail Mode 2 · Capacity Conflated with Expression
capacity
dispositional · system property
=
expression
occurrent · time-bound event
Having had an expression of intelligence is not being intelligence.
Expression is an event that happened. Capacity is a feature of a system. Different categories.
Fail Mode 3 · Selective Attribution
FAVORABLE
"I made it happen"
credit claimed by the "I"
⇄
UNFAVORABLE
"conditions were bad"
deflected to the system
The asymmetry is the tell. If the "I" had authorship, both outcomes would be its responsibility.
Selective claiming proves the "I" was never the source — only a thought commenting after the fact.
Fail Mode 4 · The Lifetime Project
→
VERDICT
"I am X"
consolidates
→
PROJECT
develop · fix ·
improve "I"
Self-evaluation often becomes lifetime self-development — same pipeline running across years.
Renovating the entity is not dissolving it. Growth happens to the system. The "I" claims ownership.
Trigger V
Anticipation
When the pipeline runs on imagined future events
Master · The Future Becomes Stakes
Three checkpoints. Run them in order.
Stop at the first that fires.
CHECKPOINT 1
Is this preparation or image protection?
Real preparation orients the system to act effectively. Image protection rehearses scenarios where identity survives. They feel similar. The difference is whether the work serves the task or the self-image.
↓
CHECKPOINT 2
What is the imagined event meant to do?
Reveal identity, threaten image, confirm worth, secure approval. The future event is being treated as data about the entity — before it has happened. Identity-stakes manufactured around a hypothetical.
↓
CHECKPOINT 3
Where is the "I" being protected from this future?
The future hasn't happened. The "I" defending against it is a thought constructed now to protect a thought that will be constructed then. Two fictions, one defense, no entity in either.
Fail Mode 1 · Preparation as Image Protection
FUNCTIONAL
"prepare for the task"
orients system to act
vs
IDENTITY
"prepare to not look stupid"
defends future self-image
Preparation directed at the task feels different from preparation directed at the image.
The image version exhausts more, lands worse, and converts every step into evidence about the entity.
Fail Mode 2 · Self-Fulfilling Pressure
ANTICIPATION
"I might
fail"
→
CONDITIONING
anxiety degrades
performance
→
CONFIRMATION
outcome confirms
the fear
Anticipation doesn't predict the future — it conditions it. The anxiety degrades the performance.
Then the outcome arrives and the pipeline says: "see, I was right about myself."
Fail Mode 3 · Pre-Suffering
imagined event
hasn't occurred
→
real contraction
body responds now
The body cannot tell the difference between a real event and an imagined one. Anticipation produces the same shame and fear the actual event would.
You suffer the verdict before any verdict has been rendered. Often most of the suffering is in the anticipation, not the event.
Fail Mode 4 · Constructing Future-Identity
IMAGINED
"if I fail
tomorrow"
→
PRE-VERDICT
"I will be
a failure"
→
PRESENT IDENTITY
"I am someone
who could fail"
The pipeline manufactures present identity from a future that may never happen.
You are not the failure you fear becoming. The "I" doing the fearing is itself a thought, constructed now, defending a thought that doesn't yet exist.
Fail Mode 5 · Decisions Become Identity Questions
PRACTICAL
"what serves the situation?"
solvable · condition-based
vs
IDENTITY
"what kind of person
would I be?"
unsolvable · entity-based
The pipeline converts practical questions into identity questions. Each branch becomes a future-self to defend or pursue.
The decision was about what to do. Ego makes it about who to be. The first has answers. The second has only constructions.
Trigger VI
Praise
When positive feedback consolidates identity silently
Master · Praise Lands
Three checkpoints. Run them in order.
Stop at the first that fires.
CHECKPOINT 1
Is this being received as information or as confirmation?
Information: someone observed the system performed. Confirmation: my image is being validated, the entity is being upgraded. The first is neutral data. The second is the pipeline running silently.
↓
CHECKPOINT 2
Notice the absence of resistance. Is the pipeline running silently?
Negative judgment hurts and triggers examination. Praise feels good and triggers nothing. The pipeline runs without interruption because no pain signals analysis. This is the most invisible activation.
↓
CHECKPOINT 3
What identification just got reinforced?
Praise consolidates an image into load-bearing identity. The same identification will later require defending. Today's pride installs the structure that produces tomorrow's shame.
Fail Mode 1 · Silent Consolidation
NEGATIVE JUDGMENT
hurts
triggers examination
vs
PRAISE
feels good
no examination triggered
Pain interrupts. Pleasure does not.
The pipeline running on praise is the same pipeline — but it consolidates identity unchallenged because nothing prompts the dismantling.
Fail Mode 2 · Building Load-Bearing Identity
→
CONSOLIDATION
"I am
capable"
→
LOAD
capability now
must be defended
Each praise event is metabolized into identity. The identity becomes load-bearing.
What once felt good now requires continuous confirmation, and any threat to it lands harder than before the praise was received.
Fail Mode 3 · Asymmetric Application of the Framework
CRITICISM
"the 'I' has no capacities"
framework applied
vs
PRAISE
"yes, I am that"
framework suspended
Using the framework only against negative judgments puts you back in the pipeline.
The framework treats positive and negative identifications identically. Selective application is image protection.
Fail Mode 4 · Praise Dependence
INSTALLATION
image built
from praise
→
MAINTENANCE
image needs
continued praise
→
VULNERABILITY
absence of praise
feels like attack
An identity built from praise needs praise to keep existing.
The neutral absence of praise becomes felt as criticism. The pipeline turns silence into a verdict, indifference into rejection.
Trigger VII
Loss / Change
When identification's substrate stops being available
Master · The Ground Dissolves
Three checkpoints. Run them in order.
Stop at the first that fires.
CHECKPOINT 1
What was the "I" identified with that's now leaving?
A role, a relationship, a capacity, a status, a possession. The pipeline built identity around something external. That external is now changing or gone. The grasping is the pipeline trying to keep the structure standing.
↓
CHECKPOINT 2
Is this identity-grief or functional grief?
Functional grief is real — losing a person you loved involves actual loss of presence, shared life, conditions that mattered. Identity-grief is the pipeline mourning the dissolution of its construction. Both can run simultaneously. Distinguish them.
↓
CHECKPOINT 3
What was actually yours to lose?
The role was external. The relationship was relational. The capacity was the system's. The status was conferred by others. The "I" never owned any of it — it identified with what was always external. The loss is real. The diminishment of the "I" is fictional, because there was no "I" being diminished.
Fail Mode 1 · Grasping at the Substrate
EXTERNAL
role · status
· capacity
→
→
GRASPING
cannot let go
without dying
The fusion makes loss feel like death. If "I am my career," losing the career feels like the "I" being annihilated.
But what was lost was always external. The "I" was never the role — it was a thought claiming to be it.
Fail Mode 2 · Restoration as Identity Rescue
FUNCTIONAL
"replace what was lost"
solve a real problem
vs
IDENTITY
"restore who I was"
rescue the construction
Looking for new work and trying to recover a previous identity look similar. They are different operations.
The first solves a practical problem. The second tries to rebuild a self that was never there.
Fail Mode 3 · The New Identity from Loss
→
CONSTRUCTION
"I am someone
who lost X"
→
NEW LOAD
loss-identity needs
defending
The pipeline doesn't just lose identity — it builds new identity from the loss itself.
"The widow," "the laid-off worker," "the one who lost the championship." Same machinery, new content. The construction project resumes immediately.
Fail Mode 4 · Capacity Decline as Self-Diminishment
capacity declined
system property changing
=
"I am diminished"
entity-claim about a thought
Aging, illness, fatigue — capacities change in real time. The system shifts.
"I am less than I was" assigns the change to an entity that was never there. The system varies. The "I" was a thought all along.