Log in

or use your email

Search the Library

Keyword search across Doctrine Analysis, Core Glossary, Comparative Theology, and Regional Analysis. Mention a language name for the best results — e.g. "remnant burmese" or "what glossary terms conflict for burmese."

Type at least 2 characters to search.

Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Download Translation Skill

Linguistic Gap Analysis

Linguistic Gap Analysis — Jude — English → Punjabi

PRD Phase 1, Step 8 Core passage (theological anchor): Jude 1:3–23 Scope mandate: This analysis covers the entire Letter of Jude (Jude 1:1–25). Jude is a single-chapter epistle; “full-book coverage” here means full-verse coverage, first verse to last. No verse range is treated as out of scope, even where a verse contributes no new vocabulary beyond what is already logged in the Core Glossary (08) and Term Registry — such verses are explicitly noted as reviewed, no new gap below rather than silently omitted.


0. Method and Relationship to the Romans Baseline

The Romans translation_memory.json and bible_term_registry.json remain the language authority. This analysis:

  1. Assumes every REUSE term listed in the Core Glossary (08) is already settled and does not re-argue it.
  2. Focuses on the gap between what the baseline glossary already covers and what Jude specifically requires — new terms, new doctrinal collocations of existing terms, and new collision risks that arise only because of Jude’s distinctive vocabulary (τηρέω, ἀσέβεια, δεσπότης, ψυχικός, ἔλεος as structural inclusio, etc.).
  3. Produces the four PRD-mandated deliverables: (A) doctrine vocabulary matrix, (B) missing-vocabulary vs. crowded-semantic-neighborhood fencing, (C) transliteration vs. paraphrase decisions, (D) ranked ambiguity list.

Jude is short (25 verses) but doctrinally dense and rhetorically repetitive by design (the fivefold ἀσεβ- root in vv.14–15; the fivefold τηρέω in vv.1, 6[×2], 13, 21, 24; the threefold OT type-catalogue in vv.5–7 and again in v.11). Punjabi’s gap profile for Jude is therefore less about finding words than about enforcing lexical discipline across repetitions and fencing off crowded semantic neighborhoods shared with Sikh devotional, Sant-tradition, and Khalsa martial-dharmic vocabulary — the same class of risk the Romans baseline documents, now concentrated in a much smaller textual space.


A. Doctrine Vocabulary Matrix

For each of the six curriculum doctrines: available Punjabi terms, their weaknesses, and the recommended strategy.

A.1 Contending for the Faith Once Delivered

AspectDetail
Primary passagesJude 1:3, 1:20
Available termsਨਿਹਚਾ [REUSE, High], ਨਿਹਚਾ ਦੀ ਰਾਖੀ ਲਈ ਜਤਨ ਕਰਨਾ [NEW, High], ਸੌਂਪੀ ਗਈ [NEW, Medium], ਇੱਕੋ ਵਾਰ [NEW, Medium], ਅੱਤ ਪਵਿੱਤਰ ਨਿਹਚਾ [NEW, High]
WeaknessesPunjabi has no single verb that cleanly isolates “contend” (ἐπαγωνίζεσθαι, an athletic-contest metaphor) from the martial register. The two nearest one-word candidates, ਲੜਨਾ and ਜੂਝਣਾ, both default in ordinary Punjabi religious-political usage toward fighting/struggling against an opponent, immediately activating ਧਰਮ ਯੁੱਧ (dharam yudh) and the Ardas line “ਰਾਜ ਕਰੇਗਾ ਖਾਲਸਾ” — a live, not merely historical, register in contemporary Punjab. There is also no idiomatic single word for “a fixed, closed deposit of teaching” (παραδοθείσῃ) that does not risk sounding like a legal contract (ਸਮਝੌਤਾ, already rejected at the baseline level for “covenant”) if mistranslated loosely.
Recommended strategyRetain the Core Glossary’s multi-word phrase ਨਿਹਚਾ ਦੀ ਰਾਖੀ ਲਈ ਜਤਨ ਕਰਨਾ (“to strive/labor for the protection of the faith”) rather than any single martial verb. The compound deliberately foregrounds defense of a possession (ਰਾਖੀ, “guarding/watching over”) over offensive struggle. Pair every occurrence of ਸੌਂਪੀ ਗਈ with a brief exegetical note that the “once for all delivered” body of teaching is a closed apostolic deposit — a genuine structural (not theological) parallel to the finality Punjabi Sikh hearers already associate with the Guru Granth Sahib, useful as a comprehension bridge but never presented as doctrinal equivalence.

