Executive Summary — Jude — English → Punjabi

Why it matters

Jude is a short, single-chapter, doctrinally dense epistle whose central pastoral argument — that believers are actively “kept” by God while actively responsible to “keep themselves” — depends on a single recurring Greek verb (τηρέω) appearing six times across just 25 verses. Punjabi has no Bible-translation precedent for this pattern (Romans, the baseline anchor, does not use it this way), so this curriculum requires new, first-principles translation infrastructure layered on top of — never contradicting — the established Romans Language Package. Punjab’s dual religious landscape (Sikh-majority, Hindu-minority, in a Gurmukhi-script context) also means several of Jude’s own distinctive terms (ਦਯਾ/mercy, ਪਰਮੇਸ਼ੁਰ-ਹੀਣ/ungodly, ਸ਼ੈਤਾਨ/devil) sit closer to live, competing theological frameworks than most Romans-baseline vocabulary did.

Key findings

• Full-book coverage confirmed: all 25 verses of Jude’s single chapter have been analyzed verse-by-verse (semantic analysis, glossary, term registry, doctrine registry, doctrine analysis, linguistic gap analysis); no section was silently omitted.
• 20 curriculum doctrines identified, spanning the whole letter, not only the core passage (Jude 1:3–23): 5 Critical, 13 High, 2 Medium, 0 Low.
• 18 doctrines require mandatory human theologian review; 2 require native speaker review; 0 are automated-only — a notably higher theologian-review proportion (90% of doctrines) than typical for this pipeline, reflecting Jude’s compressed doctrinal density.
• 79 terms are logged in assets/translation_memory.json: 17 Critical-risk, 25 High-risk, 20 Medium-risk, 17 Low-risk. The 42 Critical+High terms (53% of the glossary) require mandatory theologian review at every occurrence.
• One genuinely new consistency requirement not present in the Romans baseline: τηρέω (“keep/kept”) must receive matching Punjabi phrasing at all six occurrences (1:1, 1:6 ×2, 1:13, 1:21, 1:24) to preserve Jude’s central literary inclusio — flagged as the single highest-priority translation rule in this package.
• One genuine source-text ambiguity (σπιλάδες, 1:12, “hidden reefs” or “blemishes”) must be preserved rather than resolved, per the baseline’s ambiguity-handling protocol.

Risks

• Critical: Confusing Jude 1:5’s Exodus-generation warning (“saved…yet destroyed for unbelief”) with loss of Christian salvation, or reading it as confirming a Sikh gradualist, merit-maintained mukti framework.
• Critical: Inconsistent τηρέω rendering across its six occurrences, erasing the epistle’s central theological architecture (gracious keeping vs. judicial confinement).
• High: Rendering “ungodly” (ἀσεβής) with the tempting root-transparent ਅਧਰਮੀ, which would reactivate the Khalsa martial-dharmic (ਧਰਮ ਯੁੱਧ) collision the baseline already closed off for “righteousness” — now the first time this discipline extends to a negative theological term.
• High: ਦਯਾ (mercy) collapsing into the Sikh Panj Gun tradition’s framing of daya as an independently cultivated personal virtue, rather than God/Christ’s initiating compassion reflected derivatively among believers.
• High: Rendering “contend earnestly for the faith” (1:3) with a martial verb (ਲੜਨਾ/ਜੂਝਣਾ), inviting a hearing of communal-religious struggle (Khalsa Raj aspiration) rather than steadfast doctrinal defense.
• High: ਸ਼ੈਤਾਨ (the devil, 1:9) being absorbed into Sikh theology’s internal-vice framework (Haumai/Panj Vikar) rather than understood as a real, personal, external adversary.
• Medium: Jude’s six compressed Old Testament allusions (Exodus, fallen angels, Sodom, Cain, Balaam, Korah) in vv.5–7, 11 outrunning the target audience’s low shared OT narrative literacy without mandatory background glosses.

Opportunities

• ਪ੍ਰੇਮ-ਭੋਜ (love feasts, 1:12) has genuine positive resonance with ਲੰਗਰ, the Sikh communal-kitchen tradition, offering a natural comprehension bridge for shared table-fellowship — provided it is not allowed to import langar’s seva-merit theology.
• ਸੌਂਪੀ ਗਈ (the faith “once for all delivered,” 1:3) has a structural (not theological) parallel to the Sikh community’s reverence for the closed, complete Guru Granth Sahib, usable to help explain the concept of a fixed apostolic deposit.
• ਦਾਸ (servant, 1:1) as Jude’s humble self-designation has broad positive resonance in Punjabi devotional culture generally, a low-risk, natural-fit term.
• δεσπότης handled as ਮਾਲਕ (1:4) demonstrates the glossary’s capacity for controlled, documented exceptions to baseline forbidden-substitution rules without weakening the rules themselves — a template other curricula in this pipeline can reuse when a genuinely distinct source term arises.

Recommended actions

1. Merge assets/translation_memory.json (this curriculum, v1) into the Phase 2 enforcement pipeline alongside the Romans baseline TM before any segment translation begins; do not treat the two as competing sources.
2. Lock the τηρέω rendering (ਸੁਰੱਖਿਅਤ ਰੱਖਿਆ ਹੋਇਆ / ਰੱਖਣਾ) and the ਦਯਾ source-anchoring requirement as pre-translation decisions, confirmed across all six/four occurrences respectively, before any individual segment in either family is finalized.
3. Route all 18 theologian-review doctrines and all 42 Critical/High terms through mandatory human theologian review per assets/doctrine_risk_registry.json and assets/bible_term_registry.json; do not allow automated-only approval for any of them.
4. Commission the six OT-background explanatory notes (Exodus generation, fallen angels, Sodom, Cain, Balaam, Korah) as accompanying teaching material, not inserted into the translated biblical text itself.
5. Load analysis/12_ai_translation_requirements.md (this curriculum’s extension) together with the Romans baseline requirements document at every Phase 2 translation session; the two are additive, not alternatives.