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 Konkani 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 relevant, how the Romi Konkani Catholic tradition renders the same concept differently

Governing principles

1. Devanagari, Hindu-context-facing register over Romi Konkani reuse — this glossary makes deliberate, independent choices suited to a Devanagari-literate, often Hindu-background audience, rather than importing the Roman-script Catholic tradition’s already-settled but differently-audienced vocabulary (see Translation Landscape).
2. Explicit rejection, not silent avoidance — every Critical-risk term records why the obvious Hindu-tradition word is wrong (see alternatives_rejected), so a translator or reviewer understands the reasoning rather than just following a rule.
3. Honest handling of unavoidably shared terms — where a term (देव) cannot be cleanly disambiguated by word choice alone, the glossary says so explicitly and specifies a mitigation practice (contextual exclusivity-marking) rather than pretending a clean substitute exists.
4. 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.