A.2 Judgment on Ungodly False Teachers

AspectDetail
Primary passagesJude 1:4, 6, 8–13, 14–16, 18–19
Available termsਪਰਮੇਸ਼ੁਰ-ਹੀਣ / ਪਰਮੇਸ਼ੁਰ-ਹੀਣਤਾ [NEW, High], ਨਿਆਂ [NEW, High], ਸਦੀਪਕ ਅੱਗ [NEW, Critical], ਸ਼ੈਤਾਨ [NEW, High], ਪ੍ਰਭੁਤਾ [NEW, High], ਦੋਸ਼ੀ ਸਾਬਤ ਕਰਨਾ [NEW, Medium]
WeaknessesThe obvious root-transparent rendering of “ungodly” would be ਅਧਰਮੀ (built on ਧਰਮ). The baseline has already banned ਧਰਮ for “righteousness” precisely because of its Khalsa martial-dharmic resonance; ਅਧਰਮੀ as the direct antonym would reintroduce that exact frame into a doctrine (judgment on false teachers) that has nothing to do with dharam yudh. Punjabi also lacks a native abstract-noun pattern that mirrors Greek’s fivefold ἀσεβ- repetition in vv.14–15 without sounding stylistically repetitive to a Punjabi ear trained to vary vocabulary for elegance — translators will be tempted to smooth the repetition.
Recommended strategyBuild “ungodly” on the already-neutral ਪਰਮੇਸ਼ੁਰ root (ਪਰਮੇਸ਼ੁਰ-ਹੀਣ, “lacking/without God”) rather than the ਧਰਮ root, exactly as logged in the Term Registry. Explicitly instruct translators to retain the fivefold repetition in vv.14–15 rather than varying it for style — this is a Step-12 AI-instruction-level rule, not merely a glossary note, because the rhetorical hammering is Jude’s own device.

A.3 Old Testament Warnings as Types (Israel, Angels, Sodom)

AspectDetail
Primary passagesJude 1:5, 1:6, 1:7, 1:11
Available termsਮਿਸਰ, ਦੂਤ [NEW, Medium], ਸਦੂਮ ਅਤੇ ਅਮੂਰਾਹ [proper noun, Low], ਨਿਹਚਾ ਕਰਨਾ [NEW, High], ਬਚਾਉਣਾ [NEW, High], ਕਇਨ ਦਾ ਰਾਹ / ਬਿਲਆਮ ਦੀ ਭੁੱਲ / ਕੋਰਹ ਦਾ ਵਿਰੋਧ [proper nouns, Low]
WeaknessesThe target audience’s low Old Testament narrative literacy (already flagged at the baseline level for Romans) is more acute here: Jude alludes to six distinct OT episodes (Exodus/wilderness, fallen angels, Sodom, Cain, Balaam, Korah) in rapid, compressed succession across only seven verses, assuming the reader already knows each story. Punjabi has no shortage of adequate proper-noun transliterations; the gap is not lexical but pedagogical — bare transliteration without a background gloss will simply be opaque.
Recommended strategyTreat each of the six typological references as requiring a mandatory one-to-two-sentence background gloss in accompanying teaching material (not in the biblical text itself), flagged for native-speaker/theologian review as a content-delivery requirement rather than a translation-choice requirement. Ensure ਨਿਹਚਾ ਕਰਨਾ / ਬਚਾਉਣਾ in v.5 are read together as physical rescue followed by later unbelief and destruction — not as a loss of Christian ਮੁਕਤੀ, which is Critical-risk-adjacent territory needing explicit safeguarding (see D.2 below).

