Executive Summary: Jude → Pashto Language Package

Why it matters

Jude is a short, structurally tight epistle built on a single recurring argument — that God who has always kept his people will keep them to the end, even as false teachers who failed to keep their own position face certain judgment. Translating it into Pashto for a persecuted, Muslim-background house-church readership carries outsized risk relative to its length: in just 25 verses, the letter stacks two of this pipeline’s highest-collision terms (رحمت “mercy” and مالک/خداوند “master/lord”) back-to-back, cites two non-canonical Jewish texts, and depicts angels sinning — a direct collision with mainstream Sunni angelology. Getting Jude wrong is easy to do quietly, because its central argument depends on a single Pashto verb root (ساتل) recurring identically five times across the whole book; ordinary translation practice (varying verbs for style) would silently destroy that argument without ever triggering an obvious “wrong word” error.

Key findings

• 17 distinct doctrines identified across full-book coverage (all 25 verses, salutation through doxology): 4 Critical, 11 High, 2 Medium, 0 Low. 15 require mandatory human theologian review; 2 require native speaker review; none are automated-only.
• 63 total terms now recorded in the Jude translation_memory.json: 14 inherited exactly from the Romans baseline (faith, grace, saints, holy, holy_spirit, lord, jesus, messiah, god, apostle, glory, peace, sin, called) plus 49 new terms this book introduces. Of the 63: 7 Critical, 20 High, 26 Medium, 10 Low.
• The letter’s single most important translation decision is not a doctrinal word choice but a structural consistency requirement: the keep/preserve word-family (τηρέω/φυλάσσω) must render identically as ساتل at all five occurrences (1:1, 1:6, 1:13, 1:21, 1:24), or Jude’s entire argument (angels failed to keep themselves → judgment reserved in darkness → believers commanded to keep themselves → God alone able to keep believers) becomes invisible in Pashto.
• Jude 1:4 stacks two distinct Greek titles (δεσπότης, κύριος) onto Christ in one clause — the letter’s most concentrated deity claim. مالک is licensed only for δεσπότης and must never substitute for خداوند (κύριος), reversing none of the Romans baseline’s existing rejection of مالک as a κύριος rendering.
• The book’s author-name itself is a live disambiguation risk: یهودا (Jude) is the identical name behind “Judas Iscariot” and “Judah,” requiring mandatory apposition (“Jude, brother of James”) at every introduction.

Risks

• رحمت (mercy) detachment risk (Critical, 4 occurrences): as one of Islam’s two central divine-attribute names (Ar-Rahman, Ar-Rahim), an un-anchored رحمت invites a generic, non-Christological reading at exactly the verses (1:21-23) carrying the letter’s pastoral climax.
• Title collapse risk (Critical, Jude 1:4): conflating مالک/خداوند in either direction flattens Jude’s sharpest Christological argument.
• Canon/inspiration exposure (Critical, 1:9, 1:14-15): Jude’s citation of 1 Enoch and the Assumption of Moses tradition risks either feeding the regional tahrif (corrupted-scripture) narrative or destabilizing confidence in the closed biblical canon if left unexplained.
• Structural-consistency failure (High, cross-book): because Jude is short enough to be split across multiple parallel Phase 2 workers, the five-occurrence ساتل chain is uniquely vulnerable to silent inconsistency that no single-segment review would catch.
• False-friend angelology (High, 1:6, 1:8-10): پرښته’s mainstream sinless-angel association runs directly counter to Jude’s picture of judged, rebellious angels.
• Legal-category misimport (High, 1:7): زنا would smuggle a specific Islamic hadd-penalty legal framework into a passage about divine eschatological, not human legal, judgment.

Opportunities

• Persecution-context resonance: Jude’s “love feasts” (1:12) and its picture of a small community defending itself from internal corruption map naturally onto today’s secret Pashto house-church gatherings — a genuine pastoral asset, not merely a translation gap.
• نفساني/روحاني pairing gives Pashto readers a vivid, native-vocabulary contrast (soul-driven appetite vs. Spirit-indwelt life) unavailable as cleanly in some other language pairs in this pipeline.
• ساتل’s dual-direction argument (God keeps; believers must keep themselves) offers strong assurance-of-salvation teaching material precisely where mainstream regional piety treats such certainty as presumptuous.

Recommended actions

1. Load assets/translation_memory.json (Jude) alongside the Romans baseline TM before any Phase 2 segment translation begins; treat both files’ entries with identical non-negotiable priority.
2. Run the dedicated post-batch ساتل consistency pass and مالک/خداوند title-separation pass described in analysis/12_ai_translation_requirements.md after all parallel workers complete Jude segments, before Doctrinal Fidelity Review sign-off.
3. Route all 15 theologian-tier doctrines and all Critical/High-tier terms through mandatory human theologian review per the escalation rules; do not permit automated-only clearance anywhere in this book.
4. Fix the Jude 1:22-23 three-group textual-variant reading at the Language Package level (already recorded) so no downstream document contradicts it.
5. Supply theologian-authored explanatory notes for the Enoch/1 Enoch and Michael/Assumption-of-Moses citations before any teaching material built on 1:9 or 1:14-15 ships to end users.

---

This document summarizes Phase 1 Steps 1–11 for the Jude curriculum. See analysis/11_doctrine_analysis.md, assets/doctrine_risk_registry.json, assets/bible_term_registry.json, assets/translation_memory.json, and analysis/12_ai_translation_requirements.md for full supporting detail.