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, theological, and legal risks identified in Culture Analysis and Comparative Theology. Every term entry records:

  • The approved Malay translation and a phonetic pronunciation guide
  • The doctrine risk tier (Critical/High/Medium/Low)
  • Explicitly rejected alternatives, with reasons, including where a term collides with a legally contested word (Allah), an Insider Movement-style alternative (Isa, Al-Masih), or a specific Islamic doctrine (syafaat)
  • Notes explaining any non-obvious translation choice

Governing principles

  1. Established Alkitab usage over invention or Islamic-vocabulary substitution — where the Alkitab already has a settled rendering (Allah, Yesus, Kristus, Roh Kudus), this glossary follows it rather than proposing an alternative or adopting an Insider Movement-style Islamic-vocabulary substitute.
  2. Explicit naming, not silent avoidance — every Critical-risk term records the specific Islamic doctrine, legal controversy, or civilizational echo it stands in tension with (see alternatives_rejected and notes), so a translator or reviewer understands why softening the term would misrepresent the source text or concede real ground.
  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 legal/political and mainstream-Sunni-doctrinal risks that distinguish this Language Package from every other Language Package in this pipeline.