- conforms_to::[[Conviction Form Contract]]
- in_domain::[[Deep Context Architecture]]
- authored_by::[[Deep Context Community]]
- has_lifecycle::[[Seed Stage]]
- has_curation::[[Working Draft]]
Translation Over Convergence
When vocabularies meet — across contributors in one graph, or across graphs that interoperate — the project's response is translation rather than convergence. Both edges land in the graph as distinct claims; a facilitating agent interprets between the vocabularies rather than normalizing them into a shared ontology.
Why It Is Held
Convergence and translation are two different answers to the same question — whose vocabulary wins? — and the costs of each are not equivalent. Convergence answers by flattening: the normalized vocabulary wins, contributor distinctions dissolve into the merged terms, and the participants who shaped the shared ontology acquire natural authority over everyone who arrives later. Translation answers by keeping each vocabulary intact: critiques::[[X]] and challenges::[[X]] stay as distinct predicates, and the agent reading across them interprets without collapsing.
The three costs of convergence are structural properties of the move, not contingent failure modes. Consensus creates priesthoods — newcomers face a choice between learning an ontology they did not shape or going elsewhere to form a parallel community with its own language. Standardized language becomes dogma — a vocabulary fixed by authority stops evolving with the understanding of practitioners doing the work. Flattening destroys encoded meaning — merging three distinct predicates that each preserved a different distinction produces a term less precise than any of the originals. Translation avoids all three by leaving the distinctions in place and carrying the interpretive work at the reading layer instead.
Translation is operationally viable because agents that read author-declared edges can already see the structure the predicates encode. When critiques:: and challenges:: both appear, an agent does not need to pick one — it can traverse both and present the distinction to a reader who may care about it. The cost of keeping both is local (one more predicate in the vocabulary, one glossary entry naming the distinction); the cost of flattening them is global (every node using either loses its original distinction). The asymmetry makes translation the cheap move, not the disciplined one.
What It Asks
Agents working across vocabularies act as translators, not extractors. When an agent mediates between a graph and a human contributor, the agent's role is to read what the author declared and interpret it — not to infer edges the author did not declare or rewrite edges the author did.
Reviews flag normalization attempts. When a reviewer proposes rewriting a predicate to "the standard term," or merging predicates whose distinctions are load-bearing to the contributors who use them, the suggestion is treated as a vocabulary-arbitration move that needs authorization rather than a hygiene improvement.
Cross-system interop adds translation layers rather than shared vocabularies. When the graph connects to another graph whose predicates differ, the response is a translation document — a gloss naming the correspondence and the distinction each side preserved — rather than schema alignment. The connected graphs stay sovereign; the translation layer between them is what makes mutual intelligibility possible.
New predicates that arrive with new contributors are treated as translation candidates, not hygiene problems. A predicate unique to the contributor's tradition enters the local vocabulary and sits alongside existing predicates that overlap in meaning; a glossary entry documents the distinction the new predicate preserves.
Drift Recognition
The stance has drifted when agent workflows start normalizing predicates at read time. An agent summarizing the graph that silently maps critiques:: and challenges:: to a canonical disagrees_with:: has converged; an agent that presents both and names the distinction has translated. The change is usually invisible in any single output but accumulates across summarization passes until the graph a reader reconstructs from agent summaries is simpler than the graph the contributors actually wrote.
Cross-system handoffs that reach for a shared language rather than a translation layer are a louder signal. When two graphs propose to interoperate by agreeing on a shared ontology rather than by documenting the translation between their respective ontologies, flattening has already begun; the agreement's scope is the measure of what gets erased.
A review cadence in which normalization suggestions go unchallenged is subtler drift. The reviewer's preference for the canonical predicate is not flagged as vocabulary arbitration; the contributor's distinct predicate gets rewritten silently; the local vocabulary shrinks without any explicit decision to shrink it.
Sources
- Allen, Christopher. "Wikilinks and Named Edges," 2026 — the "Why vocabulary diversity matters across systems" and "Naming conventions across systems" sections develop the translation-over-convergence argument and supply the three-cost analysis this Conviction rests on.
Relations
-
grounded_in::[[Vocabulary Diversity Is a Feature]]
- The substrate Conviction. This Conviction specializes the diversity stance with a concrete operational rule for what happens when vocabularies meet. Without the diversity Conviction, the translation rule has no normative basis — translation is what the project does because vocabulary diversity is a feature it is committed to preserving.
-
informed_by::[[Consensus Creates Priesthoods]]
- The Observation supplies the empirical grounding for the first of the three convergence costs this Conviction's Why rests on — convergence creates natural-authority asymmetries that alienate newcomers. Ghost link until the Observation is seeded in the same commit group.
-
informed_by::[[Wikilinks and Named Edges Gist (Christopher Allen, 2026)]]
- The gist's "Why vocabulary diversity matters across systems" section supplies the three-cost analysis and the mutual-intelligibility-through-translation alternative this Conviction's Why compresses.
-
informed_by::[[Creating Shared Language and Shared Artifacts Post (Christopher Allen, 2009)]]
- The 2009 post's banker-cryptographer-layperson framing of how different communities legitimately use the same word differently is upstream of this Conviction's operational commitment to keep both
critiques::andchallenges::intact rather than normalizing them.
- The 2009 post's banker-cryptographer-layperson framing of how different communities legitimately use the same word differently is upstream of this Conviction's operational commitment to keep both
-
contrasts_with::[[Adopt Predicate Atomicity]]
- Both are vocabulary-discipline commitments operating at different scopes. Adopt Predicate Atomicity governs within a vocabulary — a predicate must answer one question, and overloaded predicates are split. Translation Over Convergence governs across vocabularies — when two vocabularies meet, both stay intact and translation bridges them. The two commitments compose: each vocabulary keeps its own single-axis predicates, and translation handles the cross-vocabulary case.
-
informs::[[source_voice -- whose thinking is captured when different from the author]]
- informs::[[responds_to -- direct reply creating a conversation thread]]
- informs::[[assists_by -- facilitation by agent or person]]
- Three Predicates adopted from an adjacent plural-contributor corpus's practice. Each preserves a distinction the home corpus surfaced — authorship split (source_voice), conversation threading (responds_to), facilitation-vs-authorship (assists_by). Adopting them here rather than folding them into existing local predicates is translation-not-convergence at the predicate layer.