Linguistic Gap Analysis — Mark (Koine Greek → Hindi)

0. Method and Scope

This analysis extends the baseline Romans/Galatians Language Package to the Gospel of Mark, in service of the eight assigned doctrines and their anchor, the core passage Mark 10:35-45. It does not repeat term-by-term definitions already fixed in translation_memory.json and bible_term_registry.json; instead it asks the four Step 8 questions the PRD requires:

1. What does the doctrine vocabulary matrix look like — for each doctrine, what Hindi resources exist, what is weak about them, and what strategy resolves the weakness?
2. Where does Hindi have no ready term (missing vocabulary), and where does it have too many overlapping terms drawn from competing religious systems (crowded semantic neighborhoods needing a fence)?
3. Where should the translation transliterate rather than paraphrase, and vice versa?
4. Ranked across the whole book, which ambiguities carry the highest doctrinal risk?

Full-book coverage confirmation. Every chapter of Mark (1–16) was reviewed for load-bearing vocabulary gaps. Chapters that contribute no new gap beyond what is already logged below are explicitly marked “reviewed — no new gap” in §5. No chapter was silently skipped.

---

1. Doctrine Vocabulary Matrix

For each doctrine: the Hindi terms currently available (baseline-inherited or Mark-new), the specific weakness of the existing resource, and the recommended mitigation strategy. Full citations and final renderings live in 08_core_glossary.md; this section explains why those choices were forced.

1.1 Jesus as the Suffering Servant and Son of God

Available Hindi terms	Weakness	Recommended strategy
परमेश्वर का पुत्र (Son of God)	None intrinsic — the phrase is doctrinally sound — but Mark uses it as a five-point literary bracket (1:1, 1:11, 3:11/5:7, 9:7, 14:61, 15:39); a translator working document-by-document could paraphrase individual occurrences for local flow and destroy the bracket.	Mandate byte-identical rendering at all six anchor occurrences; flag any deviation automatically.
मनुष्य का पुत्र (Son of Man)	Hindi has no existing devotional vocabulary carrying Daniel 7’s exalted-judge sense; a literal gloss (“man’s son”) reads as a humble self-reference only, losing the co-present authority/glory sense. गुरुपुत्र or अवतार-adjacent phrasing were considered and rejected (avatar collision).	Retain the literal compound मनुष्य का पुत्र as a fixed title (not a description), reinforced by a standing translator note at first occurrence (2:10) explaining the double sense (humility + Daniel 7 exaltation), refreshed at 8:31, 10:45, 13:26, 14:62.
दुख उठानेवाला सेवक (Suffering Servant, descriptive, not a fixed Markan phrase)	Mark never uses a single lexical tag equivalent to Isaiah’s “Servant of the LORD”; the doctrine is conveyed narratively (ransom saying, Gethsemane, the cross) rather than by one term. Hindi risks inventing a devotional title not actually in the text.	Do not coin a standing title; instead ensure the doctrine surfaces through consistent rendering of ransom (10:45), the cup (10:38; 14:36), and the cry of dereliction (15:34) — the three textual anchors — rather than through a summary label.
महिमा (glory)	Standard Hindi religious vocabulary treats glory/light as separable from and opposed to suffering (a triumphant deity is glorious; a suffering one is pitiable, not majestic). Mark’s argument (glory through suffering) runs directly against this cultural default.	Attach a mandatory translator note at 10:37 and 13:26 stating explicitly that Christ’s महिमा in Mark is inseparable from, not opposed to, his suffering — reusing the baseline’s existing glory entry but with a Mark-specific addendum.

1.2 The Kingdom of God Breaking In

Available Hindi terms	Weakness	Recommended strategy
परमेश्वर का राज्य	The baseline fixes this at Medium risk (Romans’ usage is mostly future/ethical). Mark 1:15’s ἤγγικεν (perfect tense, “has drawn near”) asserts a decisive already-arrived dimension the baseline register does not anticipate. Hindi’s natural aspectual options (आ गया है = fully arrived; आ रहा है = still coming) each resolve the tension in only one direction.	Elevate to High for Mark (already reflected in the core glossary). Render 1:15 with निकट आ गया है (“has drawn near/arrived close”) rather than either extreme, with a standing note explaining the already-not-yet structure, cross-referenced at 9:1 and 14:25.
भेद (mystery)	Adequate lexically, but the term’s ordinary Hindi register (a puzzle, a secret) does not by itself convey “revealed to insiders, hidden from outsiders by God’s own design,” a distinctly election-adjacent idea.	Pair भेद with explicit surrounding context at 4:11 rather than relying on the word alone; cross-reference to the Messianic Secret doctrine.
अशुद्ध आत्मा / दुष्टात्मा (unclean spirit/demon)	India’s living exorcism traditions (ojha, tantric ritual, bhoot-pret vocabulary) supply an entire competing explanatory and ritual framework for possession phenomena. A translation that borrows folk vocabulary (भूत-प्रेत) imports that framework’s assumptions about causation and remedy.	Retain अशुद्ध आत्मा (built on the baseline’s पवित्र आत्मा contrast) and require a note distinguishing Christ’s unilateral divine authority (a word of command) from ritual exorcism practice (multi-step, mediated, often fee-based).
the elect (चुने हुए लोग)	Shares a root with भाग्य/नियति/किस्मत-adjacent vocabulary in casual religious Hindi speech even though the technical term itself is fate-free.	Reinforce with the baseline’s existing “never भाग्य/नियति/किस्मत” prohibition at every occurrence (13:20,22,27).

