Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

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 Odia translation and transliteration
  • The doctrine risk tier (Critical/High/Medium/Low)
  • Explicitly rejected alternatives, with reasons — several of which are specific Jagannath-tradition words and ritual concepts (ଠାକୁର, ଅବତାର, ଦେଉଳ) rather than generic Hindu-tradition vocabulary
  • Notes explaining any non-obvious translation choice

Governing principles

  1. Established usage over invention — where existing Odia Bible translation already has a settled rendering (ପରମେଶ୍ୱର, ଯୀଶୁ, ପ୍ରଭୁ, ପରିତ୍ରାଣ, ନିୟମ), this glossary follows it rather than proposing an alternative.
  2. Explicit, institution-specific rejection, not generic avoidance — every Critical-risk term records why a rejected alternative is wrong, and where relevant, names the specific Jagannath-tradition ritual or practice (Nabakalebara, seba, Rath Yatra) that makes the rejected term risky, rather than gesturing at “Hindu syncretism” generically.
  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 Jagannath-specific reasoning unique to this Language Package.