Skip to content

Local Rule Design

Design simple local rules so decentralized interactions produce a desired system-level pattern.

The Diagnostic Story

Symptom: Local actors each make reasonable-looking choices, but the combined result is congestion, gaps, duplication, or conflict that no one intended. Central coordinators are overloaded trying to specify every action because the system has no shared rule for how locals should decide. A desirable pattern appears in some pockets but does not reliably reproduce itself across the whole.

Pivot: Translate the desired macro-pattern into executable local rules: specific enough for a local actor to apply with the information they have, but defined at the level of interaction logic rather than individual assignments. Provide feedback so local actors can see when the aggregate is diverging from intent, and create a revision path so rules can be updated when emergence goes wrong.

Resolution: Decentralized coordination improves without central command of every action, because the interaction rules produce the desired pattern rather than leaving it to chance or supervision. The system gains adaptive capacity as actors respond to local conditions within a shared rule envelope. Coordination load shifts from constant oversight to better-designed rules.

Reach for this when you hear…

[urban traffic] “Everyone is trying to avoid the same congested street, so they all use the same alternate route and now that one is worse than the original.”

[ecological management] “Every individual grazer is just taking what looks available to them, but we have no rule for when a patch needs rest, so the whole commons degrades without anyone choosing to overgraze it.”

[distributed team] “We said 'use your judgment' about who handles what, and now three people are doing the same ticket and four others are waiting for someone else to pick up theirs.”

Mechanisms / Implementations

  • Swarm Rules: Implement the archetype when many similar agents respond to nearby signals.
  • Market Rules: Implement the archetype by shaping decentralized bids, offers, prices, matches, eligibility, or transactions.
  • Protocol Rules: Implement the archetype in technical or procedural systems.
  • Team Working Agreements: Implement the archetype socially.
  • Community Norms: Implement local rule design through socially recognized expectations.
  • Routing Rules: Implement the archetype when the local decision is where work, traffic, cases, requests, or attention should go next.
  • Cellular Automata-like Rules: Are modeling mechanisms: each cell updates from neighboring states, and the designer observes aggregate patterns.
  • Decentralized Governance Norms: Implement local rule design in groups or federated contexts by defining local decision rights, conflict surfacing, escalation, and boundary-respecting behavior.
  • Cellular Automata Rule
  • Community Norm

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 6 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Swarm Rule Design · mechanism family variant · recognized

Design local movement, proximity, alignment, or response rules for many similar agents so a swarm-like aggregate pattern emerges.

Protocol Local Rule Design · implementation variant · recognized

Specify local protocol behaviors so independently operating components remain compatible and produce a coherent network-level behavior.

Norm-Based Local Rule Design · governance variant · likely subtype

Shape informal or semi-formal local expectations so repeated interpersonal choices generate a desired group-level pattern.

Routing Rule Design · implementation variant · recognized

Define local routing or handoff rules so distributed nodes produce reliable flow, coverage, load balance, or reachability.