Linguistic Gap Analysis — Psalms

English → Hindi Language Package | Curriculum: Psalms | Core Passage: Psalm 23:1-6

Generated: Phase 1, Step 8 Precedes/companions: 07_semantic_analysis.md, 08_core_glossary.md Authority: Extends but never contradicts the baseline Romans/Galatians Language Package (translation_memory.json, bible_term_registry.json, doctrine_risk_registry.json, 12_ai_translation_requirements.md). All established renderings in those files are locked and are cited here, not re-derived.

Purpose: This document identifies, for the eight Psalms curriculum doctrines, (a) which Hindi vocabulary is genuinely available, adequate, or absent; (b) which semantic neighborhoods are so crowded with competing Hindu/Buddhist/folk-religious associations that they require deliberate lexical “fencing”; (c) where transliteration is preferable to paraphrase (and vice versa); and (d) a ranked inventory of the curriculum’s highest-risk ambiguities for Phase 2 routing.

---

1. Method

Each doctrine was tested against three questions:

1. Availability — Does standard/established Hindi Bible vocabulary (BSI OV/NV tradition) already carry an adequate term?
2. Collision — Does the most natural-sounding Hindi candidate sit inside a Hindu, Buddhist, folk-religious, or caste-social semantic field that would import unintended meaning?
3. Repair — Can the gap be closed by (a) reusing an existing term with a mandatory disambiguating note, (b) constructing a compound/descriptive phrase, or (c) transliterating and glossing?

Risk tiers (Critical/High/Medium/Low) and review routing follow doctrine_risk_registry.json exactly. Every Hindi rendering cited below is either already locked in the baseline or already proposed in 08_core_glossary.md/bible_term_registry.json — this document does not introduce new renderings, only analyzes the gap logic behind them and flags where the gap remains only partially closed.

---

2. Doctrine Vocabulary Matrix

2.1 The Character of God as Shepherd, King, and Refuge

Sub-concept	Available Hindi terms	Weakness of available terms	Recommended strategy
Shepherd	चरवाहा (generic herdsman); गोप/गोपाल/गोविन्द (forbidden)	गोप-family terms are the default Hindi vocabulary a bhakti-formed reader reaches for first — they are more natural than चरवाहा, which is the problem: naturalness itself is the collision vector, since चरवाहा sounds slightly flat/generic by comparison to the emotionally loaded Krishna vocabulary readers already possess.	Lock चरवाहा absolutely; supply a mandatory translator note on first occurrence (Ps 23:1) explicitly distinguishing YHWH’s covenant shepherd-care from Krishna’s Vrindavan cowherd/romantic persona. Never let a lesson gloss slip into गोपाल even informally.
King	राजा (generic); combined with महिमा for “King of glory”	राजा alone is doctrinally inert (Low/Medium) for a human king but escalates to Critical the instant it names God’s installed Messiah — the same word must silently carry two different risk tiers depending on referent, which automated tools cannot detect without context tagging.	Require every occurrence of राजा to be tagged at the segment-cache level with a referent flag (earthly king / God’s own kingship / Messianic King) so risk-tier routing is not lost.
Refuge	शरण; चट्टान/गढ़ (rock/fortress); सर्वशक्तिमान (Almighty, fixed compound)	शरण is structurally the same act — fleeing to a protector for shelter — as Hindu bhakti śaraṇāgati and the Buddhist triple-refuge formula. Hindi has no unclaimed synonym; अभय (fearlessness-refuge) and आश्रय are equally claimed by devotional/ascetic usage.	Accept शरण as unavoidable (no clean alternative exists) but require a standing translator note on first occurrence per psalm distinguishing covenant refuge in one personal God from refuge-taking as one devotional option among several. दुर्ग is permanently forbidden (Durga-root collision); चट्टान/गढ़ are the safe substitutes wherever “fortress” rather than “refuge” is the operative image.

Gap verdict: No true vocabulary absence here — the gap is entirely a crowded-neighborhood problem. Hindi is rich in protector/shepherd/refuge vocabulary; the richness itself is the risk, because every rich candidate is already claimed by a specific competing devotional system.

2.2 Lament and Honest Prayer