1.3 Faith and Discipleship amid Fear

Available Hindi terms	Weakness	Recommended strategy
विश्वास (faith)	Sound baseline term, but Mark’s narrative structure pairs it repeatedly and specifically against भय/डर (fear) as its dramatic foil (4:40; 5:36; 6:50; 9:24; 16:8). A translation team working verse-by-verse might vary “fear” vocabulary (चिन्ता, घबराहट, डर, भय) for stylistic variety and inadvertently erase the deliberate five-point pattern.	Fix भय as the primary rendering across all five anchor verses; permit डर only as a secondary gloss, never as the primary term, to preserve pattern-recognition across the book.
अविश्वास (unbelief)	9:24’s “I believe; help my unbelief” is a single breath holding both viśvāsa and its negation together — a paradox easily “resolved” by translators uncomfortable leaving the tension unclosed.	Translator note requiring the paradox be left intact; forbid smoothing into either “I believe fully” or “I doubt.”
चेला (disciple)	Heavily loaded with the guru-shishya paradigm: in ordinary Hindi religious usage, a चेला serves a गुरु in hope of receiving transmitted esoteric knowledge culminating in the disciple’s own liberation. Mark’s चेले instead follow Jesus into mission, servanthood, fear, failure, and the possibility of death.	Retain चेला (no better BSI-established alternative exists) but require narrative context in study materials to consistently show Jesus’ चेले sent out (6:7-13), failing in faith (4:40; 9:18-19), and called to self-denial (8:34) — not receiving private gnosis.
अब्बा, पिता (Abba, Father)	Low collision risk on the term itself, but 14:36’s juxtaposition of intimacy (“Abba”) with anguish (“deeply distressed,” “remove this cup”) can be flattened toward either pure comfort-devotion or pure despair if translated without care for both notes simultaneously.	Preserve the transliterated अब्बा exactly as the baseline requires, paired explicitly with 14:34’s anguish language in the same segment cache entry so both are graded together.

1.4 The Necessity of the Cross

Available Hindi terms	Weakness	Recommended strategy
दुख उठाना अवश्य है (must suffer, δεῖ)	अवश्य (“necessarily/certainly”) is also the ordinary Hindi word used for astrological or karmic inevitability (“यह होना ही था,” “भाग्य में लिखा था”). Without a note, “the Son of Man must suffer” reads as fated tragedy rather than a purposive, Scripture-fulfilling divine plan the Son embraces.	Mandatory translator note at every occurrence (8:31; 9:31; 10:33-34) distinguishing δεῖ’s grounded, personal, purposive necessity (“because it is written,” “according to the Father’s will”) from निर्धारित भाग्य (predetermined fate).
अपने आप का इन्कार करे और अपना क्रूस उठाए (deny self, take up cross)	Structurally resembles Hindu tapasya/ascetic renunciation vocabulary (त्याग, वैराग्य, आत्म-त्याग) — practices independently believed to generate merit or advance liberation.	Note required: this self-denial is a responsive act of allegiance to a Christ who has already suffered first (v.31 precedes v.34), not an independently meritorious achievement performed to earn standing.
कटोरा (cup, metaphorical)	Bare कटोरा is a literal drinking vessel; without explanation, readers either miss the OT idiom entirely or associate it with Hindu ritual offering-vessels (अर्घ्य, प्रसाद के पात्र).	Mandatory note at first occurrence (10:38) establishing the OT background (Ps 75:8; Isa 51:17,22; Jer 25:15) and carrying the note forward to 14:23-24, 14:36 rather than re-explaining or varying the term each time.
बपतिस्मा (baptism, metaphorical)	The baseline’s literal water-rite sense (1:4,8,9) is well established; 10:38-39’s metaphorical extension (“baptized with the baptism I am baptized with”) risks readers assuming a second literal rite is being promised to James and John.	Mandatory note distinguishing literal water-baptism from this metaphorical “immersion in suffering” extension, at 10:38-39 specifically.
पुनरुत्थान (resurrection)	Sound and already Critical-protected by the baseline; the risk is not the term but sequencing — if “necessity of the cross” material is translated without equally weighted resurrection material nearby, suffering could read as the whole story rather than suffering-then-vindication.	Editorial requirement (not lexical): every passion-prediction unit (8:31; 9:31; 10:33-34) must retain its resurrection clause with equal translational weight, not abbreviated.

1.5 Servanthood versus Worldly Greatness