A.4 Mercy and Rescue of the Wavering

AspectDetail
Primary passagesJude 1:2, 1:21, 1:22–23
Available termsਦਯਾ [NEW, High], ਡੋਲਦੇ ਹੋਏ [NEW, Medium], ਅੱਗ ਵਿੱਚੋਂ ਖਿੱਚ ਕੇ ਬਚਾਉਣਾ [NEW, High], ਸਰੀਰ ਨਾਲ ਦਾਗੀ ਕੱਪੜਾ [NEW, Medium]
Weaknessesਦਯਾ (daya) sits inside a genuinely crowded semantic neighborhood: it is one of the Sikh Panj Gun (core cultivated virtues) that a devotee practices as personal ethical discipline, alongside sat (truth), santokh (contentment), and so on. This is a closer collision than most baseline entries, because unlike ਕਿਰਪਾ (already carefully fenced as flowing exclusively from Christ) or ਸੰਗਤ (a genuine positive bridge), ਦਯਾ in Sikh usage is primarily something a person does, not something God initiates toward the undeserving. Jude uses ἔλεος (mercy) as a deliberate three-verse inclusio (vv.21, 22, 23) framing God’s mercy in Christ’s return as the source, and believers’ mercy to one another as a derivative response — a theological structure easily lost if ਦਯਾ reads as free-floating human virtue.
Recommended strategyAnchor every occurrence of ਦਯਾ explicitly to its source: v.21 “awaiting the mercy of our Lord Jesus Christ” (ਪ੍ਰਭੂ ਦੀ ਦਯਾ) must never be rendered as if believers generate mercy themselves; vv.22–23’s mercy-to-others must be marked (via translator note, not text insertion) as derivative from v.21’s mercy, not an independent virtue-practice parallel to Panj Gun cultivation. This is a High-risk theologian-review item distinct from, and more acute than, the baseline’s ਕਿਰਪਾ fencing.

A.5 Kept by God and Presented Blameless

AspectDetail
Primary passagesJude 1:1, 1:6 (×2), 1:13, 1:21, 1:24
Available termsਸੁਰੱਖਿਅਤ ਰੱਖਿਆ ਹੋਇਆ / ਰੱਖਣਾ [NEW, Critical], ਆਪਣੇ ਆਪ ਨੂੰ ਪਰਮੇਸ਼ੁਰ ਦੇ ਪਿਆਰ ਵਿੱਚ ਰੱਖੋ [NEW, Critical], ਡਿੱਗਣ ਤੋਂ ਬਚਾਉਣ ਦੇ ਯੋਗ [NEW, Critical], ਨਿਰਦੋਸ਼ ਕਰਕੇ ਖੜ੍ਹਾ ਕਰਨਾ [NEW, Critical]
WeaknessesThis is the single largest genuine vocabulary gap in the entire curriculum, not merely a collision risk. English/Greek τηρέω does double duty across Jude as (a) God’s gracious preservation of believers for Christ (v.1), (b) God’s judicial confinement of fallen angels (v.6, twice) and of the darkness reserved for judgment (v.13), and (c) the human-responsibility imperative to keep oneself in God’s love (v.21), resolved by God’s own keeping ability (v.24). Punjabi has no single verb carrying all of “guard/preserve/keep in custody” with this range; ਬਚਾਉਣਾ (“save/rescue”) is tempting but collapses the preserve-nuance into the separate save-nuance (already used for σῴζω), destroying the epistle’s deliberate wordplay between judicial keeping and gracious keeping. There is likewise no Punjabi Christian precedent term for this structural device, since Romans (the baseline anchor) does not use τηρέω this way — Punjabi translators have zero prior-glossary support here and must build from first principles.
Recommended strategyAdopt ਸੁਰੱਖਿਅਤ ਰੱਖਿਆ ਹੋਇਆ (“kept secure”) / ਰੱਖਣਾ as the fixed rendering-family for every τηρέω occurrence (vv.1, 6×2, 13, 21, 24) without exception, explicitly overriding the natural translator instinct to vary vocabulary across five verses for style. This is the single highest-priority consistency rule for the entire Jude Language Package (see D.1).