Sub-concept	Available Hindi terms	Weakness	Recommended strategy
Lament genre itself	विलाप (lament/wailing)	Adequate but under-used in North Indian Christian devotional register, which trends toward praise/testimony and under-represents protest-prayer; readers may find the genre culturally unfamiliar rather than lexically blocked.	No lexical fix needed; flag for native-speaker review on tone (see baseline’s honor/shame routing convention) rather than terminology.
”Why have you forsaken me”	तू ने मुझे क्यों छोड़ दिया (locked, Ps 22:1)	None at the lexical level; risk is exclusively in under-softening it.	Enforce verbatim; forbid any translator instinct to add a mitigating clause (e.g., “but I know you are near”) not present in the Hebrew.
Imprecatory prayer (cursing enemies)	No single fixed Hindi term; context-dependent	The nearest live Hindi/Indian folk category is तांत्रिक श्राप — a ritually-invoked, self-effective personal curse pronounced by a specialist, operative independent of any deity’s judicial action. Biblical imprecation is a covenant-lawsuit appeal to God, not a self-effective speech-act.	No single-term fix exists or should be sought; mandate a recurring teaching note (already logged in bible_term_registry.json) on every imprecatory psalm (109; 137:8-9) distinguishing prayer addressed to God’s justice from ritual cursing.
Waiting/hoping in unresolved distress	आशा रखना / बाट जोहना (locked)	बाट जोहना can register as passive fatalistic waiting if under-contextualized, echoing karma-patience (“this too will pass in its own time”).	Pair with explicit relational language (“in the LORD,” “for his word”) in every occurrence to keep the object of hope personal, not impersonal-cosmic.

Gap verdict: Vocabulary is available; the genre’s cultural unfamiliarity (not a lexical gap) is the primary transmission risk, alongside the imprecatory-cursing crowded neighborhood.

2.3 Praise and Worship

Sub-concept	Available Hindi terms	Weakness	Recommended strategy
Worship (verb/whole-life stance)	आराधना (locked); पूजा (forbidden)	None once पूजा is excluded — आराधना is a clean, uncontested Hindi Christian term.	No further action needed beyond enforcement.
Bowing/prostrating	झुक जाओ (preferred); दण्डवत (contextual only)	दण्डवत is the exact physical gesture Hindu devotees perform before a deity’s image, a guru, or an elder — same posture, different object; retaining it without आराधना attached would let the posture imply the object.	Always pair दण्डवत (if used at all) with आराधना, never with a bare verb of submission; default to झुक जाओ.
Sacrifice of thanksgiving	धन्यवाद का बलिदान	बलिदान/यज्ञ family carries transactional, merit-earning ritual-offering connotation (per baseline living_sacrifice caution).	Frame explicitly as heart-response contrasted with ritual, per Psalm 50:8-14’s own internal argument — the Hebrew text itself performs this contrast, which the Hindi should mirror rather than flatten.
”New song” motif	नया गीत	No collision; concrete and low-risk.	No action needed.
Selah	सेला (transliterated)	No Hindi equivalent exists for a musical/liturgical notation term; any attempted translation (“pause,” “rest”) would either look like an editorial stage direction or, worse, acquire unintended meaning.	Transliterate; do not translate.

Gap verdict: Well-supplied; the only crowded neighborhood is bowing/prostration gesture-vocabulary, already fenced by pairing rules.

2.4 Messianic Prophecy in the Psalms

Sub-concept	Available Hindi terms	Weakness	Recommended strategy
Anointing (Messiah-root vocabulary)	तेल से अभिषेक करना (locked)	अभिषेक is a live, ritually-efficacious Hindu practice (pouring oil/milk/ghee over a deity’s image, a Shivalinga, or a king’s head at coronation) popularly understood as itself activating divine presence/power in the object anointed. Because מָשִׁיחַ/Messiah shares this very root, the collision is structurally unavoidable, not merely stylistic.	Retain तेल से अभिषेक करना but require the mandatory translator note (already logged) on every occurrence keeping God as sole active agent bestowing a gift, never the rite itself as efficacious.
”Today I have begotten you”	मैं ने आज तुझे जन्म दिया है (locked)	जन्म दिया reads, if isolated from its royal-installation context, as literal birth — risking either an Arian-adjacent “the Son began to exist here” reading or, in the opposite direction, confusion with a repeatable guru/avatar-style periodic “birth” of the divine into history (echoing the very अवतार error the baseline forbids for incarnation).	Mandatory translator note on every occurrence framing this as declarative royal-enthronement language (paralleling ANE royal-adoption formulae), not ontological origination; cross-reference the baseline’s देहधारण/अवतार distinction.
Sheol	अधोलोक / शेओल (locked); पाताल (forbidden)	पाताल is not merely “a poor fit” — it is the proper name of an actual cosmological tier in Puranic literature (Naga-loka), meaning its use would not create vague resonance but a specific, named, wrong referent.	Absolute prohibition on पाताल; default to अधोलोक with शेओल transliteration available for higher-register or footnoted contexts.
Cornerstone / rejected stone	जिस पत्थर को राजगीरों ने निकम्मा ठहराया, वह भवन के सिरे का प्रधान पत्थर हो गया (locked)	Risk is confusion with the distinct, already-established baseline stumbling_stone (ठोकर का पत्थर) image — these are opposite trajectories (offense vs. vindication-into-foundation) built from unrelated OT texts.	Keep the two phrases lexically non-overlapping in all teaching material; never let भवन के सिरे का प्रधान पत्थर drift toward reusing ठोकर vocabulary or vice versa.
”The LORD said to my Lord”	यहोवा ने मेरे प्रभु से कहा (locked)	If a lesson author paraphrases loosely (e.g., “God spoke to the Lord”), Hindi’s flexible word order could obscure which of the two nouns is परमेश्वर/यहोवा and which is प्रभु, silently collapsing the two-referent argument the verse depends on.	Require this exact clause structure with both terms retained on every occurrence; forbid summarization that drops either referent.
Pierced (Ps 22:16)	छेदा गया है	No lexical collision, but a textual-critical gap: Hindi teaching material must not silently resolve the MT/LXX-DSS variant.	Footnote the textual question explicitly rather than translating around it.

