Linguistic Gap Analysis

Linguistic Gap Analysis: 2 Samuel

1. Purpose and Scope

This analysis identifies where Hindi (Devanagari, formal BSI OV/NV-register) has:

No adequate existing term for a theological concept load-bearing in 2 Samuel (missing vocabulary), requiring either a new compound phrase or a carefully fenced existing word;
An existing term shared by multiple, doctrinally distinct concepts in the same narrative (crowded semantic neighborhoods), requiring translator notes and consistent disambiguating conventions to prevent collapse;
Genuine transliteration-vs-paraphrase decision points, where the choice itself carries doctrinal weight;
The book’s highest-risk ambiguities, ranked by combined doctrinal severity and collision probability, to guide Phase 2 review routing.

Full-book coverage is maintained: every chapter of 2 Samuel 1–24 has been reviewed. Chapters contributing no new vocabulary beyond what earlier chapters or the baseline already cover are listed explicitly in §7 rather than silently omitted.

This document assumes the terms already fixed in analysis/08_core_glossary.md and assets/bible_term_registry.json (2 Samuel-specific) as settled inputs; it analyzes the reasoning behind those choices, surfaces residual risk, and ranks it for Phase 2 review-routing purposes.

2. Doctrine Vocabulary Matrix

Doctrine	Available Hindi Term(s)	Weaknesses of Available Term(s)	Recommended Strategy
The Davidic Covenant and the Promise of an Eternal Throne	वाचा (covenant, baseline); घराना (dynastic house, new); सिंहासन (throne, new); सदा के लिये / अनन्त तक (forever, new); अनन्त वाचा (everlasting covenant, new); वंश (seed/offspring, baseline pattern)	(a) घराना must carry a wordplay Hebrew executes with a single word (בַּיִת) shifting from literal to dynastic sense mid-chapter — Hindi has no single word doing both; (b) राज्य (kingdom) is homonymous with the baseline’s `kingdom_of_god` referent, risking conflation of David’s dynasty with God’s own reign; (c) सदा के लिये risks being heard as rhetorical hyperbole (as in ordinary Hindi speech, “सदा के लिये” is used loosely) rather than a binding, unconditional divine oracle.	Maintain the घर→घराना pivot exactly at 7:11 with a mandatory translator note explaining the single underlying Hebrew word. Gloss राज्य at first occurrence (7:12) distinguishing David’s human dynastic realm from परमेश्वर का राज्य. Render “forever” formulas identically at every occurrence (7:13,16,24-26,29; 22:51; 23:5) to make the unity of the promise visible across the whole book — inconsistency here is itself a translation error, not a stylistic choice.
David’s Sin and Repentance	पाप (sin, baseline); मैंने यहोवा के विरुद्ध पाप किया है (confession, new compound); क्षमा (forgiveness, new); व्यभिचार (adultery, new); हत्या (murder, new); दृष्टान्त (parable, new)	(a) क्षमा alone does not distinguish “guilt removed” from “temporal consequence remains” — ordinary Hindi usage of क्षमा implies a closed matter, risking readers concluding David suffered no further consequence, or conversely doubting the forgiveness was real once consequences appear; (b) पाप का अंगीकार (confession) risks being read as ritual/verbal formula (analogous to Hindu prāyaścitta-vacana or confession-as-ritual-speech-act) rather than genuine relational acknowledgment before a personal God.	Always pair क्षमा with an explicit teaching note distinguishing forgiveness-of-guilt (12:13b, immediate) from consequence-in-history (12:10-12,14, ongoing) — never let one paragraph state only one half. Render the confession as the full compound phrase, never abbreviated, and never render it with baseline’s `repentance` (मन फिराव) alone, since 12:13 is a specific confessional speech-act, not the general turning-of-life category (though the two are related and may be cross-referenced).
Consequences of Sin within the Covenant Family	ताड़ना (discipline, new); परिणाम (consequence, new); श्राप/श्रापित (curse, baseline reused); विद्रोह/बलवा (rebellion, new); अपमान/लज्जा (shame, new)	(a) ताड़ना risks collapsing into an impersonal cause-effect mechanism resembling कर्म-फल if not anchored to the Father-son relationship of 7:14; (b) परिणाम is deliberately chosen over फल for the same reason, but Hindi speakers may still supply a karma-frame by default given the pervasiveness of “जैसा करो वैसा भरो” idiom in daily speech; (c) श्राप carries live folk-belief connotations of a transferable, ritually liftable curse-force, risking readers looking for a counter-ritual remedy to Shimei’s curse rather than seeing David’s trust in providence.	Every occurrence of ताड़ना and परिणाम in chs. 12–24 requires the grammatical subject to remain personal and relational (a Father disciplining a son within an unbroken covenant, not an automatic law of the universe executing itself). A single boilerplate translator note, introduced once at 7:14 and referenced by pointer at each subsequent occurrence (12, 13, 15–20, 21, 24), is sufficient and preferred over repeating the full explanation every time.
God’s Steadfast Love despite Human Failure	करुणा (chesed, theological register, new); दया (chesed, general register, baseline reused); दत्तक-पुत्रता (adoption, baseline — contrast term only, not directly used in 2 Samuel)	No single existing Hindi word carries chesed’s full “covenant-loyal love that persists even through deserved discipline” sense. करुणा alone reads as generic compassion; दया alone reads as ordinary kindness; neither, standing bare, communicates covenant obligation freely kept despite the other party’s unfaithfulness — the exact theological point of 7:15 (contrasted explicitly with Saul, whose dynasty God did terminate).	Use करुणा only when supplemented by the phrase “अपनी वाचा के अनुसार” (according to his covenant) at the load-bearing occurrences (7:15; 22:51; implied 23:5); use बare दया only for simple interpersonal kindness scenes (1:23 context; 2:5-6; 9:1,3,7) where no covenant-technical weight is intended. This dual-register convention must be applied with zero exceptions or the doctrine’s central contrast (Saul terminated / David’s line never abandoned) is muted.
The Messianic Hope Rooted in David’s Line	वंश (seed, baseline pattern); सिंहासन (throne, new); अभिषिक्त (anointed-royal-office, new); मसीह (Messiah, baseline, reserved); पिता/पुत्र (davidic sonship, new); अनन्त वाचा (new)	(a) वंश’s singular/collective grammatical ambiguity (Solomon vs. ultimate Messiah) must be preserved, not resolved, in the base text — but Hindi translators habitually disambiguate collective nouns for clarity, risking accidental foreclosure of the messianic reading; (b) अभिषिक्त/मसीह is a fine but crucial distinction that inexperienced translators may collapse, anachronistically calling Saul or David “the Messiah”; (c) पिता/पुत्र (7:14) sits one verse away from a term (परमेश्वर का पुत्र) that must NEVER be used for the same referent, despite Hebrews 1:5 later applying 7:14 typologically to Christ.	Never disambiguate वंश’s referent within the translated running text itself — leave the collective singular noun as translated and reserve referent-clarification for footnotes/teaching notes only. Enforce अभिषिक्त for all pre-fulfillment royal-office uses (1:14,16; 19:21; 22:51; 23:1) and reserve मसीह exclusively for NT-confirmed eschatological reference in teaching material, never inside the 2 Samuel narrative text itself. Mandatory translator note at 7:14 distinguishing पिता/पुत्र from परमेश्वर का पुत्र, cross-referencing Hebrews 1:5 for the typological connection without collapsing the OT referent into the NT one.

