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. Claims community consensus — Uses "we," "our," "everyone," or "Noisebridge-ers" to imply the whole community agrees
3. Self-serving — The "rule" benefits the person citing it in the current situation

The Consensus Spoof

Policy Injection borrows heavily from consensus spoofing—invoking the community as if it automatically agrees with you. Watch for language like:

• "That is our policy"
• "Noisebridge-ers do X, not Y"
• "We were told..."
• "Everyone knows..."
• "This is how we do things here"

These phrases transform a personal preference into an apparent community mandate. The speaker positions themselves as a spokesperson for collective will that was never actually established.

The Social Justice Shield

Policy Injection becomes especially difficult to challenge when wrapped in social justice framing. If questioning a fabricated rule can be characterized as sexist, racist, or otherwise discriminatory, the questioner faces social risk for simply asking "where is this written?"

Example: Someone asks for clarification about a claimed policy. The claimant responds by accusing them of "mansplaining" or suggests they're only questioning because the claimant is a woman/person of color/etc.

This creates a trap: accept the fabricated rule, or be labeled a bigot for questioning it. The social justice framing is the shield; the fabricated policy is the payload.

Note: This is distinct from actual discrimination. When someone questions a real norm and does so in a discriminatory way, calling that out is legitimate. Policy Injection occurs when the accusation is deployed to avoid providing evidence for a rule that doesn't exist.

Three Examples

Example 1: "Conflicts Must Be Public"

The claim: "Bravespace is where Noisebridge-ers work out differences, not private texts."

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 "Noisebridge-ers" framing claims community consensus that doesn't exist
• 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 preference: "I prefer to discuss things publicly so there's a record" (stated as personal preference, not community 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 "our policy" framing implies this was collectively decided—it wasn't
• 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: "We Were Told Not To"

The claim: "We were told not to communicate privately when in conflict."

The situation: Someone wants to force a dispute into public channels where they have more social support.

Why it's Policy Injection:

• No one can identify who supposedly "told" the community this
• The "we were told" framing invents a phantom authority
• The claimant benefits by controlling where the conflict happens
• When pressed for a source, the claimant attacks the questioner rather than providing one

Compare to legitimate norm: "I've seen conflicts go better when discussed openly—would you be willing to talk in the public channel?" (invites rather than mandates)

The Key Test

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
Does it invoke "we/our/everyone"?	Only if actually established	Yes, to manufacture consensus
How do they respond when questioned?	They try to explain	They attack, deflect, or claim discrimination

What Policy Injection Is NOT

• Citing unwritten norms that actually exist — Many real norms are unwritten but widely recognized and independently confirmable
• Genuine confusion — Someone who's honestly 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"
• Calling out actual discrimination — The problem isn't naming real bias; it's using accusations to avoid providing evidence

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—especially when combined with accusations of discrimination.

When someone invents a rule that benefits them, claims the community already agreed to it, and attacks anyone who asks for evidence, the community loses the ability to govern itself through actual consensus.