Executive Summary: Jude — English → Persian Translation Requirements

Why it matters

Jude is 25 verses of the densest doctrinal-risk material in the New Testament for a Persian, Muslim-background house-church audience — packing apostolic authority, false-teacher judgment, three Old Testament type-sequences, an intertestamental prophetic citation, Christ’s exclusive Lordship, and a Trinitarian doxology into a single short chapter. Nearly every verse is load-bearing, and several of its terms sit directly on top of live Iranian legal-criminal categories (apostasy accusation, blasphemy law, Sharia hadd punishment) — meaning a mistranslation here is not only a doctrinal risk but a potential real-world safety risk to readers and translators. This Language Package extends the proven Romans baseline rather than starting over, reusing 18 already-battle-tested terms exactly and adding 44 new, fully-vetted entries so Phase 2 translation can proceed with the same rigor already established for Romans.

Key findings

• Full-book coverage confirmed. All 25 verses of Jude’s single chapter have been analyzed (semantic analysis, glossary, doctrine matrix, linguistic gap analysis); no section was silently omitted.
• 15 doctrines identified, matching doctrine_risk_registry.json: 5 Critical, 7 High, 3 Medium, 0 Low. 12 doctrines require mandatory human theologian review; 3 require native speaker review; none are automated-only — a notably higher theologian-review density than Romans, reflecting Jude’s compression of high-stakes content into few verses.
• 61 terms registered in bible_term_registry.json: 15 Critical, 18 High, 19 Medium, 9 Low. Combined with the doctrine-level review requirement, 33 of 61 terms (Critical+High) demand theologian-level scrutiny at every occurrence.
• Highest-severity finding: the Enoch citation (1:14-15) risks conflation with the Quranic prophet Idris, who is already exegetically exalted in Islamic tradition — a collision unique to this letter and not present anywhere in the Romans curriculum.
• Second-highest finding: Jude 1:4 stacks two distinct Christological titles (δεσπότης, κύριος) on Christ in a single verse; the established rendering (سرور / خداوند) must never be swapped with مولا, the central Shia title for Ali, without collapsing the verse’s rhetorical force.
• Pastoral-safety finding (new category, not present in the Romans package): three terms — ungodly (خدانشناس), revile/blaspheme (توهین کردن), licentiousness (بی‌بندوباری) — must avoid their nearest natural Persian synonyms (بی‌دین, کفر گفتن, زنا respectively) specifically because those synonyms name actual, currently-enforced Iranian legal-criminal categories, not because of doctrinal imprecision alone.

Risks

• Critical-tier collision risks (5 doctrines): Judgment on Ungodly False Teachers, Kept by God and Presented Blameless, Lordship and Deity of Christ, Inspiration of Scripture and Fulfillment of Prophecy, Eschatological Judgment and the Lord’s Coming. Each carries a specific, documented Persian/Shia cultural or legal collision (apostasy accusation, hifz-e Qur’an collocation, Imamate lordship-succession, Enoch/Idris conflation, Mahdi-centered eschatology displacement).
• Structural-consistency risk: the recurring verb τηρέω/φυλάσσω (“kept,” حفظ کردن) must be rendered identically at all five occurrences (1:1, 1:6, 1:13, 1:21, 1:24) to preserve Jude’s reciprocal keeping-theology; any drift silently destroys this doctrine without producing an obviously “wrong” sentence in isolation.
• Devotional-vocabulary gravity risk: two of Jude’s most vivid terms — رحمت (“mercy”) and گمراهی (“wandering/error,” in “wandering stars”) — sit on top of the single most repeated devotional vocabulary in daily Iranian Muslim practice (the Bismillah’s رحمت and Surah al-Fatiha’s al-dhalleen). These cannot be avoided (no viable substitute exists) and must instead be actively taught in dialogue with, not silent borrowing from, their Islamic devotional associations.

Opportunities

• Genuine bridge concepts identified and preserved, not discarded: Michael (میکائیل, Quran 2:98), Cain (قابیل, Surah 5:27-31), and عبرت (moral-lesson/warning-example, an established Islamic homiletic category) all offer real, positive points of contact that teaching material can use directly, provided narrative differences are flagged.
• Reuse discipline pays down risk fast: 18 of the highest-stakes terms (لله, عیسی, مسیح, خداوند, روح‌القدس, نجات, etc.) require zero new analysis — they inherit fully-vetted Romans baseline renderings, letting Phase 2 focus its scarce theologian-review bandwidth on Jude’s 44 genuinely new terms.
• The Jude-specific pastoral-safety layer is now explicit and auditable: by naming the exact live-legal-category collisions (apostasy, blasphemy law, hadd punishment) and their required avoidance terms, this package gives reviewers a concrete, checkable safety criterion beyond ordinary doctrinal fidelity.

Recommended actions

1. Load both translation memories for every Phase 2 Jude segment — the Romans baseline translation_memory.json and the new assets/translation_memory.json (Jude) — per the updated pre-flight checklist in 12_ai_translation_requirements.md.
2. Route all 12 theologian-required doctrines and 33 Critical/High terms through human theologian review before approval; do not permit automated-only sign-off on any segment touching these.
3. Enforce the حفظ کردن (“kept”) consistency check as a standing automated validation rule across every Jude document batch, given its unusually high silent-failure risk.
4. Brief theologian reviewers specifically on the Enoch/Idris and δεσπότης/κύριος risks before Phase 2 begins, since these are unique to Jude and have no Romans-curriculum precedent to draw on.
5. Attach mandatory teaching notes (not just glossary entries) wherever گمراهی, رحمت, نفسانی, or خنوخ appear in expository material, per the doctrinal preservation rules in 12_ai_translation_requirements.md.