A.6 Doxology and God’s Preserving Power

AspectDetail
Primary passagesJude 1:24–25
Available termsਮਹਿਮਾ [REUSE, High], ਸਮਰੱਥਾ [REUSE, High], ਮੁਕਤੀਦਾਤਾ [NEW, Critical], ਮਹਾਨਤਾ [NEW, Low], ਅਧਿਕਾਰ [NEW, Medium], ਸਦਾ ਤੋਂ, ਹੁਣ, ਅਤੇ ਸਦਾ ਲਈ [NEW, Medium]
WeaknessesNo missing vocabulary as such — every element has a workable Punjabi rendering — but the doxology compresses four distinct honorific ascriptions (glory/ਮਹਿਮਾ, majesty/ਮਹਾਨਤਾ, dominion/ਪ੍ਰਭੁਤਾ [note: v.8’s κυριότης, distinct from v.25’s fourfold list], power/ਸਮਰੱਥਾ, authority/ਅਧਿਕਾਰ) into a single verse, several sharing Punjabi roots close enough (ਮਹਿਮਾ/ਮਹਾਨਤਾ; ਪ੍ਰਭੁਤਾ/ਅਧਿਕਾਰ) that a translator under space pressure may be tempted to merge two into one, flattening Jude’s deliberately cumulative doxological climax.
Recommended strategyRender all four/five ascriptions distinctly and in full even though this produces a longer Punjabi sentence than idiomatic prose would otherwise favor; doxological fullness outweighs brevity here per the baseline’s Rule 1 (preserve every theological claim; do not minimize or compress). ਮੁਕਤੀਦਾਤਾ inherits ਮੁਕਤੀ’s mandatory Sikh/Christian distinction gloss, and “the only God, our Savior” must retain its exclusivist force without softening.

B. Missing Vocabulary vs. Crowded Semantic Neighborhoods (Fencing Requirements)

B.1 Genuinely Missing Vocabulary (no adequate existing Punjabi term; new coinage/compound required)

ConceptGapResolution
τηρέω’s five-fold structural range (preserve/guard/confine)No single Punjabi verb spans gracious keeping and judicial confinement the way τηρέω doesFixed compound ਸੁਰੱਖਿਅਤ ਰੱਖਿਆ ਹੋਇਆ / ਰੱਖਣਾ, enforced identically at all 5 occurrences (see A.5)
σπιλάδες (v.12, “hidden reefs” or “blemishes”)Genuinely double-meaning source term with no single Punjabi word covering both sensesRetain ambiguity via translator note (ਲੁਕੀਆਂ ਹੋਈਆਂ ਖ਼ਤਰਨਾਕ ਚਟਾਨਾਂ / ਦਾਗ); do not force a single reading — flagged per the baseline’s ambiguity-handling protocol
δεσπότης distinct from κύριος (v.4)Punjabi ਪ੍ਰਭੂ already fully occupies the κύριος/Lord slot; no second distinct honorific existed pre-Jude in this curriculumਮਾਲਕ, previously rejected only as a substitute for κύριος, is repurposed here for the genuinely distinct δεσπότης slot — a controlled, documented exception, not a contradiction of the baseline (see Term Registry master_sovereign)
ψυχικός vs. πνευματικός contrast (v.19)No existing Punjabi Christian technical term distinguishes “soul-governed, Spirit-absent” from ordinary “worldly” (ਸੰਸਾਰਕ)Compound ਆਤਮਾ ਤੋਂ ਬਿਨਾਂ ਸੰਸਾਰਕ ਸੁਭਾਅ ਵਾਲੇ explicitly names the absent-Spirit diagnosis rather than a vague “worldly”

