Executive Summary: Jude (English → Assamese)

Why it matters

Jude is 25 verses long — and among the most doctrinally dense chapters in the New Testament per word. This Language Package extension governs how every one of those verses gets translated into Assamese for a destination culture whose dominant religious tradition (Assamese Hinduism generally, and Srimanta Sankardev’s Ekasarana Dharma specifically) has ready-made vocabulary for almost every key term in the letter — vocabulary that means something structurally different from what Jude asserts. Get the glossary wrong here and the letter’s central arguments (a closed, defensible deposit of faith; a genuinely eternal two-destinies judgment; Christ’s absolute, undivided ownership-authority; mercy as unilateral rescue) quietly collapse into their Ekasarana or Puranic counterparts. This document set exists to prevent that collapse before Phase 2 translation begins.

Key findings

• 22 curriculum doctrines identified across the full 25-verse book (no verse silently omitted): 7 Critical, 12 High, 2 Medium, 1 Low risk.
• 87 total glossary terms now govern Jude translation: 22 inherited exactly from the Romans baseline, 65 newly formalized for this letter — including two previously-missing proper nouns (Enoch, Michael) surfaced only during gap analysis.
• 43 of those 87 terms (18 Critical + 25 High) require mandatory human theologian review — roughly half the entire glossary, reflecting Jude’s unusually high doctrinal density for its length.
• 19 of the 22 doctrines route to human theologian review; only 2 route to native-speaker review and 1 to automated review alone.
• One baseline rule is being formally extended, not overridden: mercy (কৃপা), restricted in Romans to non-salvific use, must carry a salvific/eschatological sense in Jude 1:21’s “mercy… unto eternal life” — flagged for mandatory sign-off so the extension never silently leaks into non-Jude curricula.

Risks

• Highest-severity risk (ranked #1): অনন্ত/eternal terminology (eternal chains, eternal fire, eternal life, age) — 7+ occurrences — collides with Assamese Hindu/Ekasarana cyclical cosmology (সংসাৰ, yuga-cycles), which recognizes no genuinely endless, non-repeating outcome for anyone or anything.
• Structural risk: the letter’s five-fold “kept/guard” thread (1:1, 6, 13, 21, 24) must use one identical Assamese phrase throughout, or its deliberate literary argument (believers kept positively; rebel angels kept negatively; resolved in God’s keeping-power) is severed — a QA risk as much as a lexical one.
• Sharpest single Christological risk: Jude 1:4 stacks two absolute-authority titles on Christ (δεσπότης, κύριος); rendering the first as the natural-sounding স্বামী would assimilate Christ’s ownership-authority to the standard Assamese honorific for a Hindu monastic guru-teacher.
• Directional-inversion risk (unusually subtle): ψυχικός/“soulish” (প্ৰাণিক) names spiritual deficiency in Jude — the reverse of Assamese Vedantic vocabulary, where “soul” language trends toward the higher, liberation-seeking element of a person. A careless native-speaker reviewer could miss this without explicit briefing.
• Cult-source contamination risk: Jehovah’s Witnesses’ Assamese New World Translation identifies “Michael the archangel” (Jude 1:9) with the prehuman Jesus Christ, and teaches annihilationism at Jude’s “eternal fire” passages — both must be actively excluded from this curriculum’s notes and cross-references.
• Unresolved textual-critical decisions: Jude 1:5 (who saved the people from Egypt — the Lord, Jesus, or God) and Jude 1:22-23 (two-part vs. three-part mercy structure) remain open and require theologian selection before translation, not silent defaulting to a single comparison version.

Opportunities

• Several OT touchpoints (Sodom’s judgment, Israel’s wilderness unbelief, God’s ḥesed-like mercy) have genuine cross-tradition resonance with Jewish and Islamic frameworks and can be used as constructive teaching bridges without doctrinal compromise.
• The letter’s doxological form (stacked divine attributes: glory, majesty, might, authority) has a real poetic parallel in Assamese Vaishnavite nam-kirtan hymnody — an opportunity to teach the form of exalted praise while sharpening, rather than blurring, the object of that praise (the only God, through Jesus Christ our Lord, not a supreme deity within a devotional hierarchy).
• Because Jude is short and self-contained, its glossary and doctrine registries can be fully finalized and theologian-approved in a single review pass — a faster path to Phase 2 readiness than a longer book would allow.

Recommended actions

1. Secure mandatory theologian sign-off on all 12 baseline-extension/first-formalization items flagged in 08_core_glossary.md’s summary table before writing them into a locked translation_memory.json version 2.
2. Confirm the two unresolved textual-critical decisions (Jude 1:5 subject; Jude 1:22-23 structure) with the assigned theologian before any Phase 2 translation of those verses begins.
3. Lock the “kept/guard” (ৰক্ষা কৰি ৰখা) and “eternal” (অনন্ত) consistency rules as document-level, not segment-level, QA gates in Phase 2 Step 17 — per-segment review alone cannot catch a cross-verse consistency failure in a 25-verse book with this much repetition-dependent argumentation.
4. Brief every native-speaker and theologian reviewer explicitly on the প্ৰাণিক (soulish) directional-inversion risk before review begins; this is the one risk in the package most likely to be missed by a reviewer relying on ordinary Assamese linguistic intuition.
5. Verify the provisional YouVersion version ID (see 05_translation_landscape.md §6) against the live bible.com catalog before any Phase 2 automated hyperlink generation goes live.
6. Scope-lock the mercy (কৃপা) extension to Jude-only in the Phase 2 pipeline configuration, with an explicit automated check preventing its salvific sense from leaking into any Romans-curriculum segment reprocessed after this package is loaded.

---

This summary reflects Phase 1 Steps 1–8 outputs (semantic analysis, core glossary, comparative theology, linguistic gap analysis, translation landscape, doctrine analysis) and Steps 9–10 outputs (translation memory, AI translation requirements) produced for the Jude curriculum, all built to extend — and never contradict — the Romans Language Package baseline.