Gap verdict: This is the curriculum’s most gap-dense doctrine — not because Hindi lacks words, but because the closest available words (अभिषेक, जन्म, पाताल) are simultaneously the most theologically loaded in the destination culture’s competing traditions.

2.5 Confession and Forgiveness (Psalm 51)

Sub-concept	Available Hindi terms	Weakness	Recommended strategy
Sin/transgression/iniquity (three-word Hebrew stack)	पाप (locked); अपराध (transgression); दोष (iniquity)	Hindi has three usable nouns, but general usage tends to flatten all three toward पाप, erasing Psalm 51’s own rhetorical stacking (חֵטְא/פֶּשַׁע/עָוֹן) which is a deliberate feature of the psalm’s confession structure.	Enforce the three-way distinction consistently within Psalm 51 teaching material specifically, even though elsewhere in Psalms a single पाप may suffice.
Cleansing (ritual-purity vocabulary redirected inward)	मुझे शुद्ध कर; मुझे धो दे	Unlike most of the baseline’s holiness vocabulary, שׁuddha here is not a false friend — the Hebrew itself performs the redirection from ritual to moral cleansing (explicit in vv.16-17) — but a reader unfamiliar with that redirection could default to a ritual-bathing (स्नान) reading.	Mandatory translator note stating the redirection is deliberate and textual, not a translation softening; cross-reference the baseline’s baptism caution against स्नान.
”Create in me a clean heart”	मेरे लिये शुद्ध मन उत्पन्न कर	Risk of collapsing सृजन/उत्पन्न (ex-nihilo divine creative act) into a self-improvement or yogic-attainment verb (सुधारना, निर्मल करना implying the practitioner’s own effort).	Require the same creative-agency verb family as सृजनहार throughout; forbid any verb implying self-directed purification.
Broken/contrite spirit	टूटा हुआ मन, दुःखित और चूर हृदय	Adjacent to (but must be kept distinct from) tapasya-style voluntary ascetic self-mortification, a merit-earning category in Indian religious practice where suffering itself generates spiritual credit.	Frame explicitly as Spirit-produced repentance received as a gift, not an achievement the sinner manufactures through self-affliction.
Holy Spirit (OT occurrence)	पवित्र आत्मा (locked)	Minor: Psalm 51:11 is one of very few explicit OT Spirit references; risk is theological (progressive revelation) rather than lexical.	Recommended note on progressive revelation without softening personhood.

Gap verdict: Vocabulary is adequate and, unusually for this curriculum, the Hebrew’s own internal move (ritual → moral) works with rather than against the Hindi lexicon — the risk is pedagogical clarity, not term availability.

2.6 The Righteous and the Wicked (Psalm 1)

