Executive Summary — Mark Hindi Language Package

Why it matters

The Gospel of Mark is being added to the Hindi Bible Study Translation Requirements Interface, anchored at Mark 10:35-45 (James and John’s request; the ransom saying) and spanning all eight assigned doctrines across the entire book (chapters 1–16). This curriculum introduces the single highest-stakes new doctrinal term in the Hindi Language Package to date — the ransom for many (छुटकारे का दाम) — alongside a paradoxical, caste-sensitive reworking of servanthood language (सेवक/दास) that must be handled with the same rigor the baseline applied to Galatians’ freedom (स्वतंत्रता) terminology. Getting this package right protects Mark’s central claim — that Jesus is the divine Son who reveals his glory precisely through suffering and service, not despite it — from being flattened by India’s dominant religious vocabulary (avatar-descent, guru-disciple transmission, karma-fruit, caste-purity, and self-attained liberation).

Key findings

• Full-book coverage confirmed. All 16 chapters were reviewed chapter-by-chapter (semantic analysis, glossary, doctrine matrix, comparative theology, linguistic gaps, translation landscape); no chapter contributes zero doctrinal content, and every pericope contributing no new term beyond what is already catalogued is explicitly marked “reviewed — no new doctrine/gap” rather than silently omitted.
• 101 terms now govern Phase 2 translation, split between 33 terms inherited exactly from the Romans/Galatians baseline (with two risk-tier elevations — kingdom_of_god and baptism — explicitly justified for Mark’s usage) and 68 new terms this book introduces, most concentrated in the core passage and the passion narrative (chs. 10, 14–15).
• The core passage (10:35-45) is the single densest concentration of Critical-risk material in the book, containing the apex ransom term, the substitutionary preposition ἀντί (के बदले), the Son of Man title, the servant/slave escalation, and the Trinity-adjacent “it is not mine to give” clause — five of this analysis’s top-ranked ambiguities converge in eleven verses.
• 25 assigned/supplementary doctrines are tracked in doctrine_risk_registry.json, with the registry’s own risk_summary recording 13 Critical + 14 High = 27 doctrines requiring mandatory human theologian review, 3 requiring native speaker review, and 0 automated-only.
• At the term level, bible_term_registry.json (Mark) catalogs approximately 94 terms, of which ~30 are Critical and ~41 are High (≈71 terms, 76% of the glossary) requiring theologian review; 19 are Medium (native speaker review); 4 are Low (automated review only).

Risks

• Ransom-for-many (10:45) is the highest-stakes single term in the Hindi Language Package to date. Two of the three most natural-sounding Hindi words a translator might instinctively reach for (मुक्ति, मोक्ष) are absolutely forbidden because they describe self-attained liberation from samsara — the exact theological inverse of a price paid, once, by God’s own initiative on the captive’s behalf.
• Servanthood language (सेवक/दास, 9:35; 10:43-45) carries live social danger in India. The same दास root is already Critical/negative in the Galatians baseline (bondage to sin/law); Mark redeploys it positively (voluntary greatness-through-service). Without a mandatory cross-reference note at every occurrence, students may perceive Scripture as self-contradictory, and without caste-sensitivity framing, the teaching could be misheard as endorsing caste-assigned servitude rather than overturning it.
• The Son of Man title (14 occurrences) has no ready Hindi analogue. Hindi risks either flattening it to generic “a human being” (losing Daniel 7’s exalted-judge background) or assimilating it to अवतार (forbidden avatar-descent theology already barred by the baseline incarnation entry).
• Ritual-purity teaching (7:14-23) directly confronts caste-linked śuddha/aśuddha systems governing touch, food-sharing, and social hierarchy in India — the highest social-application risk in the book, requiring theologian-supervised pastoral framing, not merely correct vocabulary.
• δεῖ (“must suffer,” 8:31; 9:31; 10:33-34) is lexically identical to ordinary Hindi fatalistic speech (“यह होना ही था,” destiny/karma language); without a mandatory disambiguating note at all three passion predictions, “The Necessity of the Cross” risks being heard as Jesus’ fate rather than the Father’s freely embraced redemptive purpose.
• The blasphemy-against-the-Spirit warning (3:28-29) carries acute pastoral misapplication risk — an anxious reader could wrongly conclude a specific sin of theirs is now permanently unforgivable, undermining the gospel’s universal offer, unless the mandatory pastoral note is applied without exception.

Opportunities

• Mark’s own retained-Aramaic practice (Abba, Ephphatha, Eloi Eloi lama sabachthani) gives the Hindi translation a built-in, source-text-sanctioned model: transliterate, then gloss immediately in-text — exactly mirroring what Mark himself does, rather than requiring the translation team to invent a new convention.
• India’s shepherd-king, agrarian (yoke), and honor/status-seating cultural vocabulary map naturally onto several of Mark’s images (6:34’s shepherd compassion; 10:37’s seating-of-honor request), reducing translation risk in those specific passages relative to the book’s hardest terms.
• The mainstream Hindi Bible tradition (O.V./N.V.) already handles the core passage’s lexical choices well (per 05_translation_landscape.md); the primary gap is under-annotation, not mistranslation — meaning targeted translator notes, not wholesale re-translation, close most of the remaining risk.
• Impartiality-of-God and unity-in-Christ threads already established in the Galatians baseline (no distinction of status before God) directly reinforce Mark’s servanthood doctrine, allowing this curriculum to build on existing anti-caste-hierarchy groundwork rather than starting from zero.

Recommended actions

1. Lock assets/translation_memory.json (Mark) as authoritative before any Phase 2 segment work begins, alongside the baseline Romans/Galatians file; enforce the ransom-saying triad (छुटकारे का दाम / के बदले / प्राण) as a single atomic unit at 10:45, never processed piecemeal.
2. Route the entire core passage (10:35-45) to theologian review as a fixed unit, regardless of individual term risk tier, per the escalation rule fixed in 12_ai_translation_requirements.md.
3. Apply the mandatory cross-reference note at every सेवक/दास occurrence (9:35; 10:43-45), pairing doctrinal clarity (distinct from Galatians’ negative slavery sense) with pastoral sensitivity (distinct from caste-assigned servitude).
4. Confirm the Hindi O.V. YouVersion version ID at Phase 2 kickoff and propagate it into this package’s frontmatter, per the action item logged in 05_translation_landscape.md §6.1.
5. Prioritize batch-processing order using the ranked ambiguity list in 06_linguistic_gap_analysis.md §4: ransom/ἀντί first, Son of Man title second, δεῖ-necessity third, servant/slave cross-curriculum consistency fourth — before lower-risk chapters are queued.
6. Commission the theologian-supervised pastoral framing note for Mark 7:14-23 (clean/unclean vs. caste-purity systems) as a standalone deliverable, given its social-application risk exceeds its narrow lexical footprint.
7. Adopt the Hindi N.V./modern bracketing convention for Mark 16:9-20 (textual-critical footnote, not silent inclusion or exclusion), subject to human theologian sign-off, per the recommendation already fixed in 05_translation_landscape.md.

---

This document summarizes 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/translation_memory.json, assets/bible_term_registry.json, and assets/doctrine_risk_registry.json. It must be read alongside those source documents, not in place of them, before Phase 2 translation work begins.