Policy Injection

Policy Injection is a social manipulation pattern where someone states a fabricated rule as if it were established community policy, typically to gain advantage in a dispute.

The term draws from computer security: just as SQL injection exploits trust in user input to insert malicious code, Policy Injection exploits trust in member assertions to insert fabricated rules.

How to Recognize It

Policy Injection has three key features:

1. Stated as fact, not preference — "That's our policy" rather than "I think we should..."
2. Self-serving — The "rule" benefits the person citing it in the current situation
3. Not actually a rule — It's not documented, and others can't corroborate it

Three Examples

Example 1: "Conflicts Must Be Public"

The claim: "We work out differences in public channels, not private messages. That is our policy."

The situation: Someone sends a private message attempting reconciliation. The recipient ignores it and posts a public callout instead, citing the above "rule."

Why it's Policy Injection:

• No such rule exists in any documentation
• The claimant benefits by denying their counterpart a private off-ramp
• The claimant doesn't follow it themselves—they have allies send private messages on their behalf

Compare to legitimate norm: "I prefer to discuss things publicly so there's a record" (stated as preference, not policy)

---

Example 2: "One Member Can Veto"

The claim: "Any single member can veto donations. That's our policy."

The situation: Someone wants to block a donation they personally oppose.

Why it's Policy Injection:

• The community uses consensus, but no "single-member veto on donations" rule exists
• The claimant benefits by gaining unilateral blocking power
• The claimant would not accept being blocked by this same "rule"

Compare to legitimate concern: "I have concerns about this donation and want to discuss it at the meeting" (uses actual process)

---

Example 3: "I Define What's Unsafe"

The claim: "If I say something is unsafe, then it's unsafe."

The situation: A disagreement about whether a proposed modification to the space is safe.

Why it's Policy Injection:

• Safety decisions are made collectively, not unilaterally
• The claimant benefits by gaining authority over the decision
• The claimant dismisses others' safety concerns in other contexts

Compare to legitimate advocacy: "I have safety concerns about this and think we should discuss it" (raises concern without claiming authority)

The Key Test

Ask yourself:

Question	Legitimate Norm	Policy Injection
Who benefits?	The community	The claimant
Do they follow it themselves?	Yes	No
Can others confirm this rule exists?	Yes	No
How do they respond when asked "where is this written?"	They try to explain	They attack or deflect

What Policy Injection Is NOT

• Citing unwritten norms that actually exist — Many real norms are unwritten but widely recognized
• Genuine confusion — Someone who's wrong about a rule will be relieved to be corrected, not defensive
• Stating preferences — "I prefer X" is not the same as "X is our policy"

Why It Matters

Policy Injection undermines consensus governance by letting individuals bypass collective decision-making. It shifts the burden of proof onto others to disprove a fabricated rule, and it makes questioning assertions socially risky.

When someone invents a rule that benefits them and attacks anyone who questions it, the community loses the ability to govern itself through actual consensus.