Sub-concept	Available Hindi terms	Weakness	Recommended strategy
Way/path (two ways)	मार्ग / राह	मार्ग is the master-key term of India’s religious-pluralism vocabulary (bhakti mārga, jñāna mārga, karma mārga — “many paths, one destination”). Psalm 1’s entire argument is structurally the opposite claim: exactly two mutually exclusive ways with opposite, non-negotiable outcomes. This is the single highest-stakes term-choice in this doctrine because the grammar of Hindi religious pluralism is built into the word itself.	Mandatory translator note on first use of every “two ways” passage (Ps 1; 23:3; 25:4; 119:1; 139:24) stating explicitly “two ways, not many paths.” Consider supplementing with a numeral-marked phrase (दो मार्ग / दो राहें) in Psalm 1 specifically to make the binary structural, not merely lexical.
Righteous/wicked persons	धर्मी / दुष्ट	धर्मी reuses the धर्मी morpheme from the baseline’s Critical justification compound (धर्मी ठहराया जाना), which is a strength (doctrinal continuity) but requires vigilance that bare धर्म never creeps back in as a gloss on “righteous conduct.”	Reinforce the धर्मी-not-धर्म boundary explicitly in Psalm 1 teaching material, since this doctrine is exactly where a careless paraphrase (“the person who follows dharma”) would be most tempting and most damaging.
Fool (moral, not intellectual)	मूर्ख	Risk of reading as an insult to low intelligence or education rather than the Hebrew’s specific sense (practical, willful denial of God).	Gloss on first use: “lives as if there is no God,” not “lacks intelligence.”
Meditate (on the law)	मनन करना	मनन/ध्यान-adjacent Hindi vocabulary carries strong yogic/meditative-technique connotations (emptying the mind, attaining a state) in popular usage, which would invert the Hebrew’s sense of chewing on an external, given, verbal revelation.	Frame explicitly as reflective engagement with God’s spoken/written word, never content-free contemplative practice.
Perish (final destiny of the wicked)	नाश हो जाएगा	If narrated loosely, could be heard as one stage in an ongoing cycle rather than a final, linear outcome — collision with cyclical/rebirth cosmology.	Keep grammatically and rhetorically final; avoid any phrase suggesting continuation or return.

Gap verdict: मार्ग is this doctrine’s central, unavoidable, high-stakes crowded-neighborhood term; every other term in this doctrine is manageable with standard notes.

2.7 Covenant Faithfulness (Hesed)

Sub-concept	Available Hindi terms	Weakness	Recommended strategy
Hesed (steadfast covenant love)	करुणा (default) / वाचा की करुणा (covenant-explicit contexts)	This is the single largest genuine lexical gap in the entire curriculum: Hindi (and Sanskrit-derived religious vocabulary generally) has no word combining loyalty + faithfulness + mercy + relational commitment the way hesed does. करुणा is the best available anchor but is independently claimed by Buddhist ethics as a cultivated, self-generated virtue (a brahmavihara one trains oneself to feel toward all beings impartially) — nearly the opposite of hesed’s particular, covenant-bound, freely pledged loyalty to specific covenant partners.	Accept करुणा as unavoidable base vocabulary (continuity with existing Hindi Bible tradition, e.g., Psalm 136’s refrain) but require वाचा की करुणा as the mandatory compound wherever the covenantal, relationship-specific dimension is the actual teaching point (Ps 23:6; 89; 103; 107; 136 as a teaching unit) — never leave करुणा unqualified in a doctrinally load-bearing sentence. This is the highest-frequency Critical term in the whole curriculum and warrants a dedicated glossary card in every lesson touching it.
Covenant	वाचा (locked)	No collision; strong, established, relational (not merely contractual) Hindi Bible term.	No further action needed.
Promise/oath	प्रतिज्ञा (locked); शपथ (oath, Medium)	वरदान remains forbidden (deity’s boon for austerity/devotion — merit-conditioned, reverse of unconditional covenant promise).	Continue enforcement; no new gap.

Gap verdict: Hesed is a genuine vocabulary absence (no true equivalent exists), not merely a crowded neighborhood — the compound-phrase strategy is a workaround, not a discovered native term, and should be documented to reviewers as such rather than presented as a fully adequate solution.

2.8 Kingship and the Messianic King (Psalms 2 and 110)

