QUIET
Quiet signal
“It's technically accurate, so I'm not lying” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “Technically true isn’t the same as clearly stated.”
SCRIPT CHECK · 60 SECONDS
“It's technically accurate, so I'm not lying”
See what this thought is changing.
Five quick questions show how often it appears, how believable it feels, and what it makes you avoid. You’ll get one private next step.
What this self-check measures
This is not a diagnosis and there is no pass or fail. It measures the current frequency, credibility, and behavioral cost of “It's technically accurate, so I'm not lying”, including the private rule underneath it: If the sentence can survive a literal audit, I can treat it as clean — even when it lets the most relevant fact stay hidden. The rule protects you from feeling like a liar, but it also protects the blur between accuracy and candor.
See all result bands
PRESENT
Present in the background
“It's technically accurate, so I'm not lying” wins some small decisions before you catch it. Your useful interruption is: “I can name the plain fact without polishing away the edge.”
ACTIVE
Active pattern
“It's technically accurate, so I'm not lying” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: Open a note and rewrite one recent work sentence in two columns: “technically accurate” and “plainly stated.” Keep both versions private and circle the detail that changes the reader’s understanding most.
DOMINANT
Getting the final word
Right now, “It's technically accurate, so I'm not lying” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: Open a note and rewrite one recent work sentence in two columns: “technically accurate” and “plainly stated.” Keep both versions private and circle the detail that changes the reader’s understanding most.