Policy Injection: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
Revised: Added consensus spoofing section, social justice shield dynamic, replaced safety example
Revised: Reframed around avoiding human engagement; replaced procedural "legitimate" examples with genuine engagement alternatives
Line 2: Line 2:


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.
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.
== The Core Dynamic ==
At its heart, Policy Injection is about '''avoiding genuine human engagement'''. By invoking a fabricated rule, the claimant creates a procedural barrier that blocks actual conversation:
* Instead of explaining their real concerns, they cite "policy"
* Instead of listening to counterarguments, they point to "how we do things"
* Instead of negotiating, they enforce a rule that doesn't exist
* Instead of connecting as humans, they interact only through procedure
The fabricated rule becomes a wall. You can't negotiate with a wall.


== How to Recognize It ==
== How to Recognize It ==
Line 46: Line 57:
* The claimant benefits by denying their counterpart a private off-ramp
* 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
* The claimant doesn't follow it themselves—they have allies send private messages on their behalf
* '''Most importantly:''' It blocks the human connection the other person was offering


'''Compare to legitimate preference:''' "I prefer to discuss things publicly so there's a record" (stated as personal preference, not community policy)
'''What genuine engagement looks like:''' Actually reading the reconciliation message and responding to it—even if the response is "I'm not ready to talk yet, give me a few days."


----
----
Line 61: Line 73:
* The "our policy" framing implies this was collectively decided—it wasn't
* The "our policy" framing implies this was collectively decided—it wasn't
* The claimant benefits by gaining unilateral blocking power
* The claimant benefits by gaining unilateral blocking power
* The claimant would not accept being blocked by this same "rule"
* '''Most importantly:''' It avoids having to explain their actual concern or hear anyone else's perspective


'''Compare to legitimate concern:''' "I have concerns about this donation and want to discuss it at the meeting" (uses actual process)
'''What genuine engagement looks like:''' "I'm worried we don't have space for this—where would it go? Can we talk through whether this actually fits our needs?" This opens a conversation instead of shutting one down.


----
----
Line 77: Line 89:
* The "we were told" framing invents a phantom authority
* The "we were told" framing invents a phantom authority
* The claimant benefits by controlling where the conflict happens
* The claimant benefits by controlling where the conflict happens
* When pressed for a source, the claimant attacks the questioner rather than providing one
* '''Most importantly:''' It transforms "I don't want to talk to you privately" into an institutional mandate, avoiding the vulnerability of stating a personal boundary


'''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)
'''What genuine engagement looks like:''' "I'd feel more comfortable discussing this where others can see the conversation—would you be open to that?" This is honest about preferences without fabricating rules.


== The Key Test ==
== The Key Test ==
Line 94: Line 106:
|-
|-
| Does it invoke "we/our/everyone"? || Only if actually established || Yes, to manufacture consensus
| Does it invoke "we/our/everyone"? || Only if actually established || Yes, to manufacture consensus
|-
| Does it open or close conversation? || Opens dialogue || Shuts it down
|-
|-
| How do they respond when questioned? || They try to explain || They attack, deflect, or claim discrimination
| How do they respond when questioned? || They try to explain || They attack, deflect, or claim discrimination
Line 104: Line 118:
* '''Stating preferences''' — "I prefer X" is not the same as "X is our policy"
* '''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
* '''Calling out actual discrimination''' — The problem isn't naming real bias; it's using accusations to avoid providing evidence
* '''Setting personal boundaries''' — "I need space right now" is honest; "We have a policy of disengagement" is fabrication


== Why It Matters ==
== 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.
Policy Injection undermines consensus governance by letting individuals bypass collective decision-making. But more fundamentally, it '''replaces human connection with procedural walls'''.
 
A community can't function when members use fabricated rules to avoid talking to each other. Consensus requires actual engagement—listening, explaining, negotiating, sometimes disagreeing. Policy Injection short-circuits all of that by invoking authority that doesn't exist.


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.
When someone invents a rule that benefits them, claims the community already agreed to it, and attacks anyone who asks for evidence, they're not just manipulating governance. They're refusing to be in community with the people around them.


[[Category:Community]]
[[Category:Community]]
[[Category:Conflict Resolution]]
[[Category:Conflict Resolution]]

Revision as of 04:47, 30 December 2025

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.

The Core Dynamic

At its heart, Policy Injection is about avoiding genuine human engagement. By invoking a fabricated rule, the claimant creates a procedural barrier that blocks actual conversation:

  • Instead of explaining their real concerns, they cite "policy"
  • Instead of listening to counterarguments, they point to "how we do things"
  • Instead of negotiating, they enforce a rule that doesn't exist
  • Instead of connecting as humans, they interact only through procedure

The fabricated rule becomes a wall. You can't negotiate with a wall.

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
  • Most importantly: It blocks the human connection the other person was offering

What genuine engagement looks like: Actually reading the reconciliation message and responding to it—even if the response is "I'm not ready to talk yet, give me a few days."


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
  • Most importantly: It avoids having to explain their actual concern or hear anyone else's perspective

What genuine engagement looks like: "I'm worried we don't have space for this—where would it go? Can we talk through whether this actually fits our needs?" This opens a conversation instead of shutting one down.


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
  • Most importantly: It transforms "I don't want to talk to you privately" into an institutional mandate, avoiding the vulnerability of stating a personal boundary

What genuine engagement looks like: "I'd feel more comfortable discussing this where others can see the conversation—would you be open to that?" This is honest about preferences without fabricating rules.

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
Does it open or close conversation? Opens dialogue Shuts it down
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
  • Setting personal boundaries — "I need space right now" is honest; "We have a policy of disengagement" is fabrication

Why It Matters

Policy Injection undermines consensus governance by letting individuals bypass collective decision-making. But more fundamentally, it replaces human connection with procedural walls.

A community can't function when members use fabricated rules to avoid talking to each other. Consensus requires actual engagement—listening, explaining, negotiating, sometimes disagreeing. Policy Injection short-circuits all of that by invoking authority that doesn't exist.

When someone invents a rule that benefits them, claims the community already agreed to it, and attacks anyone who asks for evidence, they're not just manipulating governance. They're refusing to be in community with the people around them.