Skip to content

Documented Plurality of Users

Treat independent, publicly recorded adoption by multiple unrelated communities as graded evidence that a shared artifact codifies something general and fit-for-purpose — a warrant signal, not a truth-maker, that collapses the moment the adopters share a hidden source.

Core Idea

Documented plurality of users is an OBO Foundry governance principle that treats independent adoption by multiple communities as a formal quality signal for a shared artifact — an ontology, vocabulary, dataset, or standard — and requires that adoption be publicly recorded. Three components must all hold: plurality (more than one community), independence (adopters sharing no funder, PI, or mandate, which gives the signal its evidential value), and documentation (a verifiable public record). It is a warrant signal, not a truth-maker.

Scope of Application

Documented plurality of users lives within the governance of shared digital infrastructure — vocabularies, standards, protocols, and reference datasets under a stewarding body; its bite comes from the operational definitions of community, use, and documentation that only a governance context supplies.

  • Ontology federation — the OBO Foundry membership criterion (GO annotated by UniProt, FlyBase, WormBase, MGI).
  • Internet and web standards — the IETF "running code" requirement of multiple independent implementations.
  • Data-resource accreditation — ELIXIR core-data-resource designation, GBIF publisher accreditation.
  • Software and API quality signals — "used-by" counts and reverse-dependency lists surfaced to adopters.

The deeper convergence-as-warrant pattern in convergent evolution or parallel discovery belongs to the parent (convergent_independent_adoption), not the principle.

Clarity

Naming this principle gives a governing body an operational handle on a question that otherwise stays impression: is this a genuine community standard, or a one-group vocabulary dressed as one? It converts a vague "is this widely used?" into three checkable conditions — plurality, independence, documentation. Its deepest clarifying move fixes what the count is evidence for: it separates a warrant signal from a truth-maker, so adoption raises the probability of fitness without guaranteeing correctness or condemning the obscure-but-correct, and it makes independence the load-bearing condition to police.

Manages Complexity

A governing body cannot deeply read every competing submission and judge its fitness against every community it claims to serve. The criterion compresses that unbounded burden into a single readable proxy: a public count of independent adopters, distilled testimony from communities that each paid the cost of adoption. The evaluation reduces to checking the three conditions that make the count informative, after which generality follows as a Bayesian inference. It isolates the one parameter that can corrupt the compression — independence — telling the steward exactly what to interrogate.

Abstract Reasoning

Reduced to a documented count under one guarded condition, the principle licenses inferences turning on warrant, not truth. A diagnostic move reads the independent adoption count as graded evidence of generality, and a single-source roster as a one-group vocabulary dressed as a standard. A boundary-drawing move separates warrant from truth and gates what the count may decide — it may enter a decision, not settle correctness. An interventionist move polices independence, predicting the warrant collapses precisely when adopters share a hidden source (pseudo-plurality).

Knowledge Transfer

Within shared-infrastructure governance the principle transfers as mechanism across substrates sharing the count-document-verify architecture, because the cargo is one warrant move: read independent documented adoption as graded evidence of fit, guarded by independence. It carries without translation across ontology federation, internet standards, data-resource accreditation, and software quality signals, with the warrant-not-truth-maker limit and the pseudo-plurality guard intact. Beyond governance the named principle does not travel; what does is the parent — independent convergence on the same shape is evidence the shape names something real — which recurs in convergent evolution, parallel discovery, and multiple realizability, carried by a candidate convergent_independent_adoption (with social_proof as the cognitive cousin).

Relationships to Other Abstractions

Local relationship map for Documented Plurality of UsersParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.DocumentedPlurality of UsersDOMAINPrime abstraction: Convergent Evolution — is a kind ofConvergentEvolutionPRIME

Current abstraction Documented Plurality of Users Domain-specific

Parents (1) — more general patterns this builds on

  • Documented Plurality of Users is a kind of Convergent Evolution Prime

    Plurality of users is independent convergence specialized to adoption of a shared knowledge artifact as graded quality evidence.

Hierarchy paths (3) — routes to 3 parentless roots

Neighborhood in Abstraction Space

Documented Plurality of Users sits in a sparse region of the domain-specific corpus (61st percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Trust Infrastructure for Shared Knowledge (6 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12