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 ontology-governance principle that treats independent adoption by multiple communities as a formal quality signal for a shared artifact — an ontology, a controlled vocabulary, a reference dataset, or a standard — and requires that this adoption be publicly recorded so prospective users and governing bodies can verify it.

The mechanism has three components that must all be present for the criterion to have force. The first is plurality: more than one community uses the artifact. A single-community vocabulary, however technically competent, has not been tested against the interpretive diversity that real interoperability requires; it may encode assumptions specific to one domain, one organism, or one laboratory workflow that make it a poor fit for others. The second is independence: the adopting communities are genuinely separate — different institutions, different research programs, different organizational decision chains. Independence is the structural condition that gives the adoption signal its evidential value. If two communities share a funder, a principal investigator, or a mandate that requires adoption, their convergence on the same vocabulary is uninformative about the vocabulary's generality; it may reflect institutional pressure rather than fit-to-purpose. The third is documentation: the adoption is publicly recorded in a form that prospective users can verify — a registry entry, a usage list maintained by the governing body, peer-reviewed publications citing the artifact, or a formally tracked list of implementing databases. The documentation converts the adoption fact from informal knowledge (people who happen to know the community use it) into an institutionally verified warrant that can be consulted and cited.

The principle is operational within the OBO Foundry membership criteria: a candidate ontology submitted for inclusion must demonstrate active independent use by multiple communities, not merely a declaration of intent to be reusable. This operationalisation addresses a specific failure mode in shared vocabulary governance — the one-group vocabulary that is submitted as a community standard but has been developed by and for one research group and reflects that group's conceptual commitments, terminological choices, and curation priorities rather than those of the broader community it nominally serves. The documented-plurality criterion catches this failure at submission rather than after wide deployment has created lock-in.

The same pattern appears in adjacent governance regimes. The IETF requires multiple independent interoperating implementations before advancing a protocol from Proposed Standard to Internet Standard. ELIXIR's core data resource designation counts independent depositing and consuming communities. Package managers surface "used by" counts and reverse-dependency lists as quality proxies for prospective adopters. In each case, the structural commitment is the same: independent convergence on the same artifact, documented and verifiable, is read as evidence that the artifact names or codifies something sufficiently general and well-formed to be useful beyond its originators.

The principle is a warrant signal, not a truth-maker. A widely-adopted vocabulary can encode a conceptual error that propagates with adoption; a poorly-adopted one may be correct but merely obscure. The criterion delivers Bayesian evidence — independent convergence raises the probability that the artifact is fit-for-purpose — conditional on the independence condition being genuinely satisfied, and it provides no protection against coordinated mis-adoption or against lock-in to an early-mover vocabulary that later proves inadequate.

Structural Signature¶

Sig role-phrases:

the shared artifact — an ontology, controlled vocabulary, reference dataset, or standard whose fitness a governing body must judge
the plurality condition — adoption by more than one community, so the artifact has been tested against interpretive diversity rather than one group's idiom
the independence condition — adopters that are genuinely separate (no shared funder, PI, or mandate), the structural condition that gives the adoption signal its evidential value
the documentation condition — a public, verifiable record (registry entry, usage list, citation track, implementer roster) converting informal adoption into a consultable warrant
the warrant inference — the engineered move: an independent, documented adoption count read as graded Bayesian evidence of fit-for-purpose generality and shared maintenance durability
the warrant-not-truth-maker limit — the scope ceiling: adoption may raise confidence but cannot certify correctness (popular-but-wrong) or condemn the obscure-but-correct
the pseudo-plurality failure mode — the corruption guarded against: adopters sharing a hidden source, laundering institutional pressure as evidence of fit, plus nominal-compliance masquerading as genuine use

What It Is Not¶

