Nehemiah → Bengali Language Package: Executive Summary

Why it matters: Nehemiah’s core passage (8:1-12) makes the Bible-translation task itself the subject of Scripture — Ezra’s team reads the Law “distinctly” (מְפֹרָשׁ) so a people whose working language had shifted could actually understand it. This curriculum sits at an unusually contested point in the Bengali religious-vocabulary landscape: it must render prayer, priesthood, covenant, joy, fear of God, and ritual purification into a Bengali script and vocabulary shared by Hindu-majority West Bengal and Muslim-majority Bangladesh, without borrowing either tradition’s competing theological freight.

---

Key findings

• 12 doctrines identified across all 13 chapters (not just the core passage): 1 Critical (The Word of God Read, Understood, and Obeyed), 9 High, 2 Medium, 0 Low. 10 of 12 doctrines (83%) require human theologian review; the remaining 2 require native-speaker review. Zero doctrines are automated-only — a structural feature of the Bengali landscape, not a curriculum-specific weakness.
• 80 terms are seeded into translation_memory.json for this curriculum: 14 copied exactly from the Romans baseline (“inherited”), 66 new to Nehemiah. Of these, 25 terms carry Critical or High risk and require mandatory theologian review (4 Critical, 21 High) — roughly one in three of all seeded terms.
• আনন্দ (joy) is the single highest-risk word in the whole package. It is unavoidable as Bengali’s word for spiritual joy, but is also the operative term of Bengali Vedantic (সৎ-চিৎ-আনন্দ) and Vaishnava bhakti (ব্রহ্মানন্দ) bliss-theology. No substitute exists; risk is managed only by the standing rule that it must never appear unanchored — always সদাপ্রভুতে আনন্দ.
• Three genuine lexical gaps required constructed Bengali compounds with no independent circulation outside this curriculum: নিয়মপ্রেম (chesed, covenant loyalty), নিয়ম-অঙ্গীকার (amanah, sealed pledge), and সুস্পষ্টভাবে অর্থ বুঝিয়ে (mephorash, “distinctly/with interpretation” — the term that names this pipeline’s own methodology).
• The OT covenant name সদাপ্রভু must never be conflated with প্রভু, the baseline’s NT Lordship-of-Christ confession term — a distinction with no equivalent complexity in the Romans package alone, since Romans never has to render YHWH as a proper name.

---

Risks

• Ritual-vocabulary collision (High): পবিত্র করা (ceremonial purification, ch.12) sits one translator’s-note away from being read as Hindu shuddhi; যাজক (priest) sits one word-choice away from পুরোহিত’s Brahmin-officiant associations; প্রার্থনা sits between পূজা (Hindu) and নামাজ (Islamic) ritual categories on either side.
• Communal-boundary language (High): পৃথক করা (“separate,” ch.13) and শত্রু (“enemy,” chs. 4, 6) are the two terms most likely to be misread through real, present-day Hindu-Muslim or caste-boundary lenses in Bangladesh and West Bengal — the doctrine analysis flags this as the curriculum’s most socially sensitive residual risk.
• Anthropomorphic idiom risk (High): “The good hand of my God” (2:8, 18; 5:19) risks being absorbed into Hindu iconographic conventions of deities with literal multiple hands unless a figurative-language note accompanies it every time.
• Fear-vocabulary conflation (High): Bengali ভয় must carry three distinct senses (ordinary fear, dread of enemies, reverential fear of God) that Hebrew keeps separate (pachad vs. yirah); collapsing them undermines the ethics of Nehemiah 5 and risks importing Islamic taqwa’s legal-submission frame uninvited.

---

Opportunities

• Self-referential teaching hook: Nehemiah 8:8’s מְפֹרָשׁ names exactly what this translation pipeline does — Phase 2 lesson material can make this explicit, turning a translation-methodology risk into a distinctive teaching strength unique to this curriculum.
• Reinforced cross-curriculum consistency: Reusing সামর্থ্য (never শক্তি) for both Romans’ “power of God” and Nehemiah’s “joy of the LORD is your strength” lets teachers draw a direct, doctrinally safe intertextual link between the two curricula.
• Baseline term reuse reduces net-new risk surface: 14 of 80 terms needed zero new analysis, having already been fully vetted in the Romans package (ঈশ্বর, পবিত্র, পাপ, নিয়ম, ব্যবস্থা, ধন্যবাদ, মণ্ডলী, ভাববাদী, দায়ূদ, ইস্রায়েল, অনুগ্রহ, ঈশ্বরের সামর্থ্য, পরজাতি, ঈশ্বরের পরিচালনা).

---

Recommended actions

1. Route all 25 Critical/High terms and all 10 Critical/High doctrines through mandatory human theologian review in Phase 2 Step 17, per the escalation rules in 12_ai_translation_requirements.md.
2. Enforce the six standing translator notes (qahal/মণ্ডলী typology, hand-of-God figurative language, purification-rite distinction, separation-not-exclusion framing, ভয়/ঈশ্বরভয় disambiguation, আনন্দ anchoring) as reusable templates rather than redrafting per occurrence, to guarantee consistency across all 13 chapters.
3. Treat Nehemiah 8:1-12 segments as maximal-priority review items in every batch — this is the curriculum’s sole Critical doctrine and its theological anchor.
4. Native-speaker-review, as a single consistency pass, the eight named city gates (chs. 3, 12) and the usury/Sabbath framing (chs. 5, 10, 13) before Phase 2 begins, since these carry Low-to-Medium doctrinal risk but High consistency risk if handled inconsistently across chapters.

Full detail: analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, analysis/11_doctrine_analysis.md, analysis/04_comparative_theology.md, analysis/06_linguistic_gap_analysis.md, assets/translation_memory.json, assets/bible_term_registry.json, assets/doctrine_risk_registry.json.