Core Glossary
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 Dogri translation and transliteration
- The doctrine risk tier (Critical/High/Medium/Low)
- Explicitly rejected alternatives, with reasons
- Notes explaining any non-obvious translation choice, including where a term is deliberately distinguished from the nearest Hindi equivalent
Governing principles
- Dogri-specific over Hindi-adjacent — where a fluent Hindi Christian term is available and would be the path of least resistance (सुसमाचार, अनुग्रह), this glossary deliberately records a Dogri-specific alternative instead, so the curriculum serves Dogri as its own target language rather than reading as Hindi with Devanagari respelling.
- Explicit rejection, not silent avoidance — every Critical-risk term records why the tempting alternative is wrong, whether that alternative comes from avatar theology tied to Raghunath Mandir’s Rama devotion or from the Vaishno Devi pilgrimage’s mannat vow economy.
- Confirm against the BSI Dogri Bible — because formal Dogri Bible translation is recent, several entries flag the need to reconcile this Language Package’s provisional renderings against the current published Bible Society of India Dogri Bible before wide deployment.
- 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.
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.