Available Hindi terms	Weakness	Recommended strategy
सेवक (servant, διάκονος general sense)	Same root as the baseline’s ecclesial-office सेवक/सेविका (deacon); more seriously, India’s caste system has historically assigned service labor to specific communities as an inherited, involuntary social status (sevā as caste-duty). A universal call to सेवक-hood for every disciple, translated without care, could be heard as endorsing that inherited hierarchy rather than overturning it.	Distinguish explicitly from the office sense by context; frame सेवक-hood in study materials as a freely chosen posture available to and required of every disciple regardless of birth status — the opposite of caste-assigned servitude. Mandatory theologian + pastoral-sensitivity review.
दास (slave, δοῦλος positive sense)	Identical Hindi root to the baseline’s negative “slavery” entry (bondage to sin/law in Galatians); the same word now names the paradigm of greatness in Mark 10:44. Left unglossed, a student moving between the Galatians and Mark curricula could perceive a direct contradiction. Additionally, दास carries live social resonance (bonded labor, Dalit-rights discourse) in contemporary India.	Mandatory cross-reference note at every Mark occurrence distinguishing voluntary self-subordination to others’ good (Mark’s sense) from being held in bondage to sin/law (Galatians’ sense). Escalate visibly across the verse sequence 9:35 (सेवक) → 10:43 (सेवक) → 10:44 (दास), preserving Mark’s own rhetorical escalation.
बड़ा (great, μέγας)	If softened to a generic “good person,” the paradox (status-greatness is redefined as servanthood, not merely accompanied by it) disappears.	Retain बड़ा’s ordinary status/honor connotation intact so the paradox is felt as a genuine reversal, not diluted into vague moral encouragement.
प्रभुता करना / अधिकार जताना (lord it over / domineer, negative)	Both share roots with terms used positively elsewhere for Christ’s own Lordship (प्रभु) and authority (अधिकार). Without a fencing note, a reader could infer that Lordship/authority themselves are condemned rather than their coercive, self-serving abuse.	Mandatory note at 10:42 distinguishing κατακυριεύω/κατεξουσιάζω (Gentile rulers’ coercive self-serving rule) from Christ’s own benevolent, legitimate Lordship/authority exercised throughout the book.

1.6 The Messianic Secret

Available Hindi terms	Weakness	Recommended strategy
किसी को न बताने की चेतावनी (silence-command narrative pattern)	This is not a single lexical item but a recurring narrative act (ἐπιτιμάω/φιμωθῆναι/σιωπᾶν at 1:34,44; 3:12; 5:43; 7:36; 8:26; 8:30; 9:9). Hindi has no fixed idiom for “messianic secrecy” as a category; left to individual translators, each occurrence might be rendered with a different verb (मत बताना, चुप रहो, न कहना), obscuring the pattern’s deliberateness.	Fix one consistent phrase across all eight occurrences; require a standing note (not repeated in full each time, but linked) explaining this is a deliberate strategy against premature/misunderstood disclosure, not narrative shyness or false modesty.
गुरुजी (Teacher, address to Jesus)	गुरु is the master category of Hindu religious authority — a lineage-transmitted, often venerated status. Used as the sole title for Jesus, it would assimilate him into “one guru among many” precisely where Mark is building toward the Christological climax the Secret withholds until the cross.	Balance every गुरुजी occurrence contextually with प्रभु/मसीह elsewhere in the same unit so no single passage lets गुरु stand as Jesus’ only characterization.
मसीह (Messiah/Christ)	The term itself is baseline-fixed and sound; the risk is structural — Peter’s confession (8:29) and the high priest’s interrogation (14:61) must be recognizable as deliberate parallels (both use the identical title), a pairing easily lost if either occurrence drifts even slightly in phrasing.	Enforce byte-identical rendering at 8:29 and 14:61-62 specifically, beyond the general “render मसीह consistently” rule.

1.7 Jesus’ Authority over Sickness, Sin, and Nature

Available Hindi terms	Weakness	Recommended strategy
अधिकार (authority, ἐξουσία)	New Mark coinage (not in the baseline); risk is boundary-confusion with सामर्थ्य (raw power, reserved for δύναμις) and with its own negative cognate usage at 10:42.	Keep अधिकार strictly for ἐξουσία (teaching authority, 1:22,27; forgiving sins, 2:10; Sabbath-lordship, 2:28; commanding spirits, 1:27; interrogated, 11:28-33); note the deliberate contrast with the negative sense flagged in §1.5.
पापों की क्षमा (forgiveness of sins)	माफी, the more casual everyday Hindi word for “sorry/pardon,” would understate the specific divine-prerogative claim Jesus makes at 2:5-10 — a claim serious enough to trigger a blasphemy accusation. India’s live karma-debt framework (sin as a debt worked off across lifetimes, not forensically forgiven by a personal God) is the most likely misreading if the term is softened.	Retain क्षमा (not माफी); require a note at 2:5-10 that this is Jesus exercising a divine prerogative, provoking deliberate controversy — not routine priestly absolution or karmic debt-cancellation.
पवित्र आत्मा के विरुद्ध निन्दा (blasphemy against the Holy Spirit)	Highest pastoral risk in the whole book: an unglossed rendering could be read by an anxious new believer as “some specific sin I may have committed is now permanently unforgivable,” directly undermining the universal gospel offer elsewhere affirmed.	Mandatory pastoral note at every occurrence (3:28-29) clarifying this names a settled, deliberate, ongoing rejection of the Spirit’s own testimony to Christ — not a single act any troubled conscience need fear having committed.
शुद्ध / अशुद्ध (clean/unclean)	Directly overlaps India’s deeply embedded caste-linked ritual-purity vocabulary (touch-pollution, food-sharing restrictions, caste-based अशुद्धता). Jesus’ relocation of defilement to the heart (7:14-23) has real caste-disruptive implications that a purely lexical translation will not surface on its own.	Theologian-supervised framing required, drawing an explicit (not merely implied) line from 7:14-23 to the dismantling of purity-based social hierarchy, paralleling the baseline’s existing Galatians commensality caution.
चंगा होना / बचना vs उद्धार पाना (σῴζω dual sense)	A single Greek verb spans literal healing and eschatological salvation; a Hindi translation team defaulting to one fixed rendering throughout would either over-theologize routine healing narratives (उद्धार everywhere) or strip healing of its sign-value pointing toward fuller salvation (चंगा होना everywhere, with no cross-reference).	Apply the documented dual-track protocol (already logged in bible_term_registry.json) verse-by-verse, with a translator note at each theologically weighted occurrence (8:35; 10:26; 13:13,20) flagging the shared root with the physical-healing occurrences (5:23,28,34; 6:56; 10:52).