3. Missing Vocabulary: Concepts with No Adequate Existing Hindi Term

These are cases where neither the baseline glossary nor ordinary formal Hindi supplies a ready term, requiring either a compound phrase or a carefully constructed new rendering.

Gap	Why It Is a Gap	Chosen Solution	Residual Risk
בַּיִת (bayith) literal/dynastic double sense (7:1-17)	Hebrew exploits a single noun meaning both “physical house” and “dynasty/lineage” — the chapter’s entire irony (David offers to build God a house; God instead builds David a “house”) depends on the SAME WORD shifting sense. No Hindi noun does both.	Two distinct nouns: घर (literal, vv.1-2, 5:11) and घराना (dynastic, from v.11 onward), bridged by a mandatory translator note at the v.11 pivot making the underlying wordplay explicit for the reader/teacher.	Splitting the wordplay into two words necessarily surfaces in translation what Hebrew leaves as a single elegant pun; some rhetorical force is unrecoverable without the note. The note is therefore promoted from “recommended” to “mandatory” status.
חֶסֶד (chesed) as covenant-loyal love that survives unfaithfulness (7:15; 22:51)	Neither करुणा (compassion) nor दया (kindness) alone carries the specific sense of a covenant obligation voluntarily, permanently kept even when the other party fails to keep their side.	करुणा + मandatory supplementary phrase “अपनी वाचा के अनुसार” at theologically load-bearing occurrences; बare दया reserved for low-stakes interpersonal contexts.	Even with the supplementary phrase, हिन्दी readers may still hear करुणा primarily as an emotional disposition rather than a legally/covenantally binding commitment; ongoing catechetical reinforcement (not lexical choice alone) is required to fully close this gap.
נָגִיד (nagid) vs מֶלֶךְ (melekh) — divine designation to office vs. dynastic/political kingship (7:8)	Hindi राजा covers both senses indiscriminately; there is no single common Hindi word isolating “one whom God has personally designated to rule” as distinct from “one who rules by hereditary or conquest right.”	प्रधान (with गloss) for nagid, राजा reserved for melekh contexts elsewhere in the book.	प्रधान is a serviceable but somewhat flat rendering; it lacks राजा’s narrative vividness. Native speaker review recommended to confirm प्रधान reads naturally in running narrative prose rather than as a bureaucratic title import.
בְּרִית עוֹלָם as a fixed, capstone terminological unit (23:5)	This is the one verse in 2 Samuel where “covenant” and “forever” are welded into a single named theological formula; Hindi has no pre-existing fixed idiom for this exact compound.	अनन्त वाचा, built by combining two already-independently-fixed renderings (वाचा from baseline; अनन्त from this book’s ad-olam convention).	Low residual risk PROVIDED the two component renderings have in fact been used with total consistency in chs. 7 and 22 beforehand — if either component drifted earlier in the book, 23:5’s capstone effect collapses. This is a consistency-audit item for Phase 2, not a lexical gap per se.
חִזָּיוֹן (chizzayon) as God-initiated, not devotee-sought, prophetic disclosure (7:17)	दर्शन is the natural, established Hindi Bible term, but ordinary religious usage of दर्शन (temple/guru darshan) inverts the direction of agency: a devotee travels to seek darshan of a deity/guru. Hebrew chizzayon is God unilaterally disclosing himself to a passive, addressed prophet.	Retain दर्शन (no better established alternative exists) but attach a mandatory translator note reversing the expected agency: God gives; Nathan does not seek or attain.	This is a “false-friend familiar term” risk rather than a true vocabulary gap — the word exists but its normal use-direction is backwards from the biblical sense. Flag as high-priority for the translator-note enforcement mechanism (see §6).
פ ליטה / restoring-through-discipline dual outcome (7:14-15 taken together)	English “he will discipline him… but my steadfast love will not depart” is a single coordinated promise; Hindi lacks an idiomatic short form holding both discipline-without-abandonment together without sounding contradictory.	Render as two clauses joined by परन्तु (but), explicitly retaining the concessive structure rather than compressing into a single simplified statement.	Risk of a rushed or paraphrastic Phase 2 rendering flattening the concessive structure into either “God punishes” or “God is only kind,” losing the doctrinally central both-and. Escalate to theologian review (already reflected in the doctrine_risk classification of this passage).

