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 Maithili translation and transliteration
  • The doctrine risk tier (Critical/High/Medium/Low)
  • Explicitly rejected alternatives, with reasons
  • Notes explaining any non-obvious translation choice

Governing principles

  1. Native Maithili grammar over Hindi transplant — even where the underlying Sanskrit tatsama vocabulary is shared with Hindi, this glossary renders phrases using Maithili’s own postpositions, verb infinitives, and honorific verb agreement, rather than a word-for-word Hindi substitution.
  2. Explicit rejection, not silent avoidance — every Critical-risk term records why the obvious Vaishnava/Shaiva-tradition word, or the tempting Sita-exemplar comparison, is wrong (see alternatives_rejected), so a translator or reviewer understands the reasoning rather than just following a rule.
  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.