1.8 The Ransom for Many

Available Hindi terms	Weakness	Recommended strategy
छुटकारे का दाम (ransom, λύτρον)	No existing single Hindi word names “the specific price paid to release a captive/slave.” Candidates considered and rejected: मुक्ति-मूल्य (contains the forbidden मुक्ति root); प्रायश्चित्त (already reserved by the baseline for propitiation, a distinct atonement facet, and risks conflating ransom-price with self-performed penance); बलिदान (too generic — loses the specific commercial “price for release” sense and risks assimilation to ritual-offering vocabulary).	Coin the compound छुटकारे का दाम, built transparently on the baseline’s already-established छुटकारा (redemption) root plus दाम (“price”), making the transactional sense explicit rather than implicit. Mandatory theologian review at 10:45, cross-referenced to the baseline redemption entry.
के बदले (ἀντί, “instead of/in place of”)	Hindi के लिये is the natural default rendering for “for,” but के लिये alone collapses ἀντί’s specifically substitutionary sense into the weaker, more general benefactive sense also used for ὑπέρ at 14:24 (“poured out for many”). If both prepositions are rendered identically, the ransom saying’s substitutionary logic (one life given in place of many) is diluted into vague benefit-for-others language.	Fix के बदले for ἀντί (10:45) and reserve a distinguishable phrasing for ὑπέρ (14:24), with a translator note cross-linking the two so the jointly-substitutionary, jointly-covenant-inaugurating logic remains visible without conflating the two prepositions’ distinct nuances.
प्राण (ψυχή, soul/life)	आत्मा was considered and rejected — it is already reserved for the Holy Spirit and for a technical Pauline “self,” and using it here would create serious category confusion between Christ’s soul given in death and the divine Spirit. प्राण itself is not risk-free: in popular Hindi religious/yogic usage प्राण denotes a impersonal vital breath-energy (as in prāṇāyāma), which could reduce “he gave his life” to a metaphysical life-force transaction rather than a real, personal, embodied death.	Retain प्राण (no better option exists) but require a standing note that this is Christ’s actual embodied human life laid down in a real death, not a yogic life-force teaching — cross-referenced to 8:35-37’s parallel “losing/gaining one’s ψυχή” language.
यह मेरी देह है / यह वाचा का मेरा लोहू है (this is my body / blood of the covenant)	Bread-and-cup ritual language is acutely vulnerable to assimilation into Hindu yajna/prasad vocabulary, where a worshipper offers something to a deity to secure favor — the reverse direction from the Supper, where Christ gives himself to his disciples.	Mandatory theologian review; explicit note establishing the gift’s direction (God/Christ → sinner, not sinner → deity); distinguish from the baseline’s separate corporate “body of Christ” (church) metaphor, which is a different referent entirely.
वाचा (covenant) reused at 14:24	Sound baseline term, but its Ransom-adjacent use at 14:24 (echoing Exodus 24:8 and Isaiah 53:12) must visibly connect back to 10:45’s ransom saying for students to see the two texts as one integrated doctrine, not two separate ideas.	Editorial cross-reference requirement linking 10:45 and 14:24 in all study materials treating “The Ransom for Many.”

---

2. Missing Vocabulary vs. Crowded Semantic Neighborhoods

2.1 Missing Vocabulary (Hindi has no ready-made equivalent; a compound or coined phrase is required)