4. Crowded Semantic Neighborhoods Requiring Fencing

These are cases where an existing Hindi word is already doing service for multiple concepts — either within the baseline Romans/Galatians package, within 2 Samuel itself, or against the surrounding Hindu/Hindi religious semantic field — such that occurrences must be actively “fenced apart” with notes and consistent disambiguating conventions.

4.1 राज्य (rājya) — “kingdom”

Neighbors sharing this word: baseline kingdom_of_god (परमेश्वर का राज्य, God’s own sovereign reign) vs. this book’s davidic_kingdom (David’s human dynastic realm, 2 Samuel 7:12,13,16).
Fencing required: Mandatory translator note at first occurrence (7:12) stating explicitly that David’s राज्य is the human, historical, dynastic vehicle through which God’s typological purposes advance, not identical to or a synonym for परमेश्वर का राज्य. Never allow ग्रंथ-भर में (across the book) an unqualified राज्य to be read as if it were the baseline’s fully divine-kingdom sense.
Failure mode if not fenced: Either David’s dynasty is quietly divinized (a “kingdom of God on earth” reading that overclaims), or conversely God’s own kingdom is trivialized into a merely political/dynastic category.

4.2 दया / करुणा — “mercy/kindness” vs. chesed’s covenant-loyalty

Neighbors sharing this space: baseline mercy (दया, general compassion, Romans 9, 11); baseline kindness_of_god (कृपा, Romans 11:22 kindness/severity contrast); this book’s steadfast_love_chesed (करुणा, theological register).
Fencing required: Reserve कृपा exclusively for its baseline non-grace usage (never introduce it into 2 Samuel’s chesed passages, to avoid a third overlapping near-synonym crowding the same semantic space). Within 2 Samuel itself, apply the करुणा(+वाचा-phrase)/दया split rigorously per §2 above.
Failure mode if not fenced: Three semi-overlapping Hindi words (दया, करुणा, कृपा) doing service for at least four distinct theological registers (general mercy, kindness/severity contrast, covenant chesed, common grace) will blur into an undifferentiated “God is nice” impression, losing the doctrinal precision each register carries in its source context.

