The rule that feels obviousYou see the text sent at 2:47 PM. It's now 3:04, and there's no reply. Your mind assembles a sequence: silence equals avoidance; avoidance equals something to hide; something to hide equals the same thing as before. The rule feels airtight because once you found out about the lie, every delay after that was genuinely suspicious. So now you can't separate a dead phone battery from dishonesty. They look identical in the moment you're waiting.
OLD SCRIPT DETECTED
“Every delay means they're lying again”
Try this response:
“The scanner was built from one real lie. This delay might be something else entirely. I'm noticing the scan, not assuming the result.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Every delay means they're lying again”
YOUR RECORDED RESPONSE
“The scanner was built from one real lie. This delay might be something else entirely. I'm noticing the scan, not assuming the result.”
ONE PRIVATE MOVE
Identify one recent delay that triggered scanning. Write down what the delay meant according to your scanner. Find out what actually happened. Note whether they match. Repeat only if you find a genuine pattern, not a single match.
The three-minute investigation
How one real experience rewires detectionThe scanner wasn't built by paranoia. It was built by evidence. When you discovered the lie, your attention sharpened in a specific way: you learned to notice what you'd missed—the hesitation, the vague timeline, the conversation that stopped when you entered the room. That learning was real and appropriate. The problem is the scanner can't tell the difference between 'this looks like the pattern' and 'this is the pattern.' A forgotten notification sounds like deception because both require your mind to fill in a story about what someone else is thinking.
Testing the scanner on a single delayPick one ordinary delay from today or this week—a text unanswered for two hours, a call not returned until evening, a story with a timeline that doesn't quite match your memory. Sit with the delay itself without checking anything. Write down what your scanner says the delay means. Then find out what actually happened. Don't expect one answer to prove the scanner is broken. Just notice: did the scanner predict accurately this time, or did it predict the shape of the old lie instead of what was really going on?
TRACE · 01/04
How this script runs you
- A two-hour silence in a conversation launches a hidden investigation: checking sent times, reviewing past messages for evidence, reconstructing their location based on previous patterns.
- You notice an inconsistency in a detail—they said they left work at five but mentioned being there at five-thirty—and the contradiction feels identical to discovery of the actual lie, even though this one might be a memory mistake.
- You catch yourself checking something (location, read receipts, search history) and then feel ashamed, which makes you check again to see if the shame itself is justified.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Trust Scanner
Any delay, silence, or inconsistency in their story is the same category of threat as the lie that actually happened. The scanner was right once, so it knows what betrayal looks like. Delays prove something is being hidden. Silence means they're aware you'd find it out, so they're staying quiet. A mismatched detail confirms the pattern.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- The scanner was built from one real lie. This delay might be something else entirely. I'm noticing the scan, not assuming the result.
- If I'm genuinely worried about what the delay means, I can ask directly instead of assembling proof in my head.
- One time the scanner is right doesn't mean it's right every time. I'm learning the difference by checking: what actually happened, not what the wait felt like.
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
“Every delay means they're lying again”
I say
“The scanner was built from one real lie. This delay might be something else entirely. I'm noticing the scan, not assuming the result.”
Then I do one thing
Identify one recent delay that triggered scanning. Write down what the delay meant according to your scanner. Find out what actually happened. Note whether they match. Repeat only if you find a genuine pattern, not a single match.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Every delay means they're lying again". Word for word — the wipe targets the sentence, not the vibe.
- Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
- Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
- Run the loop: play it every morning and night, log one proof action a day for 7 days.
Straight answers
Why does a small inconsistency in a story feel as serious as the original lie?
Your attention learned to detect that specific pattern—the vague moment, the missing detail. When you notice those patterns now, your mind treats them as the same threat level, even though a misremembered time is not the same as deliberate deception. The scanner can't measure degrees; it only has on and off.
If I stop checking when I feel suspicious, won't I miss something real?
Checking in secret doesn't protect you from real problems; it usually confirms the story your scanner is already telling. If something actually feels wrong, naming it directly to the person who can answer it is a different action entirely than checking without asking.
How do I know if the delay is really a sign of something wrong or just a delay?
You find out by reality-testing, not by interpretation. Ask. Then compare the answer to what you predicted the delay meant. Over time, you'll see which predictions match what's actually happening and which ones match the shape of the old lie instead.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Getting Past the Affair: A Program to Help You Cope, Heal, and Move On — Gordon et al., Guilford Press, 2004
- Surviving Infidelity: Making Decisions, Recovering from the Pain — Schneider & Corley, Adams Media, 1999