Vocabulary Diversity Is a Feature

When contributors from different naming traditions meet in a shared graph, the differences in their predicates, their classification names, and their typed relations are not noise to normalize. They are design decisions each tradition made about what distinctions matter. The project holds that vocabulary diversity across contributors is a feature of the graph and a property the graph is committed to preserving, not a friction to resolve.

Why It Is Held

Each naming tradition encodes decisions that would be destroyed by flattening. Choosing estate over workspace encodes stewardship and generational continuity; choosing gardener over content curator encodes a living-systems relation to knowledge; choosing critiques:: over challenges:: encodes a particular stance toward disagreement. The names are not cosmetic labels on interchangeable concepts — the names are the concepts, and the web of associations each name activates is the context through which every subsequent inference runs. Collapsing multiple naming traditions into a single shared vocabulary erases the distinctions that made each tradition legible to the communities it came from.

Convergence pressure carries costs that are not evenly distributed. When a community converges on a shared vocabulary, the participants who helped create it acquire natural authority, and newcomers face a choice between learning an ontology they did not shape or creating a parallel community with its own vocabulary. Standardized language stops evolving with the understanding of practitioners doing the work. Flattening three distinct predicates into one merged term produces an impoverished vocabulary less precise than any of the originals. The alternative — keeping each vocabulary intact and translating between them — preserves what each tradition built.

The stance is what makes author-declared edges load-bearing. When one contributor writes critiques::[[X]] and another writes challenges::[[X]], both edges land in the graph as distinct claims. An agent reading across them translates rather than normalizing, and the contributors remain participants in their own naming rather than subjects of the system's extraction. Without the stance, author-declared edges drift toward agent-normalized edges at read time, and the graph silently converges on whichever vocabulary the normalizing agent prefers.

What It Asks

Authors translate between vocabularies rather than normalize them. When a contributor brings naming that differs from existing conventions, the first response is to understand what distinction the new naming encodes — not to route it back to an existing predicate.

New predicates join the local vocabulary rather than being turned back at the door. A predicate unique to one contributor's tradition is added to CONVENTIONS.md and used. A predicate that overlaps with existing ones is kept as distinct whenever the contributor's distinction is load-bearing, with a glossary entry documenting the overlap and the difference.

Reviews flag convergence pressure as a drift signal. When a reviewer suggests "use the standard predicate" without asking what distinction the original carried, the suggestion is itself a sign that the reviewer is treating vocabulary variation as error rather than as preserved distinction. The review surface for vocabulary is translation, not normalization.

Cross-system collaboration adds translation layers rather than shared vocabularies. When the graph interoperates with another graph whose predicates differ, the response is a gloss document or a typed cross-reference — not schema alignment. Mutual intelligibility through translation is the target; a single shared ontology is not.

Drift Recognition

The stance has drifted when the project starts treating contributor vocabularies as problems to resolve rather than as distinctions to preserve. Convergence pressure appears in reviews without being flagged; new predicates stop being added to the local vocabulary because authors default to existing terms; the CONVENTIONS.md vocabulary list stops growing by accretion.

A reader scanning the graph after drift would see convergence toward a single vocabulary — redundant predicates merged without preserving the merged distinction, contributor-specific terms replaced silently during review, glossary entries for the project's local dialect disappearing from the vocabulary section rather than being kept as translation anchors. A cross-system interop attempt that reaches for a shared schema rather than a translation layer is a louder signal of the same drift. None of these require a structural Requirement to fail; they accumulate as cultural erosion.

Sources

Relations