4.3 पवित्र (pavitra) — “holy”

Neighbors sharing this word: baseline sense (moral/relational set-apartness, Romans); this book’s use for the ark’s dangerous, consuming holiness (2 Samuel 6:6-7, Uzzah’s death).
Fencing required: A translator note at 6:6-7 clarifying that this occurrence foregrounds holiness’s dangerous dimension — the peril of approaching a holy God on merely human, uncommanded terms — which is a genuine but under-emphasized facet of the same underlying concept as the baseline’s moral-purity sense, not a separate word requiring separate treatment. No lexical change is needed, only teaching emphasis.
Failure mode if not fenced: Readers accustomed to the baseline’s “holy = morally set apart for godly living” association may find Uzzah’s death seemingly arbitrary or unjust without the note restoring holiness’s dangerous-otherness dimension.

4.4 दर्शन (darśana) — “vision”

See §3 above (missing-vocabulary entry); also a crowded-neighborhood item because दर्शन’s dominant living cultural sense (devotee-sought sight of deity/guru) actively competes with, rather than merely under-specifying, the biblical sense. This is the single most acute “familiar-word, reversed-agency” collision in the book.

4.5 अभिषिक्त / मसीह — “anointed” vs. “Messiah”

Neighbors sharing this conceptual space: baseline messiah (मसीह, Critical, reserved for the fulfilled eschatological title); this book’s anointed_one_royal (अभिषिक्त, descriptive royal-office title for Saul/David within the narrative).
Fencing required: As fixed in assets/bible_term_registry.json: अभिषिक्त for every in-narrative occurrence (1:14,16; 19:21; 22:51; 23:1); मसीह reserved exclusively for teaching-note cross-references to NT fulfillment, never appearing in the translated 2 Samuel text itself.
Failure mode if not fenced: Translating “the LORD’s anointed” as मसीह anywhere in 2 Samuel’s narrative text would assert that Saul or David is personally “the Messiah,” a direct doctrinal error and a significant Critical-risk drift.

4.6 पिता/पुत्र (davidic sonship) vs. परमेश्वर का पुत्र (Son of God)

Neighbors sharing this space: baseline son_of_god (Christ’s unique, eternal, ontological Sonship); this book’s davidic_sonship (a covenantal father-son relationship extended to a human dynastic heir, 7:14).
Fencing required: Mandatory translator note at every occurrence of 7:14 distinguishing the two categories while showing the NT’s own typological use of this verse (Hebrews 1:5) — the note must do both jobs (distinguish AND connect) or either the Christological doctrine is diluted (Solomon quietly deified) or the messianic trajectory is lost (the verse reads as having no further significance).
Failure mode if not fenced: This is arguably the single highest-stakes fencing requirement in the entire book, given its direct intersection with two Critical-risk doctrines simultaneously (Davidic Covenant and Sonship/Deity of Christ).

4.7 वाचा (vācā) — “covenant” (human treaty vs. divine covenant)

Neighbors sharing this word: political covenants between men (2 Samuel 3:12-13; 5:1-3) vs. God’s unconditional covenant with David (2 Samuel 7; 23:5).
Fencing required: Teaching notes at chs. 3 and 5 flagging these as human political treaties, distinct in kind (conditional, bilateral, revocable) from the unconditional, unilateral, divine covenant of ch. 7. No lexical change — वाचा remains correct in both cases — but the referent distinction must not be allowed to default to “just another treaty” in the reader’s mind when ch. 7 is reached.
Failure mode if not fenced: Students may wrongly assume the Davidic covenant is renegotiable or conditional on David’s performance, like the earlier political treaties, undermining the doctrine of an unconditional eternal promise.