B.2 Crowded Semantic Neighborhoods Requiring Active Fencing

These are cases where an adequate Punjabi term exists but sits close enough to a live, competing Sikh or Hindu concept that its use without an explicit boundary risks doctrinal blur — the same risk class the baseline documents for ਕਿਰਪਾ, ਮੁਕਤੀ, ਧਾਰਮਿਕਤਾ, etc.

Punjabi TermNeighboring ConceptDistanceFencing Required
ਦਯਾ (mercy)Panj Gun virtue of daya (Sikh cultivated personal ethic)Close — shares the exact lexical itemEvery occurrence must anchor mercy’s source in God/Christ’s initiative, never presented as a virtue independently cultivated by the believer (see A.4)
ਸ਼ੈਤਾਨ (devil, v.9)Sikh Haumai / Panj Vikar (internal-vice framework for “evil”)Moderate — different lexical item but risk of conceptual reabsorptionExplicit teaching-note framing ਸ਼ੈਤਾਨ as a real, personal, external adversary, not a symbol for inner moral struggle
ਸੌਂਪੀ ਗਈ (the faith once delivered, v.3)Guru Granth Sahib as closed, complete, eternal-Guru revelationStructural parallel, not lexicalUse the parallel only as a comprehension bridge for “closed deposit”; explicit note that the Bible does not occupy the same living-Guru revelation-structure role
ਪ੍ਰੇਮ-ਭੋਜ (love feasts, v.12)ਲੰਗਰ (Sikh communal-kitchen meal tradition)Close — genuine positive resonance, already logged as an OPPORTUNITY termUse to aid comprehension of shared table-fellowship; must not import langar’s seva-merit theology as the meal’s purpose
ਨਿਹਚਾ ਦੀ ਰਾਖੀ ਲਈ ਜਤਨ ਕਰਨਾ (contend, v.3)ਧਰਮ ਯੁੱਧ / Khalsa political-martial struggleClose — shared cultural register even without shared lexical rootNever render with ਲੜਨਾ/ਜੂਝਣਾ; the Core Glossary’s non-martial compound is mandatory, not stylistic
ਪਰਮੇਸ਼ੁਰ-ਹੀਣ (ungodly)ਧਰਮ / ਅਧਰਮੀ (Khalsa dharmic-martial righteousness frame)Close — the rejected alternative sits one morpheme awayਧਰਮ-root variants are absolutely forbidden here exactly as for “righteousness” in the baseline
ਦੇਹਧਾਰਨ-adjacent incarnation background (implicit in Jesus’ identity throughout Jude, though not a distinct doctrine term in this letter)ਅਵਤਾਰ (avatar-descent) / ਨਿਰੰਕਾਰ (Waheguru’s formlessness)Inherited from baselineNo new gap; baseline fencing applies unchanged wherever teaching materials touch Christ’s full deity and humanity in Jude 1:4, 21, 25

B.3 Vocabulary Present and Adequately Fenced Already (No New Gap — Reviewed)

The following recurring elements were reviewed across the full letter and found to require no new vocabulary decision beyond what the baseline and Core Glossary already settle: ਪ੍ਰਭੂ (Lord, vv.4,5,9,14,17,21,25), ਯਿਸੂ/ਮਸੀਹ (Jesus/Christ, throughout), ਪਰਮੇਸ਼ੁਰ (God, vv.1,4,21,25), ਪਵਿੱਤਰ ਆਤਮਾ (Holy Spirit, vv.19–20), ਪਵਿੱਤਰ ਲੋਕ (saints, vv.3,14), ਸੱਦਿਆ ਹੋਇਆ (called, v.1), ਸ਼ਾਂਤੀ (peace, v.2), ਕਿਰਪਾ (grace, v.4), ਪਾਪ/ਪਾਪੀ (sin/sinner, v.15), ਮਹਿਮਾ (glory, vv.8,24,25), ਸਮਰੱਥਾ (power, vv.24–25), ਸੰਗਤ-adjacent fellowship concepts (v.12’s underlying koinōnia), ਮੰਡਲੀ-adjacent church concept (vv.4,12,19), ਰਸੂਲ (apostle, v.17), ਮੂਸਾ/ਮਿਸਰ/ਆਦਮ/ਦਾਊਦ-class proper nouns.


