Core Glossary

translation_memory.json is the enforced glossary for every Phase 2 translation in this curriculum. This document summarizes its shape and the principles behind it; see the Glossary Risk Groups for the full per-term entries.

Composition

The glossary currently holds 47 terms spanning all four risk tiers, drawn from the doctrines identified in Doctrine Analysis and grounded in the cultural risks identified in Culture Analysis. Every term entry records:

• The approved Kannada translation and transliteration, preferring established Dravidian-root Kannada vocabulary (ನಂಬಿಕೆ, ತಂದೆ, ಒಡಂಬಡಿಕೆ, ಅನ್ಯೋನ್ಯತೆ) where it already exists in Kannada Christian usage
• The doctrine risk tier (Critical/High/Medium/Low)
• Explicitly rejected alternatives, with reasons — including, distinctively in this Language Package, terms rejected not because they mean the wrong thing but because they route toward the Lingayat Aikya-merger trajectory
• Notes explaining any non-obvious translation choice

Governing principles

1. Established usage over invention — where existing Kannada Bible translation already has a settled rendering (ದೇವರು, ಯೇಸು, ಕರ್ತ, ಕ್ರಿಸ್ತ, ಸುವಾರ್ತೆ), this glossary follows it rather than proposing an alternative.
2. Explicit rejection of both words and trajectories — every Critical-risk term records why a rejected alternative is wrong, whether that is a simple false-friend meaning (ಅವತಾರ for incarnation) or a subtler destination mismatch (ಐಕ್ಯ for salvation, which sounds like deliverance but ends in merger).
3. Version-controlled and append-only in Phase 2 — if a new term is discovered during document translation, it is added to translation memory and the version number incremented, never silently improvised per-document (see the AI Translation Requirements’ Translation Memory Load and Enforcement Instructions).

Relationship to the Doctrine Risk Registry

Every glossary term’s doctrine field links back to an entry in doctrine_risk_registry.json, so a term’s risk tier is always traceable to the specific doctrine it protects — the glossary enforces vocabulary, the doctrine registry explains why that vocabulary matters, including the trajectory risk unique to this Language Package.