Concept	Why Hindi lacks a ready term	Resolution
λύτρον (ransom-price for a captive/slave)	Hindi’s closest single words (मुक्ति-मूल्य, प्रायश्चित्त, बलिदान) each import a forbidden or conflicting theological frame (see §1.8).	Coined compound छुटकारे का दाम.
Son of Man as a title (not description)	No indigenous Hindi religious category names “a genuinely human figure who is simultaneously an exalted, dominion-receiving heavenly judge.” The nearest structural analogue, अवतार, is doctrinally forbidden (temporary/repeatable deity-descent).	Literal compound मनुष्य का पुत्र fixed as a title, reinforced by a standing note at first occurrence.
δεῖ (purposive divine necessity, distinct from fate)	Hindi अवश्य/निश्चित रूप से carries no built-in distinction between “must, because God has purposively ordained and Scripture requires it” and “must, because fate/karma has determined it.”	Retain दुख उठाना अवश्य है but attach a mandatory disambiguating note at every occurrence rather than seeking a new single word (none exists).
ἀντί vs ὑπέρ (substitution vs general benefaction)	Hindi के लिये covers both Greek prepositions by default; no natural single-word fence exists between them.	Reserve के बदले for ἀντί only; use a distinguishable benefactive phrasing for ὑπέρ at 14:24; cross-reference both.
κατακυριεύω / κατεξουσιάζω (coercive domineering, distinct from legitimate lordship/authority)	Hindi’s natural derivational options (प्रभुता करना, अधिकार जताना) are built from the very same roots used positively elsewhere for Christ. No unrelated root exists to mark the negative sense unambiguously.	Accept the shared-root terms but require the fencing note described in §1.5 at every occurrence.
”Ransom for many” as an integrated doctrinal unit spanning 10:45 and 14:24	No existing catechetical shorthand in Hindi Christian usage names this two-text unit.	Editorial/structural solution (cross-referencing), not lexical.

2.2 Crowded Semantic Neighborhoods (Hindi has too many overlapping candidate terms drawn from competing systems; a fence is required to keep them from bleeding into each other)

Hindi root/term	Competing senses crowding the neighborhood	Fence required
आत्मा	(a) पवित्र आत्मा — personal Holy Spirit; (b) अशुद्ध आत्मा — unclean spirit/demon; (c) प्राण — used instead for ψυχή to avoid a third collision; (d) Vedantic ātman — the impersonal universal Self, never intended anywhere in Mark but always latent as a hearer’s default association	Never use आत्मा for ψυχή (reserved: प्राण). Always modify आत्मा with पवित्र or अशुद्ध — bare आत्मा must not stand alone in a theologically loaded sentence in Mark.
दास / दासत्व	(a) Galatians’ negative bondage-to-sin/law sense (baseline, already Critical); (b) Mark 10:44’s positive voluntary-self-subordination sense; (c) live Indian social/legal resonance (bonded labor, caste servitude, Dalit-rights discourse)	Mandatory cross-reference translator note at every Mark occurrence naming both the Galatians contrast and the social-sensitivity dimension (§1.5).
गुरु / गुरुजी	(a) Respectful address to Jesus as teacher (Mark’s actual usage); (b) the full Hindu guru paradigm — lineage authority, veneration, esoteric transmission, a status a disciple never formally outgrows	Balance every गुरुजी occurrence with प्रभु/मसीह nearby (§1.6); never let गुरु stand as Jesus’ only or dominant title in a given passage.
शुद्ध / अशुद्ध	(a) Biblical ritual-purity categories reinterpreted morally by Jesus (7:14-23); (b) Hindu caste-linked ritual-purity/pollution system (touch, food, birth-status)	Theologian-supervised note making the caste-disruptive implication explicit, not merely lexically correct (§1.7).
प्रभु / प्रभुता / अधिकार	(a) Christ’s own exclusive, benevolent Lordship/authority (Critical baseline, positive throughout Mark); (b) 10:42’s negative κατακυριεύω/κατεξουσιάζω (coercive Gentile rule) sharing the identical Hindi root	Explicit contrastive note at 10:42, and at 2:28’s positive “Lord of the Sabbath” reuse, so the two valences are never allowed to blur into each other (§1.5, §1.7).
चेला / शिष्य	(a) Mark’s committed followers sent into mission/suffering; (b) the guru-shishya disciple seeking private liberating knowledge	Retain established चेला but require consistent contextual framing per §1.3.
फल (fruit)	Not directly present in Mark’s core vocabulary, but the parable of the sower/vineyard (4:1-20; 12:1-12) and any harvest imagery risk the same कर्म-फल (karma-fruit) collision already documented for Galatians.	Where “fruit”/harvest language appears in parable material, apply the same singular-genitive-construction caution already fixed in the baseline (fruit_of_the_spirit entry) even though Mark’s own occurrences are not Critical-tier doctrine terms in this curriculum.
नरक / गेहेन्ना	(a) Biblical Gehenna — final, non-cyclical judgment; (b) Hindu नरक (naraka) — a temporary punitive way-station within an ongoing rebirth cycle	Transliterate गेहेन्ना as the primary rendering; permit नरक only as a carefully qualified gloss with a mandatory distinguishing note (§already fixed in the term registry; reaffirmed here).
कटोरा (cup)	(a) OT suffering/judgment idiom; (b) Hindu ritual offering-vessel imagery (अर्घ्य, प्रसाद-पात्र)	Mandatory note at first occurrence tying the term to its OT background, not ritual-vessel imagery (§1.4).
मुक्ति / मोक्ष	Absolutely forbidden across the whole curriculum family (baseline + Galatians + Mark) for salvation, redemption, ransom, and freedom vocabulary — the single most crowded and most dangerous neighborhood in the entire Language Package, because these are also the two most natural-sounding Hindi words a translator unfamiliar with the glossary would reach for instinctively.	Absolute prohibition, re-affirmed for Mark: never for उद्धार, छुटकारा, छुटकारे का दाम, or any Ransom-for-Many vocabulary. Validation-layer automated check required on every segment.

