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

John — persian

TRI knowledge bundle for John (persian).

Executive Summary

Executive Summary: Gospel of John Language Package (English → Persian)

Why it matters

The Gospel of John carries the New Testament’s densest concentration of direct, explicit deity-of-Christ claims (the Logos, the seven “I Am” sayings, “I and the Father are one,” “My Lord and my God”) — and Persian’s dominant religious frame is Twelver Shia Islam, whose tawhid doctrine treats exactly these claims as the paradigm case of shirk. This curriculum’s core passage, John 3:1-21, adds a second acute risk on top of that: the new birth “of water and the Spirit” collides with two independent Persian ritual-purification defaults (Islamic wudu/ghusl, Zoroastrian water-purity rite), and its present-tense judgment claim (“already condemned”) runs directly against the Islamic mizan deeds-weighing framework that defers all verdicts to the Last Day. Getting this book right for Iranian and Afghan house-church, Muslim-background readers is higher-stakes than Romans on almost every Christological axis.

Key findings

  • 89 total terms now govern Phase 2 translation for John: 31 inherited unchanged from the Romans baseline and 58 new John-specific terms, all seeded into assets/translation_memory.json.
  • Of those 89 terms, 65 (31 Critical + 34 High) — roughly 73% — require human theologian review before first use, per the priority-order rules in analysis/12_ai_translation_requirements.md.
  • At the doctrine level, assets/doctrine_risk_registry.json (John) records 37 doctrines: 15 Critical, 15 High, 5 Medium, 2 Low30 of 37 (81%) require human theologian review, versus 5 requiring native speaker review and 2 automated-only.
  • John introduces two entirely new categories of risk not present in the Romans baseline: (1) a documented, live Persian/Shia apologetic tradition identifying the Paraclete with a predicted Muhammad (disputed παράκλητος/περικλυτός etymology), and (2) two structurally untranslatable Greek wordplays central to the core passage (ánōthen’s “again”/“from above” double sense; the πνεῦμα/πνέω wind-spirit pun), neither of which can be resolved by better word choice and both require mandatory translator notes.
  • The single highest-stakes term identified across the whole book is the absolute ἐγώ εἰμι (“I am,” من هستم), which collides directly with the Avicennan/Islamic philosophical category of wājib al-wujūd (necessary self-existence reserved for God alone) and underlies all seven predicated “I Am” statements.

Risks

  • Theological dilution risk: the documented Hezare No controversy (softened “Son of God” rendering, provoking Iranian house-church backlash) is a live precedent; John’s μονογενής (“only begotten,” یگانه) and the absolute “I AM” are exactly the kind of terms a well-meaning translator might instinctively soften — this must be actively resisted per the forbidden-substitutions list.
  • Syncretism risk: Lamb of God, “it is finished,” and “Savior of the world” all sit adjacent to the Karbala/Hussein martyrdom-intercession devotional pattern, which is a categorically distinct, popularly central Shia practice, not merely a weaker analogue — mistranslation here risks Christ’s atonement being read as one devotional pattern among others rather than unique and sufficient.
  • Untranslatable wordplay risk: three Greek double-meanings (ánōthen, πνεῦμα/πνέω, ὑψωθῆναι) have no Persian lexical solution; silent resolution in Phase 2 output would flatten the core passage’s own narrative pedagogy (Nicodemus’s modeled misunderstanding) and must be caught by mandatory translator notes, not left to translator discretion.
  • Consistency risk at scale: κόσμος (“world,” جهان) occurs roughly 78 times across three distinct senses; without per-occurrence sense-tagging before batch processing, parallel Phase 2 workers risk producing inconsistent disambiguation.

Opportunities

  • Worship in Spirit and Truth (John 4:20-24) offers a constructive, non-polemical bridge into Shia shrine-pilgrimage piety (Karbala, Mashhad) by teaching that true worship was never fundamentally about location — an invitation rather than a confrontation.
  • Overcoming the World (John 16:33) offers a genuine bridge to Shia victory-through-suffering devotional intuition (Hussein’s martyrdom as spiritual triumph despite apparent defeat), provided Christ’s victory is taught as unique and cosmic rather than one more instance of righteous martyrdom.
  • Persian’s native, pre-Islamic vocabulary (خدا, خداوند, حیات) continues to give this Language Package a genuine asset the Arabic-language pipeline lacks: these terms are not Quranic loanwords and can be filled with Christian content without first dislodging an entrenched competing religious ownership of the word itself.
  1. Lock assets/translation_memory.json (John edition, v2) and assets/bible_term_registry.json (John edition) as the enforced baseline before any Phase 2 segment work begins; do not permit ad hoc term substitution.
  2. Route all 30 theologian-review doctrines and all 65 Critical/High terms through human theologian review before first Phase 2 use, per the escalation rules in analysis/12_ai_translation_requirements.md.
  3. Pre-annotate κόσμος (“world”) sense per occurrence in source-segment metadata before translation begins, rather than leaving disambiguation to per-segment translator judgment.
  4. Batch-lock the John-specific proper-noun table (Nicodemus, Bethesda, Siloam, Golgotha, etc.) into translation memory before parallel chapter-level Phase 2 workers begin, to prevent inconsistent spellings.
  5. Brief all reviewers explicitly on the Paraclete/periklytos-Muhammad apologetic tradition and the Karbala/Hussein martyrdom-intercession pattern before John 1, 4, 14-16, and 19 review passes — these are the two most distinctively John-specific (as opposed to generic Romans-baseline) risk categories in the entire book.

See analysis/11_doctrine_analysis.md for the full doctrine matrix and chapter-by-chapter coverage trace, analysis/06_linguistic_gap_analysis.md for the underlying linguistic gap analysis, and analysis/12_ai_translation_requirements.md for the enforced Phase 2 instruction set.

View full executive summary page →

Culture Impact Analysis

Doctrines

Glossary

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