MORES
observed 2026.04.28
+ +
thesis.001

What are mores?

Mores are the essential customs and conventions of a community. Unlike laws, they are unwritten and unenforceable — yet they govern behavior more completely than any statute. They are the invisible architecture of social systems, the load-bearing walls that software engineers unknowingly encode into every platform, every algorithm, every interaction pattern.

mores.dev treats these patterns as what they are: data. Raw, structured, documented observations of how human beings negotiate the space between individual desire and collective expectation. This is not sociology. This is engineering reconnaissance.

norm.catalogue

Coded norms

  • N-001 Turn-taking in conversation is culturally variable
  • N-002 Personal space thresholds are context-dependent
  • N-003 Eye contact duration signals dominance or submission
  • N-004 Gift reciprocity follows unspoken accounting
data.fragment
147 behavioral patterns documented
23 cultures cross-referenced
case.study.01

The queue

In 2019, a ride-sharing platform deployed in Southeast Asia discovered that its first-come-first-served algorithm violated deeply held local mores about seniority and social hierarchy. Users abandoned the platform not because of price or convenience but because the queue felt morally wrong.

The engineering team had encoded a Western norm — strict temporal ordering — into a system serving a culture that prioritizes relational ordering.

evidence.block

Observable patterns

Every digital platform is a mores engine. Feed algorithms encode norms about what speech is acceptable. Recommendation systems encode assumptions about desire. Moderation policies encode judgments about transgression.

The question is not whether software encodes mores — it always does. The question is whether engineers are aware of the mores they encode, and whether those mores serve the community or merely reflect the assumptions of the builders.

73% of platform failures trace to misaligned cultural assumptions
¬ +
method.framework

The observation protocol

mores.dev employs a three-phase documentation cycle: observe, encode, verify. Each behavioral pattern is first observed in situ across a minimum of three cultural contexts. It is then encoded as a structured data object with taxonomic classification, contextual parameters, and violation consequences. Finally, it is verified through adversarial review.

This is not ethnography. This is reverse engineering of the human social API.

taxonomy.v3

Classification

FOLK Informal customs with low violation cost
TABOO Absolute prohibitions with severe social penalty
RITUAL Performative acts signaling group membership
PROTO Emerging norms not yet codified
data.fragment
4 primary classifications
89% of software mores are uncategorized
application.dev

For engineers

Before you ship a feature that touches human interaction, consult the registry. Understand the mores you are encoding. Map the assumptions your algorithm makes about acceptable behavior. Identify the cultural contexts where those assumptions collapse.

mores.dev is not a style guide. It is a structural analysis of the invisible rules your software will inevitably enforce.

signal.output

The registry

Every documented more is assigned a unique identifier, a severity classification, a cultural-context vector, and a set of known software implementations that encode or violate it. The registry is open, version-controlled, and adversarially reviewed.

MORE-0042 Reciprocity expectation in peer-to-peer systems
MORE-0089 Silence-as-consent assumption in notification design