---

3. Transliteration vs. Paraphrase Decisions

Mark contains an unusually high concentration of retained Aramaic/Hebrew expressions (a stylistic feature of the source text itself), which the translation should generally mirror rather than dissolve into paraphrase — Mark himself transliterates-then-glosses, and the Hindi should follow the same pattern.

3.1 Transliterate (retain source-language sound, then gloss immediately in-text)

Term	Hindi transliteration	Gloss required	Rationale
Abba	अब्बा	(implicit — पिता follows in the source itself, 14:36)	Baseline-established; preserves filial intimacy the formal पिता alone cannot fully carry.
Ephphatha	एफ्फाता	खुल जा	Mark’s own text transliterates then glosses (7:34); Hindi should mirror the source’s practice exactly, not normalize it away.
Eloi, Eloi, lama sabachthani	एलोई, एलोई, लमा शबक्तनी	(immediate exact gloss of Ps 22:1’s Hindi rendering)	Genuine cry of anguish citing Scripture; softening into rhetorical metaphor loses the reality of the moment; must not be pre-resolved into comfort language.
Hosanna	होशाना	brief note: liturgical acclamation from Ps 118, literally “save now”	Established liturgical loanword; note ties it back to the σῴζω root discussed in §1.7.
Beelzebul	बील्ज़ेबूल	brief gloss: byname for the ruler of demons	Proper noun; low doctrinal risk once glossed.
Legion	लीजियन	brief gloss: Roman military unit (~6,000)	Proper noun; conveys narrative scale, not doctrinally hazardous.
Corban	कुरबान	brief gloss: a vow dedicating assets “to God” to avoid supporting parents	Legal-technical term; a paraphrase would need a full sentence anyway, so transliteration + gloss is more economical and preserves the term’s technical flavor.
Gehenna	गेहेन्ना	mandatory eschatological distinguishing note (see §2.2)	Paraphrasing as नरक alone would import the wrong (cyclical) cosmology; transliteration is the safer default, with नरक permitted only as a secondary qualified gloss.
Amen	आमीन	none needed (already fully naturalized in Hindi Christian usage)	Baseline-established.

3.2 Paraphrase (compound Hindi phrase required; a single transliterated or borrowed word would either not exist or would mislead)

Concept	Hindi paraphrase	Rationale for paraphrase over transliteration/single word
λύτρον (ransom)	छुटकारे का दाम	No Hindi or Sanskritic loanword exists that isolates the specific commercial “price paid for release” sense without collision (see §1.8, §2.1).
Son of Man (as title)	मनुष्य का पुत्र	A transliteration of the Aramaic bar enash would be opaque to Hindi readers and carry no inherited resonance; the literal compound at least preserves surface meaning while the standing note supplies the Danielic depth.
Son of Man must suffer	दुख उठाना अवश्य है	δεῖ has no Hindi single-word equivalent capturing purposive-not-fatalistic necessity; paraphrase plus mandatory note is required (§2.1).
Deny himself, take up his cross	अपने आप का इन्कार करे और अपना क्रूस उठाए	An idiom-for-idiom search (e.g., existing Hindi ascetic vocabulary) would import tapasya connotations; literal paraphrase, glossed against that misreading, is safer than any more “natural-sounding” Hindi idiom.
ἀντί (“instead of,” 10:45)	के बदले	No transliteration is possible (this is a grammatical preposition, not a proper noun or set phrase); the paraphrase must be precise enough to survive contrast with ὑπέρ at 14:24.
κατακυριεύω / κατεξουσιάζω	उन पर प्रभुता करना / उन पर अधिकार जताना	Descriptive paraphrase is unavoidable; no single pejorative-domination word exists in formal Hindi register that would not itself need glossing.
This is my body / blood of the covenant	यह मेरी देह है / यह वाचा का मेरा लोहू है	These are theologically load-bearing declarative sentences, not proper nouns; paraphrase (with mandatory notes fencing off ritual-offering vocabulary) is the only option.
Messianic-secret silence commands	किसी को न बताने की चेतावनी	A recurring narrative pattern, not a single source-language lexeme; a fixed Hindi paraphrase applied consistently is required to make the pattern visible in translation (see §1.6).

3.3 Borderline Case Requiring Explicit Editorial Decision

ἐγώ εἰμι (“I am,” 6:50; 14:62). Neither pure transliteration (impossible — this is ordinary Greek grammar, not a proper name) nor a fully “natural” colloquial Hindi rendering (यह तो मैं हूँ, rejected as too casual) will do. The editorial decision recorded in the term registry is to use the plain declarative मैं हूँ without softening particles, relying on context and a theologian’s note (not a lexical device) to carry the possible Exodus 3:14/Isaiah 43:10-13 echo. This is flagged here because it is the clearest case in Mark where no transliteration/paraphrase choice alone can bear the theological weight — only editorial framing can.

---

4. Ranked List of the Highest-Risk Ambiguities in Mark

