Linguistic Gap Analysis
Linguistic Gap Analysis — Ezra (English → Hindi)
0. Purpose and Method
This document performs the Phase 1 Step 8 linguistic gap analysis for the Ezra curriculum, destination language Hindi. It answers three questions the downstream Phase 2 translation pipeline needs answered before any segment is translated:
- Where does Hindi already have safe, load-bearing vocabulary (inherited from the Romans/Galatians baseline) that Ezra can reuse without modification?
- Where does Hindi lack any ready equivalent for a concept central to Ezra’s doctrine set, requiring either a new compound, a transliteration, or a paraphrase — and where does Hindi instead have too many competing candidate terms, each carrying unwanted associations that must be actively fenced off?
- Which specific ambiguities carry the highest doctrinal stakes, and therefore require mandatory theologian review routing in
doctrine_risk_registry.json?
Ezra sits in a different register than Romans/Galatians: it is OT narrative, heavy with cultic/temple vocabulary, Persian-period administrative loanwords, and a covenant-renewal drama enacted through corporate confession. Its single greatest translation hazard is not abstract soteriological vocabulary (as in Romans) but concrete ritual-practice vocabulary — altars, burnt offerings, fasting, priesthood, purity/separation — landing in a Hindi lexical field saturated with living Hindu ritual equivalents. This document treats that hazard as the organizing theme.
All findings here are consistent with, and load-bearing for, 08_core_glossary.md and assets/bible_term_registry.json, which this analysis linguistically justifies.
1. Doctrine Vocabulary Matrix
For each of the six curriculum doctrines: what Hindi vocabulary is available, what is structurally weak about it, and what strategy Phase 2 must follow.
1.1 God’s Sovereignty over Pagan Nations and History
| Element | Detail |
|---|---|
| Available Hindi terms | परमेश्वर (baseline REUSE), यहोवा (NEW, Tetragrammaton), स्वर्ग का परमेश्वर (NEW), वही परमेश्वर है (NEW), पृथ्वी के सब राज्य (NEW), मन को प्रेरित किया (NEW), मुझे यह भार सौंपा है (NEW), परमेश्वर का विधान / संप्रभुता (baseline REUSE, providence/sovereignty family) |
| Weaknesses | (a) Hindi has no OT-register personal-name-of-God tradition of its own outside Bible translation; यहोवा is a Bible-specific coinage that untrained readers may parse as an obscure proper name rather than recognizing its weight as the covenant name. (b) “God of heaven” (स्वर्ग का परमेश्वर) risks being heard as a functional sky-deity title in a religious landscape with Indra/Varuna-type sky gods — a title, not an exclusivity claim. (c) “Stirred the spirit” risks assimilation to India’s living oracle/possession vocabulary (आवेश, भूत-प्रवेश), which would turn sovereign providential moving-of-the-will into a spirit-possession event. (d) The baseline’s providence entry (परमेश्वर का विधान) was built for a New Testament pastoral register (“all things work together”); Ezra needs the same underlying doctrine applied to a pagan king’s political decree, a use-case the baseline never anticipated. |
| Recommended strategy | Reuse परमेश्वर unmodified. Introduce यहोवा as the required OT proper-name register, glossed at first occurrence per teaching unit as “यहोवा परमेश्वर.” Every occurrence of “God of heaven” must be paired within the same teaching unit with the unqualified corrective “वही परमेश्वर है” (1:3) so diplomatic breadth and covenant exclusivity are taught together, never the first alone. Render “stirred the spirit” with मन (never आत्मा) plus a standing translator note distancing it from आवेश. Extend, do not replace, the baseline providence entry to explicitly cover God’s sovereignty over unregenerate rulers (Cyrus) as a distinct sub-case from God’s fatherly care of believers (Romans 8:28). |
1.2 Restoration of Temple Worship
| Element | Detail |
|---|---|
| Available Hindi terms | यहोवा का भवन / मन्दिर (NEW), वेदी (NEW), होमबलि (NEW), बलिदान (REUSE-adjacent to baseline living_sacrifice), याजक (NEW), लेवी (NEW transliteration), फसह (NEW), अख़मीरी रोटी का पर्व (NEW), झोपड़ियों का पर्व (NEW), समर्पण (NEW), आराधना (baseline REUSE), पवित्र (baseline REUSE) |
| Weaknesses | This is the single densest collision zone in the entire curriculum. Hindi’s ready-to-hand ritual vocabulary (मन्दिर, होम, यज्ञ, बलि, पूजा, पुरोहित/पंडित, व्रत) is drawn almost entirely from a living, currently-practiced Hindu ritual system with structurally similar surface features (a sacred building, a priestly class, fire-offerings, purity rules, festival calendars) but a radically different theology (repeatable meritorious ritual maintaining cosmic/relational order vs. a once-for-all typological system pointing to and fulfilled in Christ). Every noun in this doctrine’s vocabulary set has a Hindu ritual near-neighbor that is more natural and more fluent than the biblically safe alternative — which is precisely the danger. |
| Recommended strategy | Systematic “type/shadow, fulfilled in Christ” framing note attached at first occurrence per teaching unit to the whole offering/altar/temple vocabulary cluster, not just to individual terms. Prefer भवन over मन्दिर as the primary rendering for the temple building itself; मन्दिर permitted only as a secondary gloss with the fulfillment note attached. होमबलि is retained as the established compound (no viable safer alternative exists) but requires mandatory theologian review at every occurrence, not just first use, given its exceptionally close phonological and conceptual proximity to Vedic होम/यज्ञ. याजक/लेवी must never be rendered पुरोहित/पंडित. Passover and the unleavened bread feast should be actively taught as forward-pointing to Christ (1 Corinthians 5:7) — a positive strategy that converts a comprehension risk into a teaching asset rather than merely a hazard to avoid. |
1.3 Rebuilding and Covenant Renewal
| Element | Detail |
|---|---|
| Available Hindi terms | बहाली (baseline REUSE), वाचा (baseline REUSE), नींव (NEW), स्वेच्छा-भेंट (NEW), हाथों को मजबूत किया (NEW), यरूशलेम को जाना / ऊपर जाना (NEW), उसकी दया सदा की है (NEW) |
| Weaknesses | बहाली and वाचा transfer cleanly from the baseline because Romans 9-11 already established both as doctrinally load-bearing (Israel’s future restoration; covenant as relational bond). The risk here is not collision but thinness: the baseline वाचा entry was built for the grand redemptive-historical covenants (Abrahamic, Davidic, new covenant); Ezra 10:3 uses the same word for a local, corrective, community-specific pledge to put away foreign wives. Without a teaching note, students may either (a) inflate the Ezra 10 covenant to redemptive-historical weight it does not carry, or (b) deflate their sense of वाचा’s solemnity generally by seeing it used for a merely disciplinary local agreement. “Go up to Jerusalem” also risks importing Hindu तीर्थयात्रा (merit-earning pilgrimage) vocabulary if translated loosely as a journey of religious achievement rather than a commissioned, grace-grounded return. |
| Recommended strategy | Retain वाचा unmodified but add an explicit register note distinguishing “the great covenants” from “this local corrective covenant” every time Ezra 10:3 is taught. Render “go up” concretely (यरूशलेम को जाना / ऊपर जाना) and explicitly avoid यात्रा/तीर्थयात्रा vocabulary; a short note that this movement is commissioned by prophecy and decree, not initiated by the worshipper’s own merit-seeking, is recommended at first occurrence (Ezra 1:3). |
1.4 Confession and Corporate Repentance
| Element | Detail |
|---|---|
| Available Hindi terms | पापों का अंगीकार करना (NEW, REUSE-component of अंगीकार करना), मन फिराव (baseline REUSE), पाप (baseline REUSE), दोष / अपराध (NEW), उपवास (NEW), शपथ (NEW), कांपती हुई सभा (NEW), हमारे अपराध हमारे सिर से ऊँचे हो गए हैं (NEW), पवित्रस्थान में खूँटा/मेख (NEW) |
| Weaknesses | The single sharpest term-collision risk in this doctrine is अंगीकार करना, which the baseline reserved exclusively for the Romans 10:9-10 confession-of-faith-unto-salvation formula (“यीशु प्रभु है” confessed unto justification). Ezra 9-10 needs the same verb for a structurally different speech-act: corporate, communal confession of sin, not confession of faith. If students learn अंगीकार करना only through the Romans register, they may either fail to recognize Ezra’s confession as a real theological category, or conversely import a salvation-confession weight onto Ezra 9 that overstates its soteriological function (confession here does not itself justify; it is the fruit of already-covenant people responding to revealed guilt). उपवास is also a crowded neighborhood term — Hindu व्रत/उपवास practice is thoroughly merit- and boon-oriented, and “fasting” without a corrective note will default to that frame in readers’ minds. |
| Recommended strategy | Use पापों का अंगीकार करना consistently for Ezra’s usage, with a mandatory translator note at first occurrence distinguishing it explicitly from अंगीकार करना used for the Romans 10:9-10 salvation confession — same verb root, different object (पाप vs. यीशु प्रभु है), different theological function (repentance-response vs. justification-instrument). Keep दोष/अपराध (guilt-liability) lexically separate from पाप (general sin) to preserve Ezra 9’s legal-liability register. उपवास requires a standing translator note: biblical fasting here is humble petition to a God who is free to answer, not a technique that obligates God or accrues personal merit. |
1.5 The Role of Scripture in Community Renewal
| Element | Detail |
|---|---|
| Available Hindi terms | मूसा की व्यवस्था (baseline REUSE of व्यवस्था), शास्त्री (NEW), अपने मन को व्यवस्था खोजने के लिये तैयार किया (NEW), तेरे परमेश्वर की व्यवस्था / राजा का आदेश (NEW, disambiguated compound), भविष्यद्वक्ता (baseline REUSE), भविष्यवाणी (baseline REUSE), राजादेश / आदेश (NEW) |
| Weaknesses | व्यवस्था transfers cleanly and is non-negotiable (the baseline already forbids धर्म here). The acute new problem Ezra introduces is structural, not lexical: Aramaic דָּת (“dat”) is used in the source for both “the law of your God” and “the law of the king” (Ezra 7:25-26) — a single word doing double duty that English disambiguates with “law of God” / “law of the king” but that a literal Hindi parallelism (व्यवस्था … व्यवस्था) would re-collapse, eroding the baseline’s insistence that व्यवस्था names Torah exclusively. शास्त्री is also a crowded-neighborhood term: it is the standard title for a Hindu scholar-expert in the शास्त्र (Vedic/Hindu scripture corpus), and without context could imply Ezra’s authority derives from a parallel-but-different scriptural tradition rather than the one true revealed Torah. |
| Recommended strategy | Disambiguate डेट/dat: व्यवस्था exclusively for “the law of your God,” राजा का आदेश/नियम for “the law of the king,” with an explicit translator note explaining that Hindi is disambiguating what the single Aramaic term left fused in the source. Never allow both clauses to render with व्यवस्था. For शास्त्री, attach a first-occurrence note anchoring Ezra’s expertise specifically to व्यवस्था (Mosaic law) as a wholly separate textual authority from the Hindu शास्त्र corpus — the title is borrowed, the referent is not shared. |
1.6 Separation from Syncretism
| Element | Detail |
|---|---|
| Available Hindi terms | जातियों की अशुद्धता से अलग हुए (NEW), पवित्र वंश (NEW), देश के लोग (NEW), देश के लोगों से विवाह संबंध (NEW), अलग हुए लोग / पृथक हुए लोग (NEW), पवित्र (baseline REUSE) |
| Weaknesses | This is the doctrine with the highest single-term stakes in the book. Three separate but reinforcing collision hazards converge here: (a) अशुद्धता (impurity) sits directly adjacent to Hindu शुद्धि/अशुद्धि ritual-purity and caste-pollution categories; (b) पवित्र वंश (“holy seed/lineage”) sits directly adjacent to Brahmin-lineage/caste hereditary-purity ideology; (c) देश के लोग (“peoples of the land”) and the intermarriage prohibition sit directly adjacent to ethnic-nationalist or ethnic-purity readings that would be a serious pastoral distortion in the modern Indian context, where such readings could be misused to justify communal exclusion on ethnic rather than religious-fidelity grounds. Unlike most crowded-neighborhood problems elsewhere in this book, here the danger runs in both directions simultaneously: softening the text erases the real doctrine of covenant fidelity, while a literal, unglossed rendering actively invites a caste- or ethnicity-based misreading the text does not intend. |
| Recommended strategy | Every occurrence of this doctrine’s core vocabulary (terms 36, 46, 47, 55 in the core glossary) requires a mandatory theologian-authored teaching note stating explicitly and consistently: the concern is religious — undivided covenant worship, no mixing with foreign-deity devotion — not ethnic ancestry, caste rank, or ritual-pollution status. This note must travel with the vocabulary as a fixed unit, not be left to individual translators’ discretion per occurrence. Do not attempt to find a “safer” single-word substitute for अशुद्धता or वंश — the risk is structural (concept collision), not a matter of finding a better word, and any substitute would only relocate the same problem. |
2. Missing Vocabulary vs. Crowded Semantic Neighborhoods
Two distinct failure modes appear in this curriculum and must be handled with opposite strategies. Missing vocabulary = no natural Hindi term exists at all, requiring coinage, compounding, or transliteration. Crowded semantic neighborhoods = Hindi has several candidate terms, and the danger is that the wrong (more fluent, more natural-sounding) one gets used by default, importing unwanted theology. Fencing means explicitly ruling out the fluent-but-wrong candidates in the translation memory, the way the baseline already fenced मुक्ति/मोक्ष away from उद्धार.
2.1 True Missing Vocabulary (requires coinage/transliteration, no real collision risk)
| Concept | Gap | Resolution |
|---|---|---|
| Urim and Thummim | No Hindi concept for priestly oracle-lots at all | Transliterate: ऊरीम और तूमीम + mandatory explanatory gloss at first use |
| Nethinim | No equivalent social category | Transliterate: नतीनीम + explanatory gloss (“those given/dedicated to temple service”) |
| Treasurer (gizbar), Governor (Tirshata/pechah) | Persian administrative loanwords with no exact Hindi civil-service parallel | Use existing generic Hindi administrative vocabulary (खजांची; अधिपति/हाकिम) — functional equivalence sufficient, low doctrinal stakes |
| ”Weighed the vessels” accountability scene | No specific gap; simply unfamiliar as a spiritual-formation teaching point | Plain administrative vocabulary (तौला/नाप-जोख की) with a teaching note on financial integrity, not a translation problem per se |
| Feast of Tabernacles / Feast of Unleavened Bread | No Hindi festival-calendar equivalent | Descriptive compound translation (झोपड़ियों का पर्व; अख़मीरी रोटी का पर्व) + explanatory teaching note tying to the Exodus narrative, since OT narrative literacy is assumed low per the baseline’s audience profile |
2.2 Crowded Semantic Neighborhoods Requiring Active Fencing
These are the highest-priority entries for this analysis, because an unfenced crowded neighborhood is more dangerous than a true gap: a true gap is visibly a gap and forces a deliberate decision, while a crowded neighborhood invites an unreflective, fluent, wrong choice.
| Hindi lexical field | Competing candidates | Why it’s crowded | Fencing rule |
|---|---|---|---|
| The name/title of God | यहोवा / प्रभु / परमेश्वर / ईश्वर / भगवान | Five terms cluster around “God/Lord” with distinct required registers (Tetragrammaton vs. NT Lordship title vs. generic-but-doctrinally-precise vs. generic-acceptable vs. forbidden) | यहोवा reserved for OT covenant-name contexts only; प्रभु reserved for NT Lordship-of-Christ contexts (baseline); परमेश्वर generic default; ईश्वर/भगवान both forbidden throughout Ezra as throughout the baseline. Never let यहोवा and प्रभु substitute for each other even though both could loosely gloss as “Lord.” |
| Sacrificial/offering vocabulary | होमबलि / बलिदान / यज्ञ / बलि / प्रायश्चित्त | All five are live options for “offering” in general Hindi religious register, and several are also live Vedic/Hindu ritual terms | होमबलि retained only for עוֹלָה (burnt offering) as established compound; बलिदान for general sacrificial vocabulary per baseline living_sacrifice caution; यज्ञ forbidden absolutely (too direct a Vedic fire-ritual reference); प्रायश्चित्त reserved per baseline exclusively for NT propitiation (Romans 3:25) and must not drift into Ezra’s guilt-offering vocabulary, which instead uses दोष-बलि |
| The temple building | भवन / मन्दिर / गिरजाघर | मन्दिर is the most natural, fluent Hindi word for “temple” but is also the standard word for a functioning Hindu temple with ongoing पूजा/darshan practice | भवन primary; मन्दिर permitted only as glossed secondary term with fulfilled-in-Christ note; गिरजाघर (church building) is a baseline-forbidden false friend and must never appear here |
| Priestly/scribal office titles | याजक / पुरोहित / पंडित / शास्त्री | Hindu religious vocabulary offers close, fluent near-synonyms for every biblical priestly/scholarly office | याजक and शास्त्री retained as the only permitted renderings; पुरोहित and पंडित are hard-forbidden substitutions, consistent with the baseline’s existing prohibition |
| Purity/impurity vocabulary | अशुद्धता / अपवित्रता / छूत / जूठा | Multiple Hindi terms for ritual impurity exist, several tied to caste-pollution categories (छूत/untouchability-adjacent vocabulary; जूठा food-contamination vocabulary) | अशुद्धता retained (per baseline’s own “sin” entry note) as the least caste-coded option, but mandatory theologian note required distinguishing covenant-fidelity impurity from caste-pollution categories at every occurrence; छूत and जूठा are hard-forbidden — both carry direct untouchability/caste-contamination associations wholly foreign to the text’s meaning |
| Fasting/self-denial vocabulary | उपवास / व्रत / तपस्या | All three describe religious self-denial but carry escalating merit-accumulation connotations (उपवास mildest, तपस्या strongest ascetic-achievement connotation) | उपवास permitted as the least merit-coded option, with mandatory standing translator note; व्रत and तपस्या hard-forbidden — both are saturated with vow-for-boon and ascetic-merit logic incompatible with Ezra 8’s humble-petition framing |
| ”Seed/lineage/descendants” vocabulary | वंश / जाति / नस्ल / कुल | पवित्र वंश (“holy seed”) sits at the intersection of religious lineage (acceptable, per baseline seed_of_david/seed_of_abraham pattern) and caste/ethnic lineage (unacceptable) | वंश retained (consistency with baseline pattern) but जाति and नस्ल are hard-forbidden as renderings anywhere near this doctrine’s vocabulary, since जाति in particular is the very word used for caste/community identity in contemporary Hindi and would actively invite the misreading this doctrine must resist |
| ”Stirred the spirit” vocabulary | मन को प्रेरित किया / आत्मा जगाई / आवेश में लाया | Multiple candidate verbs exist for “arousing” a person’s inner disposition, several overlapping with possession/trance vocabulary | मन को प्रेरित किया retained; आत्मा-based renderings avoided to prevent confusion with पवित्र आत्मा (Holy Spirit, baseline-reserved); आवेश-family vocabulary hard-forbidden as it names literal spirit-possession in Indian folk/temple practice |
| ”Eye of God” idiom | दृष्टि / आँख / नज़र | आँख (literal eye) and नज़र (gaze, esp. evil-eye) are both live options, but नज़र specifically activates the evil-eye folk-belief system | दृष्टि (gaze/attentiveness, more abstract) preferred over both; नज़र hard-forbidden per the same logic as the baseline’s Galatians 3:1 “bewitched” caution |
3. Transliteration vs. Paraphrase Decision Framework
Ezra requires more transliteration decisions than Romans/Galatians because of its Persian-court administrative vocabulary and untranslatable cultic technical terms. The following decision rules govern each category:
3.1 Decision Rule
Transliterate when: (a) the source concept has no meaningful Hindi conceptual analogue at all (true gap, §2.1), so paraphrase would either be inaccurate or require an unwieldy multi-word gloss every occurrence; or (b) the term is a proper name or an already-established Hindi Bible-tradition transliteration (BSI OV convention) whose consistency across the whole Hindi Bible corpus outweighs any translation gain.
Paraphrase/compound-translate when: the source concept does have Hindi vocabulary available, but every single-word candidate carries an unacceptable doctrinal collision risk (crowded neighborhood, §2.2) — in which case a multi-word compound or descriptive phrase can thread the needle where no single word can (e.g., जातियों की अशुद्धता से अलग हुए rather than a single word for “separated”).
3.2 Transliteration Decisions
| Term | Decision | Rationale |
|---|---|---|
| यहोवा (YHWH) | Transliterate | No Hindi concept for a personal covenant-name of God exists outside Bible tradition; this is the establishing case, and BSI OV precedent already exists |
| लेवी, नतीनीम, फसह | Transliterate | Established names/technical terms with no native Hindi equivalent; explanatory gloss required for नतीनीम only |
| ऊरीम और तूमीम | Transliterate | Wholly untranslatable cultic technical term; gloss mandatory |
| All proper names (कुस्रू, दारा, अर्तक्षत्र, नबूकदनेस्सर, जरुब्बाबेल, शेशबज्जर, यशूअ, हाग्गै, जकर्याह, एज्रा) | Transliterate, established BSI OV forms | Proper-name consistency across the whole Hindi Bible corpus takes priority; यशूअ specifically must never merge with यीशु (see term registry caution) |
| आमीन-style liturgical transliterations (not present in Ezra but relevant to any cross-referenced doxology) | Transliterate per baseline precedent | Consistency with established baseline transliteration standard |
3.3 Paraphrase/Compound Decisions
| Term | Decision | Rationale |
|---|---|---|
| ”Separated from the filthiness of the nations” | Paraphrase as full compound clause, never a single word | No single Hindi word for “separation” avoids all three collision risks (caste purity, ethnic purity, ritual pollution) simultaneously; only the full clause with its theologian’s note can |
| ”Law of your God” / “law of the king” | Paraphrase-disambiguate into two distinct Hindi phrases | Source Aramaic fuses both into one word (דָּת); Hindi must actively separate what the source left ambiguous, the reverse of the usual translation problem |
| ”Stirred the spirit” | Paraphrase as मन को प्रेरित किया, not a single verb | Protects against both the possession-vocabulary collision and the Holy-Spirit-vocabulary collision simultaneously |
| ”Hand of the LORD was upon him” | Retain as idiomatic compound with translator note | A literal one-word “power” rendering would lose the providential-favor idiom; a fully paraphrased “God helped him” would lose the recurring structural refrain function across chapters 7-8 |
| ”Holy seed” | Retain as compound (पवित्र वंश) plus mandatory note, not replaced by a single word | As above — no single word avoids the caste-lineage collision; the compound-plus-note is the only viable strategy |
4. Ranked List of Highest-Risk Ambiguities
Ranked by combined severity (doctrinal centrality × collision proximity × frequency across the book). All Critical-tier items require mandatory theologian review at every occurrence per doctrine_risk_registry.json routing; this ranking determines review-priority sequencing within Phase 2.
| Rank | Ambiguity | Passages | Risk Tier | Why It Ranks Here |
|---|---|---|---|---|
| 1 | होमबलि (burnt offering) vs. Vedic होम/यज्ञ | 3:2-6; 8:35 | Critical | Closest phonological and conceptual proximity of any term in the book to a live, currently-practiced Hindu ritual (Vedic fire-sacrifice); highest risk that a reader assimilates the whole doctrine of restored temple worship into an ongoing meritorious-ritual framework rather than a fulfilled-in-Christ typological system |
| 2 | जातियों की अशुद्धता से अलग हुए / अलग हुए लोग (separation from syncretism) | 6:21; 10:11,16 | Critical | Bidirectional failure risk (softening erases the doctrine; literal rendering invites caste-purity misreading) — the only term cluster in the book where both translation extremes are simultaneously dangerous |
| 3 | पवित्र वंश (holy seed) | 9:2 | Critical | Direct collision with Brahmin-lineage/hereditary-purity ideology; compounding effect when read alongside rank 2 in the same chapter sequence |
| 4 | यहोवा vs. प्रभु vs. परमेश्वर register discipline | Throughout | Critical | Foundational to every other doctrine in the book; a single lapse (e.g., using प्रभु for the Tetragrammaton) would blur the OT/NT titular distinction the whole Language Package depends on |
| 5 | मन को प्रेरित किया (stirred the spirit) vs. आवेश (possession) | 1:1,5 | Critical | The book’s opening verse and its central sovereignty claim; a possession-register misreading would corrupt the doctrine of providence from the very first sentence students encounter |
| 6 | वही परमेश्वर है (he is God) vs. स्वर्ग का परमेश्वर (God of heaven) sequencing | 1:2-3 | Critical | The entire exclusivity argument depends on these two titles being taught as a pair, in sequence; teaching either title in isolation inverts or dilutes the monotheistic claim |
| 7 | तेरे परमेश्वर की व्यवस्था / राजा का आदेश disambiguation | 7:25-26 | High | Single Aramaic דָּת term risks collapsing the Torah/royal-decree distinction that is otherwise carefully guarded (व्यवस्था reserved exclusively for Mosaic law) everywhere else in the Language Package |
| 8 | पापों का अंगीकार करना vs. baseline अंगीकार करना (Romans 10:9-10 salvation confession) | 9:6-15; 10:1 | High | Cross-curriculum vocabulary reuse risk: same verb root, different theological function (repentance-response vs. justification-instrument); students moving between Romans and Ezra material are the specific vulnerability |
| 9 | उपवास (fasting) vs. व्रत/तपस्या merit-fasting | 8:21-23 | High | Fasting is one of the most universally recognized religious practices in the Indian context, making the merit-accumulation default reading unusually strong without active correction |
| 10 | देश के लोग / intermarriage prohibition vs. ethnic-purity reading | 4:1-4; 9:1-2; 10 | High | Real pastoral risk of the text being weaponized toward communal/ethnic exclusion if the religious-syncretism framing is not made explicit and repeated |
| 11 | यहोवा का भवन / मन्दिर vs. ongoing Hindu मन्दिर function | Throughout, esp. 1,3,6 | High | Highest-frequency collision term in the book (appears in nearly every chapter); cumulative exposure risk even though each individual occurrence is only High, not Critical |
| 12 | उनके परमेश्वर की दृष्टि उन पर थी (eye of God) vs. नज़र (evil eye) | 5:5 | High | Folk-belief collision parallel to the baseline’s own documented Galatians 3:1 caution; same mechanism, different chapter |
| 13 | यहोवा का हाथ उस पर था (hand of the LORD) vs. आशीर्वाद/स्पर्श ritual blessing-transfer | 7:6,9,28; 8:18,22,31 | High | Risk of recasting providential enablement as a magical touch-transference, paralleling guru-blessing devotional practice |
| 14 | याजकपद से अशुद्ध ठहराए गए (disqualified from priesthood, genealogical) | 2:61-63 | High | Genealogical verification for covenant office risks reading as validation of hereditary caste-office logic if not explicitly historicized and tied to a now-fulfilled arrangement |
| 15 | शास्त्री (scribe) vs. Hindu शास्त्र-scholar title | 7:6,11-12,21 | Medium | Title-borrowing risk is real but lower-stakes than the above, since the surrounding narrative context (Ezra’s devotion specifically to व्यवस्था) supplies disambiguation fairly reliably |
5. Summary Recommendations for Phase 2
- Load the full crowded-neighborhood fencing table (§2.2) into the Phase 2 AI system prompt’s forbidden-substitution list, extending the existing Romans/Galatians forbidden list rather than replacing it.
- Route all fifteen ranked ambiguities in §4 through the review tiers already assigned in
doctrine_risk_registry.json; items 1-6 require theologian review at every occurrence, not merely first use, given their combination of high frequency and high collision severity. - Attach the two “traveling teaching notes” identified in this analysis — (a) the temple/offering-vocabulary fulfilled-in-Christ note, and (b) the separation-from-syncretism religious-not-ethnic note — as standing fixtures of their respective vocabulary clusters in the translation memory, rather than leaving their inclusion to per-segment translator discretion.
- No new single-word coinages are recommended anywhere in this analysis; every unresolved collision risk is better handled by a compound phrase plus a standing note than by inventing a novel Hindi term with no reception history.
This analysis is the linguistic foundation for 08_core_glossary.md and assets/bible_term_registry.json; all doctrine-vocabulary decisions recorded there should be traceable to a finding in this document. See doctrine_risk_registry.json for review-routing enforcement and 12_ai_translation_requirements.md for the Phase 2 system-prompt integration of the forbidden-substitution rules established here.