C. Transliteration vs. Paraphrase Decisions

Jude presents an unusually high density of proper names and technical formulae in a very short text, requiring explicit per-item transliteration-vs-paraphrase rulings.

ItemDecisionRationale
ਯਹੂਦਾਹ (Jude, author name)Transliterate, with mandatory disambiguating note distinguishing from Judas IscariotThe Punjabi form is phonetically close to other biblical “Judah/Judas” names; confusion risk is real for a low-OT/NT-literacy audience
ਮੀਕਾਏਲ ਮਹਾਂ ਦੂਤ (Michael the archangel)Transliterate name + paraphrase title (ਮਹਾਂ ਦੂਤ, “great/chief angel”) rather than a loanwordNo existing Punjabi Christian precedent for “archangel” as a single word; the paraphrase is transparent and avoids inventing an opaque neologism
ਪ੍ਰਭੂ ਤੈਨੂੰ ਤਾੜੇ (“The Lord rebuke you,” v.9)Paraphrase in full sentence form, not compressedThis is a quoted formula of deferred judgment; compressing it risks losing its function as a citation of a known extra-biblical/Jewish tradition (the dispute over Moses’ body) rather than Jude’s own free composition
ਹਨੋਕ…ਭਵਿੱਖਬਾਣੀ ਕੀਤੀ (Enoch prophesied, vv.14–15)Transliterate name; paraphrase the citation as reported speech, with explicit non-canonicity noteMust not let smooth integration of the quotation imply 1 Enoch is canonical Scripture; the paraphrase should read as Jude citing Enoch, structurally parallel to how Punjabi Bible tradition already handles OT quotations within NT text
ਕਇਨ ਦਾ ਰਾਹ / ਬਿਲਆਮ ਦੀ ਭੁੱਲ / ਕੋਰਹ ਦਾ ਵਿਰੋਧ (the three OT type-names, v.11)Transliterate the proper names; paraphrase the accompanying noun (“way,” “error,” “rebellion”) rather than force a single Punjabi noun-pattern across all threeEach Greek noun (ὁδός/way, πλάνη/error, ἀντιλογία/rebellion) carries a distinct nuance about the nature of each figure’s sin; flattening all three into one repeated noun would lose Jude’s rhetorical variety here — the one place in the letter where variety is original and repetition would be the error
ਅੱਬਾ-class Aramaic/Hebrew loanwordsNot applicable in Jude (no Abba-equivalent occurs) — noted for completeness; no transliteration decision requiredReviewed, no new gap
ਆਮੀਨ (Amen, v.25)Transliterate, reusing baseline form exactlyEstablished liturgical convention
Σωτήρ → ਮੁਕਤੀਦਾਤਾ (Savior, v.25)Paraphrase/compound (not transliterate), built on ਮੁਕਤੀA loanword or transliteration (“Sotar”) would be opaque to Punjabi readers and forfeit the load-bearing connection to ਮੁਕਤੀ that the mandatory Sikh/Christian distinction gloss depends on
δεσπότης → ਮਾਲਕ (Master, v.4)Paraphrase using existing Punjabi vocabulary, not transliteration or loanwordਮਾਲਕ is common, transparent Punjabi; no reason to import a Greek loanword when a distinct-but-safe existing term is available (see B.1)

