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: 3 John (English → Nepali)

Why it matters

3 John is 14 verses long — and per doctrine density relative to length, it is one of the highest-risk books in this pipeline. A single personal letter concentrates two Critical-risk doctrines and six High-risk doctrines into one chapter, several turning on a single clause or a single rare Greek word with no ready Nepali equivalent. Nepal’s specific religious landscape — Hindu Kingdom history, caste hierarchy formally codified until 1963, living Newar Tantric and Himalayan Buddhist practice, and a young, once-restricted church — means several of this letter’s most ordinary-sounding words (सत्य, प्रेम, आत्मा, योग्य, अतिथि) sit on genuinely contested theological ground. Getting this short letter wrong is easy; getting it right requires the same rigor as a full epistle.

Key findings

  • Doctrine risk: 10 doctrines identified across the full book (all 14 verses reviewed; none silently omitted). 2 Critical + 6 High = 8 of 10 doctrines require mandatory human theologian review — 80% of this book’s doctrinal content, a notably higher proportion than typical for this pipeline given the letter’s short length and doctrinal density.
  • Term risk: Of 39 book-specific terms captured in the extended glossary, 2 are Critical and 9 are High — 11 of 39 terms (28%) require theologian-level scrutiny, plus 4 inherited-Critical baseline terms (परमेश्वर, पवित्र आत्मा, येशू, प्रभु) held in reserve for cross-references.
  • The single highest-risk item in the whole book: 3 John 1:11’s “the one who does good is of God” is exceptionally exposed to a पुण्य (merit-accumulation) misreading shared by both Nepali Hindu and Buddhist ethical frameworks — the same collision the baseline already flags for “grace,” now surfacing in a new, grammatically vulnerable form.
  • A second, distinct Critical collision: 3 John 1:2’s “soul” (ψυχή) cannot use आत्मा without simultaneously colliding with (a) the reserved Holy-Spirit term, (b) Hindu Vedantic Ātman doctrine, and (c) Buddhist अनात्मन् (no-self) teaching — a triple collision resolved by adopting प्राण instead.
  • 3 John introduces vocabulary largely absent from the Romans baseline: technical hospitality-partnership terms (προπέμπω, ἀξίως τοῦ θεοῦ, ὑπολαμβάνω vs. ἐπιδέχομαι) and institutional leadership-abuse terms (φιλοπρωτεύων, ἐκβάλλω), several requiring coined compound phrases since no single Nepali word exists.

Risks

  • Merit-theology collision (Critical): 1:11’s “is of God” clause and, more broadly, any teaching on good works risk being heard as पुण्य-style merit accumulation rather than fruit of an existing relationship with God.
  • Anthropology collision (Critical): Any lapse into आत्मा for “soul” would simultaneously blur the Trinity (confusing “soul” with the Holy Spirit) and import Hindu/Buddhist self-doctrines foreign to the text.
  • Caste-worthiness collision (High): “Worthy of God” (1:6) is vulnerable to Nepal’s own legally-codified worthiness-by-birth history (the 1854 Muluki Ain) if रendered without an explicit anchor to God’s character.
  • Ritual-authority collision (High): “Elder” (1:1) risks drifting toward गुरु/पुरोहित/लामा status categories — hereditary, ritual, or reincarnate-lineage authority foreign to this letter’s functional, servant-shaped, correctable office.
  • Cultural-maxim collision (High): Nepal’s actively promoted “अतिथि देवो भव” hospitality maxim is a ready-made, culturally prestigious wrong frame for 1:5-8 that a translator could import unconsciously, precisely because it “sounds right.”
  • Ritual-vision collision (High): “Has not seen God” (1:11) risks being read through दर्शन, the still-practiced weekly devotional viewing of a deity’s image at shrines such as Pashupatinath.
  • Under-translation risk (High): “Cast out” (1:10) and “loves to be first” (1:9) both risk being softened or read as neutral leadership behavior rather than named sin, given Nepal’s pronounced rank/seniority-consciousness.

Opportunities

  • 3 John’s warm, personal register is well-suited to a young, relationally-oriented Nepali church audience; सहभागिता-style fellowship language, already emotionally weighted from the Romans package’s own notes on the church’s history of legal restriction, can be extended naturally here.
  • The letter’s built-in contrastive structure (Gaius/Demetrius vs. Diotrephes) offers a strong teaching hook for distinguishing biblical servant-leadership from both Nepali social-rank assumptions and hereditary/ritual religious-authority models.
  • Because 3 John shares no direct vocabulary overlap with 2 John apart from the “elder” self-designation, this Language Package establishes a reusable precedent (प्राचीन, गवाही दिनु, अतिथि-framing caution) for any future Johannine-letter curriculum added to this pipeline.
  1. Route all 8 Critical/High-risk doctrines (per assets/doctrine_risk_registry.json) through mandatory human theologian review before Phase 2 segment approval — no exceptions, especially for 1:11.
  2. Enforce the book-specific forbidden-substitution list (आत्मा, कर्म, दर्शन-family nouns, भक्ति, गुरु/पुरोहित/लामा, विश्वासी, नमस्कार) at automated validation, per analysis/12_ai_translation_requirements.md.
  3. Require mandatory [TRANSLATOR NOTE] fencing at first occurrence of सत्य, प्रेम, प्राण, and the “is of God” clause in every Phase 2 segment, even though these are not lexical innovations, because the risk is contextual/theological rather than vocabulary-level.
  4. Validate structural consistency automatically, not just via glossary lookup: गवाही दिनु/गवाही across all six occurrences (1:3, 1:6, 1:12 x3) and स्वीकार गर्नु across both negative occurrences (1:9, 1:10).
  5. Brief native speaker reviewers specifically on the “अतिथि देवो भव” and दर्शन collision risks before hospitality- and leadership-themed lessons enter Phase 2, since these are cultural default-frames rather than obvious mistranslations and are the likeliest errors to pass an inattentive review.

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