REALITYWIPE

OLD SCRIPT DETECTED

She demos what I built and gets the credit

Try this response:

Her demo rides on the system I kept standing up.

Take the 60-second self-check

SEE THE PRACTICE

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

THE THOUGHT

She demos what I built and gets the credit

YOUR RECORDED RESPONSE

Her demo rides on the system I kept standing up.

ONE PRIVATE MOVE

Open a private note and make a three-line list of the invisible pieces you handled this week: one fix, one decision, one cleanup. Save it with today’s date.

The build behind the demo

SCENE_01

Her slide deck, your week

You’re in the room when she opens the deck and walks through the feature like it arrived fully formed. The flow is clean, the bugs are gone, and the questions sound easy because you already solved the hard parts. Then the thought lands: She demos what I built and gets the credit. What she shows is the surface. What you remember is the late-night fixes, the invisible handoffs, the parts that only looked simple because you made them stable.

SCENE_02

The part that turns to bitterness

The private meaning arrives fast: if the demo gets praise, the work itself must not have counted. So you go quiet. You stop offering context in reviews, trim your notes to the bare minimum, and leave the maintenance trail unnamed. Sometimes you even imagine a visible failure, just so the room has to see what held everything together. The cost is that your own work becomes harder to point to, even for you.

SCENE_03

Treat the demo as a routing problem

A cleaner reading is less flattering but more useful: the credit followed the presentation, not the labor. That’s a visibility problem, not a value verdict. You can route attention without a confrontation by naming the backbone in your own record. Write down the systems, fixes, or decisions you carried, then make them readable before the next review or handoff. The work was real before it was visible.

TRACE · 01/04

How this script runs you

  • Your best quarter looks thin on paper because the thing you did best was keep the system from needing rescue.
  • Watching someone else present your work leaves you irritated, then annoyed at yourself for being irritated.
  • You start to fantasize about a breakdown because you think only a visible problem would prove you mattered.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Invisible Infra Script

If I didn’t present it, name it, or make it obvious, then it won’t count as mine. The hidden rule turns clean handoffs and stable systems into proof that you were just background support, so you keep score by visibility instead of by what you actually held together.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • Her demo rides on the system I kept standing up.
  • If it’s missing from the notes, I’ll write the work in myself.
  • The credit path is visible work too, and I can map it.

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

She demos what I built and gets the credit

I say

Her demo rides on the system I kept standing up.

Then I do one thing

Open a private note and make a three-line list of the invisible pieces you handled this week: one fix, one decision, one cleanup. Save it with today’s date.

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: "She demos what I built and gets the credit". 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

Why does this hit harder when the demo is polished?

Because polish hides the rough edge you absorbed. A smooth presentation can make the labor behind it disappear, which can feel like the room is rewarding the surface and erasing the backbone. The sting is about visibility, not only the outcome.

Isn’t this just jealousy?

Sometimes the feeling arrives as jealousy, but the pattern is more specific: you’re reacting to credit drifting toward the person who showed the work while your behind-the-scenes labor stayed unnamed. The signal is often, “my part wasn’t seen,” not “I want what she has.”

What if I can’t make a scene or correct her in the moment?

You don’t have to. The useful move here is private and concrete: record what you built, what you stabilized, and what would have broken without your work. That gives you a clearer trail for your own use later, without forcing an immediate confrontation.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script