Judges → Arabic Translation Requirements: Executive Summary

Why it matters

Judges is being added to an Arabic-language Bible curriculum series anchored by a Romans Language Package already tuned to the specific theological collision-points of Arabic’s dominant religious environment. Judges introduces a different risk profile than Romans: instead of dense soteriological abstractions, it is narrative-driven, cyclical, and institutional (judges, kings, vows, a consecrated deliverer, an ambiguous Angel of the LORD) — and several of its central terms sit directly on top of live, high-stakes Islamic legal and theological categories (apostasy/ridda, dhimmi taxation, prophetic “warner” titles). Getting this book wrong risks either real-world danger to Arabic-speaking readers of Muslim background (via apostasy-law-adjacent vocabulary) or doctrinal dilution of the book’s own argument for a righteous King, ultimately fulfilled in Christ.

Key findings

• Full-book scope confirmed. All 21 chapters have been analyzed; every chapter contributes to at least one of the six named curriculum doctrines or is explicitly logged as “reviewed, no new risk” (e.g., 10:1-5, 12:8-15).
• The core passage (2:6-19) is the theological hinge, not the boundary. It supplies the operative vocabulary — cycle refrain, covenant-unfaithfulness metaphor, divine compassion, Spirit-empowering formula, moral-decline comparative — that every subsequent judge-narrative reuses rather than re-coins.
• 53 terms are now fixed in assets/translation_memory.json: 13 inherited exactly from the Romans baseline (god, lord, holy_spirit, covenant, grace, salvation, sin, peace, exhort, israel, prophet, power_of_god, kingdom_of_god) and 40 new Judges-specific entries.
• Term-level Critical + High risk count: 24 (10 Critical, 14 High) — every one of these requires mandatory human theologian review at every occurrence per the escalation rules.
• Doctrine-level risk count (registry): 17 of 25 cataloged doctrines require human theologian review (4 Critical + 13 High), 6 require native speaker review (Medium), and 2 are automated-only (Low).
• A small, high-consequence forbidden-substitution list drives most of the risk mitigation: الارتداد (never for apostasy/relapse — collides with Islamic ridda law), جِزْيَة (never for forced labor — collides with dhimmi taxation), bare نذير (never for Nazirite — collides with “warner,” a Quranic prophetic descriptor), and definite/title-level الخلاص (never for a human judge’s rescue — must stay reserved for Christ alone).

Risks

1. Apostasy-law collision (Critical). Any slipped use of الارتداد/اِرْتَدُّوا anywhere in the cycle-refrain, covenant-lawsuit, or relapse material is not a stylistic error — it imports a real, dangerous modern legal accusation onto ancient Israel and onto any Muslim-background reader who hears it applied loosely.
2. Salvation-register bleed (Critical). Because human “deliverance” and Christ’s “salvation” share the same Arabic root (خلص), inconsistent definite/indefinite usage across six judge-cycles risks either cheapening Christ’s unique atonement or wrongly crediting a human judge with eternal salvation.
3. Angel of the LORD flattening (Critical). Arabic مَلاك defaults to “ordinary created angel” in both everyday and Islamic theological usage; without deliberate scaffolding at 2:1, 6:11-24, and 13:3-22, the book’s strongest OT Christophany material goes doctrinally silent.
4. Harlotry-metaphor literalization (Critical). زنى’s exact overlap with the Islamic ḥadd-crime term risks the covenant-marriage metaphor (2:17 and parallels) being received as a literal, transferable moral accusation rather than God’s own chosen figure of speech.
5. Human-sacrifice misreading (Critical). Jephthah’s vow outcome (11:34-40), if under-framed, risks readers concluding Scripture condones child sacrifice — a serious apologetic liability distinct from, and larger than, any wording choice.
6. Inclusio breakage (High, structural). The book’s defining refrain (17:6/21:25) must be string-identical; any Phase 2 batch-processing drift between the two occurrences silently destroys the intended literary bracket and its theological payoff.
7. Nazirite/“warner” category error (High). An unqualified نذير at Samson’s introduction misfiles him into the Islamic prophetic-office semantic field.

Opportunities

• صنم (idol) and مثل (fable/parable) offer genuine, low-friction convergence with Quranic vocabulary and can be leveraged pastorally rather than merely flagged as risk.
• Generational moral-decline rhetoric (2:19’s “more corrupt than their fathers”) resonates with widely shared Islamic hadith-tradition decline narratives — a real bridge point for teaching Moral Decline and the Need for a Righteous King.
• Deborah’s unqualified prophetess/judge role is a genuinely distinctive biblical claim against mainstream Islamic prophetology’s all-male anbiyāʾ list — worth teaching directly as a point of contrast rather than softening.
• Hospitality violation at Gibeah (ch.19) resonates strongly with Arab cultural diyafa values, giving the atrocity narrative unusual rhetorical force for this audience when framed carefully.

Recommended actions

1. Lock all 24 term-level Critical/High entries and all 17 theologian-routed doctrines into Phase 2 validation as automatic-flag, non-optional human review — no automated or native-speaker-only approval path for these.
2. Enforce the Judges-specific forbidden-substitution list (الارتداد, جِزْيَة, bare نذير, definite/title-level الخلاص for judges) with the same batch-validation rigor already applied to the Romans baseline’s forbidden list (عيسى, الشريعة, التزكية, etc.).
3. Add a dedicated cross-check pass in Phase 2 batch processing specifically for the 17:6/21:25 inclusio and the six full cycle-refrain instances, since ordinary segment-by-segment parallel processing is the most likely point of accidental inconsistency.
4. Require companion/teaching-material scaffolding (not verse-text alteration) for every Angel-of-the-LORD, harlotry-metaphor, and Jephthah’s-vow occurrence, per the doctrinal preservation rules in analysis/12_ai_translation_requirements.md.
5. Carry forward the Romans baseline’s YouVersion citation convention (Van Dyck AVD/ID 13 primary, NAV KEH/ID 101 secondary) unchanged for all Judges citations, using book code JDG.