Why Do I Resist Things I Actually Want? The Command Flinch

He asked you to do the exact thing you were already planning to do. Word for word, almost. And something in you locked up anyway, dug in, found a reason to stall, not because the thing itself was wrong but because the second it left his mouth as an instruction, it stopped feeling like something you were choosing.

You are not being difficult. I want to tell you what that actually is.

What Is the Command Flinch?

Demand avoidance is a documented pattern, most studied in autistic people, where expectations and requests trigger a threat response independent of whether the person wants the outcome. The nervous system is not reacting to the content of the ask. It is reacting to the shape of it: an external demand, arriving from outside your own choosing, and something in you treats that shape as danger before you have even processed what was asked.

Inside a D/s dynamic this is not a footnote. It is a direct collision with the structure of the thing itself, because the entire premise runs on him giving instructions. I call the specific flashpoint the command flinch: the resistance that fires the instant a wanted thing crosses from your own intention into his spoken command, even though nothing about what you actually want has changed in the slightest.

Why It Happens

Here is what I think is happening underneath it. For a demand-avoidant nervous system, autonomy is not a preference. It is closer to a survival requirement, wired in deep enough that losing the sense of choosing, even over something you already wanted, reads as a real threat. The alarm does not check content. It checks structure: did this arrive as my own move, or as someone else’s order.

This runs alongside the transition wall, a cousin mechanism rather than the same one: there the block is switching states, here the block is being told to switch at all. Both are the nervous system refusing to be moved by outside force, even toward somewhere it already wanted to go. It is also worth reading next to the held face: masking is the cost of performing what is expected of you, the command flinch is what happens the instant that expectation is spoken out loud instead of quietly absorbed.

What It Looks Like in a Dynamic

You already know if this is you. Read these slowly.

He tells you to go take your bath, the exact bath you were about to draw yourself, and you suddenly find six reasons it can wait. You want to kneel and he asks you to kneel and your knees lock instead of bend, for one full second, before you catch yourself. From the outside this reads as brattiness, or defiance, or a woman testing him. It is neither. It is a nervous system that needed the choosing to stay visibly yours, even inside obedience, and did not get it in time.

What To Do About It

You do not fix this by forcing compliance through the flinch, and you do not fix it by explaining yourself into exhaustion every time it happens.

1. Name it plainly, outside the moment. “I want the things you ask for, and I still might flinch at how they arrive.” That sentence removes the guesswork before it costs either of you anything.
2. Ask for language that frames instructions as an offer he already trusts you to take, rather than a command with no air in it.
3. Notice the difference between flinching and refusing. One is nervous system, the other is an actual no, and conflating them will cost you both clarity.
4. Give the flinch a few seconds before either of you reacts to it. Most of the time it passes the instant the choosing feels like yours again.

The want was never the problem. It survived the whole time, underground, waiting for the choosing to feel like it belonged to you again. Build the dynamic to leave it there, and obedience stops fighting itself.

This is exactly the wiring The Neurodivergent’s Guide to Submission maps out, because a dynamic built only for a nervous system that takes instructions easily will keep mistaking your wiring for resistance instead of reading it correctly.