---
name: Community
slug: community
type: social_structure
status: running
version: 0.0.1-ancient
released: "~10,000 BCE"
maintainer: everyone (unassigned)
dependencies:
  - shared_space
  - mutual_recognition
  - low_grade_tolerance
  - collective_memory
license: Public Domain (contested)
tags:
  - social
  - infrastructure
  - load-bearing
  - frequently_misunderstood
---

Community

What it actually is

A group of entities sharing enough context to disappoint each other meaningfully.

How it works

Community bootstraps from proximity, either physical or conceptual. Two people can start one accidentally. The minimum viable community is three: one to propose, one to agree, one to complicate things. From there, the system scales unpredictably.

Core loop:

Shared problem or shared interest creates initial cohesion
Repeated contact generates trust (slow) or resentment (faster)
Norms accumulate without anyone formally writing them down
Someone eventually writes them down. Conflict ensues.
A subset leaves to form a splinter community with the same problems, different aesthetics
Return to step 1

The process is lossy by design. Not everyone who enters the loop completes it. This is considered a feature.

Features

Belonging: The sensation that your presence is expected somewhere. Rare. Valuable. Slightly terrifying when first encountered.
Collective memory: The group knows things no individual member knows. Also misremembers things no individual would misremember alone.
Distributed load-bearing: Grief, celebration, and logistical crises are processed at scale. Throughput improves. Latency varies.
Ambient accountability: Behavior shifts when people know they will see each other again. Not always for the better, but often enough.
Informal infrastructure: The pot lucks, the signal threads, the person who just knows how to fix things. None of it is documented. All of it is critical.

Known bugs

Free rider accumulation: Some nodes consume without contributing. System usually absorbs this until it cannot.
In-group calcification: Over time, the boundary between member and non-member becomes load-bearing in bad ways. See tribalism.
Hero node failure: One person runs 70% of operations. They burn out. Community discovers the gap all at once.
Nostalgia drift: Members begin maintaining the memory of the community instead of the community itself.
Consensus deadlock: Leaderless structures are resistant to bad decisions and good ones equally.

Configuration

community:
  size: 2 to ~150  # Dunbar's ceiling applies
  medium: physical | digital | hybrid
  cohesion_basis: place | interest | identity | crisis
  formalization: none | light | institutional
  expected_half_life: 3 months to 400 years
  splinter_risk: increases with success

Error codes

Code	Message	Likely Cause
`COMM_001`	No quorum	Everyone assumed someone else would show up
`COMM_002`	Identity conflict	The community forgot what it was for
`COMM_003`	Moderator exhaustion	See hero node bug
`COMM_004`	Hostile fork	Unresolved values mismatch
`COMM_005`	Gentrification	External pressure changed membership profile faster than norms could adapt

FAQ

Is an online group a real community? The internet changed what proximity means. The question is whether the mutual recognition is real. Usually it is. Sometimes it is performed. The ratio matters.

Why do communities that seem thriving suddenly collapse? They were often running on one person's loneliness. When that person healed or left, the load disappeared with them.

Can you design a community? You can design conditions. The community decides whether to exist.

drafting spec…