Community Norm¶
Protocol — instantiates Local Rule Design
Implements local rule design socially by creating locally recognized expectations for contribution, moderation, reciprocity, repair, or boundary enforcement.
A community norm coordinates the conduct of many loosely-tied members not by price and not by delegated authority but by shared, locally-recognized expectations whose entire force comes from legitimacy and peer response — approval, reputation, gentle correction, and repair after a breach. Nobody is assigned to enforce it; the signal is the reaction of peers, and the rule survives because respected members model it and newcomers absorb it. What makes it this mechanism is that its power is organic and reputational, and it drifts — norms are continually renegotiated as membership and context change. It confers no formal decision rights and gates nothing; it shapes how people behave by shaping what the group visibly expects.
Example¶
A photography-critique forum wants feedback that is useful and kind rather than drive-by dunking, but no moderator can read every thread. Over time a norm settles in: a critique leads with what works, then offers one concrete improvement, on the assumption that the poster wants to grow. Reputation — upvotes, "helpful" badges, the respect of being quoted — accrues to critics who follow it. When someone posts a harsh takedown, the regulars don't reach for a report button; they model a repair, reframing the harsh note into a constructive one and letting the newcomer see the difference. New arrivals learn the norm just by reading. Then a large influx of newcomers arrives after the forum is featured somewhere, quality dips, and the regulars re-articulate the norm in a fresh pinned post — the norm bending to absorb the change rather than snapping.
How it works¶
- Make the expectation legible. Examples, pinned explanations, and visible good behavior teach the rule without codifying it into law.
- Peer response is the enforcement signal. Approval, reputation, and quiet correction reward and punish — no official is needed.
- Repair over punishment. The standard reaction to a breach is to model the better behavior, keeping the violator inside the community.
- Legitimacy from modeling. Norms hold because respected members visibly live them, not because anyone decreed them.
- Renegotiated as the group changes. Membership shifts and context drift force the norm to be re-articulated over time.[n1]
Tuning parameters¶
- Explicitness — tacit understanding versus a written code of conduct. Codifying aids newcomers and consistency but can ossify and invite rules-lawyering.
- Enforcement intensity — gentle correction versus visible sanction. Gentle preserves belonging but tolerates repeat offenders; sanction deters but can feel punitive.
- Reputation visibility — how prominent status signals are. Visible reputation motivates but can breed status-seeking over substance.
- Who models the norm — any member versus recognized elders. Broad ownership scales; narrow ownership keeps it coherent but fragile.
- Renegotiation openness — how readily the norm is re-opened when challenged, trading stability against adaptability.
When it helps, and when it misleads¶
Its strength is scaling conduct without policing: it produces cooperative order across far more interactions than any moderator could touch, adapts as the group learns, and feels legitimate precisely because it is peer-held rather than imposed.
Its failure mode is drift and erosion — under a growth spurt or a newcomer influx the shared understanding thins faster than it can be transmitted, the classic "Eternal September" in which each wave of arrivals never fully absorbs the norm.[n1] Enforcement can also go uneven (leniency for in-group friends) or harden into exclusion. The classic misuse is a platform declaring a norm from the top with no legitimacy behind it; it reads as a slogan and changes nothing. The guarding discipline is to keep norms legible, ensure respected members keep modeling them, watch for drift, and deliberately renew the norm after any influx.
How it implements the components¶
local_rule— the recognized expectation each member is expected to follow at the moment of interaction.feedback_signal— peer approval, reputation, and correction are the signals that enforce the norm and tell members how to adjust.rule_revision_loop— the norm is renegotiated and re-articulated as membership and context change.exception_or_escalation_rule— repair and gentle correction are the standard response when a member breaches the norm.
A community norm does not implement autonomy_boundary (formal, assigned decision rights) or boundary_condition (a mandate or charter that bounds authority) — its force is legitimacy and peer response, not delegated power; the machinery of who-formally-decides-what belongs to Decentralized Governance Norm. A community norm is organic and peer-held; a governance norm is chartered and role-bound.
Related¶
- Instantiates: Local Rule Design — a community norm is the socially-enforced instance of producing group order from many local interactions.
- Sibling mechanisms: Swarm Rule · Cellular Automata Rule · Market Rule · Protocol Rule · Team Working Agreement · Routing Rule · Decentralized Governance Norm
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Implements local rule design socially by creating locally recognized expectations for contribution, moderation, reciprocity, repair, or boundary enforcement, making its operative form a standing rule, threshold, contractual commitment, or policy constraint governing future conduct.
Independent corroboration: The frozen evidence defines Community Norm as 'Implements local rule design socially by creating locally recognized expectations for contribution, moderation, reciprocity, repair, or boundary enforcement', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Organization, Role & Governance — Its operative form is a standing socially enforced expectation, even though legitimacy comes from community modeling rather than formal policy.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Sociology & Anthropology
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: Sociology and anthropology cohered social norms as locally recognized expectations enforced through legitimacy, reputation, modeling, and peer response.
Related originating lineages:
- Psychology — Social-learning and conformity research explain individual uptake and maintenance of group expectations.
Review resolution: The source defines an organic, reputational expectation maintained through peer approval, correction, modeling, and drift. Sociology and anthropology cohered norms as community-level order, while social psychology's independent group-norm lineage materially explains conformity and internalization and is therefore retained.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The archetype source warns not to confuse community norms with commons governance: the norm shapes conduct through legitimacy, whereas commons governance centers on the shared resource. A community norm can serve a commons but is not defined by one.
[n1] "Eternal September" names the moment an online community stopped being able to acculturate newcomers because they arrived faster than the norms could be transmitted — a lasting shorthand for norm erosion under unbounded growth. ↩a ↩b