4.8 शांति / मेल-मिलाप — political peace/reconciliation vs. soteriological peace/reconciliation

Neighbors sharing this word: baseline peace (शांति, Romans 5:1, peace with God through justification) and reconciliation (मेल-मिलाप, Romans 5:10-11, restored relationship with God); this book’s use of both for David’s political reconciliation with Israel after Absalom’s rebellion (2 Samuel 19).
Fencing required: A translator note at ch. 19 distinguishing this as circumstantial, interpersonal/political peace, while noting the intentional thematic analogy (both are restored relationship following a breach) without asserting theological identity between the two.
Failure mode if not fenced: Either the political reconciliation is read with inappropriately heavy soteriological weight, or, conversely, students fail to notice the deliberate literary echo the narrative invites between human and divine reconciliation patterns.

4.9 धार्मिकता (dhārmikatā) — “righteousness” (relative/comparative vs. forensic/imputed)

Neighbors sharing this word: baseline righteousness (Critical, forensic imputed standing before God received by faith, Romans 3-4) and imputed_righteousness; this book’s use in David’s song (2 Samuel 22:21,25, “according to my righteousness”), which is David’s own relative, comparative covenant-loyal conduct in a specific historical conflict.
Fencing required: MANDATORY translator note at 22:21,25 (already flagged Critical in the prior-output registry) stating plainly that this is not a claim to self-earned justification before God and must never be taught as if David is asserting NT-style forensic righteousness by his own merit.
Failure mode if not fenced: Without the note, 2 Samuel 22 could be read as contradicting Romans 3:10-20’s “no one is righteous,” or as David modeling self-justification — both serious doctrinal distortions given this term’s Critical status in the baseline.

5. Transliteration vs. Paraphrase Decisions

Term	Decision	Rationale
יהוה (YHWH)	Transliterate: यहोवा	Established BSI OV convention; must remain visibly distinct from परमेश्वर (generic Elohim) so the personal, covenant-bearing proper name is perceptible whenever it occurs — a paraphrase (“the LORD God”) would erase this distinction the Hebrew text itself maintains throughout.
מָשִׁיחַ (royal-office sense, Saul/David)	Paraphrase/descriptive title: अभिषिक्त (NOT transliterated as मसीह)	Transliterating here would import the baseline’s Critical-risk, eschatologically-loaded मसीह into a pre-fulfillment narrative context, anachronistically calling Saul or David “the Messiah.” A descriptive paraphrase correctly signals “one anointed to this office” without claiming eschatological fulfillment.
בְּרִית עוֹלָם	Paraphrase (compound of existing fixed renderings): अनन्त वाचा	No transliteration option exists (not a proper name); the compound must be built from already-fixed component renderings rather than invented afresh, to preserve cross-textual consistency with chs. 7 and 22.
חִזָּיוֹן / prophetic vision	Paraphrase using existing established term: दर्शन (with mandatory note)	No untransliterated alternative exists that is both natural Hindi and already established in Bible-translation tradition; transliterating the Hebrew (चिज्जायोन) would be unnatural and pedantic. The safer path is retaining the natural but note-guarded दर्शन rather than inventing new vocabulary.
רְפָאִים (Rephaim)	Transliterate: रापाई (with footnote gloss)	A paraphrase attempt (e.g., दानव, “demon/giant”) risks importing Puranic demon-mythology connotations entirely absent from the historical-ethnographic Hebrew referent. Transliteration with an explanatory footnote is the safer, doctrinally neutral path — consistent with how baseline handles other untranslatable proper/ethnic nouns.
נָגִיד (nagid) vs מֶלֶךְ (melekh)	Paraphrase: प्रधान vs राजा (not transliterated)	Both are common-noun office designations, not proper nouns; natural Hindi vocabulary exists and should be used, with the distinction enforced by consistent word-choice rather than transliteration.
Personal and place names (Nathan, Bathsheba, Uriah, Absalom, Ammon, Gibeon, etc.)	Transliterate per established BSI OV/NV forms	Follows the existing baseline convention (`12_ai_translation_requirements.md` §Transliteration Standards) of using established Hindi Bible proper-name forms; no new decision required, but must be audited for consistency across all 24 chapters in Phase 2.
אָמַן root family (ne’eman / “amen” etymological link, 7:16)	Do not transliterate the root itself; retain established आमीन transliteration only for its liturgical occurrence elsewhere, and use a native paraphrase (विश्वासयोग्य/स्थिर/दृढ़) for ne’eman in 7:16	The etymological connection is a teaching-note observation, not a translation instruction; the running text should read naturally in Hindi rather than force an artificial cognate-transliteration that would sound foreign and unnatural in 7:16’s narrative prose.

