Nahum → Bengali: Phase 1 Executive Summary

Format: Smart Brevity

Why it matters

Nahum 1:1–8 anchors a curriculum on God’s justice, sovereignty, and comfort — but Nahum’s Hebrew vocabulary is the most syncretism-exposed material this Bengali Language Package has yet processed. Its dense divine-wrath and theophanic-power imagery (storm, fire, earthquake, flood) sits directly on top of Bengal’s own Shakta-Hindu devotional vocabulary for Kali and Durga, and its central refuge term is one phonetic step from Bengal’s most venerated goddess name. Getting Phase 1 terminology decisions right here is what stands between Nahum reading as covenant-faithful justice against real historical cruelty, and Nahum being unconsciously absorbed into an existing fierce-goddess devotional frame.

Key findings

• Full-book coverage complete. All three chapters of Nahum (1:1–15; 2:1–13; 3:1–19) have been analyzed; every section not separately tabulated (2:3–8; 3:8–15) is explicitly confirmed reviewed and found to introduce no additional doctrine or term.
• New covenant-name requirement. יהוה must render as সদাপ্রভু, never as the baseline’s প্রভু — protecting the baseline’s own reserved NT Christological usage while giving Nahum’s OT covenant God his own established Bengali term.
• Highest-severity single ambiguity: refuge vocabulary. מָעוֹז (“stronghold,” Nahum 1:7) must render as আশ্রয়, never দুর্গ, because দুর্গ sits etymologically adjacent to দুর্গা (Durga) — a collision made worse by the fierce-power imagery surrounding it in the same chapter.
• A live pastoral risk unique to this book: Nahum’s judgment oracle against Nineveh can read as contradicting the Qur’an’s own account of Nineveh’s repentance under Yunus (Surah Yunus 10:98) unless study materials explicitly note the century-long gap and Nineveh’s relapse — a requirement not present in the Romans baseline.
• 43 total terms now govern Nahum translation: 6 inherited baseline Romans terms (reused or retained as protective contrast entries) plus 37 new Nahum-specific terms.

Risks

• 16 Nahum-specific Critical/High risk terms require mandatory human theologian review at every occurrence (3 Critical: YHWH/সদাপ্রভু, God/ঈশ্বর as reused, will-not-acquit; 13 High: LORD of hosts, jealous God, avenging, wrath, indignation, fierce anger, slow to anger, great in power, stronghold/refuge, make a complete end, bearer of good news, “I am against you,” harlotries) — in addition to the baseline’s own Critical/High terms retained here as protective contrast entries (God, Lord/reserved, Gospel/reserved, Power of God).
• 8 of 15 doctrines (2 Critical + 6 High) in the Nahum doctrine risk registry require human theologian review; 4 require native-speaker review; only 3 are automated-review-only.
• The single highest-density risk zone is the discourse-level pairing of “slow to anger” and “will not acquit” in 1:2–3 — a structural risk that breaks the doctrine if Phase 2 segmentation ever splits these two clauses across separate translation units.
• Secondary but real risks: lion imagery (2:11–12, Durga’s vahana), sorceries/harlotries (3:4, overlapping living Bengali folk-occult vocabulary), and vision/দর্শন (1:1, Hindu devotional beholding).

Opportunities

• Bengal’s Bay of Bengal cyclone exposure and deltaic flood geography make Nahum’s storm and flood judgment imagery (1:3, 1:8) unusually vivid and require no cultural adaptation — a genuine asset unavailable to many other target languages.
• The prophet’s own name (Nahum = “comfort”) offers a strong pastoral hook for the “Comfort for the Oppressed” doctrine once glossed at first occurrence.
• God’s sovereignty over empires (2:13; 3:5) is a comparatively safe bridge concept for Muslim-background readers, given the strong Qur’anic parallel in Allah’s sovereignty over the rise and fall of nations.

Recommended actions

1. Load assets/translation_memory.json (Nahum) and assets/bible_term_registry.json (Nahum) alongside — never instead of — the baseline Romans equivalents before any Phase 2 segment translation begins.
2. Enforce Nahum 1:2–3 as a single, non-splittable theologian-review unit in Phase 2 segmentation and batch processing.
3. Attach the Nineveh/Yunus sequencing note to any study material reaching Muslim-background audiences, per analysis/12_ai_translation_requirements.md Doctrinal Preservation Rule 7.
4. Route all 16 Nahum-specific Critical/High terms and both Critical doctrines through mandatory human theologian review before Phase 2 sign-off; route the 4 Medium-tier doctrines through native-speaker review.
5. Carry the §3.2 “Crowded Semantic Neighborhoods” fencing list from analysis/06_linguistic_gap_analysis.md into the Phase 2 validation layer with the same enforcement weight as the baseline’s Critical Forbidden Substitutions list.