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 and linguistic realities identified in Culture Analysis and Linguistic Gap Analysis. Every term entry records:

  • The approved Hebrew translation and transliteration
  • The doctrine risk tier (Critical/High/Medium/Low)
  • Explicitly rejected alternatives, with reasons — including, distinctively for Hebrew, Modern Hebrew forms that have drifted from the Biblical Hebrew sense
  • Notes explaining any non-obvious translation choice

Governing principles

  1. Biblical Hebrew precision over Modern Hebrew convenience — where a word has drifted (tzedakah, kiddush, hashgachah), this glossary restores the Biblical Hebrew theological sense rather than defaulting to the more familiar contemporary usage.
  2. Engage the existing Jewish framework, don’t silently override it — every Critical-risk term records the specific Tanakh-based or Rabbinic content a reader will already supply, so a translator or reviewer understands what must be actively addressed rather than assumed away.
  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, even where textually well-grounded, still requires deliberate theological framing for a Hebrew-speaking reader.