Governance rules must be public and predictable
Aliases: moderation policy · due process · governance transparency · consistency
What it is
Procedural transparency makes governance rules, scope, handling path, and possible consequence public and predictable to affected people. It does not expose every anti-abuse detail; it lets people understand a boundary before acting and their procedure after action.
Why it happens
Opaque governance leaves members guessing what is allowed, who decides, and how to correct. Predictability supports behavioural adjustment, evidence, and consistency oversight, reducing arbitrariness.
The second-order mechanism requires separating two kinds of transparency that most governance systems conflate, having achieved only the first: rule discoverability (can the written text be found) and application consistency (is the same rule enforced the same way across cases). The first is easy — publish a policy page and it is done. The second is much harder, because it requires enforcers to hold the same standard across thousands of individual judgment calls. What actually suppresses the sense of arbitrary power is the second kind, and most users judge a governance system's transparency not by whether they read the policy text but by whether observed outcomes match what the rule's wording led them to expect. A clearly written rule that is inconsistently applied to comparable cases still feels unpredictable to the people subject to it — a state of formal transparency with substantive opacity, which can erode trust faster than never publishing the rule at all, because it creates a gap between "should be predictable" and "isn't."
Studying it
- Paradigm: usability-test members' understanding of rules and handling paths by having them predict a specific case's outcome and comparing it to the actual result; run consistency analysis across a batch of comparable cases to check whether similar conduct receives similar handling.
- Variables: discoverability, comprehension, cross-case consistency (quantifiable as inter-rater agreement), handling time, appeal rate, and trust.
- Methodological caution: reading or agreeing to terms is not comprehension — ask people to predict a case outcome in their own words. Consistency analysis must control for differences in case severity, or divergent outcomes may reflect different facts rather than inconsistent enforcement.
Where it stops holding
Anti-gaming, privacy, and immediate safety action cannot expose all detection detail; the reason for confidentiality, public principles, and after-the-fact explanation should still exist. The value of rule discoverability itself is also situational: in a small community where members are few and already familiar with how the governing party tends to act, whether rules are written down matters less — expectations form from observing past handled cases. Once membership scales up, moderators rotate, or automation is introduced, a written rule and consistent enforcement become the primary source of expectation, and that is the setting where this pattern actually matters.
Applying it
- Explain prohibited, allowed, and grey cases with scenarios placed at the relevant action point, so discoverability lands at concrete touchpoints rather than a standalone policy page.
- Publish process, roles, timing, and appeal route, and date rule changes so application consistency can be externally checked.
- Audit written rules against actual cases on a schedule, treating a mismatch as a signal the rule itself needs revision, not merely an enforcement slip.
- Verification: sample members and cases to test correct outcome prediction and remedy discovery; separately sample comparable cases for outcome agreement rate — a persistently low rate points to an enforcement problem rather than a text problem.