REALITYWIPE

OLD SCRIPT DETECTED

Taking longer to recover means I'm washed

Try this response:

Four days of soreness is data, not a verdict.

Take the 60-second self-check

The Fourth-Day Stairs

The Fourth Morning

On the fourth morning after a hard interval session, your calves are still tight going down the stairs — two years ago that soreness was gone by day two. You open the app, see the recovery score sitting low, and before you've even had coffee you're running the math: three days it used to take, now it's four, and climbing.

The Quiet Trim

So you quietly trim tonight's session before you've even felt it — drop a set, skip the scrimmage, tell the group chat it's 'an easy week.' You start scheduling around soreness you're predicting instead of soreness you've actually got, and you watch the twenty-four-year-old on your team take the reps you didn't sign up for.

The Private Log

Instead of trusting the math you did in your head, open a private note and log today's actual numbers — reps finished, soreness out of ten, how the stairs felt. Do that for a week. A slow day next to three solid ones is a pattern you can read; one stiff morning was never a verdict.

TRACE · 01/04

How this script runs you

  • You check a recovery score before deciding whether today's effort was earned or a mistake.
  • You start calling a slower recovery week 'proof' instead of just logging what actually happened.
  • You catch yourself counting how many days a session used to cost you, like a scoreboard running against you.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Expiration Date

If a session takes longer to recover from than it used to, the count of days is treated as a verdict on whether you still belong on the field — not as one variable among many that changes with load, sleep, and training history.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • Four days of soreness is data, not a verdict.
  • My recovery time changed. My training history didn't disappear.
  • I can log today's numbers without turning them into an age.

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

Taking longer to recover means I'm washed

I say

Four days of soreness is data, not a verdict.

Then I do one thing

Open a private note, log today's actual soreness and rep count, and check it again after a week of entries instead of guessing.

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: "Taking longer to recover means I'm washed". 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

Is four days of soreness after a hard session actually a sign I'm 'washed'?

A longer soreness window mostly reflects that specific session's load and your current recovery capacity — it isn't a single verdict on your overall athletic worth. A pattern across several sessions tells you more than any one slow week.

Should I quietly scale back a session in advance because I expect to recover slower now?

Trimming a session before you've even felt it locks in the story before you've tested it. Running the session as planned and logging what actually happens afterward gives you real numbers instead of a prediction.

What does it mean if a teammate half my age recovers faster than I do?

Recovery speed differs with age, training history, sleep, and load — a teammate's quicker bounce-back describes their circumstances, not a ranking of who still belongs in the game.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script