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

Executive Summary

Executive Summary — Jude Language Package (Kurdish)

Phase 1, Step 11 Deliverable

Curriculum: Jude (single-chapter, 25-verse epistle) Core passage: Jude 1:3–23 Destination language: Kurdish (Kurmanji dialect, Latin script) Extends: Romans baseline Language Package (does not contradict it)


Why it matters

Jude is short but doctrinally dense: 25 verses generate 17 distinct doctrines and roughly 64 tracked theological terms, a load-bearing density higher per-verse than the Romans baseline. Two of the letter’s central vocabulary choices — “contend” (Têkoşîn kirin) and “kept/preserved” (Parastin) — carry risks specific to Kurdish that do not have a close Romans analog: one collides directly with the region’s defining political-liberation vocabulary and Islamic jihad-adjacent language, the other is a single verb whose consistent, invariant use across five scattered verses IS the letter’s own theological argument. A single inconsistent rendering of either term silently breaks doctrine that a reviewer checking any one verse in isolation would not detect.

Key findings

  • 12 Critical-risk and 26 High-risk terms (38 of 64 tracked terms, ~59%) require human theologian review under the Jude-specific bible_term_registry.json — a higher Critical/High proportion than the Romans baseline.
  • 7 of 17 doctrines are Critical-risk and 6 are High-risk (13 of 17, ~76%, route to mandatory human theologian review; 3 to native speaker review; 1 automated-only) per doctrine_risk_registry.json.
  • Jude introduces a genuinely new risk category absent from the Romans package: real-world legal/safety exposure. “Blaspheme” (Heqaretkirin) is Critical not only theologically but because blasphemy carries live criminal and social consequences in several of the four Kurdish-populated states, especially Iran — this term requires dual theological-AND-safety review at every occurrence.
  • Jude’s Christology moment (1:4’s stacked “Master and Lord,” δεσπότης + κύριος) requires a genuinely new second Kurdish title, “Serwer,” alongside the already-Critical “Xudan” — collapsing them into one word would flatten the letter’s own rebuke of the false teachers who deny exactly this double claim.
  • Three Old Testament/Qur’anic-shared narratives (Cain/Qabîl, Sodom/Qawmê Lût, Korah/Qarun) are genuine comprehension assets, while fallen-angel doctrine (1:6) is a genuine comprehension liability against mainstream Islamic angelology’s sinless-angels premise — both cut against the region’s default theology in opposite directions within the same short passage (vv.5-11).
  • The letter’s pastoral climax (vv.22-23, “mercy … snatch from the fire”) must sharply distinguish wavering believers (Dudilan) from the condemned false teachers denounced throughout — a distinction with no Romans precedent to build on, since Romans has no equivalent “insider-in-danger” pastoral category.

Risks

  • Political misreading of the thesis verb (1:3): “Têkoşîn kirin” (contend), left unqualified, risks the entire letter being heard as a call to Kurdish political or armed struggle rather than steadfast doctrinal defense — the single highest-severity risk identified in this package.
  • Silent doctrinal collapse via inconsistent verb choice: “Parastin” (kept/preserved) must render τηρέω identically at all five occurrences (1:1, 1:6, 1:13, 1:21, 1:24); any drift erases Jude’s own wordplay that the same divine “keeping” underlies both judgment and preservation, and this failure mode is invisible to segment-by-segment review.
  • Legal/safety exposure: improper rendering of “blaspheme” using an Arabic-cognate “kufr”-adjacent term could expose translators, reviewers, or end users to real blasphemy-law jeopardy in some of the four host states.
  • Political anchoring drift in the doxology (1:25): “Rizgarker” (Savior) and “Desthilatdarî” (dominion/authority) both sit inside the Kurdish nationalist-political vocabulary field already flagged in the Romans baseline; unanchored use in the letter’s most quotable, most-memorized verse compounds this risk beyond its Romans-baseline severity.
  • Category confusion between judged and rescued groups: conflating the “ungodly” false teachers (1:4-19) with the “wavering” believers (1:22-23) would invert Jude’s carefully graduated pastoral response.

Opportunities

  • Cain, Korah (as Qarun), and Sodom and Gomorrah (as Qawmê Lût) are strong, genuinely shared Qur’anic narrative parallels that can be leveraged for audience comprehension with only light narrative-difference framing required.
  • Mîkaîl (archangel Michael) and Îblîs (the devil) are recognized Qur’anic figures offering a real entry point for teaching, provided their distinct Jude-specific narrative content (the Moses’-body dispute) is explicitly introduced rather than assumed.
  • Kurdish classical Sufi mystical-love poetry (Melayê Cizîrî, Ehmedê Xanî) offers a genuine warmth resource for the letter’s affectionate opening and closing sections (1:1-3, 20-23), consistent with the same asset already identified for Romans 8 and 12.
  • The native compound “Dilovanî” (mercy) avoids the Arabic-cognate “rehm’s” dilution into the generic Islamic Rahman/Rahim attribute, giving Jude’s mercy-toward-waverers passage a term cleanly anchored to Christ’s specific saving compassion.
  1. Adopt assets/translation_memory.json (version 2) and the Jude-specific bible_term_registry.json/doctrine_risk_registry.json as mandatory pre-flight loads for all Phase 2 Jude segment processing, per analysis/12_ai_translation_requirements.md.
  2. Mandate a dedicated cross-occurrence consistency reconciliation pass for “Parastin” and “Bêxweda/Bêxwedatî” after parallel Phase 2 processing completes and before Step 17 review, given Jude’s short length makes single-worker assignment a viable alternative mitigation.
  3. Route all blasphemy-vocabulary segments (1:8, 1:9, 1:10, 1:15) through BOTH theological and safety review, not theological review alone.
  4. Require a documented translator decision (not a silent tool default) at the Jude 1:5 textual variant and at the Jude 1:9/1:14-15 extra-biblical citations.
  5. Prioritize theologian review time, where constrained, using the ranked ambiguity list in 06_linguistic_gap_analysis.md §4 (Têkoşîn kirin, Parastin, Heqaretkirin, Rizgarî-family anchoring, Serwer/Xudan stacking, and Desthilatdarî, in that order).

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