OLD SCRIPT DETECTED
“Any inconsistency means it's happening again”
Try this response:
“I'm scanning, not seeing. I name what I'm doing before I build the timeline.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Any inconsistency means it's happening again”
YOUR RECORDED RESPONSE
“I'm scanning, not seeing. I name what I'm doing before I build the timeline.”
ONE PRIVATE MOVE
When you notice an inconsistency, write down the gap you found and one honest question: 'Does this actually need clarification, or is my scanner treating normal human vagueness as a threat signal?' Answer in writing, then decide: ask directly, or let it rest. Keep the note…
The Receipt That Didn't Match the Story
- The Scanner Makes Its CaseYou ask what time they left work. 'Around 5:30,' they say. You see the badge swipe time later: 5:47. That seventeen-minute gap wasn't mentioned. Your mind doesn't file this under 'normal human vagueness.' It files it under 'the beginning of the pattern again.' One inconsistency. One. And suddenly you're in the hallway at midnight, constructing the timeline, because that gap is proof the scanner was right to stay vigilant. This is how it works: the contradiction lands, and every system you have treats it as a fresh instance of the original breach.
- What You're Actually ObservingThe scanner was installed because something real happened. That part is not in question. But a seventeen-minute lag in recall, a detail that shifts because someone was tired or thinking of something else, a story that gets refined when asked a second way—these are the ordinary texture of human speech. The scanner can't tell the difference between a dead phone battery and a deliberate silence because it was built to catch the one thing that actually broke trust. It has no off switch. It has no recalibration menu. It just keeps scanning everything at the same threat level, and calling every minor discrepancy the same category as the thing…
Name the Scan, Then Check Reality
Before the midnight hallway, before the investigation loop, you can interrupt one step earlier. When you notice the contradiction, you can say to yourself—only to yourself—'I'm scanning, not seeing.' That's not denying what you found. It's naming what you're doing. Then you make a choice: Is this inconsistency actually concerning enough to ask about directly? Or is it the kind of small detail-shift that happens in ordinary life? If it matters, say it out loud to the person who can answer it, not to your own head in the dark. If it doesn't, let the scanner finish its alert and then step away from the construction site. The scanner…
TRACE · 01/04
How this script runs you
- A small gap in someone's timeline—they said one time, the evidence shows another—launches a full private investigation that feels identical to uncovering the original lie.
- You catch yourself checking details without deciding to check, then feel shame for the checking itself, because checking feels like proof you've become the person you didn't want to be.
- A story that shifts slightly when told a second way registers as a broken promise, even though you know people forget small details, because your threat-detector can't separate negligence from intentional deception.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Trust Scanner
Every inconsistency proves the same thing the original breach proved. A forgotten timestamp, a detail refined in retelling, a minor contradiction—they all belong in the same box as the lie that actually happened. If the scanner catches it, it must mean the pattern is starting again. Small gaps are not small; they are early warning signs of the exact category of betrayal you promised yourself would never happen twice.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- I'm scanning, not seeing. I name what I'm doing before I build the timeline.
- This inconsistency is real, and I decide now whether it's actually worth asking about.
- One data point at a time: I check this one thing against reality, then I stop.
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
“Any inconsistency means it's happening again”
I say
“I'm scanning, not seeing. I name what I'm doing before I build the timeline.”
Then I do one thing
When you notice an inconsistency, write down the gap you found and one honest question: 'Does this actually need clarification, or is my scanner treating normal human vagueness as a threat signal?' Answer in writing, then decide: ask directly, or let it rest. Keep the note…
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Any inconsistency means it's happening 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 contradiction feel exactly like the original lie?
The scanner doesn't have categories. It caught something once, and now it treats every inconsistency as the same threat level. A timeline gap and a deliberate deception look identical to the system that was built to catch one of them. The difference lives in what you do next—ask directly, or build a theory in silence.
If I notice an inconsistency, doesn't that mean I should check for more proof?
Noticing is not the same as verifying. The moment you shift from 'I saw a gap' to 'I'm building a case,' you've left reality-testing behind. One inconsistency is information. Constructing a full timeline from a single detail is how the scanner locks into loop mode. If the gap matters, ask. If you're building a pattern from one thread, you're scanning, not checking.
What if this time the inconsistency actually is the start of the pattern happening again?
Then asking directly will tell you that. The scanner didn't fail because it noticed the gap—it failed if it spent three hours constructing an entire narrative from a single detail without checking a single fact. Reality-testing means asking one question and listening to one answer. Not building the case first, then asking for permission to believe it.
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