6. Ranked List of This Book’s Highest-Risk Ambiguities

Ranked by combined severity (doctrinal centrality × collision probability with Hindi/Hindu semantic neighbors), for Phase 2 review-routing priority. All items ranked “Critical tier” require mandatory human theologian review on every occurrence, consistent with the baseline’s escalation conventions.

“Christ lives in me”-class collision: davidic_sonship (7:14) vs. son_of_god. The single highest-stakes ambiguity in the book. A one-verse proximity error (using परमेश्वर का पुत्र for David’s heir, or omitting the distinguishing note) simultaneously damages two Critical baseline doctrines (Sonship of Christ; Deity of Christ) and this book’s own Messianic Hope doctrine. Tier: Critical.
House/dynasty wordplay pivot (7:1-2 vs. 7:11ff, घर→घराना). The chapter’s central rhetorical structure depends on this pivot; a translator defaulting to one word throughout (most likely collapsing everything to घर, the more common word) destroys the entire “David wants to build; God will build” irony that carries the covenant’s central surprise. Tier: Critical.
राज्य homonymy with baseline kingdom_of_god. Silent, because the word is common and unremarkable in isolation — a translator with no specific flag might never realize a note is needed, unlike more “exotic” terms that visibly demand caution. This makes it a stealth risk: high probability of being missed precisely because it looks unremarkable. Tier: Critical.
धार्मिकता in David’s song (22:21,25) read against Romans 3-4’s forensic sense. Same Hindi word, opposite argumentative direction (David affirms relative righteousness; Paul denies any human righteousness) — a reader moving between the Romans and 2 Samuel curricula without the mandatory note could conclude the curricula contradict each other on a Critical-risk term. Tier: Critical.
चesed’s करुणा/दया split (7:15; 22:51 vs. lower-stakes occurrences). High probability of translator drift toward using whichever word is more stylistically convenient in a given sentence, rather than tracking the theological-register distinction — and because both words are individually unremarkable, drift would not trigger an obvious red flag in ordinary proofreading. Tier: High.
दर्शन’s reversed agency (7:17). The risk is not that the word is wrong, but that its most common cultural association (devotee-sought darshan) runs in the opposite direction from the biblical meaning (God-initiated disclosure) — a “false friend” that feels safe precisely because it is familiar. Tier: High.
अभिषिक्त/मसीह boundary across chs. 1, 19, 22, 23. Four separate occurrences across a 24-chapter book increase the statistical probability that at least one will drift toward मसीह under stylistic pressure (मसीह being the more instinctively “correct-sounding” word for “anointed” to a translator not tracking this specific baseline reservation). Tier: High.
श्राप’s ritual-curse-magic resonance (Shimei, ch. 16) vs. the baseline’s judicial-anathema sense vs. plain human insult. Three distinct categories (human curse-utterance with no independent potency; ritually liftable folk curse; God’s fixed judicial verdict) share one Hindi lexical field, and 2 Samuel’s occurrence is the weakest of the three (mere human speech) — the risk is teaching material overstating its gravity by unconsciously importing the baseline’s judicial-anathema weight into Shimei’s comparatively minor scene. Tier: High.
ताड़ना/परिणाम’s proximity to कर्म-फल idiom (7:14; chs. 12-24). Extremely high cultural-collision probability given “जैसा करो वैसा भरो” is near-proverbial in everyday Hindi, but the doctrinal core (a Father’s relational discipline, not impersonal cosmic mechanism) is recoverable with a well-placed, reusable note — hence High rather than Critical, since the term itself (परिणाम, deliberately not फल) already resists the collision at the lexical level. Tier: High.
वाचा’s shared use for human political treaties (chs. 3, 5) and the unconditional divine covenant (ch. 7, 23). Moderate risk: the doctrinal payload (unconditional vs. conditional covenant) rests on narrative context rather than a separate word, so a careless summary could imply the Davidic covenant is renegotiable like the earlier treaties. Tier: Medium-High.
वंश’s grammatical singular/collective ambiguity (7:12). The risk is a translator’s well-intentioned impulse toward “clarity” prematurely resolving the near/far referent (Solomon vs. Messiah) that the Hebrew — and sound exegesis — deliberately leaves open in the base text. Tier: High (per the baseline’s own precedent for this exact pattern in seed_of_abraham, Galatians 3:16).
पवित्र’s dangerous-otherness facet (Uzzah, 6:6-7) underemphasized relative to its moral-purity baseline association. Lower risk because no lexical substitution is at stake — only a teaching-emphasis gap, correctable with a note rather than requiring any translation decision to change. Tier: Medium.

