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.

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

Executive Summary: Ezra

English → Arabic Language Package | Phase 1 Complete

Curriculum: Ezra 1–10 Core passage: Ezra 1:1-11 Destination language: Arabic (Modern Standard Arabic, Christian register, Van Dyck/NAV tradition)


Why it matters

Ezra is a full-book Old Testament translation project into a language whose dominant living tradition is Islam — a first for this Language Package, which was built and proven on Romans (New Testament, Pauline argument). Ezra introduces an entirely new risk class the Romans baseline never had to solve: lexical collision with Islamic sacred geography and ritual vocabulary (بيت الله = the Kaaba; قربان/أضحية = Eid sacrifice; كاهن = pre-Islamic diviner), layered on top of the familiar Critical/High doctrinal-confusion risks the baseline already manages (God, Lordship, covenant, law). Get the Temple phrase wrong once and every reader’s mental map shifts to Mecca — this is the single highest-frequency, highest-severity risk in the entire book (30+ occurrences).

Key findings

  • 69 glossary terms now govern Ezra translation: 13 inherited exactly from the Romans baseline (God, LORD, Holy, Law, Covenant, Israel, Gentiles, Prophet, Prophecy, David, Seed of David, Thanksgiving, Kingdom of God) and 56 new Ezra-specific terms.
  • 30 of the 69 terms (8 Critical + 22 High) require mandatory human theologian review before Phase 2 output is accepted — a materially higher Critical/High density than Romans, driven by Ezra’s OT ritual, genealogical, and administrative vocabulary.
  • 20 doctrines are tracked in the doctrine risk registry: 5 Critical, 9 High, 5 Medium, 1 Low14 total require human theologian review, 5 require native speaker review, 1 is automated-only.
  • The single most dangerous phrase in the book is “house of the LORD/house of God” — it must render as بيت الرب / الهيكل and must never become بيت الله (the Kaaba’s exclusive Islamic designation), across every one of its 30+ occurrences (chs. 1, 3–8).
  • Cyrus (كورش) carries a Critical background risk independent of vocabulary: popular Islamic exegesis identifies him with the Qur’anic Dhul-Qarnayn (Q18:83-98), a righteous monotheist — directly contradicting the text’s own point (1:7) that Cyrus remained polytheist while God sovereignly used him.
  • Genuine positive bridges exist and should be actively used, not avoided: يد الله (Q48:10) for “the hand of the LORD,” رجس (Q5:90) for idol-impurity, and شكر/صوم for thanksgiving/fasting all offer real common ground when paired with the doctrine’s distinguishing content.

Risks

  • Critical (5 doctrines / 8 terms): Sovereignty over Pagan Nations, Restoration of Temple Worship, Confession and Corporate Repentance, Separation from Syncretism, Covenant Identity and the Holy Seed — plus the standalone Critical terms كورش, بيت الرب/الهيكل, الناموس (OT extension), اعتراف, النسل المقدَّس.
  • High (9 doctrines / 22 terms): includes the acute tribal-identity risk around “holy seed” (النسل المقدَّس) in a culture with strong qabila lineage-purity and sharif/sayyid descent concepts — mishandling this term risks reinforcing exactly the blood-purity thinking the doctrine must reject.
  • Structural risk: Ezra’s two Aramaic blocks (4:8–6:18; 7:12–26) are administrative/legal register, not devotional register — translators must not apply the baseline’s Aramaic-intimacy precedent (Abba) here.
  • Social/political risk: أورشليم vs. القدس and إسرائيل’s contemporary political loading both recur throughout the book’s post-exilic setting and require the same deliberate pastoral framing the baseline established for Romans 9–11.

Opportunities

  • Ezra’s confession-and-repentance narrative (chs. 9–10) is a strong teaching bridge into corporate (not merely individual) spirituality — a category underused in individualized-tawbah-default piety, and a genuine complement to the Romans package’s assurance-of-salvation material.
  • The يد الله and شكر/صوم bridges allow constructive, respectful engagement with shared vocabulary rather than avoidance — consistent with the baseline’s own precedent (shukr, qawiyy) of using genuine common ground without diluting doctrine.
  • No Ezra-specific term required inventing new Arabic vocabulary; every genuine lexical gap (hesed, “stirred up the spirit,” corporate confession, covenant-return) is resolved with an established word or footnoted compound phrase, keeping the whole package inside existing Arabic Christian theological literature.
  1. Lock assets/translation_memory.json (Ezra) and assets/bible_term_registry.json (Ezra) as the enforced Phase 2 databases; no segment translation proceeds without loading both, per 12_ai_translation_requirements.md.
  2. Route all 8 Critical-term and 22 High-term occurrences, and all 14 theologian-tier doctrines, through human theologian review before acceptance — no automated approval path for these.
  3. Apply the absolute بيت الله prohibition as a hard validation gate (not a soft flag) given its 30+ occurrence frequency and severity.
  4. Brief theologian reviewers specifically on the Cyrus/Dhul-Qarnayn and holy-seed/tribal-purity risks before Phase 2 begins — these require background knowledge the term-level flag alone won’t convey.
  5. Carry the Van Dyck-primary / NAV-secondary YouVersion citation convention (EZR.{chapter}.{verse}, version IDs 13/101) forward unchanged from the language-wide 05_translation_landscape.md.

Cross-reference: assets/translation_memory.json, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, analysis/11_doctrine_analysis.md, analysis/12_ai_translation_requirements.md.

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