Executive Summary
Executive Summary: Genesis (English → Arabic)
Why it matters: Genesis is the theological foundation the rest of Scripture — including the already-completed Romans package — builds on, and for an Arabic-speaking, Sunni-majority-context readership it is also the single most contested book in the Bible relative to a competing scriptural tradition. Nearly every major doctrine assigned to this curriculum (Creation, Image of God, the Fall, the Abrahamic Covenant, Providence) has a direct, named counterpart or rival claim in the Quran and mainstream Islamic theology. Phase 2 translation cannot proceed safely without the term- and doctrine-level scaffolding this Phase 1 package now provides.
Key findings
- The Image of God (صورة/شبه, Genesis 1:26-27) is the single highest-severity term in the entire curriculum — higher-collision than any individual Romans term — because Islamic tanzīh theology treats any suggestion of human-divine resemblance as tashbīh, bordering on shirk. No alternative rendering exists; the term is fixed and the risk must be managed entirely through mandatory explanatory scaffolding at every occurrence.
- The Abrahamic narrative (chs. 12–22) is the book’s most consequential fork, because Genesis names Isaac — not Ishmael — as both the covenant heir (21:12, quoted directly in Romans 9:7) and the near-sacrificed son of chapter 22, directly contesting the Ismail-primacy reading embedded in Hajj ritual and Eid al-Adha commemoration.
- Genesis supplies four direct Old Testament root-texts for Pauline doctrines already Critical in the Romans baseline: 15:6 (imputed righteousness → Romans 4:3), 21:12 (children of promise → Romans 9:7), 25:19-34/48 (election → Romans 9:10-13), and 50:20 (providence → Romans 8:28). Cross-document rendering consistency on these four texts is a Phase 2 hard requirement, not a stylistic preference.
- 68 new Genesis-specific terms and 17 baseline terms with Genesis-specific usage notes have been catalogued in
assets/translation_memory.json(85 total), extending the baseline Romans glossary without altering any existing baseline rendering. - Of the 85 catalogued terms, 39 (18 inherited + 21 new… corrected: 18 Critical + 21 High = 39) are Critical or High risk (18 Critical: 5 inherited + 13 new; 21 High: 8 inherited + 13 new), each requiring mandatory human theologian review per the established baseline routing convention.
- Of the 22 doctrines tracked in
assets/doctrine_risk_registry.json, 18 (7 Critical + 11 High) require human theologian review; 4 Medium-risk doctrines require native speaker review; zero doctrines are automated-review-only — a markedly heavier oversight load than the Romans baseline’s already-substantial 29-of-40 theologian-review ratio. - Genuine positive bridges exist and should be used deliberately, not merely avoided as risk: the Joseph/Yusuf narrative (chs. 37-50) has near-universal positive familiarity across Muslim and Christian Arabic readers alike; Noah’s ark (الفلك) and the flood (الطوفان) use identical Quranic vocabulary; divine titles العلي and القدير map directly onto two of Allah’s 99 names; dreams as divine communication are affirmed in both traditions.
Risks
- Highest-priority flashpoints requiring mandatory theologian sign-off before any Phase 2 output is accepted: Image of God (1:26-27), the Fall/origin of sin (ch. 3), the Abrahamic covenant’s Isaac/Ishmael fork (12-22), the Binding of Isaac (ch. 22), Hagar and Ishmael’s narrative treatment (16, 17, 21, 25), Joseph’s explicit providence statements (45:5-8; 50:20), the protoevangelium and Shiloh/scepter messianic prophecies (3:15; 49:8-12), and Israel’s naming/etymology (32:28).
- Vocabulary-level risk is concentrated, not diffuse: a small number of terms (صورة/شبه, جنة عدن, هاجر/إسماعيل, شيلون, روح الله, استراح) carry disproportionate collision risk relative to their frequency and must receive priority reviewer attention in every batch.
- Register/fatalism risk: the readily available, colloquial Arabic vocabulary for “God’s plan” (القدر) is doctrinally unsafe for this curriculum’s Providence doctrine; the doctrinally correct vocabulary (العناية الإلهية) is comparatively bookish, creating a persistent register-vs-precision tension Phase 2 reviewers must actively manage rather than resolve by defaulting to the more natural-sounding but theologically flattening term.
- Content-sensitivity risk (non-doctrinal): chapters 34 (Dinah) and 38 (Judah and Tamar) contain material requiring careful pastoral handling in teaching material, independent of any glossary/doctrine-tracking concern.
Opportunities
- Use the Joseph narrative as the curriculum’s primary trust-building bridge. Its near-universal familiarity (Surat Yusuf) gives Phase 2 material an unusually strong on-ramp before the harder theological material in later lessons.
- Lean into the genuine convergence points (creation-from-nothing vocabulary, the ark/flood, dream-revelation, the divine titles العلي/القدير, “male and female” in 1:27/Quran 49:13) as deliberate teaching bridges rather than merely surviving them as neutral overlaps.
- Reuse, rather than reinvent, baseline Romans scaffolding for four of Genesis’s Critical doctrines (imputed righteousness, election, providence, messianic promise) — this is a direct efficiency gain from having the Romans package already completed and battle-tested.
Recommended actions
- Lock
assets/translation_memory.jsonandassets/doctrine_risk_registry.json(Genesis) as authoritative before any Phase 2 segment translation begins, consistent with the baseline’s own load-order mandate. - Route all 18 Critical-risk terms and all 7 Critical-risk doctrines to mandatory pre-approved theologian sign-off before their first Phase 2 use, not merely flagged for post-hoc review.
- Brief all reviewers explicitly on the Isaac/Ishmael fork and the Image of God scaffolding requirement as the two highest-stakes, highest-frequency review items, ahead of batch processing.
- Enforce cross-document consistency checks on the four Genesis-to-Romans root-text pairs (15:6↔4:3; 21:12↔9:7; 25:19-34↔9:10-13; 50:20↔8:28) as an automated validation gate, not a manual spot-check.
- Proceed to Phase 2 with
analysis/12_ai_translation_requirements.md(Genesis extension) and the baseline requirements document both loaded for every translation session.
This summary synthesizes Phase 1 Steps 1-11 for Genesis. See assets/translation_memory.json, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, and analysis/11_doctrine_analysis.md for full supporting detail.