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 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 Modern Greek translation and a transliteration (included for every term in this Language Package, since precise pronunciation and spelling both matter for a script this curriculum’s broader pipeline otherwise renders only in Latin-script languages)
  • The doctrine risk tier (Critical/High/Medium/Low)
  • Explicitly rejected readings, specific to either secular semantic bleaching or patristic/liturgical over-accretion as relevant to that term
  • Notes explaining the direction and nature of the term’s two-thousand-year semantic drift from Paul’s own usage

Governing principles

  1. The Koine text as the anchor — where Modern Greek has drifted, this glossary anchors back to the NT’s own first-century usage rather than to either later patristic theological development or later secular usage, treating both as things to actively correct for rather than assume.
  2. Explicit bidirectional disambiguation, not silent avoidance — because Greek’s risk runs in two opposite directions (accretion and bleaching) depending on the term, every Critical-risk term’s notes specify which direction applies and why, rather than using a single boilerplate warning.
  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.

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 and names its direction of semantic drift, the doctrine registry explains why that vocabulary matters.