Ranked by combined severity (doctrinal centrality × collision danger with Hindu/Indian religious vocabulary), with the core passage’s own ambiguities given priority weighting consistent with the PRD’s anchor-not-scope principle.

1. λύτρον / “ransom for many” (10:45) — के बदले substitution logic. The apex term of the core passage. If छुटकारे का दाम drifts toward मुक्ति/मोक्ष-adjacent liberation language, or if के बदले is flattened to the weaker के लिये, the entire doctrine “The Ransom for Many” collapses into vague benefaction rather than a substitutionary price paid by a personal God’s initiative. Highest-severity ambiguity in the book.

2. “Christ lives in me”-class ego/identity risk transposed to Mark’s “deny himself” (8:34) and “not my will but yours” (14:36). Though Mark lacks Galatians 2:20’s exact phrasing, the same advaitic collision risk (dissolution of the personal “I” into an impersonal will/Self) attaches to Gethsemane’s submission language and to the call to self-denial. A Hindi rendering that reads as ego-dissolution rather than personal, relational submission would misdirect the Necessity of the Cross doctrine at its most intimate moment.

3. Son of Man (μανθεν τοῦ ἀνθρώπου) — title vs. description ambiguity across 14 occurrences. Because Hindi has no inherited category matching Daniel 7’s exalted-suffering-human figure, every occurrence risks silent flattening into “a human being” (losing the exaltation) or silent elevation into avatar-adjacent language (violating the baseline’s incarnation prohibition). The risk compounds because this term appears at every doctrinal hinge point: authority (2:10,28), suffering-necessity (8:31; 9:31; 10:33-34), ransom (10:45), and eschatological glory (13:26; 14:62).

4. δεῖ παθεῖν (“must suffer”) vs. karmic/fated inevitability. अवश्य है is lexically correct and simultaneously the exact word ordinary Hindi speakers use for “it was bound to happen” in a fatalistic sense. Without the mandatory note at all three passion predictions, the doctrine “The Necessity of the Cross” risks being heard as Jesus’ fate rather than the Father’s redemptive purpose freely embraced.

5. दास (positive, 10:44) vs. दासत्व (negative, Galatians baseline) — cross-curriculum contradiction risk. A student encountering both curricula could reasonably conclude Mark and Galatians disagree about slavery’s moral valence unless the cross-reference note is applied without exception at every Mark occurrence.

6. शुद्ध/अशुद्ध (clean/unclean, 7:14-23) — caste-purity collision. Because Indian ritual-purity vocabulary is not merely religious but socially load-bearing (caste, touch, commensality), an under-noted translation could either (a) inadvertently endorse caste-purity logic by leaving it unchallenged, or (b) provoke unintended social/political reaction if handled too bluntly without theologian-supervised pastoral framing.

7. प्राण (ψυχή, “life,” 10:45; 8:35-37) — yogic vitalism collision. Christ’s प्राण given as the ransom must be read as a real embodied human life surrendered in actual death, not a life-force/prana transaction; conflation with pranayama-adjacent vitalism would abstract away the concreteness of the cross.

8. κατακυριεύω/κατεξουσιάζω vs. legitimate प्रभु/अधिकार (10:42). Shared roots with Christ’s own positive Lordship/authority create a live risk that condemning worldly domination could be misheard as condemning Lordship itself — directly undercutting the Suffering-Servant-and-Son-of-God doctrine in the very passage (10:35-45) meant to display authority rightly exercised through service.

9. The Messianic Secret’s silence-command pattern (eight occurrences) — consistency risk, not single-term risk. Because this is a distributed narrative pattern rather than a lexical item, the danger is not mistranslation of any one verse but inconsistent translation across the eight occurrences, which would make the pattern invisible and collapse a distinct assigned doctrine into unremarkable narrative color.

10. γρηγορεῖτε (“watch/be alert,” 13:33-37; 14:34-38) — narrative-link risk. Lower doctrinal stakes than items 1-9, but the deliberate irony (the disciples told to watch, then found asleep) depends entirely on identical vocabulary across the two passages; independent stylistic variation would erase a structurally significant authorial link.

11. Blasphemy against the Holy Spirit (3:28-29) — pastoral misapplication risk. Doctrinally narrow (a single verse) but pastorally severe: an anxious reader could misapply an under-noted rendering to their own conscience, producing genuine spiritual harm disproportionate to the term’s textual footprint.

12. γεέννα vs. नरक (9:43-48) — eschatological-cosmology collision. Real but lower-frequency risk (one passage) compared to items above; still requires the transliteration-plus-note protocol fixed in §3.1.

13. σῴζω dual-sense healing/salvation verb — sign-value dilution risk. Spread across many healing narratives (5:23 etc.), the risk is diffuse (any single occurrence is only Medium-High) but cumulative: if the dual-track protocol is applied inconsistently across a long translation project with multiple workers, Mark’s deliberate healing-as-sign strategy could be lost book-wide even though no single verse is mistranslated outright.

14. Cup (κτήριον, 10:38; 14:23-24,36) — ritual-vessel misassociation. Contained risk (three related passages); manageable with the single mandatory note established at first occurrence and carried forward.