Sub-concept	Available Hindi terms	Weakness	Recommended strategy
King/kingship (God’s installed Anointed)	राजा; महिमा का राजा (King of glory)	As noted in 2.1, राजा silently shifts risk tier by referent; Psalm 2 and 110 are exactly the referent that maxes out the risk (installed Messianic King = intersects Critical Lordship/Deity-of-Christ doctrine).	Theologian review mandatory on every राजा occurrence in Psalms 2, 45, 72, 110, 145 specifically (not just flagged generally); referent-tagging at segment-cache level as in 2.1.
”The LORD said to my Lord”	यहोवा ने मेरे प्रभु से कहा (locked)	See 2.4 — repeated here because this doctrine and Messianic Prophecy converge precisely at Psalm 110:1.	Cross-reference both doctrine entries in teaching material; do not treat as two separate translation decisions.
Priest (Melchizedek line)	याजक; पुजारी (forbidden)	पुजारी denotes a contemporary Hindu temple ritual functionary typically embedded in caste-based (often Brahmin) priestly lineage — importing caste-priesthood assumptions Melchizedek’s order is explicitly prior to and outside of.	Lock याजक; forbid पुजारी absolutely, with a note explaining the caste-lineage contrast is itself part of Melchizedek’s theological significance (a priest-king outside the Levitical/any caste system).
”The LORD reigns” (declarative present kingship)	यहोवा राज्य करता है	No lexical collision, but doctrinal-pairing risk: teaching material must not present God’s own eternal reign and the Messianic King’s derived, installed reign as competing or redundant claims.	Theologian review recommended to ensure the two kingship strands (Ps 93-100 vs. Ps 2/72/110) are taught as complementary, not duplicative.
Throne (applied to Christ)	तेरा सिंहासन, हे परमेश्वर (locked, Ps 45:6)	Low lexical-collision risk but Critical-by-doctrinal-linkage via Hebrews 1:8.	Theologian review required whenever this verse is used to teach Deity of Christ specifically (not merely Davidic kingship generally).

Gap verdict: No true vocabulary gap; the entire risk surface is doctrinal-linkage risk carried by an otherwise ordinary word (राजा) whose theological weight is invisible at the lexical level and must be captured by context-tagging rather than glossary substitution.

---

3. Missing Vocabulary vs. Crowded Semantic Neighborhoods

3.1 Genuinely Missing Vocabulary (no adequate native term exists; compound/descriptive construction required)

Concept	Why no native term exists	Workaround adopted	Residual risk after workaround
Hesed	Combines loyalty + faithfulness + mercy + freely-pledged covenant commitment; no single Hindi/Sanskrit-derived word carries all four components simultaneously.	करुणा (base) / वाचा की करुणा (covenant-explicit compound)	Compound is a workaround, not a discovered equivalent; risk of the covenant dimension quietly dropping out in casual paraphrase whenever वाचा is omitted. Requires standing vigilance, not a one-time fix.
Nephesh (as self-address, not “immortal soul”)	Hebrew nephesh names the whole living person/vitality, resisting the soul-body dualism embedded in most available Hindi religious vocabulary (आत्मा as a discrete, potentially disembodied/pre-existent self).	प्राण / मन (never आत्मा)	Workaround is stable but requires ongoing enforcement discipline, since आत्मा is the more “obvious” translator instinct for “soul” and will recur as an error unless actively checked every occurrence.
Imprecatory prayer (as a distinct genre-term)	No Hindi term names “covenant-lawsuit prayer appealing to God’s justice against an enemy” as opposed to self-effective ritual cursing; the two acts are lexically and functionally merged in popular usage.	No fixed term; context-dependent phrasing plus mandatory teaching note	Genuinely unresolved at the lexical level; the doctrine depends entirely on explanatory apparatus (notes) rather than a term choice, which is itself a residual pedagogical risk if notes are dropped in abbreviated lesson formats.
The paidagōgos-style “two ways” binary framing of מָלֶךְ/דֶּרֶךְ (way) as exactly two, not many	Hindi religious vocabulary for “path” is inherently pluralistic in connotation; no unmarked Hindi word for “way” carries an inherent binary-exclusivity sense.	मार्ग/राह plus mandatory “two ways, not many paths” note; optional numeral-marking (दो मार्ग)	The binary sense must be reintroduced editorially every time; it is not carried by the word itself, so any omission of the accompanying note silently reactivates the pluralist default reading.

3.2 Crowded Semantic Neighborhoods Requiring Fencing (native term exists but is heavily claimed by a competing tradition)