General principle applied: transliterate proper nouns and established liturgical formulae (names, ਆਮੀਨ); paraphrase theological-technical vocabulary using the Core Glossary’s compound strategy, following the same discipline the baseline applies to ਧਰਮੀ ਠਹਿਰਾਇਆ ਜਾਣਾ and ਲੇਖੇ ਲਾਈ ਧਾਰਮਿਕਤਾ (multi-word phrases preferred over single-word compression whenever a single Punjabi word would lose a load-bearing nuance).


D. Ranked List of This Letter’s Highest-Risk Ambiguities

Ranked by combined severity (doctrinal weight × likelihood of translator drift), highest first.

D.1 — CRITICAL: Inconsistent rendering of τηρέω (“keep/preserve”) across vv.1, 6(×2), 13, 21, 24

Jude’s entire theological architecture rests on the inclusio between believers “kept for Jesus Christ” (v.1) and God “able to keep [them] from stumbling” (v.24), with the judicial confinement of fallen angels and darkness (vv.6, 13) forming an ironic counter-pattern in between. If translators vary the Punjabi verb across these five occurrences for stylistic elegance (a strong natural pull in formal Punjabi prose), the reader loses the ability to perceive the pattern at all. Mitigation: hard-lock ਸੁਰੱਖਿਅਤ ਰੱਖਿਆ ਹੋਇਆ / ਰੱਖਣਾ across all five occurrences as a non-negotiable Step-12 AI instruction, validated at Step 17 review with a dedicated cross-reference check (not merely a general glossary-compliance check).

D.2 — CRITICAL: v.5’s “saved…yet destroyed for not believing” read as loss of Christian ਮੁਕਤੀ

Jude 1:5 recalls that the Lord “saved” (ਬਚਾਇਆ) a people out of Egypt who were later destroyed for unbelief. If this is not carefully distinguished from the baseline’s Critical-risk ਮੁਕਤੀ doctrine, a Punjabi reader could conclude either (a) that Christian salvation itself can be lost through later unbelief — a serious doctrinal distortion — or (b) conversely, given Sikh mukti’s gradualist, effort-dependent framework, that this passage confirms salvation as something maintained through ongoing meritorious performance. Mitigation: mandatory theologian-reviewed translator note at v.5 clarifying this is a historical Exodus-generation warning against presumption, addressed to those never savingly united to Christ by faith in the first place, not a description of a believer forfeiting the ਮੁਕਤੀ secured in Christ described elsewhere (vv.3, 21, 25).

D.3 — HIGH: ਦਯਾ (mercy, vv.21–23) collapsing into the Sikh Panj Gun virtue-practice framework

As detailed in A.4/B.2, this is a closer lexical collision than the baseline’s ਕਿਰਪਾ fencing, because Jude 1:22–23 explicitly commands believers to show mercy — creating real risk that ਦਯਾ reads as a human virtue to cultivate independently of its stated source (Christ’s own mercy, v.21) rather than a derivative overflow of it.

D.4 — HIGH: σπιλάδες (v.12) — genuine two-way ambiguity (“hidden reefs” vs. “blemishes/stains”)

Unlike most entries in this analysis, this is not a translator-drift risk but a genuine textual ambiguity inherited from the Greek itself. A single forced Punjabi rendering (either ਖ਼ਤਰਨਾਕ ਚਟਾਨਾਂ or ਦਾਗ alone) would silently resolve an ambiguity the original leaves open, misrepresenting the source text’s own uncertainty to reviewers and learners alike. Flagged per the baseline’s ambiguity-handling protocol for native-speaker review with both readings preserved in the translator note.

D.5 — HIGH: ਪਰਮੇਸ਼ੁਰ-ਹੀਣ (ungodly) drifting toward ਧਰਮ-root vocabulary under stylistic pressure

Because ਧਰਮ-based vocabulary is so lexically natural and abundant in Punjabi religious registers generally, a translator working quickly across Jude’s five-fold repetition in vv.14–15 may reach for ਅਧਰਮੀ purely for rhythmic variation, unknowingly reactivating the exact Khalsa martial-dharmic collision the baseline explicitly closed off for “righteousness.” This is a high-likelihood, high-severity drift risk precisely because it does not feel like a theological decision to the translator in the moment.