15. गुरुजी as address to Jesus (9:5; 10:35,51; 11:21; 14:45) — guru-paradigm dilution. Present throughout but self-correcting if the balancing rule (§1.6) is consistently applied; ranked lowest among the Critical/High-tier ambiguities because no single occurrence, taken alone, threatens core doctrine — the risk is cumulative under-correction across the whole book rather than any one high-stakes verse.

---

5. Full-Book Chapter Review Log

Confirming PRD full-coverage mandate. Chapters already generating new gaps are cross-referenced to the section above; chapters generating no additional gap beyond what is logged are marked explicitly.

Chapter	New gap(s) identified	Cross-reference
1	Kingdom “has drawn near” (already-not-yet aspect); unclean spirit; disciple-call; immediately (style)	§1.2, §2.2, §1.3
2	Forgiveness of sins; Sabbath-lordship (positive प्रभु use); Son of Man (authority sense)	§1.7, §1.5, §2.1
3	Blasphemy against the Holy Spirit; Beelzebul/Satan; apostle-appointment	§1.7, §3.1
4	Mystery/parable; fear (first anchor, 4:40); sower/harvest फल-adjacent caution	§1.2, §1.3, §2.2
5	Legion; fear (second anchor, 5:36); σῴζω healing sense (Jairus’s daughter, hemorrhaging woman)	§3.1, §1.3, §1.7
6	ἐγώ εἰμι (6:50, first occurrence); compassion; hardened hearts; fear (third anchor, 6:50)	§3.3, §1.1, §1.3
7	Clean/unclean; Corban; tradition of the elders; Ephphatha	§1.7, §3.1, §2.2
8	Son of Man must suffer (first passion prediction); “get behind me, Satan”; deny self/take up cross; glory (10:37 anticipation)	§1.4, §1.1, §2.1
9	Second passion prediction; Transfiguration (“beloved Son, listen”); unbelief (9:24); Gehenna; cause to stumble; Messianic Secret silence (post-Transfiguration)	§1.4, §2.2, §1.3, §1.6
10	Core passage. Ransom; ἀντί; cup; baptism (metaphorical); servant/slave escalation; lord-it-over/domineer; authority; great; “prepared”/“not mine to give”; Son of David (Bartimaeus); “all things possible with God”	§1.4, §1.5, §1.8, §2.1
11	Hosanna; house of prayer/den of robbers; Lord (11:3 usage; consistent with §1.1)	§3.1, §2.2
12	Cornerstone/rejected stone; Son of David riddle (12:35-37); Sadducee resurrection debate	§1.1, §1.4
13	Kingdom eschatological horizon; abomination of desolation; the elect; Son of Man coming in clouds; gospel to all nations; watch/be alert (first anchor)	§1.2, §2.1, §4 item 10
14	Third passion prediction; Last Supper (body/blood of covenant); Gethsemane (Abba, flesh is weak, not my will but yours); watch/be alert (second, ironic anchor); ἐγώ εἰμι (second occurrence, trial); Messiah interrogation (parallel to 8:29)	§1.4, §1.8, §3.3, §1.6
15	King of the Jews (mocking irony); Eloi Eloi lama sabachthani; temple curtain torn; centurion’s Son-of-God confession (climax of the 1:1→15:39 bracket)	§1.1, §3.1
16	Resurrection proclamation (“he has risen; he is not here”); fear (final anchor, 16:8, textually significant ambiguous ending); longer-ending textual-critical note (gospel to all creation)	§1.1, §1.3

No chapter of Mark was found to contribute zero doctrinally relevant vocabulary — even chapters not carrying a Critical-tier term (e.g., ch. 11’s temple action, ch. 12’s debates) surface at minimum a Medium-risk term requiring native-speaker review, consistent with Mark’s densely doctrinal, fast-paced narrative style. All sixteen chapters are therefore represented above with an explicit finding rather than a silent omission.

---

6. Summary Recommendations Carried Forward to Phase 1 Step 1 (Core Glossary) and Beyond

1. Adopt all Part A (reused) and Part B (new) terms from 08_core_glossary.md as fixed; this analysis provides the justification for each new coinage and fence, not an alternative vocabulary.
2. Every crowded-neighborhood term identified in §2.2 requires a standing translator note, not a one-time footnote, because these collisions recur across many chapters — the note should be attached to the term in translation memory itself so it travels with every occurrence.
3. The ranked ambiguity list in §4 should directly drive Phase 2 review-routing priority within the Critical/High tier: items 1-3 warrant first-pass theologian attention in any batch processing order.
4. The core passage (Mark 10:35-45) alone contains four of this analysis’s top-eight ranked ambiguities (items 1, 5, 8, and components of 3 and 4), confirming its suitability as the curriculum’s theological anchor while underscoring that full-book coverage surfaces comparably severe risks elsewhere (notably 14:22-36 and 15:34-39) that must not be under-resourced relative to the anchor passage.

---

This document is the Step 8 companion to 07_semantic_analysis.md and 08_core_glossary.md. It must be loaded, alongside the baseline translation_memory.json, bible_term_registry.json, and doctrine_risk_registry.json, before any Phase 2 segment translation of Mark begins.