Executive Summary — Nahum (English → Arabic)

Why it matters

Nahum brings the Arabic Language Package into genuinely new territory: an Old Testament judgment oracle against a named empire, addressed to a destination culture where that empire’s capital (نينوى) is a positively remembered Quranic city and where that empire’s ethnic descendants (Assyrian/Chaldean/Syriac Christians) are a living, persecuted minority — mostly in Iraq. Unlike Romans, the risk here is not primarily which word to choose but which unstated context must be supplied so the text is not misheard as contradicting the Quran, condemning a living ethnic group, or commenting on the modern Israeli-Palestinian conflict. Get this book right, and the wrath/comfort tension at its center (1:2–7) becomes one of the most theologically productive bridges in the whole curriculum, because Arabic already has strong, favorable vocabulary for divine justice against oppression (Al-Muntaqim, Al-Qahhar, dhulm).

Key findings

• 17 doctrines identified, full-book coverage confirmed (Nahum 1–3, every verse mapped in analysis/11_doctrine_analysis.md); 9 require human theologian review (2 Critical + 7 High), 6 require native speaker review, 2 are automated-only — a materially different risk shape than Romans, concentrated in the character of God and contested proper nouns, not Christology.
• 46 terms recorded in the Nahum-specific translation_memory.json/bible_term_registry.json (8 inherited exactly from the Romans baseline, 38 new); 3 Critical-risk + 5 High-risk = 8 terms require theologian-level enforcement, concentrated in: الله/الرب (continuity), الرب صالح (goodness of God, 1:7), إله غيور (jealous God, 1:2), غضب الله (wrath, 1:2/1:6), نبوءة/massa (1:1), مُبَشِّر (1:15), and إسرائيل (2:2).
• No genuine lexical gaps found — Arabic’s classical/Quranic register is unusually well-supplied for theophany, siege, and judgment vocabulary. The dominant risk pattern is crowded semantic neighborhoods (favorable: منتقم, الظلم; unfavorable: وحي, غيور, نار) requiring active fencing rather than word invention.
• Three destination-culture-specific collision points not present in the Romans baseline: (1) Nineveh’s Quranic repentance narrative (10:98) vs. Nahum’s later judgment; (2) modern Assyrian/Chaldean/Syriac Christian ethnic sensitivity; (3) the political weight of “Isra’il” in Nahum 2:2, inheriting but extending the baseline’s existing Romans 9–11 caution.

Risks

• Highest risk (ranked #1 in linguistic gap analysis): splitting Nahum 1:2–6 (wrath) from 1:7 (goodness) into two different divine dispositions — this single failure mode would undermine both this book’s central doctrine (“Comfort for the Oppressed”) and the baseline’s Critical lord continuity with Romans 10:9.
• Apologetic exposure: leaving the Nineveh/Jonah-Quran tension unaddressed risks the entire book being read as ignorant of, or evasive toward, Quran 10:98 — a proactive, not reactive, teaching requirement.
• Pastoral/safety exposure: judgment language against أشور/نينوى, if not explicitly scoped to ancient imperial policy, risks being heard as condemnation of a present, historically persecuted Christian minority.
• Political exposure: Nahum 2:2’s “Israel” reference, if untreated, risks being read as commentary on the present Israeli-Palestinian conflict rather than ancient covenant restoration.
• Internal-consistency exposure: مُبَشِّر (1:15) shares a root with البشارة, which the baseline explicitly rejects for “gospel” — without an explicit note, the package can appear to contradict itself.

Opportunities

• Strong, favorable bridge vocabulary unmatched elsewhere in the curriculum: منتقم/ينتقم (Al-Muntaqim), طويل الأفق/بطيء الغضب (Al-Halim), الظلم/الظالم (a major condemned Quranic category), حصن/ملجأ (resonant with استعاذة refuge-devotion), سيادة الله (Al-Malik/Al-Qahhar) — genuine common ground rare in this Language Package.
• Nahum’s own name (ناحوم, “comfort/relent”) is a ready-made teaching hook tying the prophet’s identity directly to the book’s argument.
• Christological forward bridges available even in this OT-only book: God’s rebuke of the sea (1:4) anticipates Christ’s rebuke of the storm (Mark 4:39); the “no healing” reversal (3:19) sets up later NT healing/Healer typology.

Recommended actions

1. Load assets/translation_memory.json (Nahum) alongside the unmodified Romans baseline TM before any Phase 2 segment work; never treat the two as interchangeable or duplicative.
2. Route all 9 theologian-review doctrines and all 8 Critical/High terms through human theologian review before approval, per assets/doctrine_risk_registry.json and analysis/12_ai_translation_requirements.md’s escalation rules.
3. Enforce the mandatory first-occurrence framing notes (Nineveh/Jonah timeline, Assyrian ethnic non-transfer, Israel political non-transfer, wrath-goodness unity, mevasser/gospel non-contradiction) as a validation-gate requirement, not an optional footnote — absence of the note should block segment approval with the same severity as a lexical error.
4. Prioritize reviewer attention on Nahum 1:1–8 (7 of 17 doctrines, both Critical doctrines) as the theological anchor, while ensuring chapters 2–3 are not deprioritized to the point of silent omission — every verse in all three chapters is already mapped in analysis/11_doctrine_analysis.md.

---

This summary synthesizes analysis/06_linguistic_gap_analysis.md, analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, analysis/11_doctrine_analysis.md, analysis/04_comparative_theology.md, assets/translation_memory.json, assets/bible_term_registry.json, and assets/doctrine_risk_registry.json. All figures above are drawn directly from those documents and are internally consistent with them.