Log in

or use your email

Search the Library

Keyword search across Doctrine Analysis, Core Glossary, Comparative Theology, and Regional Analysis. Mention a language name for the best results — e.g. "remnant burmese" or "what glossary terms conflict for burmese."

Type at least 2 characters to search.

Welcome to the Library

What is this?

The Library publishes the doctrine-aware translation research behind tri-bible.ai, one language and book at a time — free to read and reuse.

How to navigate

Pick a language, then a book, in the sidebar. Each book has a Doctrine Analysis, a Core Glossary, and, for the language as a whole, a Comparative Theology and Regional Analysis. Use the search icon in the top nav to jump straight to a term or doctrine instead of browsing.

What the risk tiers mean

Every doctrine and glossary term is labeled with how easily it could be misread or mistranslated in that language's own cultural and religious context:

Critical
A wrong word choice here risks distorting core theology — always reviewed by a theologian before use.
High
A real, well-documented risk of confusion with another tradition or belief system — needs theologian review.
Medium
Worth a native speaker's second look, but not likely to distort the core meaning.
Low
Minor wording nuance — low risk of confusion either way.

Work with us

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

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Download Translation Skill

Executive Summary

Jeremiah — Executive Summary (Hmong Language Package, Baseline v1.0)

Why it matters

The Hmong Jeremiah Language Package delivers the first doctrinally-supervised translation-requirements framework for Jeremiah in Hmong, anchored to Jeremiah 31:31-34 (The New Covenant) — the single most theologically load-bearing passage in the Old Testament for the New Covenant doctrine that Romans, Luke, and Hebrews all presuppose. This package extends, and never contradicts, the existing Hmong Romans Language Package baseline, giving the pipeline its first Old Testament / Hebrew-source-language Language Package and its first sustained engagement with Hmong Traditional Religion’s shamanic (txiv neeb), ancestor-veneration, and fate (hmoov) frameworks across an entire prophetic book rather than a single epistle.

Key findings

  • Full-book coverage complete: all 52 chapters of Jeremiah reviewed; every chapter either contributed new terminology/doctrinal load or is explicitly logged “reviewed — no new load” (analysis/11_doctrine_analysis.md Part B) — no chapter silently skipped.
  • 7 assigned doctrines, all Critical or High risk, zero Medium/Low: The New Covenant, Judgment for Covenant Unfaithfulness and Idolatry, False Prophets versus True Prophecy, and God’s Sovereign Plans for His People are Critical; The Weeping Prophet and the Cost of Faithful Ministry, Individual Responsibility, and Hope of Restoration after Exile are High. All 7 require mandatory human theologian review before publication with no automated-review bypass.
  • Translation memory contains ~30 inherited Romans terms reused verbatim plus ~48 newly-surfaced Jeremiah terms, of which 13 are Critical-risk and 18 are High-risk (31 Critical+High terms total), plus 2 additional Medium-High escalated terms (cup of wrath; wash-heart-from-evil) — the highest single-book term-risk density yet produced in this pipeline.
  • Three unresolved [TRANSLATOR REVIEW NEEDED] flags remain by design and must not be silently closed: (1) the pagan-king-as-”servant” instrument-of-judgment title (Jer 25:9, 27:6); (2) the untranslatable massa “burden/oracle” Hebrew pun (Jer 23:33-40); (3) the Baal/“husband” wordplay at Jer 31:32, which must be footnoted, never pun-reproduced.
  • Three new Hmong-Traditional-Religion collision points not present in the Romans baseline were identified: the shamanic diviner (txiv neeb) as a named living counter-authority to true prophecy; the kwv txhiaj funeral-lament tradition as both a genuine bridge and a ritual-function risk for the Weeping Prophet doctrine; and clan-based intergenerational liability as a direct structural challenge to Individual Responsibility.

Risks

  • Highest risk: kev cog lus (covenant) heard as an ordinary revocable, bilateral Hmong betrothal/clan-alliance pact rather than God’s unilaterally-sustained covenant — this directly undermines the core passage if not paired with explicit teaching every time.
  • Systemic risk: the hmoov (impersonal fate) collision, already Critical in the Romans baseline, now recurs across three additional Jeremiah-specific sites simultaneously (potter/clay sovereignty, “plans of God” at 29:11, and “restore the fortunes”), raising the aggregate probability that at least one occurrence slips through without the mandatory disambiguating framing.
  • Syncretism risk: any drift toward the Hmong culture-hero legend Yaj Saub when rendering “prophet,” or any neutral presentation of shamanic divination vocabulary, would collapse the False-Prophets-versus-True-Prophecy doctrine’s entire discernment framework.
  • Ritual-function bleed risk: Jeremiah’s lament vocabulary (kev quaj ntsuag) carries a genuine cultural bridge to Hmong sung funeral-lament (kwv txhiaj) that is entangled with ancestor-soul-guidance ritual — without a disambiguating note at every occurrence (not just first use), the Weeping Prophet doctrine risks dilution into generic bereavement.
  • Prosperity-gospel drift risk: Jeremiah 29:11 (“plans for welfare… a future and a hope”) is a documented high-risk site for detachment from its actual seventy-years-of-exile context and reframing as a general prosperity promise.

Opportunities

  • Strong positive bridges exist and should be leveraged, not merely fenced: Hmong debt-redemption custom (kinsman-redemption, Jer 32’s field purchase), clan-adoption and lineage-inheritance custom, agricultural yoke/harvest imagery, and — with appropriate fencing — the kwv txhiaj lament tradition’s emotional register all give this curriculum unusually rich, culturally resonant teaching material relative to Romans.
  • Cross-Testament doctrinal bridges are strong and largely pre-verified: tus Ceg Ncaj Ncees (Righteous Branch) and Tus Tswv Yog Peb Txoj Kev Ncaj Ncees (LORD Our Righteousness) reuse the exact Romans-fixed ncaj ncees root, giving learners a direct lexical bridge from Jeremiah’s messianic hope into the Romans Justification-by-Faith doctrine.
  • Individual Responsibility (Jer 31:29-30) offers a rare apologetic opening: its logic parallels Qur’anic individual-accountability language and karma-based frameworks more closely than most doctrines in this pipeline, useful for interfaith-aware discipleship contexts even as it must correct the Hmong clan-liability framework.
  1. Route all Phase 2 generation touching Doctrines 1, 2, 4, or 5 (Critical) and 3, 6, or 7 (High) to mandatory human theologian review before publication — no exceptions, per assets/doctrine_risk_registry.json.
  2. Enforce the assets/translation_memory.json qualifier rules structurally (never optionally) at every occurrence, with special attention to the three simultaneous hmoov-collision sites (§ “Systemic risk” above).
  3. Escalate the two standing unresolved terms (Nebuchadnezzar-as-servant; the massa pun) to human theologian + native speaker review before any Phase 2 content touches Jer 23, 25, or 27.
  4. Require the kev quaj ntsuag disambiguating note at every one of its seven chapter-occurrences (8, 9, 13, 14, 16, 20, 31), not only on first introduction, per the Weeping Prophet doctrine’s mandatory preservation rule.
  5. Carry forward the Yaj Saub permanent-forbidden-substitution rule with heightened vigilance specifically around messianic Branch language (Jer 23:5, 33:15), where proximity risk is highest even when the correct term is used.

Library content is free and openly licensed under CC BY-NC-SA 4.0 — share and adapt it for non-commercial use, with attribution to tri-bible.ai.

Give feedback

How would you rate this page?

0 / 500 words