Executive Summary — Mark 1–16 (English → Gujarati)

Why it matters

Mark is the Gospel where Jesus’ identity (Suffering Servant, Son of God, Son of Man) and his mission (the ransom for many) are stated in their most compressed, load-bearing form — nowhere more than in the core passage, Mark 10:35-45. Translating it into Gujarati means working directly on top of Gujarat’s two dominant living religious vocabularies — Vaishnav/Swaminarayan bhakti (devotee-service, guru-discipleship, romantic-devotional prem, avatar theology, centered on Dwarka) and Jain ascetic-karma metaphysics (self-effort liberation, jīva soul-substance, tapa austerity, cyclical hell-realms) — both of which supply fluent, natural-sounding Gujarati words that carry the wrong theology. This is not a hypothetical risk: it is the default outcome unless every Critical and High-risk term is actively fenced.

Key findings

• Doctrine-level risk (24 full-book doctrines, corrected per analysis/11_doctrine_analysis.md): 10 Critical, 13 High, 1 Medium, 0 Low. 23 of 24 doctrines require mandatory human theologian review; only 1 (Universal Mission to the Nations) requires native speaker review; zero doctrines are automated-review-only — a markedly higher-stakes profile than the Romans baseline.
• Term-level risk (new Mark-specific terms, per analysis/08_core_glossary.md and assets/bible_term_registry.json): 11 Critical, 14 High, 13 Medium, 10 Low new terms, in addition to 23 baseline Romans terms reused/extended (one of which, covenant, is elevated from High to Critical specifically for Mark’s 14:24 New Covenant institution).
• The single highest-stakes translation decision in the entire curriculum is જીવ (life/soul) in Mark 10:45: it is the exact Jain metaphysical term for jīva, the karma-bound soul-substance seeking self-attained liberation — and no substitute Gujarati word exists. The core passage also carries ખંડણી (ransom), ઘણાંઓને બદલે (substitutionary “for many”), and સેવક/દાસ (servant/slave) — four unavoidable lexical collisions concentrated in eleven verses.
• Mark’s collision profile differs structurally from Romans’: Romans collided mainly with Jain merit/karma vocabulary (justification, salvation). Mark collides evenly with both Jain ascetic-purity vocabulary (suffering, self-denial, defilement, Gehenna) and Vaishnav bhakti devotional vocabulary (servant, slave, teacher/guru, romantic prem) — because Mark’s central doctrine, servanthood modeled on the Suffering Servant, sits directly on Gujarat’s rich sevā/dāsa-bhāva devotional-service poetic tradition (Narsinh Mehta’s “Hari no Dās”).
• Chapters 8 and 10 are the priority-review chapters: Chapter 8 is the Peter’s-confession/first-passion-prediction/Messianic-Secret hinge; Chapter 10 is the core passage itself and carries the book’s highest cumulative linguistic-gap density (per analysis/06_linguistic_gap_analysis.md Section 5).
• Existing circulating Gujarati Bible translations do not solve these problems for us: both the formal (IRVGUJ) and common-language (ERV-GU) traditions render Gehenna as unqualified નરક, soften the ransom’s substitutionary force, and were not built with sustained attention to Jain doctrinal collision points.

Risks

• જીવ / ખંડણી / ઘણાંઓને બદલે (Mark 10:45): highest-severity risk in the curriculum; failure here collapses the ransom doctrine into either Jain self-liberation or a softened, non-substitutionary self-sacrifice ethic.
• સેવક / દાસ (9:35, 10:42-45): these are not neutral words needing an afterthought footnote — they are actively pulled toward bhakti’s merit-generating, status-elevating devotional-service register, the precise inversion of Jesus’ point.
• નરક vs. ગેહેન્ના (9:43-48): નરક is the natural, default Gujarati word and is used unqualified by every circulating translation surveyed; using it without a mandatory footnote imports a cyclical, self-regulating karmic-hell frame onto a final, personal divine judgment.
• ગુરુ pull on ઉપદેશક/પ્રેરિત: especially acute at Mark 10:35, where James and John address Jesus as “Teacher” at the exact opening of the ransom pericope.
• માનવપુત્ર (Son of Man, 11 occurrences): highest-frequency Critical term in the book; constant risk of flattening into “a mere human,” especially attractive to Jain-background readers.
• Doctrinal review capacity: 23 of 24 doctrines and roughly 25 of the highest-tier terms require mandatory human theologian sign-off — a substantially heavier Phase 2 review load than Romans, requiring resourcing before Phase 2 begins at scale.

Opportunities

• Mark 7:15-23 and 11:15-17/15:37-39 (heart-originating defilement; temple-access barrier removed by Christ’s death) offer unusually direct, pastorally resonant teaching moments in a Gujarati context where both caste- and community-based religious access restrictions and external-purity practice remain culturally live.
• Mark 12:28-34’s Great Commandment is an area of unusually strong convergence with Jewish tradition (direct Shema/Leviticus 19:18 citation) — a rare opportunity to teach continuity with, rather than only contrast against, a scriptural tradition, even as પ્રેમ must be fenced against bhakti’s romantic-mystical prem register.
• The already-completed Language Package infrastructure (semantic analysis, core glossary, term/doctrine registries, comparative theology, linguistic gap analysis, translation landscape survey) gives Phase 2 an unusually well-prepared foundation — every high-risk term already has a documented fencing strategy, not just a translated word.

Recommended actions

1. Lock assets/translation_memory.json (Mark) and this package’s forbidden-substitution list into Phase 2 tooling before any segment translation begins, with automatic rejection of ગુરુ, ભૂત, unqualified નરક, મુક્તિમૂલ્ય, દંડ, and તપ-family vocabulary for Christ’s suffering/self-denial.
2. Route Mark 10:35-45 for full-passage theologian sign-off, not merely term-level flags, given its unique concentration of unresolved collisions.
3. Prioritize Chapters 8 and 10 in the Phase 2 batch schedule, consistent with analysis/06_linguistic_gap_analysis.md’s ranked findings.
4. Mandate the footnote requirements specified in analysis/12_ai_translation_requirements.md for son_of_man, ransom, for_many, life_soul, “I am,” hell_gehenna, blasphemy_holy_spirit, servant, slave, and lord_it_over at every occurrence, with no discretionary exceptions.
5. Confirm the IRVGUJ YouVersion version_id against the live catalog before Phase 2 hyperlink generation is executed at scale (currently a placeholder per analysis/05_translation_landscape.md §5.1).
6. Resource theologian review capacity proportionate to the 23-of-24-doctrine review load identified above before scheduling Phase 2 throughput targets.

---

This summary synthesizes analysis/04_comparative_theology.md, analysis/05_translation_landscape.md, analysis/06_linguistic_gap_analysis.md, analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, analysis/11_doctrine_analysis.md, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, and assets/translation_memory.json. It does not introduce new doctrinal or lexical decisions; all figures are drawn directly from those artifacts.