You've reread it enough times that the words are starting to look fake. Maybe it was three letters. Maybe it was one of those replies that's technically polite but lands like a door closing. Your brain has already drafted four endings to the relationship, and the message is still twelve characters long.
Here's what nobody tells you about decoding texts: the text is rarely the problem. The ambiguity is. Texting strips out tone, facial expression, body language, and timing, the channels humans actually use to read each other. What's left is a few words on glass, and the part of your brain built to scan the people you depend on for danger fills in the missing data with worst-case scenarios.
The size of that gap has been measured. In a series of experiments on tone in written messages, senders predicted their sarcasm or seriousness would land correctly 78 percent of the time. Actual accuracy was 56 percent, barely better than a coin flip. The readers, meanwhile, were about 90 percent confident in their interpretations either way. Hold that trio of numbers, because it describes your thread exactly: he thinks his text was clear, it probably wasn't, and the certainty you feel about what it meant is the least reliable part of the whole exchange.
That's not a character flaw. It's an attachment alarm working on terrible data. The same system that once watched faces around a fire for signs of rejection is now reading "okay" with a period at the end.
The fix isn't to feel less. The fix is to separate what was sent from what your body decided it meant. This guide gives you the framework first, then delivers on the number in the title: 20 specific phrases, what each usually means, what it means from different senders, what you're most likely to over-read it as, and what to send back.
