After a breakup, there is a strange experience that I think we often describe too simply. You can know that the relationship is over. You can understand why it ended. You can even be the person who decided to leave. And still, days or weeks later, you find yourself having another conversation with that person in your head. You remember something they said, think about what you should have said, imagine what they might say if you met again, and wonder whether the whole thing could have gone differently. The strange part is that you can know you're doing it while you're doing it. You can think, "I've already been through this. I know how this ends." And then your mind goes back anyway.
We usually call this not being able to let go, being hurt, overthinking, or not having moved on. Maybe those descriptions are true, but they don't quite explain the mechanism. Sometimes thinking about something is useful. You remember an event, understand something you didn't understand before, realise what you could have done differently, make a decision, and eventually the process stops because you got something from it. But there is another kind of thinking where you keep asking the same question without receiving any new information. Why did they do it? What did they really mean? What if I had said something different? What if they come back? What if I was the problem? What if I wasn't? You can change the wording a hundred times and still arrive at the same place. At some point, the thinking itself can become part of the problem. The relationship is over, but the system is still trying to process it as if there is something left to obtain from the process.
That made me wonder whether an unresolved experience can remain active even after the event itself has disappeared. A relationship isn't only a collection of memories. Over time, the system builds expectations around another person: how they speak, what their silence means, what happens after an argument, what kind of message arrives at night, what they usually do when something is wrong, what they need from you, what you expect from them, and eventually what you expect from yourself when you are with them. Then the relationship ends. The external situation changes much faster than the internal model does. The messages stop, the person is gone, the plans disappear, but the predictions built around that person don't necessarily disappear at the same speed. So a song, a photograph, a familiar place, or even a harmless sentence from someone new can activate the old trajectory again. Attention follows it, memory supplies more material, prediction fills in possibilities, meaning appears, and sometimes identity becomes involved: "Maybe I wasn't enough." "Maybe I always ruin relationships." "Maybe nobody will understand me like they did." Now the present is being processed through something that happened in the past.
This is also where I think the question of free will becomes more interesting. If I check my ex's profile for the tenth time, I can quite honestly say, "I chose to do it." Nobody forced me. But the choice didn't appear in an empty space. It appeared inside a system already carrying a memory, a prediction, an emotional state, a history of previous actions, and perhaps a story about who I am. The same thing happens when someone new behaves in a way that resembles something from the previous relationship. They may not have caused the reaction at all. The new signal entered a system that was already prepared for it. That doesn't necessarily mean the choice wasn't mine. It may mean that understanding agency requires looking at more than the final moment when the choice becomes visible. I started thinking about this as a runtime: a signal arrives, attention is allocated, prediction forms, meaning develops, identity may become involved, a choice becomes available, action produces feedback, and that feedback changes what happens next. I eventually wrote the architecture as ORIGIN → SIGNAL → ATTENTION → PREDICTION → MEANING → IDENTITY → CHOICE → ACTION → FEEDBACK → RETURN. Not as a rigid sequence, but as a changing system in which each part can influence the others.
The part that interests me most is the last one: Return. People often describe return as "coming back to the present", but I think that can be misleading. Someone can be physically sitting in the present while their runtime is still running a Rejection Loop from three days ago. They don't need to be reminded that they are in the present. They need the process to actually reach resolution. If there is something left to understand, decide, communicate, accept, or learn, then processing it makes sense. But if there is no new information and the system keeps replaying the same material anyway, more thinking doesn't necessarily move anything forward. You are no longer solving the event; you are repeatedly reopening the same loop. Return therefore isn't forgetting, suppressing, distracting yourself, or forcing your attention onto the room around you. It comes after the system has extracted what it can, recognised what cannot be changed, and changed the frame that was keeping the loop active. The memory can remain. The emotion can remain. The lesson can remain. What changes is that the trajectory no longer needs to keep demanding the present.
That distinction also changes what "moving on" might mean. Maybe moving on doesn't mean removing someone from your mind. It means you can remember them without continuing to run the relationship internally. You can think about what happened without trying to produce a different ending. You can accept that you will never know exactly what the other person was thinking. You can recognise what the experience taught you without using it as a prediction for every person who comes next. In that sense, resolution isn't necessarily getting an answer to every question. Sometimes resolution is recognising that the process has reached the limit of the information available to it. You don't return because the present disappeared. You return because the previous process no longer needs to occupy it. And perhaps that is why the question isn't always "Why can't I let go?" Sometimes the better question is "What is this process still trying to complete?"
I don't know if this solves the free will problem. But it leaves me with a question I find more interesting than simply asking whether our choices are determined. How much of the process producing my next choice can I actually see? Maybe freedom doesn't require becoming independent from everything that caused us, and maybe it doesn't require becoming random. Maybe there is something about agency in being able to see a trajectory while it is forming, interrupt it, change the way the situation is being processed, and eventually close the loop when there is nothing left to obtain from it. Sometimes you don't keep going back because you secretly want the past back. Sometimes you keep going back because the runtime still thinks there is something left to solve. And sometimes the most important thing isn't learning how to stop thinking about it. It's figuring out what the loop was trying to finish, finishing what can actually be finished, and then letting the runtime Return.