Hindi term/family	Competing claimant tradition	Fence required
गोप/गोपाल/गोविन्द (shepherd family)	Krishna’s Vrindavan cowherd/romantic persona in North Indian bhakti devotion	चरवाहा only; गोप-family absolutely forbidden; standing translator note on first occurrence.
दुर्ग (fortress)	Root of देवी दुर्गा, the widely venerated warrior-protector goddess	चट्टान/गढ़ only; दुर्ग forbidden throughout.
शरण (refuge)	Hindu bhakti śaraṇāgati (self-surrender to a chosen deity/guru); Buddhist three-refuges formula	Retained as unavoidable but requires disambiguating note distinguishing covenant refuge in the one true God from refuge-taking as one devotional option among many.
शक्ति / सर्वशक्तिमान (Almighty)	Shakti-goddess theology (Devi as cosmic feminine power)	शक्ति forbidden bare; सर्वशक्तिमान permitted only as the fixed compound.
अभिषेक (anointing)	Live ritual practice (deity image/Shivalinga/coronation anointing) understood as itself conferring/activating divine power	तेल से अभिषेक करना retained but requires mandatory note keeping God as sole active agent, the rite itself non-efficacious.
पाताल (Sheol candidate)	Actual named cosmological tier in Puranic literature (Naga-loka)	Absolutely forbidden; अधोलोक/शेओल only.
धाम / मंदिर (house of the LORD candidates)	धाम = Hindu pilgrimage-destination (Char Dham); मंदिर = Hindu temple	Both forbidden; घर (relational) / भवन (architectural) only.
दण्डवत (bowing)	Common Hindu devotional prostration before an image, guru, or elder	Permitted only paired with आराधना, never standing alone; झुक जाओ preferred as default verb.
मार्ग (way/path)	India’s multi-path religious pluralism (bhakti/jñāna/karma mārga)	Retained (no alternative exists) but requires the “two ways, not many paths” note on every Psalm 1-family occurrence.
पुजारी (priest candidate)	Contemporary Hindu temple ritual functionary, caste-embedded	Forbidden; याजक only.
मनन/ध्यान (meditate)	Yogic/meditative self-realization technique vocabulary	मनन करना retained but must be framed as reflection on God’s given, external word, never content-free contemplative emptying.
तांत्रिक श्राप (imprecatory-cursing neighbor concept)	Live folk-religious ritual cursing tradition	No Hindi term is used for biblical imprecation at all; the folk term is cited here only to define what must be distinguished by teaching note.
करुणा (hesed candidate)	Buddhist brahmavihara — cultivated, self-generated compassion toward all beings impartially	Retained as base term but requires वाचा की करुणा compound wherever covenant-specificity is the point; never presented as self-cultivated virtue.
आत्मा (soul/spirit — carried in from the baseline)	Vedantic ātman = brahman (individual self identical with impersonal universal Self)	Reserved exclusively for पवित्र आत्मा (Holy Spirit); नेफेש/soul contexts must use प्राण/मन instead.

---

4. Transliteration vs. Paraphrase Decision Log

Term	Decision	Rationale
Selah (סֶלָה)	Transliterate — सेला	No semantic content translatable into prose; it is a musical/liturgical notation. Paraphrasing (“pause here”) would read as an editorial stage direction absent from the Hebrew text’s own genre.
Hallelujah (הַלְלוּ־יָהּ)	Transliterate — हल्लेलूयाह	Already the fixed liturgical form across Hindi Christian tradition and the baseline; paraphrase (“praise Yahweh”) would break the Psalter’s own summary-command genre-marker function.
Amen (אָמֵן)	Transliterate — आमीन	Locked in the baseline; universal liturgical affirmation, no translatable content lost by transliteration.
Sheol (שְׁאוֹל)	Transliterate + gloss — शेओल (footnoted) / अधोलोक (default descriptive)	Paraphrase risk is severe (पाताल is a named wrong referent, not merely an imprecise gloss); transliteration with an explanatory gloss avoids importing a specific competing cosmology while still signaling “this is a proper technical term, not an ordinary Hindi word.”
Melchizedek (מַלְכִּי־צֶדֶק)	Transliterate — मलिकिसिदक	Proper name; standard Hindi Bible convention (consistent with दाऊद, मूसा, इस्राएल).
Messiah/Mashiach (מָשִׁיחַ)	Transliterate (already locked) — मसीह	Retained exactly per baseline; the term’s very shared root with “anointing” is precisely why the anointing verb (a different decision, below) must be paraphrased rather than built from the same root loosely.
Anointing with oil (מָשַׁח / דָּשֵׁן)	Paraphrase (descriptive phrase, not transliteration or single-word gloss) — तेल से अभिषेक करना	A single-word transliteration is not available in Hindi for this verb; the natural single-word candidate (अभिषेक used alone) is precisely the ritually-loaded term requiring fencing (§3.2). The full descriptive phrase, plus mandatory note, is the safer construction.
Hesed (חֶסֶד)	Paraphrase (compound construction) — करुणा / वाचा की करुणा	Transliteration (חesed) would be meaningless to a Hindi reader with no existing liturgical foothold (unlike Selah/Hallelujah, which already function as recognized worship-vocabulary loanwords in Hindi Christian usage); paraphrase via compound is the only viable path despite its imperfection (§3.1).
Begotten (“today I have begotten you”)	Paraphrase, not transliteration — मैं ने आज तुझे जन्म दिया है	No Hebrew term suitable for transliteration; the risk is entirely in paraphrase precision (declarative enthronement vs. ontological origination), managed by mandatory note rather than by lexical choice.
”The LORD said to my Lord” (two-referent formula)	Paraphrase with fixed referent-marking, not transliteration	Both नामs (परमेश्वर/यहोवा and प्रभु) are themselves already-locked Hindi terms; the decision here is about sentence structure preservation, not translation vs. transliteration in the usual sense.
Shaddai (שַׁדַּי)	Paraphrase (fixed compound), not transliteration — सर्वशक्तिमान	Transliterating “Shaddai” would produce an unfamiliar loanword carrying no inherited theological content for a Hindi reader; the fixed compound सर्वशक्तिमान is already an established, intelligible Hindi Christian divine title, provided the bare शक्ति morpheme is never detached from the compound.
Cornerstone/rejected-stone formula	Paraphrase (full clause), not single-term coinage	The image requires a narrative clause to convey vindication-through-rejection; no single Hindi noun captures it, and coining one would create an unfamiliar neologism with no Bible-tradition footing.
Zion (צִיּוֹן)	Transliterate — सिय्योन	Proper name with an already-established Hindi Bible form; no translatable content beyond the name itself.
Babylon (בָּבֶל)	Transliterate — बाबेल	Same rationale as Zion; established form.