Not a truth-maker. Documented plurality is a warrant signal, not a proof of correctness. Independent convergence raises the probability that an artifact is fit-for-purpose, but it neither guarantees a widely-adopted vocabulary is right (adoption can propagate and lock in a conceptual error) nor condemns the obscure-but-correct artifact no one has yet picked up. The count delivers Bayesian evidence, conditional on independence; it cannot settle a correctness question, which requires reading the artifact's internals.
Not a raw count of users. What gives the signal its evidential value is independence: the adopters must be genuinely separate communities with no shared funder, PI, or mandate. A large roster that traces back to one source is a pseudo-plurality that launders institutional pressure as evidence of fit — uninformative about generality however impressive the number. The independence condition is the load-bearing one to police, not the headcount.
Not a network effect. The adoption count is used as a quality signal for prospective outsiders, not as a value mechanism for insiders. Network effects are the value-grows-with-users dynamic in which adoption itself raises per-user utility; documented plurality reads the count as evidence that the artifact codifies something general, with no claim that more adopters make the artifact more useful to existing ones.
Not wisdom of the crowds. It does not aggregate independent noisy estimates of a hidden quantity to recover a truth; it counts independent adoptions and reads the count as a warrant of fit. The crowd-wisdom move averages judgments; this move treats each free adoption as distilled testimony, and its inference is about the artifact's generality, not about the central tendency of a set of estimates.
Not nominal citation or declared reusability. The criterion requires genuine use — actual incorporation in workflows — that is publicly documented, not a submitter's declaration of intent or a tally of citations. A vocabulary built by and for one group and merely asserted to be reusable fails the criterion; what counts is a verifiable record of independent communities that have already reused it in practice.

Scope of Application¶

Documented plurality of users lives within the governance of shared digital infrastructure — controlled vocabularies, standards, protocols, and reference datasets under a stewarding body; its reach is bounded to that domain, because what gives the principle its bite is the operational definition of community, use, and documentation that only a governance context supplies. The deeper convergence-as-warrant pattern that recurs in convergent evolution or parallel discovery belongs to its parent (convergent_independent_adoption), not the principle. Within the domain the same count-document-verify architecture is instantiated across these regimes.

Ontology federation — the OBO Foundry membership criterion: a candidate ontology must show active independent use by multiple communities (e.g. Gene Ontology annotated independently by UniProt, FlyBase, WormBase, and Mouse Genome Informatics).
Internet and web standards governance — the IETF "running code" requirement of multiple independent interoperating implementations before a protocol advances from Proposed Standard to Internet Standard, and analogous W3C practice.
Data-resource accreditation — ELIXIR core-data-resource designation and GBIF publisher accreditation, counting independent depositing and consuming communities.
Software and API quality signals — "used-by" counts, GitHub Used By tallies, and package-manager reverse-dependency lists surfaced to prospective adopters as governance-grade evidence of fitness.

Clarity¶

Naming this principle gives a governing body an operational handle on a question that otherwise stays a matter of impression: is this candidate artifact a genuine community standard, or a one-group vocabulary dressed as one? Without the criterion, a submission's reusability rests on the submitter's declaration of intent, and a vocabulary built by and for a single laboratory can pass review on its technical merits while quietly carrying that group's idiosyncratic conceptual commitments — caught, if at all, only after wide deployment has produced lock-in. The principle makes the failure mode legible by converting a vague "is this widely used?" into three checkable conditions: more than one adopter (plurality), adopters who do not share a funder, PI, or mandate (independence), and a public record a reviewer can consult (documentation). The sharper question a steward can now ask at submission time is not "do the authors say this is reusable?" but "can I point to independent communities that have already reused it, and verify that their convergence was free rather than coerced?"

The criterion's deepest clarifying move is to fix exactly what the adoption count is evidence for — and what it is not. It separates a warrant signal from a truth-maker: independent convergence raises the probability that an artifact codifies something general and fit-for-purpose, but it neither guarantees correctness (a widely-adopted vocabulary can propagate a conceptual error and lock it in) nor condemns the obscure-but-correct artifact that no one has yet picked up. Holding "warranted" distinct from "true" keeps a governing body from over-reading its own registry, and it makes the independence condition the load-bearing one to police — because the moment the adopting communities share a hidden source, the convergence stops being informative and the documented plurality becomes a pseudo-plurality that launders institutional pressure as evidence of fit.

Manages Complexity¶