D.6 — HIGH: “Contend earnestly” (v.3) rendered with a martial verb under time pressure or back-translation smoothing

Similar drift risk to D.5: ਲੜਨਾ/ਜੂਝਣਾ are shorter, more idiomatic, and more “punchy” than the mandated compound ਨਿਹਚਾ ਦੀ ਰਾਖੀ ਲਈ ਜਤਨ ਕਰਨਾ, creating pressure to simplify in later editing passes (e.g., for a shorter subtitle or headline in study materials) in ways that would reintroduce the ਧਰਮ ਯੁੱਧ resonance the Core Glossary was designed to avoid.

D.7 — MEDIUM: ਮਾਲਕ (v.4, δεσπότης) being confused with the baseline’s blanket rejection of ਮਾਲਕ for κύριος

Because the baseline’s translation_memory.json explicitly lists ਮਾਲਕ as a rejected alternative for “Lord,” a translator or reviewer skimming the baseline without reading the Jude-specific Term Registry entry could flag v.4’s legitimate, intentional use of ਮਾਲਕ (for the distinct term δεσπότης) as a glossary violation. Mitigation: ensure Step-12 AI instructions explicitly carve out this one controlled exception with its Greek-term justification, so automated validation does not false-flag it.

D.8 — MEDIUM: κυριότης (dominion, v.8) vs. the fourfold doxological ascriptions of v.25

ਪ੍ਰਭੁਤਾ (v.8) and the v.25 doxology’s ਅਧਿਕਾਰ (authority) share enough conceptual overlap (“lordship-adjacent power”) that a translator could conflate them into a single term across the letter, losing the fact that Jude uses two distinct Greek words (κυριότης, ἐξουσία) for two distinct rhetorical purposes — one describing what the false teachers reject (v.8), the other ascribed in worship to God (v.25).

D.9 — LOW-MEDIUM: OT type-figure background gaps (Cain, Balaam, Korah, Sodom, the Exodus generation, fallen angels) compressed into six brief allusions across vv.5–7 and v.11

Not a translation-choice ambiguity but a comprehension gap: the letter assumes narrative knowledge the target audience largely lacks. Risk is pedagogical delivery failure rather than doctrinal distortion, provided the required background glosses (see A.3) are supplied in accompanying teaching material.


Summary Table: Gap Severity Overview

RankIssueTypeSeverity
1τηρέω consistency (5 occurrences)Missing vocabulary / consistency disciplineCritical
2v.5 “saved yet destroyed” vs. Christian ਮੁਕਤੀDoctrinal collisionCritical
3ਦਯਾ vs. Panj Gun virtue frameworkCrowded semantic neighborhoodHigh
4σπιλάδες genuine ambiguitySource-text ambiguityHigh
5ਪਰਮੇਸ਼ੁਰ-ਹੀਣ vs. ਧਰਮ-root driftCrowded semantic neighborhoodHigh
6”Contend earnestly” martial-verb driftCrowded semantic neighborhoodHigh
7ਮਾਲਕ false-flag risk (δεσπότης vs. κύριος)Process/validation riskMedium
8κυριότης vs. ἐξουσία conflationTerminological precisionMedium
9OT type-figure background gapsPedagogical gapLow-Medium

This analysis extends but does not alter the baseline Romans translation_memory.json and bible_term_registry.json. All NEW terms proposed in the Core Glossary (08) and Term Registry entries referenced here must be merged into translation_memory.json (version increment) before Phase 2 segment translation of Jude begins, per the baseline’s Translation Memory Load and Enforcement Instructions. See 08_core_glossary.md for the full term inventory and [assets/bible_term_registry.json] for per-term doctrinal definitions underlying this analysis.

Library content is free and openly licensed under CC BY-NC-SA 4.0 — share and adapt it for non-commercial use, with attribution to tri-bible.ai.

Give feedback

How would you rate this page?

0 / 500 words