Executive Summary — Jude Translation Requirements (Malay)

Why it matters

Jude is 25 verses long, yet it packs an unusually high concentration of doctrinally loaded, culturally collision-prone vocabulary into that short span — more per-verse theological density than the Romans baseline this package extends. Malay-speaking readers approach this letter through a legally and constitutionally significant Islamic religious framework (Malaysia’s Allah-naming litigation, tawhid, established angelology, fiqh categories, and a deeds-weighed mercy doctrine), so getting Jude’s vocabulary right is not a stylistic nicety — mistranslating even one recurring keyword (Rahmat, Fasik, the “kept” thematic thread, the despotēs/kyrios confession) can quietly invert the letter’s own argument for the destination audience.

Key findings

• 20 curriculum doctrines identified, fully cross-referenced against every verse (1:1–25) of the single-chapter book: 8 Critical, 8 High, 3 Medium, 1 Low. Sixteen of the twenty require mandatory human theologian review before Phase 2 translation proceeds; three require native speaker review; one is suitable for automated review only.
• 62 terms are now recorded in the Jude translation memory: roughly 24 baseline Romans terms reused unchanged (Yesus, Allah, Tuhan, Roh Kudus, Iman, Kasih kurnia, and others) plus 38 new terms this letter introduces. Of the full 62-term set, 13 are Critical risk and 20 are High risk — 33 terms in total requiring theologian-level enforcement, against 23 Medium and 6 Low risk terms.
• The letter’s thematic keyword, τηρέω (“kept”), appears in five distinct grammatical forms across 1:1, 1:6, 1:13, 1:21, and 1:24 and has no single Malay word spanning its full range; this is the letter’s theological spine (“Kept by God and Presented Blameless”) and requires cross-reference tracking across the whole document, not verse-by-verse translation in isolation.
• Three separate doctrinal decisions (Jude 1:4, 1:5, 1:25) are inseparably linked and must be reviewed together: the double confession of Christ as “our only Master (Penguasa) and Lord (Tuhan),” a well-attested textual variant that may attribute the Exodus deliverance to the pre-existent Jesus himself, and the closing doxology’s “only God, our Savior… through Jesus Christ our Lord.” A decision at any one point changes the coherence of the other two.
• A genuinely new class of collision appears in Jude that the Romans baseline did not need to address: Jude 1:6’s premise of angels who chose to abandon their assigned position directly contradicts mainstream Islamic angelology (angels as ma’sum, incapable of disobedience) — a conceptual, not merely lexical, gap with no ready destination-culture frame to build on.

Risks

• Rahmat (mercy) — recurring four times (1:2, 21, 22, 23) — carries deep Islamic devotional entrenchment (Ar-Rahman, Ar-Rahim) operating within a deeds-weighed, Last-Day-contingent framework; Jude anchors mercy to a certain, Christ-secured outcome, and unfenced use at any single occurrence risks quietly importing the wrong theological framework.
• Fasik (ungodly), repeated fourfold in 1:15 alone, names a narrower and less severe Islamic fiqh category (a grave sinner remaining within the faith) than Jude’s actual target (doctrinal apostates who deny Christ’s lordship); the deliberate rhetorical repetition compounds the risk if fencing is applied inconsistently.
• Berjuang mempertahankan (contend earnestly, 1:3) risks jihad-adjacent resonance with Malaysia’s perjuangan agama political-religious vocabulary and must never stand unpaired or be confused with berjihad.
• The Enoch citation (1:14–15) raises a live canon/inspiration question (quoting non-canonical 1 Enoch material as prophecy) compounded by the Qur’anic Idris-Enoch identification and its ascension tradition, which risks conflating with the already-forbidden no-death-ascension error pattern.
• The Sodom “strange flesh” passage (1:7) intersects with Malaysia’s live dual civil/Syariah legal framework on related contemporary conduct, requiring strictly expository, non-policy-adjacent handling.

Opportunities

• Malay’s culturally comfortable hamba (servant) self-designation and genuine Islamic-tradition recognition of Mikhael/Michael and Bileam/Balaam-adjacent figures give real, usable pastoral bridges into Jude’s argument, provided each is paired with explicit fencing on the points of difference.
• The doxology’s monotheistic “only God, our Savior” language is a strong, positive resonance point with tawhid that, taught correctly alongside its Trinitarian mediating clause, can become a bridge into the fuller Christological argument rather than a stumbling block.
• Because Malay already has the longest continuous Bible translation history in this pipeline and long-settled non-syncretistic vocabulary for its highest-risk terms (Yesus, Allah, Kristus, Roh Kudus), Jude’s new vocabulary can be built on that existing foundation rather than starting from nothing.

Recommended actions

1. Load the Jude-specific translation_memory.json, bible_term_registry.json, doctrine_risk_registry.json, and 12_ai_translation_requirements.md before any Phase 2 segment translation begins; none of these Jude assets replace the Romans baseline — all extend it.
2. Route the linked Jude 1:4 / 1:5 / 1:25 deity-of-Christ cluster to a single human theologian as one review unit, not three independent items.
3. Establish a dedicated cross-reference tracking mechanism (outside ordinary term-consistency checking) for the five-occurrence τηρέω/“kept” thematic thread.
4. Apply mandatory fencing language — not forbidden-substitution avoidance, but explicit boundary-marking teaching text — at every occurrence of Rahmat, Fasik, and the angels’-own-domain passage, per the crowded-semantic-neighborhood findings in the Linguistic Gap Analysis.
5. Confirm the underlying Greek base text/English source translation’s readings at Jude 1:5 and 1:22–23 before Phase 2 begins, and record the decision explicitly rather than allowing silent harmonization.