OLD SCRIPT DETECTED
“I recalculate the drive time to prove they lied about traffic”
Try this response:
“A map estimate isn't a lie detector. I check what I actually need to know, not what an app can't measure.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“I recalculate the drive time to prove they lied about traffic”
YOUR RECORDED RESPONSE
“A map estimate isn't a lie detector. I check what I actually need to know, not what an app can't measure.”
ONE PRIVATE MOVE
Next time you open a map to check a drive time, first write down what specifically felt off before you opened it. If the line stays blank, that's your answer about what the checking was really for.
Forty-One Minutes, Not Fifty-Five
- 01 / Six-Twelve, Still on the 95
Your phone buzzes at 6:12: 'stuck on the 95, might be a while.' Nothing has happened yet — you don't know if it's true or not — but your thumb is already opening Maps before you've finished reading the message. You type in their office address and yours, set the time to now, and wait for the little clock icon to load a number. You are not curious. You are building a comparison you already know you're going to make.
- 02 / Forty-One Minutes on the Screen
The app returns 41 minutes with current traffic. They said the drive took 55. Fourteen minutes of unaccounted time — not proof of anything, but your mind treats it like a verdict already reached. You screenshot the route. You check Waze too, in case Maps is wrong. You refresh once more, watching the estimate shift by a minute either way, because if you can pin the number down precisely enough, you can finally catch the lie or finally rest. Neither happens. The checking itself becomes the relief — for about ninety seconds.
- 03 / Before You Type the Address Again
The interrupt isn't refusing to open the app. It's the ten seconds before you type the address, when you notice your hand already moving. Ask yourself one question, out loud if it helps: 'Am I checking because something specific feels wrong, or because checking is what I do now?' If it's specific — a story that changed mid-sentence — that's worth saying to them later, not to a map. If it's the reflex, close the tab. The drive time was never going to answer the real question.
TRACE · 01/04
How this script runs you
- A text mentioning traffic sends you straight to Google Maps or Waze to clock the 'real' drive time before you've asked how their day was.
- You screenshot route estimates and keep them, in case you need to compare notes against what they told you later.
- A ten-minute gap between the app's estimate and their story feels like hard evidence, even though parking, detours, and stops never show up on a map.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Trust Scanner
If the numbers don't match exactly, they lied. A drive time is treated as a fixed, provable fact — like a receipt — even though real traffic, a stop for gas, circling for parking, or a wrong turn never show up in an app's estimate. Any gap between the map's number and their number reads as deception, not as the ordinary slack of a commute nobody times to the minute.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- A map estimate isn't a lie detector. I check what I actually need to know, not what an app can't measure.
- If something feels specifically wrong, I'll ask them directly, not the traffic algorithm.
- Fourteen minutes of unaccounted time is not evidence. I close the app and notice what I'm really asking.
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
“I recalculate the drive time to prove they lied about traffic”
I say
“A map estimate isn't a lie detector. I check what I actually need to know, not what an app can't measure.”
Then I do one thing
Next time you open a map to check a drive time, first write down what specifically felt off before you opened it. If the line stays blank, that's your answer about what the checking was really for.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "I recalculate the drive time to prove they lied about traffic". 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 fourteen-minute gap between Maps and their story feel like proof?
Because the app gives you a number, and a number feels objective in a way a feeling doesn't. But drive-time estimates are averages built from typical conditions — they don't account for the specific accident, the detour, the extra minutes circling for parking, or a stop that had nothing to do with anything. A gap between an estimate and a real day is ordinary; it isn't a timestamp of guilt.
Should I keep refreshing Google Maps or Waze until the numbers finally match?
Refreshing rarely produces certainty — traffic apps update live, so the same route can show a different estimate five minutes later. Reloading until it matches your suspicion, or your hope, usually just resets the loop. If the drive time is what's actually bothering you, that's the signal worth noticing, not a number that will finally settle it.
What if I've already screenshotted several routes to compare later?
Having the screenshots doesn't obligate you to build a case from them. You can decide, separately, whether there's something specific enough to raise directly — a detail that changed, something that felt off — that isn't about minutes on a map. The screenshots answer a question about traffic patterns, not about trust.
Related old scripts
Related self-checks
Related science
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