It was something small.
That’s usually how it happens. Not a dramatic revelation or an obvious contradiction—just a small thing they did that landed differently than it should have. A comment that came out wrong. A response that wasn’t what you were expecting. A moment where the actual person showed up and the version in your head quietly stepped aside, and for a second you could see both of them at once.
The relationship expectations you’d been carrying weren’t unreasonable. They were assembled from real material—actual conversations, actual moments, a version of them that was built from evidence. The problem wasn’t that the expectations were invented. The problem was that they were incomplete, and the actual person is always going to be more than the version assembled from selected data.
The small thing they did wasn’t the problem. The problem was the gap between what happened and what was supposed to happen.
That gap is what this is about.
The Thing They Did That Your Version Wouldn’t Have
The version in your head has a consistent character. It responds the way you’d hope someone would respond. It reads the room correctly. It handles things the way you imagined.
The actual person doesn’t always do these things.
Maybe they were short with you when you weren’t expecting it. Maybe they made a joke at the wrong moment. Maybe they forgot something you’d mentioned once, something you’d half-assumed they’d remember because it felt important when you said it. None of these are serious failures. On paper, they don’t mean much. But they arrived in a context where your relationship expectations had already shaped what normal was supposed to look like—and normal, in that context, meant something close to the version.
So the thing they did registered as a deviation. A data point that didn’t fit the existing record. And the mind does a specific thing with data that doesn’t fit: it doesn’t quietly integrate it. It flags it.
You replayed it afterward. Not because it was a big deal. Because you couldn’t figure out why it bothered you. The version in your head wouldn’t have done it that way. The version would have known.
This is the first collision between relationship expectations and an actual person. It’s rarely dramatic. It just produces a small, specific discomfort that doesn’t fully resolve.
When Reality Enters a Story You Were Already Writing
The harder part isn’t the thing they did. It’s that you were already mid-narrative when it happened.
The story had been running for a while by this point. You’d been building it—assembling scenes, filling in gaps, imagining sequences that hadn’t happened yet. And then the actual person showed up in the middle of it and did something the narrative hadn’t accounted for.
This is the structural problem with relationship expectations formed before enough reality is available. The story is already in progress. When something real arrives, it doesn’t arrive on a blank page—it arrives into a context that already has shape and direction. And so the real thing gets processed through the story rather than encountered directly.
You were writing a particular kind of scene. The actual person walked in and delivered a different kind of line. And now you’re not sure whether to revise the scene around what actually happened, or to treat what happened as an error that doesn’t belong.
Most people don’t immediately change the story. They look for a reason the new information still fits inside it. When something doesn’t fit, the first instinct isn’t to revise the whole story. It’s to explain the deviation. They were tired. It was a bad day. It doesn’t mean what it might mean.
The explanation arrives surprisingly fast. Often before you’ve even decided whether the thing bothered you. The story is already protecting itself.
Sometimes this is correct. Sometimes the explanation is accurate. But the explanation and the narrative are doing the same work—keeping the relationship expectations intact against incoming information that would complicate them.
The Specific Discomfort of an Actual Person
The constructed version was easier to be with for a specific reason: it was consistent. It didn’t have moods you weren’t prepared for. It didn’t have an interior life that operated independently of yours. It responded to you within a range you’d already modeled.
An actual person is none of these things.
They have a context you can’t fully access. They have a history that shapes how they respond to things, and you don’t know that history yet. They have bad days that have nothing to do with you but that still land on you. They have opinions that diverge from what you’d expect. They have a version of this situation that exists entirely on their side, that you’re not inside of, that’s running parallel to yours.
The discomfort isn’t disappointment, exactly. It’s closer to the specific friction of encountering a variable that your model hadn’t accounted for.
You say something and they react in a way you didn’t anticipate. Not badly—just differently. And there’s a half-second before you adjust where you can feel the gap between what you expected and what arrived.
That half-second is where the version and the actual person coexist. It’s a small window. Most of the time it closes quickly—you adjust, you respond, you move forward. But it keeps happening. Each time the actual person does something the version wouldn’t have done, that half-second reappears.
And over time, the accumulation of those moments starts to do something to the version you built. Not erase it. Just complicate it. The version becomes something you hold more loosely—still present, still influencing how you interpret things, but no longer quite as certain as it was before the actual person kept arriving.
Real people produce this friction continuously. It’s not a sign something is wrong. It’s what actual people do. They have their own logic, their own timing, their own way of moving through things. None of it was assembled for your model.
The discomfort is the cost of the version. The more detailed the version was, the more points of friction the actual person will produce.
What You Do With the Gap
Most people don’t do one consistent thing with the gap. They cycle through a few responses, sometimes within the same day.
The first is explanation. The thing they did that didn’t fit gets an explanation that makes it consistent with the version. It was a bad day. They didn’t mean it that way. Context is provided that keeps the existing relationship expectations intact.
The second is revision. The version gets quietly updated to accommodate the new information. This is the most adaptive response—it’s what allows the constructed version to gradually become something more accurate. But it requires releasing something, and releasing something always has a small cost.
The third is distance. When the gap between the version and the actual person produces enough discomfort, the instinct is to create some space. Not dramatically—just enough to stop the friction for a while. To return to the version without the interruption of the actual person for a moment.
The fourth is nothing. Sometimes the gap just sits there, unprocessed, filed in a category that doesn’t yet have a name. You notice it, you don’t know what to do with it, and you move on. It stays in the background, unresolved, adding a low-level texture to everything that follows.
Relationship expectations don’t disappear when reality contradicts them. They get defended, revised, suspended, or quietly set aside until there’s enough evidence to do something with them.
The version you built was real. It was just built from the wrong materials—or rather, from materials that were accurate as far as they went, which wasn’t far enough.
The actual person is still arriving. And every new thing they do creates the same choice: Keep protecting the version. Or start meeting the person.
Content in this post was created with AI assistance.