7. Chapters Confirmed Reviewed with No New Load-Bearing Vocabulary

Per the full-book-coverage mandate, the following chapters have been reviewed for this Step 8 analysis and confirmed to introduce no new theological vocabulary beyond terms already addressed above or in analysis/08_core_glossary.md:

Chapter 4 — narrates Ish-bosheth’s assassination; reuses house/covenant/kingship vocabulary already established in chs. 1-3. No new gap-analysis items.
Chapter 9 — David’s kindness to Mephibosheth; reuses baseline दया and this book’s सेवक/servant vocabulary; illustrates but does not newly complicate the chesed fencing already addressed in §2/§4.2.
Chapter 14 — the wise woman of Tekoa; reuses बुद्धि (wisdom_practical) fencing already addressed against ज्ञान/jñāna collision; no additional new terms.
Chapter 17 — reuses counsel/עֵצָה vocabulary (सम्मति/सलाह) established at ch. 16, fenced against यहोवा का वचन per the word_of_the_lord entry; no new items.
Chapter 18 — Absalom’s death and David’s lament; reuses the lament register (विलाप गीत/शोक-गीत) established at ch. 1; no new items.
Chapter 20 — Sheba’s rebellion and the wise woman of Abel; reuses विद्रोह/बलवा (ch. 15) and बुद्धि (ch. 14); no new items.

These chapters remain in scope for Phase 2 segment translation under the vocabulary decisions already documented; they require no additional Step 8 gap-analysis entries.

8. Summary Recommendations for Phase 2

Promote three items to mandatory-note status on every single occurrence (not merely at first occurrence): the घर/घराना pivot note (7:11), the davidic_sonship vs. son_of_god distinguishing note (7:14), and the धार्मिकता relative-vs-forensic note (22:21,25). These three carry the highest combined severity identified in §6.
Add a consistency-audit checkpoint before Phase 2 sign-off specifically verifying that सदा के लिये/अनन्त तक, वाचा, and करुणा(+वाचा-phrase) have been rendered identically across all their respective occurrences in chs. 7, 22, and 23 — the everlasting_covenant capstone term at 23:5 depends entirely on this prior consistency.
Flag राज्य for special reviewer attention precisely because it will not look flagged — recommend a standing checklist item in Phase 2 review templates reminding reviewers this common word carries a hidden Critical-tier collision risk, since its ordinariness is itself the danger.
Confirm अभिषिक्त/मसीह boundary enforcement at all four in-narrative occurrences (1:14,16; 19:21; 22:51; 23:1) as a discrete QA checklist item, given the statistically elevated drift risk noted in §6 item 7.
No further new vocabulary should be introduced in Phase 2 without following the Translation Memory Load and Enforcement Instructions in the baseline 12_ai_translation_requirements.md §“Translation Memory Load and Enforcement Instructions” — any newly discovered term must be added to translation_memory.json, assigned a risk tier consistent with this analysis’s methodology, and flagged for theologian review if Critical or High.

This document extends, and does not contradict, the baseline Romans/Galatians Language Package. All baseline forbidden substitutions (मुक्ति, मोक्ष, पुनर्जन्म, अवतार, शक्ति for God’s power, धर्म for righteousness/law, कर्म for works) remain in force throughout 2 Samuel, and this book introduces one further absolute prohibition specific to its own content: मसीह must never be used for Saul or David within the 2 Samuel narrative text itself.

Library content is free and openly licensed under CC BY-NC-SA 4.0 — share and adapt it for non-commercial use, with attribution to tri-bible.ai.