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 Gujarati translation and transliteration
• The doctrine risk tier (Critical/High/Medium/Low)
• Explicitly rejected alternatives, with reasons — distinctively, Critical terms in this Language Package typically reject one Hindu-tradition alternative AND one Jain-tradition alternative, not just one
• Notes explaining any non-obvious translation choice

Governing principles

1. Established usage over invention — where existing Gujarati Bible translation already has a settled rendering (પરમેશ્વર, ઈસુ, પ્રભુ, ખ્રિસ્ત), this glossary follows it rather than proposing an alternative.
2. Explicit dual rejection, not silent avoidance — every Critical-risk term records why both the Hindu-tradition word and the Jain-tradition word are wrong (see alternatives_rejected), so a translator or reviewer understands the reasoning for both risk axes rather than just the more commonly-discussed Hindu one.
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.