There is a third category of sabotage that is neither the firmware misfiring on its own nor an institution extracting from you at scale. It is what happens between people, in the ordinary relationships of daily life, when one person's adaptive programming runs against another person's interests — not because either person intends harm, but because the programming is doing what it was installed to do.
The parent who shames a child for crying is not, in most cases, being cruel. They are running a program installed during their own developmental window, in which crying was met with shame, and the adaptive mind recorded: crying is dangerous, stop it. When their child cries, the parent's firmware activates the same threat response, and the adaptive mind's installed program executes: make the crying stop. The mechanism is not malice. It is transmission. The parent is doing to the child what was done to them, using the same machinery, with the same urgency, and in most cases with no awareness that a program is running at all.
This is mutual sabotage. It is the adaptive mind's programming, installed in one person during their developmental window, running against another person's interests in the ordinary course of relationship. It operates in families, in friendships, in workplaces, and with particular intensity in intimate relationships, which is why the next chapter takes up that case separately.
The pattern is consistent. Person A carries an adaptive installation — a program written during their developmental window that says, for example, that conflict is dangerous and must be avoided at all costs. Person B carries a different installation — perhaps that their needs will not be met unless they escalate. When A and B interact, A's avoidance program and B's escalation program lock into a cycle that neither person chose, neither person wants, and neither person can see clearly from inside, because each person's rider is telling a story about the other person's behavior rather than about their own programming. A says B is too demanding. B says A is emotionally unavailable. Both are describing the other person's adaptive program while being unable to see their own.
The reason this category matters is that it is the one most people encounter every day, and it is the one the culture has the least useful language for. The culture offers two frames: either the other person is the problem (they are toxic, narcissistic, impossible), or you are the problem (you are too sensitive, too needy, not enough). The framework offers a third: both of you are running programs installed during developmental windows neither of you chose, and the programs are interacting in ways that produce suffering for both of you, and neither of you is the villain, and the suffering is still real, and the work is still yours to do.
This is not a frame that eliminates accountability. It is a frame that locates it more accurately. You are not responsible for the program that was installed in you. You are responsible for what you do once you can see it running. The rider's job is not to eliminate the programming. It is to build the gap — the space between the program activating and the behavior executing — and within that gap, to choose differently. This is difficult. It is the actual work. And it begins with seeing the program rather than seeing the other person as the problem.