General rule derived: Transliteration is preferred only where (a) the term is a proper name, (b) the term is a liturgical marker with no prose semantic content (Selah), or (c) the term already functions as a recognized loanword in Hindi Christian worship usage (Hallelujah, Amen). Everywhere a genuine concept must be conveyed and no such loanword tradition exists, paraphrase — however imperfect — is required, and the imperfection must be managed by mandatory translator notes rather than by seeking an elusive perfect single-word equivalent.

---

5. Ranked List of This Curriculum’s Highest-Risk Ambiguities

Ranked by combined severity (doctrinal centrality × collision probability × frequency), following doctrine_risk_registry.json tier conventions. All are routed to human theologian review unless otherwise marked.

1. Hesed (करुणा / वाचा की करुणा) — Critical. Highest-frequency load-bearing term in the curriculum (Ps 23:6 core-passage climax; Ps 89, 103, 107, 136). No true Hindi equivalent exists (§3.1); the best-available term is independently claimed by Buddhist self-cultivated-compassion theology. Every doctrinally load-bearing occurrence requires theologian review, not just first occurrence.

2. “Christ lives in me”-class advaita collision, transposed to nephesh (प्राण/मन, never आत्मा) — Critical. Second-highest-frequency term; the Psalter’s entire self-address genre (“Bless the LORD, O my soul,” Ps 42; 103; 104; 116; 146) depends on आत्मा never being substituted, or the individual self silently merges with the baseline’s already-documented Holy-Spirit/impersonal-universal-Self collision risk across dozens of psalms rather than a single verse.

3. Way/path (मार्ग) in Psalm 1’s two-ways structure — High, escalating to Critical in application. मार्ग is the master vocabulary of India’s religious pluralism; Psalm 1 makes an explicitly binary, mutually exclusive claim that is the structural opposite of “many paths, one destination.” This is the opening doctrinal unit of the curriculum’s Psalm 1 doctrine and sets the interpretive frame for every subsequent “way” reference.

4. Shepherd (चरवाहा) vs. Krishna cowherd vocabulary (गोप/गोपाल/गोविन्द) — Critical. Anchors the core passage’s opening verse (Ps 23:1) and the entire Character-of-God-as-Shepherd doctrine; the forbidden alternative is not a marginal mistranslation risk but the single most emotionally resonant, most natural-sounding devotional vocabulary a Hindi-speaking, bhakti-formed reader already possesses for exactly this image.

5. Anointing with oil (तेल से अभिषेक करना) and its Messiah-root entanglement — Critical. Ps 23:5 (core passage), 45:7, 89:20, 133:2. Uniquely dangerous because the collision is etymological, not merely cultural: מָשִׁיחַ/Messiah and the anointing verb share the same root, so the very concept the curriculum most wants to protect (Messiah) is linguistically adjacent to the concept most vulnerable to ritual-efficacy misreading (abhishek).

6. “Today I have begotten you” (Ps 2:7) — Critical. Double-edged risk (Arian-adjacent temporal-origination error vs. avatar-adjacent repeatable-divine-birth error) intersecting two Critical baseline doctrines (Sonship of Christ, Incarnation) in a single four-word Hindi clause quoted repeatedly in the NT.

