Participation Integrity and Anti-Brigading: Development Notes
Status: Development Notes: Intentionally Deferred Version: 0.2
Summary: A reserved governance and operations layer for resisting astroturfing, brigading, duplication, harassment, lobbying pressure, and review-capacity exhaustion.
Document status. This is an intentionally deferred development document. It identifies a methodology UXR expects to need, preserves useful design notes, and defines the questions that future work must answer. It does not yet establish an adopted scoring system, threshold, formula, or operating procedure.
Why this remains open. Premature precision can create false authority and lock UXR into assumptions that have not survived evidence, domain comparison, affected-person review, adversarial testing, or operational experience. UXR will not define this layer further merely to make the documentation look complete.
How this document should be reviewed. Reviewers are invited to identify missing considerations, risks, dependencies, examples, and candidate approaches. The absence of a final mechanism is intentional. A proposal should not be treated as adopted until UXR has published the evidence, tests, and reasoning supporting it.
Existing constitutional boundary. UXR already requires public contribution to be evaluated for substance rather than volume, sponsorship, institutional power, or organized pressure. Participation may inform UXR but may not redefine it around corporate or institutional agency.
Purpose. Future participation systems must remain open to criticism and lived experience while resisting attempts to manufacture consensus, exhaust reviewers, intimidate contributors, conceal sponsorship, or overwhelm evidence-based decision-making.
Threats identified so far. Collected concerns include coordinated brigading, astroturfing, duplicate submissions, automated submissions, paid influence campaigns, lobbying disguised as public feedback, harassment, retaliatory reporting, strategic ambiguity, evidence laundering, identity fabrication, and deliberate exhaustion of limited review capacity.
Priority adversarial tests. Early pilots should specifically test AI-generated mass astroturfing, coordinated queue flooding, repeated paraphrases of one source, synthetic identity networks, and campaigns designed to consume reviewer attention rather than contribute new evidence. Testing should also measure whether defenses incorrectly suppress legitimate collective reporting.
Candidate safeguards. Possible tools include behavioral rate controls, anomaly detection across submission patterns, substance-based clustering, duplicate detection, source and sponsorship disclosure, queue separation, representative sampling, provenance checks, conflict-of-interest rules, transparent moderation, escalation for coordinated manipulation, human review, and appeal. Clustering should organize materially similar evidence, not erase minority accounts or treat shared wording as automatic proof of coordination. These remain candidates, not adopted procedures.
Anti-abuse cannot become exclusion. Safeguards must not privilege professional writing, institutional credentials, conventional evidence access, technical fluency, English proficiency, wealth, public identity, or the ability to survive a burdensome verification process. A system that prevents manipulation by excluding the people most affected would violate UXR's purpose.
Anonymous and protected participation. Some contributors require anonymity or intermediary representation because disclosure could cause retaliation, job loss, deportation risk, medical consequences, family harm, or physical danger. Future integrity systems must evaluate contribution quality without treating public identity as a universal prerequisite.
Substance is not consensus. A large campaign may raise a legitimate issue, and an isolated contributor may identify a serious defect. UXR must examine evidence and reasoning rather than automatically rewarding either popularity or rarity.
Dependencies before adoption. UXR needs real participation volume, threat modeling, privacy design, moderation pilots, appeals design, accessibility testing, and evidence about how proposed controls affect legitimate contributors before adopting a fixed system.
Question for Review
Which participation threats and safeguards should UXR test without turning anti-abuse controls into new barriers to legitimate participation?
Explore the UXR Framework
- UXR: Founding Declaration
- What UXR Means by Human Agency
- The Universal Scope of UXR
- Friction, Pain, Harm, and Invisible Taxes
- UXR Independence and the One-Way Authority Rule
- How UXR Creates Accountability
- Severity, Urgency, and Recoverability: Development Notes
- Evidence Validation and Confidence: Development Notes
- Participation Integrity and Anti-Brigading: Development Notes
- UXR Intake and Evidence Collection: Working Concepts
- Contributor Continuity, Resolution Knowledge, and Reform Recognition
- UXR: Current Project Status
- Contributing to UXR