Ovinomancer
No flips for you!
I think "decision process" is not accurate. Mechanics are conflict resolution tools, not decision tools. I think that, for many, the term "associated" means that the conflict resolution mechanic is used after the conflict is fully established in the fiction and needs to be resolve. The term "dissociative" is when the conflict is not yet fully established in the fiction, and the resolution process establishes some part of the fictional conflict, not just it's resolution. So, rolling to hit after establishing the my character is attacking an orc in the fiction is "associated" because the attack is already established in the fiction so the mechanic is just resolving it. while using a power to that cause an opponent to approach and be attacked strongly is "dissociated" because the opponent's action (to approach) is not established prior to the use of the mechanic.This pretty much captures my thoughts verbatim. As I've noted previously, the term itself ("associated mechanics") makes sense --- a mechanic is "associated" if the decision process of the player maps to a decision process of the character.
But as @Fenris-77 says in the bolded part, the blunt instrument use of the term as a catch-all for why a game mechanic fails some arbitrary test for helping maintain "immersion" is misguided at best.
I don't find this to be a particularly useful distinction, though, as all things are authored in the fiction and the fight here is really about if the GM narrates the conflict entirely unilaterally or if the player has some input into the conflict as well (and not really associated/dissociated), but this is what I understand the core issue to be.