7. “The LORD said to my Lord” (Ps 110:1) two-referent formula — Critical. The most NT-quoted OT verse; Hindi’s flexible syntax makes referent-collapse a live risk in any loosely paraphrased teaching material, and the doctrinal payload (Messiah as David’s Lord, not merely descendant) depends entirely on the two referents staying visibly distinct.

8. Sheol (अधोलोक/शेओल) vs. forbidden पाताल — Critical. Unusual in this list because the risk is not gradual collision but a categorical substitution error: पाताल is not a vaguely-adjacent term but the actual proper name of a specific, different cosmological location in Hindu Puranic literature, which would functionally relocate the psalmists’ death-and-hope theology into a different religious universe entirely.

9. Refuge (शरण) as unavoidable crowded-neighborhood term — High. Structural collision with bhakti śaraṇāgati and Buddhist refuge-formulas is unresolvable at the lexical level (no clean synonym exists), making this a standing risk across every refuge psalm (2:12; 46:1; 62:7-8; 91:2; 118:8-9) rather than a single-verse problem.

10. King (राजा) referent-tagging failure (Ps 2, 72, 110, 145) — High, escalating to Critical by referent. Because the same word carries dramatically different risk tiers depending on whether the king in view is human, God himself, or God’s installed Messiah, this is a systemic process risk (loss of context-tagging in batch translation) as much as a lexical one — flagged here because Phase 2’s parallel-worker batch processing (per the baseline’s Performance Notes) is specifically vulnerable to this kind of silent context-loss.

11. House of the LORD (घर/भवन) sense-selection (Ps 23:6; 27:4; 84; 122) — High. Requires consistent context-sensitive selection between relational-dwelling and architectural senses, with दोनों धाम and मंदिर permanently excluded; a translator defaulting to either forbidden term at any single occurrence reopens both the pilgrimage-destination and ritual-shrine collisions.

12. Imprecatory cursing (Ps 109; 137:8-9) — High. The only doctrine in this curriculum with no fixed term at all — entirely dependent on accompanying teaching notes for its theological safety, making it uniquely vulnerable to omission in abbreviated lesson formats where notes are trimmed.

13. Zeal and reproach vocabulary in Messianic suffering texts (Ps 69:9,19-21; cross-referenced to Ps 22) — High. Compounds honor/shame cultural dynamics (flagged for native-speaker review per baseline convention) with direct NT Passion-narrative quotation, requiring coordinated theologian + native-speaker review rather than either alone.

14. Pierced (Ps 22:16) textual variant — High. Not a translation-choice risk in the usual sense but a transparency risk: teaching material must disclose the MT/LXX-DSS textual question rather than silently adopting one reading as uncontested, especially given this verse’s Messianic-apologetic prominence.

15. Meditate (मनन करना) yogic-technique adjacency (Ps 1:2 and throughout Ps 119) — Medium, but ranked here for frequency: recurs dozens of times across Psalm 119 alone, and every occurrence carries some risk of assimilation to content-free contemplative practice unless consistently anchored to God’s external, spoken/written word.

---

6. Summary Recommendations for Phase 2

1. Load this document alongside 08_core_glossary.md, bible_term_registry.json, and doctrine_risk_registry.json before any Psalms segment translation begins, per the baseline’s Pre-flight Checklist convention.
2. Treat हेसद, नेफेש/soul, मार्ग (Ps 1 sense), शेओल, and the Ps 2/23/45/110/133 anointing-Messiah-Sonship cluster as requiring theologian review on every doctrinally load-bearing occurrence, not merely first occurrence — these are standing rules, not one-time flags.
3. Institute referent-level context tagging (not just term-level glossary matching) for राजा and प्रभु/परमेश्वर wherever Psalms 2, 45, 72, 93-100, and 110 are in view, since identical surface vocabulary carries divergent risk tiers by referent.
4. Where no adequate Hindi term exists at all (hesed, imprecatory prayer), do not treat the compound-phrase or note-dependent workaround as a closed gap — flag these to the Doctrinal Fidelity Review (Phase 2 Step 17) as open items requiring continued monitoring across every new lesson document produced.
5. Absolutely forbidden substitutions specific to Psalms (extending the baseline’s existing forbidden list): गोप/गोपाल/गोविन्द (shepherd), दुर्ग (fortress/rock), पाताल (Sheol), मंदिर/धाम (house of the LORD), पुजारी (priest), बare शक्ति as a divine title outside सर्वशक्तिमान.

---

Load this document as part of the Phase 1 analysis set feeding 12_ai_translation_requirements.md’s Psalms-specific extensions. See 08_core_glossary.md for the full term inventory and bible_term_registry.json for enforcement-ready entries.