Executive Summary: Ruth (English → Arabic)

Why it matters

Ruth is the smallest book yet analyzed in this Arabic Language Package, but it carries a disproportionately high concentration of Critical-risk theological content relative to its length — more concentrated, chapter-for-chapter, than the Romans baseline. Its core passage (Ruth 1:16-17) is a personal conversion-and-covenant confession whose Arabic phrasing sits directly on top of the Islamic exclusivist confession pattern (the shahada), and its central redemption figure (the go’el, kinsman-redeemer) can be mistranslated with a single fluent, natural-sounding, but doctrinally disastrous word (وليّ). Getting Ruth right in Arabic is not a smaller version of the Romans task — it is a comparably high-stakes task compressed into four chapters.

Key findings

• Full-book coverage confirmed. All four chapters of Ruth were analyzed end to end; no chapter was silently skipped. Chapter 1 carries the heaviest doctrinal load (the core passage, conversion, providence, hesed); chapters 2–4 each introduce their own load-bearing legal/theological vocabulary (gleaning and favor; the threshing-floor redemption request; the legal redemption and closing genealogy).
• 44 terms are recorded in translation_memory.json for this curriculum: 9 Critical-risk and 16 High-risk (25 combined, requiring absolute glossary enforcement and theologian-level scrutiny), plus 14 Medium and 5 Low.
• 10 doctrines are recorded in doctrine_risk_registry.json: 2 Critical (Ruth’s Conversion and Covenant Confession; The Kinsman-Redeemer) and 7 High (Hesed, Levirate Marriage and Inheritance, Providence, Inclusion of Gentiles, Loyalty and Faithfulness, Genealogy to David/Christ, Permanence of Covenant Bond), plus 1 Medium and 1 Low — 9 of 10 doctrines require mandatory human theologian review.
• One collision risk is more dangerous than any single term in the Romans baseline: the natural Arabic word for “kinsman-redeemer/guardian” (وليّ) is the exact word for Sufi awliya’ (venerated saints/shrine-intercessors), a collision already flagged Critical for “saints” in the Romans package. A translator working from fluency alone, with no doctrinal flag, would very likely select this wrong word first.
• The core passage is doctrinally double-loaded: Ruth 1:16-17 contains both a Critical conversion/confession claim (structurally resembling the shahada) AND a separate High-risk covenant-permanence claim (“until death”) that deliberately anticipates Romans 8:38-39’s assurance language — two distinct doctrines requiring two distinct theologian-reviewed footnotes in the same two verses.

Risks

• Silent smoothing of the “Moabite” label. A well-intentioned translator may drop or soften المؤابية after Ruth’s conversion out of pastoral instinct — this would destroy the book’s actual argument (grace overturning exclusion without erasing identity), not merely soften its tone.
• Fatalism drift. Ruth’s provuidence language (“hand of the LORD,” Shaddai, the “chance” gleaning of 2:3) is repeated at nearly every narrative turn — far more densely than the Romans baseline’s single providence passage — creating cumulative risk of collapsing into folk qadar/maktub fatalism if not fenced at every occurrence, not just the first.
• Merit-framework leakage. أجر (sakar/reward, 2:12) sits directly on Islamic soteriology’s deeds-recompense vocabulary (mizan); without a footnote at every occurrence, this single verse could be lifted out of context to support a works-merit reading of salvation generally.
• False legal equivalence. The levirate-marriage and sandal-removal customs (ch. 4) have no direct Shari’a equivalent, but readers may assume equivalence with a known — and Islam-abolished — pre-Islamic Arabian custom if the distinguishing footnote is omitted.
• Overclaimed bridge. The positive الفداء/Eid al-Adha (Q37 ram-substitution) resonance is a genuine teaching bridge but risks being overclaimed into full doctrinal equivalence with Christ’s substitutionary redemption if not theologian-reviewed per use.

Opportunities

• Ruth is the OT’s clearest narrative case study for Providence — richer and more teachable than the Romans baseline’s single verse (8:28), giving this curriculum a strong pastoral advantage once the qadar-fencing risk above is managed.
• Ruth is Judaism’s paradigmatic convert narrative (ger tzedek) and a genuine cross-tradition bridge point — comparative theology work already surfaces productive parallels (and necessary distinctions) with Jewish gerut, Islamic universal da’wah, and Arab wafa’ (loyalty) cultural values that can be used pastorally without compromising doctrine.
• The closing genealogy (4:18-22) is a uniquely concrete, historically anchored bridge to Christ — more concrete than abstract doctrinal argument, and directly continuous with Matthew 1:5’s explicit naming of Ruth, making it a strong discipleship on-ramp once the Davidic-typology gap (Quranic Dawud vs. covenant-king Dawud) is actively taught.

Recommended actions

1. Lock the Critical/High term list now (translation_memory.json, 25 terms) into Phase 2 tooling before any batch translation begins; treat وليّ, unqualified أجر, dropped المؤابية, and unfenced qadar-language as automatic validation failures, not stylistic flags.
2. Route all 9 theologian-review doctrines through mandatory human review before any Ruth segment is marked approved — no automated or native-speaker-only sign-off for Conversion/Confession, Kinsman-Redeemer, Levirate Marriage, Providence, Inclusion of Gentiles, Loyalty/Faithfulness, Genealogy, or Permanence of Covenant Bond.
3. Attach the nine mandatory Ruth-specific footnotes (hesed, kinsman-redeemer typology, providence fencing, Moabite retention, conversion-confession disambiguation, sakar/reward fencing, levirate/sandal-removal disclaimer, gleaning-vs-zakat disclaimer, Naomi/Mara wordplay) to every corresponding Bible-text segment in Phase 2/3 output, not merely in internal translator notes.
4. Verify chapter-2 threshing-floor and gleaning material with native-speaker cultural review in addition to theologian review, given real honor/shame misreading risk and the zakat/sadaqah collision risk respectively.
5. Carry forward the kanaph (جناح) and Moabite-label consistency checks into automated validation scripts, since both are cross-chapter literary/theological devices that a segment-by-segment translation workflow could otherwise break without anyone noticing until final review.