Executive Summary — Nahum (English → Hindi)

Why it matters

Nahum pairs the destination culture’s sharpest cross-tradition collision points — a jealous, avenging, covenant-named God who is also “slow to anger” — with the Hindi-speaking world’s dominant devotional and cosmological frameworks (bhakti mercy-emphasis, cyclical pralaya cosmology, multi-deity normalcy, and honor/shame social dynamics). Getting this three-chapter book wrong risks either (a) a domesticated God whose wrath is explained away by devotional-mercy assumptions, or (b) a God whose justice reads as capricious personal vengeance or petty jealousy — both failures at the doctrinal core the curriculum exists to teach. Because Nahum is compact, nearly every verse in chapter 1 carries Critical or High doctrinal weight; there is very little “low-risk filler” in this book to buffer translation errors.

Key findings

• 9 of 13 doctrines require mandatory human theologian review (4 Critical + 5 High); only 3 route to native speaker review and 1 to automated review alone — a theologian-review ratio (69%) higher than typical NT epistle curricula in this pipeline.
• 16 of 44 Nahum-specific terms are Critical or High risk (5 Critical + 11 High), concentrated almost entirely in Nahum 1:1-8, the assigned core passage — confirming the core passage is also the book’s highest-density risk zone, not merely its thematic anchor.
• Two open cross-curriculum reconciliation items require formal theologian sign-off before Phase 2 begins: (1) חָזוֹן/दर्शन at 1:1 directly contradicts the existing Galatians revelation entry’s rejection of दर्शन, requiring a documented exception-with-guardrail rather than silent inconsistency; (2) נָקָם/पलटा लेनेवाला परमेश्वर at 1:2 departs from the historically attested Hindi OV बदला specifically to stay consistent with the baseline’s wrath_of_god anti-revenge caution — a defensible but unratified fence.
• A new Critical-tier term class enters the Language Package for the first time in this curriculum: the covenant name יְהוָה/यहोवा, which must be kept lexically distinct from परमेश्वर across all 8+ occurrences in Nahum and reconciled with any future Old Testament curriculum.
• One deliberate non-reuse of an established Critical term protects a cross-book boundary: Nahum 1:15’s “good news” (מְבַשֵּׂר) is rendered शुभ समाचार, NOT the baseline’s reserved सुसमाचार, to prevent teaching that an OT military deliverance IS the NT gospel.

Risks

• Highest risk (rank 1 of 10): “Complete end” (כָּלָה, 1:8-9) colliding with Hindu cyclical dissolution (pralaya/yuga) cosmology — Nineveh’s fall must read as linear, historical, and final, never one turn of a repeating cosmic wheel.
• Rank 2: The דर्शन/revelation precedent conflict (1:1) — unresolved, it undermines confidence in the whole Language Package’s internal coherence from the book’s very first verse.
• Rank 3: “Jealous God” (קַנּוֹא, 1:2) collapsing into ईर्ष्या (petty human envy) at the book’s foundational character-defining verse.
• Rank 4: “Vengeance” (נָקָם, 1:2) reintroducing बदला-style personal-revenge framing if the fence is not enforced.
• Rank 5: सुसमाचार/शुभ समाचार boundary erosion at 1:15 across Phase 2 batch processing.
• Secondary but acute: honor/shame misreading of “harlotries” (זְנוּנִים, 3:4) as literal content about individual women rather than the standard OT city-personification convention; “slow to anger” (1:3a) being excerpted and taught apart from “will not leave unpunished” (1:3b), inverting the doctrine’s balance.

Opportunities

• Nahum’s own name (“comfort”) and its 1:7 refuge/knowing cluster offer a genuine, low-friction bridge into Hindu devotional (bhakti) vocabulary of compassionate divine awareness — an asset for the Comfort for the Oppressed doctrine if anchored explicitly to the book’s specific historical deliverance rather than left as generalized consolation.
• The lion, locust, siege, and flood imagery (chapters 2-3) are agriculturally, pastorally, and historically intelligible to Hindi/Indian readers essentially as-is, requiring only brief historical glosses rather than new vocabulary — low-cost, high-clarity wins.
• Nahum’s compact size (3 chapters, ~47 verses) makes full-book, single-pass (non-parallel) theologian review before Phase 2 parallel batch processing operationally feasible — recommended explicitly in 12_ai_translation_requirements.md to resolve the two open reconciliation flags early.

Recommended actions

1. Obtain theologian sign-off on the two open reconciliation flags (दर्शन/revelation precedent; पलटा लेनेवाला परमेश्वर/vengeance) before any Phase 2 Step 16 parallel processing begins.
2. Enforce the Nahum 1:3 paired-clause rule as a hard segmentation constraint in Phase 2 tooling, not merely a translator note, given how easily 1:3a is independently quotable.
3. Route all Nahum 3:1-5 material through combined native-speaker + theologian review per the existing honor/shame convention, prioritizing the “harlotries” (3:4) and “city of blood” (3:1) segments.
4. Load both the baseline (Romans/Galatians) and this curriculum’s translation_memory.json and bible_term_registry.json together for every Nahum segment; validate every batch against the सुसमाचार/शुभ समाचार and यहोवा/परमेश्वर boundary rules before marking any segment approved.
5. Carry the पूरी तरह अन्त कर देना linear-history translator note on every occurrence of 1:8-9 without exception, given its ranking as the single highest cultural-collision point in the book.