A governing body facing dozens of competing or overlapping submissions cannot deeply read each candidate vocabulary, trace its conceptual commitments, and judge its fitness against every community it claims to serve — that is an unbounded curation burden, repeated per artifact. The documented-plurality criterion compresses that burden into a single readable proxy: a public count of independent adopters. Rather than re-deriving an artifact's generality from its internals, a steward consults the registry's "used-by" track and reads the count as distilled testimony from the bench — independent communities that already paid the cost of adoption, each vouching for fit by their free choice. The whole evaluation reduces to checking the three conditions that make the count informative — more than one adopter, adopters who share no funder or mandate, a verifiable record — after which generality and shared maintenance durability follow as Bayesian inferences from the documented convergence. The criterion further isolates the one parameter that can corrupt the compression, independence: as long as it holds, the adoption count substitutes for deep review; the moment it fails, the steward knows exactly which assumption to interrogate rather than re-auditing the artifact wholesale. A high-dimensional fitness judgment is thereby collapsed into a small, cheap-to-verify warrant whose evidential value turns on a single guarded condition.

Abstract Reasoning¶

Reduced to a documented count of independent adopters under a single guarded condition, the principle licenses the inferences a governing body draws when judging a shared artifact's fitness without reading it deeply — all turning on the adoption count being treated as warrant, not truth.

