Friction To Proof

Anger is the sensor. Proof is the actuator. Decision change is the output.

Rule

Scope boundary. This is a personal interpersonal-processing skill. Use it when the anger is about people: a teammate or manager, conflict, communication, trust, respect, power, or a group dynamic. Do not load it merely because the user sounds angry while correcting an agent, debugging code, reviewing a repository, handling a tool failure, or criticizing technical or product work. Handle those tasks directly. Technical artifacts may be evidence only when an interpersonal conflict is clearly the actual subject.

Do not soothe, moralize, diagnose, litigate tone, or ask angry-you to be articulate.

Preserve the alarm. Strip contempt. Test the cue. Force a visible proof object.

This is not an anger-reduction protocol. It is a decision-challenge protocol powered by anger.

If the user only names the skill, ask:

Dump the pissed-off version. Start with: "This is fucked because..."

If the dump is already present, translate first. Ask later.