01 — Executive Summary: Revelation (English → Arabic)

Why it matters

Revelation is the highest-stakes book in the TRI pipeline to date for Arabic. Unlike Romans, whose collisions are mostly abstract soteriological vocabulary, Revelation’s central images — throne, worship, lamb, bride, beast, seal, testimony — have direct, named counterparts already fixed in Quranic and hadith eschatology (al-‘Arsh, sujūd/shirk, al-Masīḥ al-Dajjāl, khātam al-nabiyyīn, shahīd, Ya’jūj wa-Ma’jūj). Every chapter, not just the core passage, carries load-bearing doctrinal vocabulary that must be translated with surgical precision — the correct word is usually unavoidable, and the risk lives entirely in the pre-loaded competing content Arabic-speaking readers, especially of Muslim background, already attach to it.

Key findings

• Full-book coverage confirmed. All 22 chapters have been analyzed (07, 08, 11 series); no chapter contributes zero new load-bearing vocabulary — even thematically “quiet” chapters (8-9, 15-16) extend wrath/judgment terms established elsewhere.
• 114 terms are now recorded in the Revelation translation memory (40 inherited exactly from the Romans baseline + 74 new Revelation-specific terms), consistent with assets/bible_term_registry.json.
• 31 of 36 registered doctrines carry Critical or High risk (15 Critical + 16 High), each requiring mandatory human theologian review per occurrence — nearly triple the baseline Romans doctrine set’s proportion of Critical-tier doctrines, reflecting Revelation’s denser deity-claim concentration (Lamb’s co-enthronement, Alpha/Omega, King of Kings and Lord of Lords all recur across multiple chapters rather than appearing once).
• 64 of the ~90 entries in the Revelation-specific term registry are Critical or High risk (27 Critical + 37 High), meaning roughly seven in ten load-bearing terms in this book require theologian sign-off before entering production translation — a materially heavier oversight burden than Romans.
• The single sharpest new risk not present in Romans: Worship of the Lamb (προσκυνέω/سجود directed at Christ while co-enthroned with God) is the paradigm case of shirk if left unexplained — the doctrinal center of the entire book and the highest-priority item on the ranked ambiguity list.
• The sharpest true conceptual gap: the Church as Bride of Christ has no positive analogue in mainstream Islamic theology (tanzīh renders it unthinkable), unlike most other doctrines, which have genuine — if incompatible — bridges (Yawm al-Dīn, al-Dajjāl, Ya’jūj wa-Ma’jūj, Jannah). This one requires net-new teaching, not correction of existing content.
• A permanent, non-negotiable fencing decision: شهيد (shahīd) is excluded from translation memory entirely for the martyrdom concept, replaced by the descriptive phrase القتلى من أجل شهادتهم, because shahīd’s battlefield/jihad/assured-Paradise soteriology is fundamentally incompatible with Revelation’s blood-of-the-Lamb-based vindication (12:11).

Risks

• Compounding deity claims. Alpha/Omega, First/Last, the Living One, and King of Kings/Lord of Lords all echo specific, named divine attributes of Allah (al-Awwal, al-Ākhir, al-Ḥayy, Mālik al-Mulk) and recur at the book’s most rhetorically climactic points (1:8, 17-18; 19:16; 21:6; 22:13). Any softening at any single occurrence undermines the cumulative argument across the whole curriculum.
• False-equivalence short-circuiting. The Beast/al-Dajjāl and Gog and Magog both offer unusually strong narrative parallels that could be mistaken for identical claims if translators or reviewers do not actively apply the required correction (the crucifixion/resurrection basis of Christ’s victory; the differing end-times sequence) at every occurrence.
• Contemporary political contamination. إسرائيل, أورشليم/القدس, and the Temple Mount/al-Ḥaram al-Sharīf all carry present-day political weight independent of, and in addition to, their doctrinal risk — requiring pastoral framing distinct from ordinary theological fencing.
• Register drift under cultural pressure. Mainstream Sunni piety’s characteristic epistemic humility about final personal/cosmic outcomes creates real pressure to soften Revelation’s confident, unhedged assurance language (“it is done,” “no more death”) — a felt cultural friction point, not merely a doctrinal one.

Opportunities

• Bridge-and-correct is available almost everywhere. Unlike Romans, most Revelation doctrines have a genuine, positive point of contact in Islamic eschatology (a real Throne, a real final Judgment, a returning ‘Isa, Paradise-garden imagery, a named apocalyptic horde) — the translation task is predominantly to use the correct, maximally loaded vocabulary while supplying the explicit corrective content the bridge requires, not to search for neutral alternatives.
• Revelation 22:8-9 (the angel’s refusal of worship) is a built-in apologetic resource the text itself supplies to distinguish legitimate divine worship of the Lamb from illegitimate creature-worship — usable pastorally rather than defensively.
• The existing Van Dyck/NAV translation landscape is largely reliable on Revelation’s hardest verses (05_translation_landscape.md), reducing the burden to enforcement and consistency rather than novel term creation.

Recommended actions

1. Load assets/translation_memory.json (Revelation) and assets/bible_term_registry.json (Revelation) alongside the baseline Romans files before any Phase 2 segment translation, per 12_ai_translation_requirements.md.
2. Route all 31 Critical/High doctrine occurrences and all 64 Critical/High term occurrences to mandatory human theologian review before production release; do not permit native-speaker-only sign-off to substitute.
3. Apply fencing language (not a one-time footnote) at first occurrence per chapter/passage cluster, given Revelation’s non-linear cross-referencing structure — a reader may encounter chapter 13’s Beast before chapter 1’s introductory material.
4. Enforce the permanent شهيد exclusion and the الخروف/حمل distinction as hard validation-layer checks, not stylistic preferences, in every Phase 2 batch run.
5. Confirm YouVersion version IDs (SVD 131, NAV 203) against the live API before Phase 2/3 batch hyperlink generation, per the existing house-style caution.