Diagnostic — read the documented adoption count as graded evidence of generality. The core inference runs from an observable warrant (a registry's "used-by" list, a citation track, a roster of implementing databases) to a hidden property (fit-for-purpose generality). A high count of independent adopters raises the probability that the artifact codifies something real and transferable rather than over-fitting one group's idiom: unrelated communities each paid the cost of adoption and, by free choice, vouched for fit. The complementary diagnostic catches the failure mode the principle was built for — a submission with a single adopter, or several adopters tracing back to one funder, PI, or mandate, is inferred to be a one-group vocabulary dressed as a community standard, carrying that group's idiosyncratic conceptual commitments. The strength of the inference is graded by the count's size and, decisively, by the independence of the adopters; the steward reasons from the documented convergence to fitness exactly to the degree that the convergence was free.

Boundary-drawing — separate warrant from truth, and gate what the count may decide. The principle's sharpest move is a scope limit on its own inference: documented plurality is a warrant signal, not a truth-maker, so the steward draws a hard line around what the count licenses. It may raise confidence that an artifact is fit-for-purpose and shares a durable maintenance base; it may not be read as a guarantee of correctness — a widely-adopted vocabulary can propagate a conceptual error and lock it in, and an obscure artifact may be correct but merely unadopted. The boundary judgment therefore forbids two over-readings: condemning the correct-but-obscure for want of adopters, and certifying the popular-but-wrong on adoption alone. A count that passes the criterion may enter a membership or quality decision as evidence; it may not settle a correctness question, which requires reading the artifact's internals.

Interventionist — police the one condition that can corrupt the warrant. Because the count substitutes for deep review only while independence holds, the load-bearing intervention is to verify independence, and the principle predicts where the warrant breaks. Confronted with an impressive adoption list, the steward audits whether the adopters share a hidden source — a common funder, a shared PI, a mandate compelling adoption — because the moment they do, the convergence stops being informative and the documented plurality becomes a pseudo-plurality that launders institutional pressure as evidence of fit. The remedy is targeted: rather than re-auditing the whole artifact, the steward interrogates the single assumption (independence) whose failure would invalidate the inference, and a second check confirms the adoption is genuine use (incorporation in workflows) rather than nominal citation or compliance. The prediction is that the warrant's evidential value collapses precisely when, and only when, that guarded condition fails — which tells the steward exactly what to test before trusting the count.

Knowledge Transfer¶

Within shared-infrastructure governance — the home domain — documented plurality of users transfers as mechanism across substrates that share the count-document-verify architecture, because the cargo is one warrant move: read independent, documented adoption as graded evidence of fit-for-purpose generality, guarded by the independence condition. It is instantiated, with the same skeleton, across ontology federation (the OBO Foundry membership criterion, e.g. GO annotated independently by UniProt, FlyBase, WormBase, MGI), internet standards (the IETF "running code" requirement of multiple independent interoperating implementations before Internet Standard), data-resource accreditation (ELIXIR core-data-resource designation, GBIF publisher accreditation counting independent depositing/consuming communities), and software quality signals ("used-by" counts, reverse-dependency lists surfaced to adopters). Across all of these the full apparatus carries without translation — the warrant-not-truth-maker scope limit, the diagnosis of a single-source roster as a one-group artifact dressed as a standard, the policing of independence as the one corruptible condition (the echo-chamber/pseudo-plurality guard), and the genuine-use-versus-nominal-compliance check — because every case is the same governing body reading a documented adoption count as distilled testimony in place of deep review. The criterion is operationally sharp inside such a governance context; the seed notes that outside one (a fuzzier general "lots of people use it") it loses exactly the operational definitions of community, use, and documentation that give it bite.

Beyond governance machinery the named principle does not travel, and the honest reading is a strong shared-abstract-mechanism one: what transfers is not "plurality of users" but the deeper pattern it operationalizes. That parent — independent convergence on the same shape, from unrelated sources, is evidence the shape names something real — genuinely recurs across radically different substrates as co-instances: convergent evolution in biology, parallel/multiple discovery in science, multiple independent implementation in standards, multiple realizability in philosophy of mind, cross-cultural recurrence in folklore. This is (B), and the cross-domain lesson should carry the parent (an emergent candidate such as convergent_independent_adoption, with the echo-chamber failure mode as its standing guard and social_proof as the cognitive cousin to the institutional version), not the governance principle. A reader who meets the OBO criterion and reaches to apply it to physical-engineering standards or museum vocabulary governance should import not the OBO machinery but the same underlying checks the parent demands — are the converging sources genuinely independent, is the convergence free rather than coerced, does the record track use rather than declaration — which is precisely the parent pattern doing the work. "Documented plurality of users," as named, keeps the governance-specific cargo (the steward, the registry artifact, the membership decision, the controlled-vocabulary/standard/dataset substrate) that stays home; stripped of it, the residue is the convergence-as-warrant parent plus a recorded-warrant rider, so the exportable structure is that parent, not the principle. See Structural Core vs. Domain Accent.

Examples¶

Canonical¶

The OBO Foundry's treatment of the Gene Ontology (GO) is the defining instance. When GO is evaluated as a community standard, the warrant is not its developers' say-so but its documented independent adoption: GO terms annotate genes independently at UniProt (proteins across all species), FlyBase (Drosophila), WormBase (C. elegans), and Mouse Genome Informatics — separate model-organism databases, separate institutions, separate funding and curation chains, each of which chose GO on its own and publicly records its GO-annotated data. That several unrelated communities converged on the same vocabulary, and that the convergence is verifiable in each database's published annotations, is read as graded evidence that GO codifies biological function generally rather than encoding one lab's idiom. A single-organism vocabulary used only by its makers would fail the criterion at submission, before wide deployment created lock-in.

Mapped back: GO is the shared artifact; use by four model-organism databases is the plurality condition, and their separate institutions and funders are the independence condition that gives the count evidential value. The published annotations are the documentation condition, and reading the convergence as evidence of general fitness is the warrant inference.

Applied / In Practice¶

The IETF applies the same principle to internet protocols through its "running code" requirement. Before a protocol can advance from Proposed Standard to full Internet Standard, the IETF requires evidence of multiple independent, interoperating implementations — separately built codebases from unrelated developers that successfully talk to one another using the spec. The demand is deliberately for independence and genuine use, not declarations: two implementations written by the same team, or a spec merely claiming to be implementable, do not qualify; the point is that unrelated developers, reading the same document, each produced working software that interoperates. Documented interoperability reports record which implementations were tested against which. This catches the one-group standard — a specification so bound to its authors' assumptions that only they can implement it — exactly as documented plurality intends, and before the protocol is enshrined and locked in across the internet.

Mapped back: Multiple interoperating implementations are the plurality condition; unrelated developers are the independence condition, and requiring same-team implementations to be disqualified is the pseudo-plurality guard. Interoperability reports are the documentation condition, and the insistence on working, interoperating code rather than a claim of implementability is the genuine-use check.

Structural Tensions¶

T1: Warrant signal versus truth-maker (adoption raises probability, not correctness). The principle's defining scope limit is that documented plurality is a warrant signal, not a truth-maker: independent convergence raises the probability that an artifact is fit-for-purpose, but it neither guarantees a widely-adopted vocabulary is correct nor condemns an obscure-but-correct one. The tension is that a registry's "used-by" count is so readable, and reads so much like validation, that a governing body is tempted to over-read its own signal — certifying the popular-but-wrong (a conceptual error that propagates and locks in with adoption) or dismissing the correct-but-unadopted. The count can enter a membership decision as Bayesian evidence but cannot settle a correctness question, which requires reading the artifact's internals. Holding "warranted" apart from "true" is the discipline the criterion demands and the one its own convenience erodes. Diagnostic: Is the adoption count being used to raise confidence in fit (licensed) or to certify correctness (an over-read the count cannot support)?

T2: Independence as load-bearing versus corruptible (the count is only as good as its guarded condition). The adoption count substitutes for deep review only while independence holds — the adopters must be genuinely separate, with no shared funder, PI, or mandate. The moment they trace back to one source, the convergence stops being informative and the documented plurality becomes a pseudo-plurality that launders institutional pressure as evidence of fit. The tension is that independence is both the single condition that gives the whole warrant its value and the one most easily faked: an impressive roster can be assembled by a coordinated or mandated network that looks like free convergence. So the criterion's entire evidential force rests on a condition that a motivated submitter has every incentive to counterfeit, and the steward's real work is auditing the one assumption rather than admiring the count. Diagnostic: Do the adopters share a hidden source — a common funder, PI, or mandate — that would turn free convergence into laundered institutional pressure?

T3: Catching the one-group vocabulary versus enabling early-mover lock-in (the warrant that guards one failure abets another). The criterion's purpose is to catch, at submission, the one-group vocabulary dressed as a community standard — before wide deployment creates lock-in. But the same adoption-as-warrant logic has a mirror failure it does not guard: an early-mover artifact can accumulate independent adopters, pass the criterion, and then prove inadequate, with its very adoption having propagated a conceptual error and entrenched it. The tension is that the mechanism which correctly rejects the untested newcomer also rewards incumbency, and a high count can reflect first-mover entrenchment rather than fitness. The warrant that protects against premature standardization can, over time, protect a flawed standard from replacement. Diagnostic: Is the adoption count evidence of genuine fitness, or of early-mover lock-in that would accrue to an inadequate artifact just as readily?

T4: Genuine use versus nominal citation or compliance (adoption must be real to be evidence). The criterion requires genuine use — actual incorporation in workflows — that is publicly documented, not a submitter's declaration of intent or a tally of citations. The tension is that the observable proxies (citation counts, "used-by" tallies, registry entries) are precisely what can be inflated without real adoption: a vocabulary can be widely cited, or nominally required, without any community actually building on it, so the documentation that is supposed to convert informal adoption into a verifiable warrant can itself record compliance theater. The check that gives the count its bite (is this genuine use?) is harder to verify than the count itself, so the easy signal and the load-bearing one diverge. Diagnostic: Does the record show the artifact incorporated into actual workflows (genuine use), or only cited, declared, or mandated (nominal adoption)?

T5: Autonomy versus reduction (a governance principle or the convergent-independent-adoption parent). Within shared-infrastructure governance the principle transfers as mechanism across the count-document-verify regimes — OBO Foundry, IETF running code, ELIXIR, package-manager "used-by" lists — because each is a governing body reading a documented adoption count as testimony in place of deep review, and outside such a context it loses the operational definitions of community, use, and documentation that give it bite. What genuinely recurs across radically different substrates is the deeper pattern it operationalizes: independent convergence on the same shape, from unrelated sources, is evidence the shape names something real — a parent (candidate convergent_independent_adoption, with social_proof as its cognitive cousin) that appears as convergent evolution, parallel discovery, multiple realizability, and cross-cultural recurrence. The tension is between a governance-specific principle (steward, registry, membership decision) and the substrate-general convergence-as-warrant pattern, plus its standing echo-chamber guard. Diagnostic: Resolve toward convergent_independent_adoption (are the converging sources genuinely independent and the convergence free?) when carrying the lesson beyond governance; toward documented plurality when a steward is judging a registered artifact for a membership or quality decision.

Structural–Framed Character¶

Documented plurality of users sits well toward the framed pole — best read as framed-leaning: an institutionally-originated, normatively-charged governance criterion constituted by a stewardship practice, not a mechanism nature runs. Four of the five criteria point framed. Its evaluative weight is real: the principle is a quality criterion — an operational membership standard that a governing body applies to admit or reject a candidate artifact — so its whole point is to license a verdict of fitness, not to describe a neutral mechanism. It is human-practice-bound in the strongest sense: it is constituted by a governance practice (a steward, a registry, a membership decision) and by the operational definitions of community, use, and documentation that only that context supplies; the entry is explicit that outside a governance context it degrades into a fuzzy "lots of people use it" and loses its bite. Its institutional origin is pronounced: it is a specific artifact of governing bodies — the OBO Foundry membership criteria, the IETF "running code" requirement, ELIXIR accreditation — drawn inside those traditions, not a fact of nature. And vocab_travels fails: steward, registry, membership decision, implementer roster, and the documentation condition are all governance furniture that does not float free.

The one structural-leaning mark is import_vs_recognize: the deeper pattern the principle operationalizes recurs across radically different substrates as genuine co-instances — convergent evolution, parallel discovery, multiple realizability, cross-cultural recurrence — recognized, not borrowed by analogy. But that recognition belongs to the parent, not to "documented plurality of users," which imports into non-governance settings only metaphorically.

The portable structural skeleton is convergent_independent_adoption: independent convergence on the same shape, from unrelated sources, is graded evidence that the shape names something real — a warrant inference guarded by an independence condition (with social_proof as its cognitive cousin and a recorded-warrant rider). That parent is exactly what the principle instantiates, not what makes "documented plurality of users" itself travel: the cross-domain reach belongs to convergent-independent-adoption (carry its checks — genuine independence, free rather than coerced convergence, use rather than declaration — anywhere), while the steward, the registry artifact, the membership decision, and the controlled-vocabulary/standard/dataset substrate are the domain accent that stays home. Its character: an institutionally-originated, normatively-charged governance criterion constituted by a stewardship practice, structural only in the convergent-independent-adoption warrant it instantiates and frames as a quality verdict — framed-leaning, not a prime.

Structural Core vs. Domain Accent¶

This section decides why documented plurality of users is a domain-specific abstraction and not a prime — separating the portable convergence-as-warrant skeleton from the governance machinery that operationalizes it.

What is skeletal (could lift toward a cross-domain prime). Strip the governance context and a thin relational structure survives: independent convergence on the same shape, from unrelated sources, is graded evidence that the shape names something real and fit-for-purpose — a warrant inference whose strength turns on the genuine independence of the converging sources, and which raises probability without certifying correctness. The portable pieces are abstract — multiple sources, a genuine-independence condition, convergence on one artifact, and a Bayesian read of that convergence as evidence of generality rather than proof of truth. This skeleton is genuinely substrate-portable, which is exactly why the entry names the parent convergent_independent_adoption (with social_proof as its cognitive cousin and a recorded-warrant rider): the same convergence-as-evidence move recurs as convergent evolution in biology, parallel/multiple discovery in science, multiple realizability in philosophy of mind, and cross-cultural recurrence in folklore — genuine co-instances, not analogies. That portable core is what documented plurality shares, not what makes it documented plurality.

What is domain-bound. Almost everything that makes the construct this criterion is shared-infrastructure-governance furniture and none of it survives extraction: the steward and governing body that applies the criterion; the registry artifact, usage list, implementer roster, and interoperability report that supply the documentation condition; the membership decision the count feeds; and the operational definitions of community, use, and documentation that give the principle its bite. The empirical cases (OBO Foundry, IETF running code, ELIXIR, GBIF, package-manager "used-by" lists) and the specific substrates (controlled vocabularies, standards, protocols, reference datasets) are equally home-bound. The decisive test: remove the governance context and the criterion degrades into a fuzzy "lots of people use it," losing exactly the operational definitions that let it catch a one-group vocabulary dressed as a standard — what remains is the bare convergence-as-warrant pattern, the looser parent, not documented plurality.

Why this does not clear the prime bar. A prime is a relational structure whose vocabulary travels and whose cross-domain transfer is recognition of the same mechanism, not analogy. Documented plurality's transfer is bimodal. Within shared-infrastructure governance it travels as full mechanism — the count-document-verify architecture, the warrant-not-truth-maker scope limit, the pseudo-plurality/echo-chamber guard, and the genuine-use check carry intact from ontology federation to internet standards to data-resource accreditation to software quality signals, genuine recognition of one warrant move. Beyond governance the named principle does not travel: a reader applying it to physical-engineering standards or museum vocabulary governance imports not the OBO machinery but the underlying checks the parent demands (are the converging sources genuinely independent, is the convergence free rather than coerced, does the record track use rather than declaration) — which is the parent pattern doing the work, reached by analogy from the governance brand. And when the bare structural lesson is needed cross-domain — independent convergence as graded evidence of a real, general shape — it is already carried, in more general form, by convergent_independent_adoption (with social_proof and the recorded-warrant rider). The cross-domain reach belongs to that parent; "documented plurality of users," as named, carries the steward, registry, membership-decision, and controlled-vocabulary machinery that should stay home.

Relationships to Other Abstractions¶

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

Documented Plurality of Users → Convergent Evolution → Multi Path Convergence → Convergence

Show alternative paths (2)

Not to Be Confused With¶

Network effect. The value-creation dynamic in which an artifact becomes more useful to existing users as more join (a telephone network, a social platform). Documented plurality reads the adoption count the other way — as evidence to an outside evaluator that the artifact codifies something general — and makes no claim that more adopters raise per-user utility. One is a value mechanism for insiders; the other is a quality signal for prospective outsiders. Tell: does adding a user raise the artifact's utility for the others (network effect), or merely add to a warrant a steward reads about the artifact's fitness (documented plurality)?
Wisdom of the crowds. The statistical recovery of a hidden quantity by averaging many independent noisy estimates of it. Documented plurality does not average estimates of anything; it counts independent adoptions and reads the count as a warrant of general fitness. Crowd-wisdom aggregates judgments toward a central value; this treats each free adoption as distilled testimony about the artifact's generality. Tell: are independent numerical estimates being averaged to find a truth (wisdom of crowds), or independent adoptions being counted as evidence a shared artifact is fit-for-purpose (documented plurality)?
Social proof. The cognitive heuristic by which an individual infers correctness or value from others' behavior ("if everyone's doing it, it must be good"). Documented plurality is the institutional formalization of the same intuition — a governing body's operational criterion with explicit plurality, independence, and documentation conditions and a warrant-not-truth-maker scope limit. Social proof is the unguarded individual cousin; documented plurality is the guarded, recorded, steward-applied version. Tell: is it an individual's fast inference from others' behavior (social proof), or a governing body's audited criterion with an independence check and a public record (documented plurality)?
De facto standard / market dominance. An artifact that has become dominant simply by capturing the most users or market share, regardless of how or why. Documented plurality is not about dominance or share; a modestly-adopted artifact passes if its few adopters are genuinely independent and their use is documented, while a hugely-adopted one fails if the roster traces to one source (pseudo-plurality). The load-bearing test is independence, not size. Tell: is the claim that this artifact won the most users (de facto standard), or that genuinely independent communities freely converged on it (documented plurality)?
Convergent evolution / parallel discovery (sibling co-instances). Independent arrival at the same biological form, or the same invention/theorem by separate researchers — cases where unrelated sources converging on one shape is read as evidence the shape names something real. These are sibling instances of the same parent pattern, not the governance criterion: they carry no steward, registry, membership decision, or documentation condition. Documented plurality is the governance-substrate instance; these are the biology and science-history instances. Tell: is there a governing body reading a public adoption record for a fitness verdict (documented plurality), or unrelated natural/intellectual processes independently landing on the same form (convergent evolution / parallel discovery)?
Convergent independent adoption (parent prime). The substrate-neutral warrant pattern the principle instantiates — independent convergence on the same shape, from unrelated sources, as graded evidence the shape names something real, guarded by an independence condition. This is what actually travels beyond governance; documented plurality is its shared-infrastructure-governance specialization. Treated more fully in the Knowledge Transfer and Structural Core vs. Domain Accent sections. Tell: strip the steward, registry, and membership decision and what remains — free independent convergence read as evidence of a real, general shape — is the parent, not documented plurality.

Neighborhood in Abstraction Space¶

Documented Plurality of Users sits in a sparse region of the domain-specific corpus (61^st 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