REALITYWIPE

OLD SCRIPT DETECTED

If I share it and it flops, I'm done

Try this response:

Flops are feedback about a piece. They don't reclassify me.

Take the 60-second self-check

SEE THE PRACTICE

Build a response for this thought—and one move to prove it.

THE THOUGHT

If I share it and it flops, I'm done

YOUR RECORDED RESPONSE

Flops are feedback about a piece. They don't reclassify me.

ONE PRIVATE MOVE

Finish one small piece—a paragraph, a sketch, a caption—intentionally rougher than you'd normally allow, and leave it private without sharing. Notice that nothing happened to you. The work exists. You exist. The flop didn't require an audience.

The Moment Before You Hit Send

  1. 01 / The Thing You've Built Sits Ready

    You've finished a draft. A piece of writing, a design, a video script—something you spent hours on. You read it once more. It feels solid. Then you imagine it landing: the silence, the one dismissive comment, the person who knows better shaking their head. You don't know if that person is real or invented, but the feeling is precise: if this doesn't land, people will know I tried and failed. That's different from just not knowing. That's evidence. So you close the file instead of sharing it.

  2. 02 / The Private Relief That Keeps It Locked

    Not sending it works immediately. The knot loosens. You don't have to wait for the verdict. You don't have to see the proof that you're not as capable as you thought. The cost feels small in that moment—just one piece not shared, just one time being careful. But the rule hardens each time you use it: only release what is impossible to criticize. Since nothing is impossible to criticize, the rule becomes never release. The short-term escape becomes a long-term silence.

  3. 03 / The Moment You Can Name and Stop

    The trigger is always the same: finished work + the image of it failing in front of witnesses. The next time you feel that image, you can name it: that's the judge arriving. Not to make it better. To prevent it from existing at all. At that moment, before you delete or close the file, you can make a choice that has nothing to do with publishing. You can choose to finish something—anything—badly. On purpose. Private. Just to prove to yourself that a flop is a thing that happens to work, not a thing that happens to you.

TRACE · 01/04

How this script runs you

  • You finish something and immediately find reasons it isn't ready—all of them things only a critic would notice.
  • The closer work gets to being shared, the more flaws you see, until you convince yourself it was never good enough to begin with.
  • You can name exactly who would dismiss it, their exact expression, their exact tone—but you've never tested whether that prediction is true.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Blank-Page Judge

If I release something and it fails publicly, I will have proven I don't belong here. The only way to protect my identity is to control whether it ever gets tested.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • Flops are feedback about a piece. They don't reclassify me.
  • I can finish badly in private and still keep the work.
  • Sending something imperfect is how imperfect work becomes better work.

Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.

INSTALL · 04/04

The protocol, on one card

When I think

If I share it and it flops, I'm done

I say

Flops are feedback about a piece. They don't reclassify me.

Then I do one thing

Finish one small piece—a paragraph, a sketch, a caption—intentionally rougher than you'd normally allow, and leave it private without sharing. Notice that nothing happened to you. The work exists. You exist. The flop didn't require an audience.

STATUS: READY_TO_INSTALL

Wipe this thought

4 minutes. Your voice. Free.

Start this exact wipe in the app →

The wipe protocol
  1. Write the thought exactly as it plays: "If I share it and it flops, I'm done". Word for word — the wipe targets the sentence, not the vibe.
  2. Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
  3. Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
  4. Run the loop: play it every morning and night, log one proof action a day for 7 days.

Straight answers

How is 'it'll flop and I'm done' different from just wanting my work to be good?

Wanting quality is about the piece. This thought makes the piece a referendum on you. A flop becomes evidence of who you are, not feedback on what you made. The difference shows up as: you delete work because you imagine failure, not because you found a concrete problem.

If I publish something bad and people do criticize it, doesn't that prove the fear is real?

One piece getting poor response tells you something about that piece in that context. It doesn't tell you that you're done, or that you shouldn't have tried. The thought collapses 'this didn't land' into 'I shouldn't exist as someone who makes,' which are not the same fact.

Why does the judge feel so specific—like I know exactly what the sneering person would say?

Your mind is good at pattern-matching and prediction. But the specificity of the imagined critique doesn't make it accurate. It makes it convincing. That's different. The way to test it is not to argue with the image, but to produce work while the judge is quiet and see what actually happens.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script