What we publish

Conflict Protocol includes copy-ready scripts, situation guides, text-message replies, workplace email/Slack language, pressure-pattern explainers, response techniques, practice prompts, and simulator examples.

Every piece should answer one practical question:

What can I say here that keeps me clear?

How we write scripts

A good script is short, sayable, and hard to pull apart.

It does not try to prove the speaker is a good person. It does not over-explain. It does not diagnose the other person. It does not invite a debate about every reason.

Good Conflict Protocol lines usually do one of five things:

  1. buy time
  2. hold a limit
  3. name the issue
  4. move work pressure into priority/tradeoff
  5. stop a loop

Weak:

I'm sorry, I really wish I could, but I already had plans and I hope you understand.

Stronger:

I can't take that on tonight. What should move if this is now the priority?

The stronger line is not colder. It is cleaner.

How we write situation pages

Situation pages start from recognizable moments.

Not abstract "communication challenges." Real moments:

  • your boss sends a Friday evening "quick favor"
  • a parent says "after everything I've done for you"
  • someone says "that never happened"
  • a friend says you are replacing them
  • a coworker presents your work as theirs

A strong situation page should include: say this first, how it sounds in context, if they push back, wrong vs better, text-message version when relevant, escalation dialogue when useful, related patterns and techniques, and a practice link where useful.

The goal is not to give one magic sentence. The goal is to help the reader recognize the pressure and keep their answer clean when the pressure changes.

How we write pattern pages

Pattern pages explain what to notice.

They should not turn every difficult person into a diagnosis. A pattern is a move in a conversation, not a clinical label for a person.

For example, gaslighting is not every disagreement about memory. In Conflict Protocol, we treat it as a pressure pattern when denial, certainty, or revision is used to make you abandon your account of what happened.

How we write technique pages

Technique pages explain what to do.

A technique is useful only if someone can use it when stressed.

  • Broken Record: repeat the answer without adding new reasons.
  • No JADE: do not justify, argue, defend, or explain after the answer is already clear.
  • Boundary: name what you will or will not do.
  • Tactic Naming: calmly name the move without turning the label into a fight.

Techniques are not personality tests. They are tools.

What we avoid

We avoid diagnosing people, telling readers to confront unsafe people, "just communicate better" advice, fake-neutral language that blames the reader for the pressure, long scripts no one would say, therapy-blog mush, corporate conflict-resolution filler, generic AI text that could fit any page, and fear-based conversion tactics.

We also avoid pretending a script can solve every situation.

Sometimes the right move is not a better sentence. Sometimes it is documentation, support, distance, HR, legal advice, or safety planning.

Safety discipline

Scripts are for ordinary pressure and difficult conversations.

If a reader is afraid of the person, being monitored, threatened, physically unsafe, financially trapped, or punished for setting limits, the priority is safety and outside support - not saying the perfect line.

We keep safety notes short because panic does not help. But we include them because the distinction matters.

Updates

We revise pages when we find duplicated template language, scripts that are too long, advice that is too generic, missing safety context, broken internal links, better examples, or product changes in the simulator.

We would rather publish fewer strong pages than many thin ones.