Founding Vocabularies Constrain Later Participants

The terms a project's architects choose during founding work -- metaphors for the problem space, predicate names, form-type labels, agent names -- enter the corpus before the broader participant set has a chance to propose alternatives. The terms calcify through repeated use, and by the time a later participant encounters them, the vocabulary is no longer under negotiation. The constraint operates regardless of whether the chosen terms are good: what matters structurally is that the later participant's position is adopter-or-dissenter rather than proposer, which is not the same deliberative standing the architects had when they picked the terms.

The Observation is adjacent to but distinct from the convergence-produces-authority dynamic recorded in [[Consensus Creates Priesthoods]]. Priesthoods describe what happens after a community has converged -- participants who shaped the converged vocabulary acquire natural authority over how it is used and extended. Founding vocabularies describe what happens before that: the pre-convergence architect-imposition step where the vocabulary the community will eventually converge on gets drafted by whoever was there first. The priesthood dynamic is downstream of the founding-vocabulary dynamic.

Grounds

The record rests on cases at different scales of vocabulary formation in technical communities, plus the project's own self-test.

The dynamic surfaces in early-cohort conversations the project drew on. Peter Kaminski named the architect-imposition risk directly: "I really want to make sure that the architects who are building the space don't over-influence the users of the space later with -- essentially poisoning their terminologies with precision, if that makes sense." And on preserving room for alternative interpretations: "I want to make sure that when we say 'this is a node', there is also the possibility for people to say, 'I think it is xyz', or 'to me it is an xyz', etc. Node is the architectural name, but that doesn't make it canonical in other persona types / contexts."

Victoria Gracia surfaced the dynamic from the dissenting-participant position in her note A Rose is a Rose is a Rose, responding to taxonomic predicate use in this project's vocabulary: "In Christopher's taxonomy, an Inquiry is a document type. But a question doesn't do something (function) and doesn't look like something (mode). A question organizes by absence... In my own vault, questions are not a type of note." The dissent is not about whether Inquiry is a reasonable type -- it is about the position of the participant who arrives after the term is already structured into the convention. Her statement "I'm not proposing that [the group] adopt my frameworks" is the same position from the opposite side: refusing to offer an alternative that would land as a competing authority rather than as a genuine proposal.

Christopher Allen named the risk from the architect-side explicitly in On Roses and Edges: "I don't want to treat this space as my prototype without saying so, and I don't want to project my reasons onto yours." And in Poppies in the Gravel: "Not because the interpretation is wrong. Because it might be the label going on too fast. The contradicts card placed between two objects I haven't opened yet." The architect-side awareness that labels imposed early foreclose distinctions the participants had not yet articulated is part of the record's source material.

The Verifiable Credentials community supplies a standards-body-scale case. The W3C Verifiable Credentials Data Model adopted "subject" as the term for the person a credential is about -- a choice made to gain acceptance across contributing organizations and now shaping how the community can reason about its own architecture. The chosen term foregrounds the issuer-target relation in a way that makes later attempts to reframe the participant role (as a sovereign principal, for instance) structurally harder; even when participants noticed the framing cost, the term had already calcified into the working vocabulary of the standards work, the implementations downstream of it, and the academic literature describing it. The pattern recurs across standards work generally: early term choices made under time pressure, political compromise, or initial-author preference calcify into the community's vocabulary before the broader participant set is positioned to propose alternatives.

The wiki tradition supplies another scale of the same dynamic. A founder seeding a wiki with a terminological frame shapes which distinctions later contributors can easily make and which require swimming against accumulated naming. The wiki-gardener distinction between page-creators (who add but rarely revise) and gardeners (who tend the accumulated vocabulary) names one structural consequence: where the founding vocabulary remains unchallenged because the people who could challenge it are in the role of adding-not-tending, the vocabulary becomes more entrenched with each new addition.

The project's own seed corpus is a current case. The Deep Context vocabulary was chosen primarily by the author of the [[Founding Conversation]]; the question the project poses to itself is whether later participants can reshape that vocabulary without forking. The Convictions [[Vocabulary Diversity Is a Feature]] and [[Terms Become Common Through Unanimity, Not Precedent]] are the project's structural responses to this Observation; their effectiveness is part of what the project's second cycle of contribution would test.

The record's limits are substantive. The claim rests on reconstructed experience of specific communities rather than on a frequency count across comparable founding moments at scale; the direction of the dynamic is what the record supports, not a specific rate at which vocabulary calcifies. Some founding vocabularies may remain genuinely revisable through sustained architect humility and contributor uptake of the invitation to revise -- the Observation does not foreclose that, but the reviewed cases show the revisability requires explicit process, not just good intentions.

What Would Revise It

A documented case where a project's founding vocabulary remained genuinely revisable through the first several cohorts of participants -- where later participants successfully renamed founding terms, split conflated ones, or retired poorly-chosen ones, and the revised vocabulary displaced the original in use -- would revise the claim. The revision would be particularly strong if the case's founding conditions matched the reviewed cases (small initial group, conversation-driven vocabulary selection, no explicit unanimity process).

A demonstrable mechanism for absorbing later-participant proposals at parity with architect-proposals -- for instance, a process where every candidate term is treated as proposal-not-adoption until explicitly agreed, which is what [[Terms Become Common Through Unanimity, Not Precedent]] attempts -- would also revise. A three-state Affirm / No objection / Object process is one candidate mechanism; its effectiveness at mitigating this Observation is part of what the project's second cycle of contribution would test.

The Deep Context practice itself is a partial test. The project's founding vocabulary was chosen primarily by the author of the Founding Conversation; the question the project poses to itself is whether later participants can reshape that vocabulary without forking. If the vocabulary remains revisable through the first several contributor cohorts, the Observation's strength weakens. If it calcifies despite the conventions, the Observation's strength holds and the project's response mechanisms require strengthening.

Sources

Relations