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: Kurdish (Kurmanji) Language Package for the Gospel of John

Why it matters

The Gospel of John is the New Testament’s most sustained, explicit argument for the deity of Christ — precisely the doctrinal territory where Kurdish-speaking audiences carry the most, and most varied, competing religious frameworks of any language in this pipeline: mainstream Sunni Islam, a historically deep Sufi mystical tradition, and two indigenous non-Islamic Kurdish religions (Yazidism, Yarsanism) found at meaningful scale nowhere else. John also concentrates this pipeline’s sharpest political-vocabulary collision risk: three separate doctrines (Kingdom of God, Freedom from Sin, Overcoming the World) each independently intersect a different strand of Kurdish nationalist-liberation language (padîşahî/statehood, azadî, serkeftin). Getting this Language Package right is the difference between John landing as Scripture and John being silently reheard as either Islamic apologetics, Sufi mysticism, or coded political speech.

Key findings

  • 28 doctrines analyzed across all 21 chapters, anchored by but not limited to the core passage (John 3:1-21), which alone touches 9 of the 28. No chapter was silently skipped; John 2 is explicitly documented as folded into adjacent doctrines rather than omitted.
  • 16 Critical-risk and 9 High-risk doctrines (25 of 28) require mandatory human theologian review — a substantially higher Critical proportion (64%) than the Romans baseline package (25%), reflecting John’s sustained Christological argument versus Romans’ more forensic-soteriological focus.
  • 104 total terms now under translation-memory enforcement for this curriculum: 33 terms inherited exactly from the Romans baseline package (God, Jesus, Lord, Son of God, Holy Spirit, Father, Resurrection, Salvation, Kingdom of God, Law, and 23 others), plus 71 new terms required by John’s distinctive vocabulary (the Word/Logos, the absolute and seven predicated “I Am” statements, New Birth, Eternal Life, the Paraclete, Unity of the Father and the Son, and more).
  • Of the 71 new terms, approximately 33 carry Critical or High risk tiers, requiring the same theologian-review routing as the doctrine registry.
  • Four source-language wordplays (anōthen’s above/again double sense; the wind/Spirit pun; the ēn/egeneto tense contrast; houtōs as manner not degree) have no Kurmanji lexical solution and are bridged entirely through mandatory translator’s notes rather than word choice — these sit inside or immediately adjacent to the core passage itself.

Risks

  • Political-vocabulary bleed (Critical, three-term cluster): Rizgarî (salvation), Padîşahiya Xwedê (Kingdom of God), Azadî (freedom, John 8), and Serkeftin (overcome, John 16:33) each independently risk being reheard as Kurdish nationalist-liberation rhetoric rather than personal, spiritual doctrine — a risk documented nowhere else in this pipeline at this density.
  • Double-direction Christological risk (Critical, four doctrines): Deity/Pre-existence, Incarnation, Sonship, and Unity of the Father and the Son each face two opposite misreadings at once — mainstream tawhid-based denial on one side, Sufi wahdat al-wujud / Yazidi divine-manifestation over-assimilation on the other. A translator’s note addressing only one direction is insufficient and must be flagged for revision.
  • Untranslatable core-passage wordplays: Nicodemus’s entire misunderstanding (3:4) depends on a Greek pun (anōthen) that collapses without a mandatory note; the same is true of the Spirit/wind analogy (3:8) central to Jesus’s teaching method in the anchor passage.
  • Severe offense risk: “Eat my flesh, drink my blood” (6:53-56), left unglossed, collides directly with blood-consumption taboos; “Word/Logos” (Peyv) will likely still evoke the Qur’anic Kalimatullah title regardless of the native-word strategy chosen.
  • Present-tense doctrine erosion: Eternal life (3:15-16,36; 5:24; 17:3) and judgment (3:18, “condemned already”) are both present-tense realities in John that the regional Islamic eschatological default (future-only paradise/Day of Judgment) will tend to silently convert to future-only framing if not actively resisted at every occurrence.

Opportunities

  • Kurdish pastoral/nomadic heritage gives the Good Shepherd (10:11), Lamb of God (1:29), and bread-of-life (6:35) imagery unusually strong, ready-made cultural resonance — genuine assets, provided the sacrificial/exclusive elements are not flattened by that same familiarity.
  • Kurdish/Zagros viticulture heritage similarly strengthens the True Vine “I Am” statement (15:1).
  • Native Kurdish vocabulary (Peyv, Xwedê, Bav) continues the Romans package’s finding that Kurdish is unusually well-resourced with non-Arabic-loan theological vocabulary compared to some neighboring languages in this pipeline — a genuine linguistic asset even where content-level teaching notes remain necessary.
  • Kurdish classical Sufi devotional poetry’s warmth register (Melayê Cizîrî, Ehmedê Xanî) can be responsibly borrowed for the Farewell Discourse’s (chs.14-17) relational tone, provided the lover/beloved metaphor is never substituted for the biblical Father/child or Shepherd/sheep metaphors.
  • Kurdish popular sentiment toward Israel, notably in Iraqi Kurdistan, remains more favorable than the regional norm, easing (without eliminating) the corporate-Jews disambiguation task inherent in John’s variable “Ioudaioi” usage.
  1. Load both the Romans baseline and John extension translation_memory.json / bible_term_registry.json / doctrine_risk_registry.json files together for every Phase 2 session; treat any value mismatch between the two files as a hard stop requiring theologian resolution.
  2. Enforce the five mandatory (non-optional) translator’s notes — absolute “I Am,” anōthen, the wind/Spirit pun, ēn/egeneto, and eat-flesh-drink-blood — as a hard validation gate before any segment is marked complete, regardless of repetition across chapters.
  3. Treat Rizgarî/Rizgar kirin, Padîşahiya Xwedê, Azadî, and Serkeftin as a single linked review cluster in Phase 2 Step 17 rather than reviewing each in isolation, since correcting one political-resonance risk can reintroduce another via a near-synonym.
  4. Require every Critical-tier double-direction doctrine (Deity/Pre-existence, Incarnation, Sonship, Unity of Father and Son) to carry explicit two-way theologian notes; reject single-direction notes at review.
  5. Prioritize John 3:1-21’s four untranslatable wordplays and John 20:31’s whole-book thesis statement as the first translator-training examples before Phase 2 batch processing begins, given their doctrinal density and cross-lesson consistency requirements.

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