Society · Protocols

UptakeOverTimestamp

Usage determines canonical status, not who minted first

Definition

Mechanism

Resolves canonical status conflicts by prioritizing Usage Volume (uptake) over Registration Time (timestamp). When querying for a concept Handle, the system returns the variant with the highest `Reference_Count` or `Execution_Count`. The usage signal it ranks on is the one UptakeAsGround establishes.

Preconditions

  1. Multiple patterns exist for similar concepts
  2. Usage metrics available

Postconditions

  1. Canonical pattern identified
  2. Squatted/Dead patterns suppressed

Invariants

  1. Canonical status is decided by the declared uptake metric.
  2. Creation date is not a factor in ranking.

Risks

Failure modes

  1. The Facebook {{problem}} (Network Effects)

    A mediocre pattern with high early uptake becomes impossible to dislodge by a superior new pattern.

  2. Cold Start

    New patterns have 0 uptake, making them invisible to discovery algorithms.

Relationships

Builds on

References

Infrastructure

Problem

A state gap with a cost of inaction

Nothing in this library builds on this pattern yet.

Reference

Identity

Ref
UptakeOverTimestamp#4583
Sema ID
sema:UptakeOverTimestamp#mh:SHA-256:4583f9cb37df87ad847dfa423729dd7b203b33e48c5a5b96cb8baca54fc56df6
Ring
1
Tier
2
Updated
2026-11-11
Supersedes
  • sema:UptakeOverTimestamp#mh:SHA-256:9f0fffcbeef00cd271526bb7a2849998c76e242ed74d36d0058b1849379c57ab
  • sema:UptakeOverTimestamp#mh:SHA-256:6bf8a742fd1b01e216ba358b07d006f38844aee39fff285c1367c13f6d2321a7
  • sema:UptakeOverTimestamp#mh:SHA-256:54445c60697025211f92b959746d4469418d7d343e673ca20f0f00fcf7937b3d