Executive Summary — Mark (English → Nepali)

Why it matters

Mark is the Bible’s most action-driven Gospel — exorcisms, healings, a storm calmed, a crucifixion — and every one of those scenes lands in a Nepali cultural environment saturated with its own competing explanatory frameworks: jhankri shamanic exorcism, Hindu avatar-monarchy memory, karma-merit ethics, and a state legal code (the Muluki Ain, in force until 1963) that formally codified caste-linked purity and hierarchy. The core passage, Mark 10:35-45 — Jesus redefining greatness as servanthood and naming his death “a ransom for many” — sits at the exact intersection of the two riskiest vocabulary zones in this entire package: servant/slave language (सेवक/दास) inside Nepal’s bhakti-seva and caste-servitude history, and ransom language (फिरौती) that must be held apart from both Hindu मोक्ष and Buddhist निर्वाण. Getting this book wrong doesn’t just blur a doctrine — it risks quietly re-baptizing Jesus as one more guru-avatar-jhankri figure inside frameworks Mark’s own narrative is written to overturn.

Key findings

• 27 doctrines identified across Mark 1-16, extending the Romans baseline’s methodology; every chapter reviewed, none silently skipped (chapter 6’s sending of the Twelve and chapter 12’s widow’s mite, for example, are explicitly folded into adjacent doctrines rather than omitted).
• 105 glossary terms now tracked in translation_memory.json: 44 inherited exactly from the Romans baseline, 61 newly introduced by Mark’s narrative content (Son of Man, ransom, unclean spirit, servant/slave, Messianic Secret vocabulary, Aramaic performative speech, and more).
• 61 of those 105 terms are Critical (22) or High (39) risk — a majority of the glossary — reflecting how densely Mark’s narrative form repeats theologically loaded vocabulary (Son of Man alone recurs 14 times) compared to Romans’ more argumentative structure.
• The single sharpest new collision risk not present in Romans: jhankri shamanic exorcism-healing practice, a live, everyday Nepali explanatory and ritual framework that risks assimilating Jesus’ exorcism/healing narratives into “a powerful shaman” rather than unique demonstrations of divine authority.
• The core passage’s two central terms — सेवक/दास (servant/slave) and फिरौती (ransom) — are both new coinages/gap-fills for this package, each requiring active fencing against, respectively, Hindu bhakti guru-seva merit-devotion plus Nepal’s own documented caste-bonded-servitude history (kamaiya labor, abolished only in stages through the 20th century), and Hindu/Buddhist liberation-from-rebirth vocabulary.

Risks

• 9 Critical and 15 High doctrines (24 of 27 total) require mandatory human theologian review of every occurrence in Phase 2 — this is a higher proportion than typical for a narrative Gospel and reflects Mark’s dense concentration of Christological titles (Son of Man, Son of God, Beloved Son) sitting one verse apart from each other, where a single conflated rendering could blur two theologically distinct claims.
• 3 Medium doctrines (Marriage and Covenant Faithfulness; Temple Judgment and True Worship; Eschatological Watchfulness) require native speaker review; zero doctrines are rated Low — Mark has no doctrinally “safe” chapter.
• The Messianic Secret motif is a Mark-specific risk absent from Romans: रहस्य’s occupation by Tantric Hindu/Vajrayana Buddhist permanent-initiatory-secrecy connotations could recast Jesus’ strategic, temporary silence as a closed esoteric teaching.
• Evangelism/mission language (16:15-16,20) carries live legal exposure under Nepal’s 2017 Muluki Criminal Code conversion-restriction provisions — a concrete legal risk, not merely a social-sensitivity concern, and Mark 16:9-20’s disputed manuscript status must be tracked as a separate textual-critical fact from any translation-doctrine decision.

Opportunities

• Nepali’s existing loanword conventions already solved the hardest problem in the book: फिरौती (ransom) is a genuine linguistic gap filled by a doctrinally neutral, secular hostage-ransom term — a cleaner solution than any available religious vocabulary, and a template for how the pipeline should treat other atonement language going forward.
• क्रूस (cross), already an established Christian-specific loanword with zero indigenous religious collision, gives Mark’s cross-bearing discipleship material (8:34; 15:24-25) an unusually safe lexical foundation to build on.
• The book’s dense narrative repetition of key terms (faith/fear, authority, kingdom of God) is a teaching asset: consistent glossary enforcement across 16 chapters will reinforce vocabulary far more thoroughly for first-generation Nepali Christian readers than Romans’ more argumentative, less repetitive structure could.

Recommended actions

1. Load assets/translation_memory.json and analysis/12_ai_translation_requirements.md (Mark versions) for every Phase 2 segment, enforcing both the Romans-inherited and Mark-specific forbidden-substitution lists simultaneously.
2. Route all 24 Critical/High doctrine occurrences — and Mark 10:35-45 in its entirety regardless of individual term risk — to mandatory human theologian review before publication.
3. Brief theologian reviewers specifically on the jhankri-shamanic and Messianic-Secret/Tantric-initiatory collision risks, which have no direct analogue in the Romans baseline review process.
4. Carry the Mark 16:9-20 textual-critical note through Phase 2 and Phase 3 as a standing curriculum footnote, distinct from any doctrinal translation flag.