Step 8 — Linguistic Gap Analysis: 2 Samuel

Purpose and Method

This document performs the PRD Phase 1 Step 8 gap analysis for the destination language (English) against the five curriculum doctrines and the full 24-chapter span of 2 Samuel, with the core passage (7:1-17) as theological anchor. Because English is simultaneously the source and destination language in this pipeline (per the baseline’s structural note), “gap” here does not mean absence of a lexical equivalent in a foreign language. It means one of three concrete linguistic problems within English itself:

1. Missing vocabulary — no single English word carries the full Hebrew concept without addition of explanatory material (e.g., chesed, bayit’s triple pun).
2. Crowded semantic neighborhoods — an English word is available but sits inside a neighborhood of competing senses (secular, legal, denominational, pop-cultural, or adjacent-but-distinct theological) that must be fenced off explicitly or the wrong sense will be silently imported.
3. Typological proximity risk — an Old Testament term’s English rendering is identical or near-identical to a New Testament technical term already defined in the Romans baseline, creating pressure to collapse two related-but-distinct senses into one.

This document does not re-derive risk tiers already assigned in bible_term_registry.json and doctrine_risk_registry.json; it explains why each gap exists linguistically and what strategy closes it, so Phase 2 content generation has actionable guidance rather than a bare risk label.

---

Part 1: Doctrine Vocabulary Matrix

Doctrine	Available English Term(s)	Weaknesses of Available Term(s)	Recommended Strategy
The Davidic Covenant and the Promise of an Eternal Throne	”covenant,” “throne,” “forever/everlasting,” “house,” “kingdom"	"Covenant” is captured by real-estate/contract law (baseline-documented). “Throne” is captured by a globally dominant fantasy-media franchise built on cynical power struggles — nearly inverted from this passage’s stable, unilateral, unconditional promise. “House” defaults to the literal-building sense, burying the temple/dynasty pun that is the chapter’s structural hinge. “Forever” is drained by casual hyperbole (“this meeting is taking forever”). “Kingdom” risks fantasy-fiction drift (shared with baseline kingdom_of_god) and typological collapse with the NT kingdom of God.	Retain all five established English words (no invented neologism) but require mandatory disambiguating context on first substantive use per document: (a) explicitly name and set aside the Game of Thrones-style throne association; (b) explicitly unpack the bayit pun (temple offered / dynasty given) at 7:2, 5, 11, 13; (c) state that “forever” here is the passage’s own non-negotiable, repeated claim (vv.13, 16), not hyperbole; (d) state the kingdom’s historical-then-typological trajectory (Solomon now, Christ ultimately) rather than collapsing the two.
David’s Sin and Repentance	”sin,” “confession,” “forgiveness/pardon,” “guilt,” “iniquity”	English “sin” is trivialized by marketing (“sinfully delicious”) and resisted by therapeutic non-judgmentalism (shared baseline risk). “Forgiveness/pardon” risks typological collapse with the baseline’s fuller forensic justification — David is not “justified” in Paul’s technical sense at 12:13; his sin’s penalty is turned aside, but the passage does not describe the once-for-all declaration of righteousness Romans documents. English also flattens three distinct Hebrew terms (chattah, avon, pesha) into one general-purpose word family (“sin,” “iniquity,” “guilt,” “transgression” used near-interchangeably), losing the Hebrew’s own moral taxonomy.	Use “sin” as the base rendering (matches baseline exactly) but add a one-time explanatory note distinguishing OT “sin put away” (12:13) from NT “justification” so the terms are not read as synonyms. Where the Hebrew text uses more than one of chattah/avon/pesha in proximity (as in Nathan’s oracle and David’s psalms), gloss the distinction briefly (missing the mark / crookedness-guilt / active rebellion) rather than silently using “sin” for all three.
Consequences of Sin within the Covenant Family	”consequences,” “discipline,” “the rod,” “bloodguilt,” “curse"	"Discipline” and “the rod” both sit in a genuinely contested contemporary neighborhood (corporal punishment debates; parenting-method controversy; associations with abuse) that did not exist for the original audience. “Bloodguilt” and trans-generational consequence language collide with strong Western individualist assumptions that guilt cannot pass between generations or persons. “Curse” is captured almost entirely by profanity and superstition in ordinary use.	Retain “discipline” and “the rod” as base renderings (matching most established English Bible translation traditions) but add explicit framing: this is fatherly correction that never revokes relationship (7:15), not abuse or abandonment — and separately, that the text’s premise of corporate/trans-generational consequence (bloodguilt, 21:1; “the sword,” 12:10) is a real feature of covenant community, not an incidental ancient assumption to be quietly dropped. Do not substitute a softer word for “the rod” merely to avoid the parenting-method controversy; gloss instead.
God’s Steadfast Love despite Human Failure	”steadfast love,” “unfailing love,” “lovingkindness,” “mercy,” “grace,” “favor”	This is the curriculum’s single largest missing-vocabulary gap. No existing single English word captures chesed (loyal, promise-keeping love-in-action that persists despite the other party’s failure). “Love” alone defaults to feeling/emotion. “Grace” (baseline Critical term) is available but denotes something meaningfully different: grace in Romans is favor extended to the undeserving generally; chesed specifically presupposes an existing covenant/relationship being kept faithfully. Using “grace” for chesed would erase that relational-prior-commitment dimension. “Mercy” underemphasizes the loyalty/faithfulness component and overemphasizes withheld punishment.	Adopt “steadfast love” as the fixed, consistent rendering across this curriculum (already used in bible_term_registry.json), reinforced on first use per document with the gloss “covenant loyalty-love — faithful commitment that continues even when the other party fails or cannot repay it.” Explicitly distinguish, once per document, from baseline grace (favor to the undeserving generally) and from ordinary “love” (feeling). Do not vary the English rendering across lessons (e.g., alternating “unfailing love” and “lovingkindness”) except where directly quoting an established Bible translation’s specific wording, to preserve learner cross-lesson recognition per the baseline’s consistency rules.
The Messianic Hope Rooted in David’s Line	”Messiah/anointed,” “son of God,” “seed/offspring,” “throne,” “kingdom”	Rendering mashiach as capitalized “Messiah” in 2 Samuel would be anachronistic — the term here is a generic ritual designation for any consecrated Israelite king (Saul included, even post-rejection), not yet the technical eschatological title the baseline reserves for the NT. “Father/son” (7:14) is a genuine collision risk with baseline son_of_god (Christ’s eternal, essential, sinless Sonship) — the text explicitly includes correction for iniquity, which cannot describe Christ. “Seed of David” risks a premature messianic-only reading that bypasses the passage’s own first audience (Nathan is answering David about Solomon, per 1 Kings 8’s confirmation).	Render mashiach in 2 Samuel as lowercase “the LORD’s anointed” / “God’s anointed one,” reserving capitalized “Messiah” strictly for the baseline’s technical NT usage. Render 7:14 literally (“I will be to him a father, and he shall be to me a son”) but attach a mandatory theological note distinguishing this adoptive/disciplinable royal sonship from Christ’s eternal Sonship, presented as the pattern the NT (Hebrews 1:5) later typologically escalates — never as an original direct description of Christ. Teach seed-of-David fulfillment in two stages: Solomon (near, historical, confirmed) then Christ (far, the NT’s own move), never inverted.

---

Part 2: Missing Vocabulary vs. Crowded Semantic Neighborhoods

2.1 Genuinely Missing Vocabulary (no adequate single English word exists)

Hebrew Concept	Gap Description	Closing Strategy
chesed (steadfast love)	No English word combines “loyalty,” “covenant commitment,” “kindness in action,” and “persistence despite the other party’s failure” in one word.	Fixed compound rendering “steadfast love” + mandatory explanatory gloss on first use (see Part 1).
bayit (temple/dynasty pun)	English “house” happens to retain the pun structurally, so this is not a total vocabulary gap — but the pun’s function (a rhetorical reversal: David offers to build; God instead promises to build) is invisible unless flagged.	Explicit editorial note at each occurrence (7:2, 5, 11, 13) explaining the wordplay; do not rely on the reader noticing it unaided.
nevalah (Tamar’s word for Amnon’s coming act, 13:12)	English “folly” is too mild; there is no single common English word carrying “senseless, morally scandalous, covenant-community-disgracing act” at the correct register.	Retain “folly” for consistency with established English Bible translation tradition, but pair with a strengthening gloss (“an outrageous, disgraceful wrong”) every time it appears in expository material, not just on first use, since the mismatch in register recurs each time.
musar/shevet combined sense of “loving, relationship-preserving correction” (7:14-15)	English “discipline” and “the rod” each carry only part of the intended sense and both attract contested contemporary associations.	Do not seek a replacement word; instead pair the retained term with the passage’s own resolution clause (v.15, “but my steadfast love will not depart from him”) every time, so the relationship-preserving half of the concept is never presented without its counterpart.
Corporate/trans-generational damim (bloodguilt, 21:1)	Contemporary English has no live, non-technical word for guilt that can be inherited by a community across a generation; “bloodguilt” itself is a scholarly/biblical-translation coinage, not ordinary speech.	Retain “bloodguilt” (already used in established English Bible translations) but always accompany it with a short explanation of ancient Near Eastern covenant-oath seriousness and corporate solidarity — do not assume the word is self-explanatory.

2.2 Crowded Semantic Neighborhoods (an English word exists but must be fenced)

English Word	Competing Occupants of the Neighborhood	Fencing Strategy
”throne”	(1) literal furniture; (2) globally popular cynical-power-struggle fantasy franchise; (3) British/Commonwealth monarchy news coverage	Explicit contrast on first use: this throne’s defining feature is that it is unconditionally guaranteed by God, the opposite of the franchise’s contested, violently unstable thrones.
”house”	(1) literal building; (2) real-estate/property idiom (“housing market”); (3) the dynasty/family-line sense the chapter actually needs	Explicit three-way disambiguation the first time 7:1-17 is taught; note that English retains a partial cultural analogy (“the House of Windsor”) that can bridge to the dynastic sense.
”covenant”	(1) real-estate deed “restrictive covenant”; (2) employment non-compete “covenant”; (3) merely a synonym for “promise” in loose speech; (4) God’s unconditional covenant with David	Explicit statement that not all covenants in 2 Samuel are the same kind of promise — human political covenants (3:12-13; 5:3) are negotiated and mutual, God’s covenant with David (ch. 7) is unilateral and unconditional; the same English/Hebrew word must not be read as implying the same terms every time.
”forgiveness” / “sin put away”	(1) casual apology-acceptance (“it’s fine, I forgive you”); (2) baseline’s fuller forensic justification doctrine	Explicit statement that 12:13’s “put away” is real but describes penalty-removal within an ongoing relationship of discipline (12:10-14), not the baseline’s once-for-all forensic declaration; do not use “justified” as a synonym for what happens to David here.
”servant”	(1) menial employee; (2) historical slavery associations; (3) honorific royal-court title (“my servant David,” 7:5, 8)	State plainly, every time the honorific sense is in view, that this is a title of highest trust and privilege, the inversion of the menial connotation contemporary readers default to.
”anointed”	(1) cosmetic/skincare usage (“anoint with oil” in beauty contexts); (2) loose motivational usage (“anointed for greatness”); (3) the baseline’s capitalized technical “Messiah”; (4) 2 Samuel’s generic royal-designation sense	Lowercase, consistent rendering “the LORD’s anointed” throughout 2 Samuel material; never substitute capitalized “Messiah” for this book’s occurrences.
”righteousness” (in “justice and righteousness,” 8:15)	(1) baseline’s forensic Romans doctrine (Critical there); (2) this book’s royal social-ethics/fair-governance sense	State explicitly, at every occurrence in this book, that this is royal governance ethics, not Paul’s “declared righteous by faith” doctrine, despite the identical English headword.
”Spirit of the LORD”	(1) baseline’s Holy Spirit doctrine (permanent, universal, post-Pentecost personal indwelling); (2) this book’s task-specific, individual-empowerment sense (23:2)	State the real continuity (same divine Person) without asserting simple identity of experience; the OT pattern is occasional and task-specific, not the NT’s abiding indwelling of every believer.
”rest”	(1) wellness/self-care sense; (2) covenantal military-political security sense (7:1)	Brief anchoring note distinguishing “God-given security from surrounding enemies” from “relaxation/self-care,” parallel to the baseline’s handling of “peace."
"ark of God”	(1) adventure-film treasure-hunt relic (pop-culture “Ark” framing); (2) the sign of God’s covenant presence	Explicitly name and set aside the pop-culture association on first use, matching the baseline’s precedent for “Abba”/ABBA.
”Zion”	(1) contemporary political “Zionism”/state-of-Israel geopolitics; (2) David’s historically captured Jebusite fortress	Anchor explicitly to the narrative referent (2 Samuel 5:7) each time, per the baseline’s parallel caution on “Israel.”

---

Part 3: Transliteration vs. Paraphrase Decisions

Since destination language = English and source language = English, “transliteration” here refers specifically to whether a Hebrew term should be carried over as a recognizable loanword/technical term (as the baseline did for “Abba”) versus fully paraphrased into ordinary English with no residual foreign-language marker.

Term	Decision	Rationale
chesed → “steadfast love” (paraphrase, not transliteration)	Paraphrase	Unlike “Abba,” chesed has no comparable pop-culture foothold as a loanword in English-speaking Christian usage generally; transliterating it (“chesed”) would create an unfamiliar technical term requiring its own gloss with no compensating benefit, whereas “steadfast love” is already the wording of major established English Bible translations (ESV, NASB) and thus carries built-in cross-translation recognizability.
mashiach → lowercase “anointed,” not “Messiah,” and not transliterated “mashiach”	Paraphrase, with capitalization reserved	Transliteration would be unnecessarily technical for a generic royal term; using the baseline’s capitalized “Messiah” would be anachronistic. Lowercase English paraphrase correctly signals “generic, not yet technical” without inventing new vocabulary.
bayit → “house,” with pun explicitly unpacked (not transliterated)	Paraphrase with mandatory annotation	English “house” is not merely adequate but genuinely retains the underlying pun structure; transliteration would sacrifice this structural asset for no gain.
nagid → “prince” (paraphrase), with brief gloss distinguishing from hereditary usage	Paraphrase	No established English Bible tradition transliterates this term; “prince” combined with an explicit note (“appointed, not hereditary”) suffices.
Ark of God (aron ha’elohim) → “ark of God” (established English rendering, not transliterated)	Paraphrase/established rendering	Long-standing English Bible tradition already uses “ark”; transliterating the Hebrew (“aron”) would produce an unfamiliar, unhelpful term.
musar/shevet → “discipline” / “the rod” (established rendering, not transliterated)	Paraphrase/established rendering	Matches long-standing English Bible translation tradition; transliteration offers no benefit and would obscure rather than clarify.
YHWH (the divine name) → “LORD” in small capitals (established convention, not transliterated as “Yahweh”)	Established typographic convention	Preserves the existing, widely recognized English Bible convention distinguishing the personal covenant name (LORD, small caps) from the title “Lord” (kyrios/adonai); switching to a transliterated “Yahweh” would break consistency with virtually every English Bible translation this curriculum’s readers already know, and is not required to convey the personal-name distinction, which the small-capitals convention itself already signals once explained.
kaphar (atonement) → “atonement” / “make atonement” (established rendering, not transliterated as “kaphar”)	Paraphrase/established rendering	”Atonement” is already a fixed, recognizable English theological term from established Bible translation tradition; transliteration would add an unfamiliar term to an already Critical-risk concept without benefit.

General transliteration policy for this curriculum: Default to paraphrase using established English Bible translation vocabulary in every case. Reserve transliteration only for cases with a clear, targeted teaching purpose the English paraphrase cannot achieve (as the baseline did uniquely for “Abba,” to leverage and then correct an unavoidable pop-culture association). No term in this curriculum’s glossary meets that bar as strongly as “Abba” did; therefore no new transliterated headword is recommended for this curriculum’s vocabulary, in contrast to the baseline’s one transliteration exception.

---

Part 4: Ranked List of This Curriculum’s Highest-Risk Ambiguities

Ranked by combined severity of (a) doctrinal centrality to the five assigned doctrines, (b) strength of the competing wrong sense, and (c) likelihood of silent, confident misreading rather than a flagged comprehension gap.

1. “Father / son” at 2 Samuel 7:14 vs. baseline son_of_god. Highest risk in the entire curriculum: the identical English words “father” and “son,” applied to the Davidic king, sit one verse away from the passage the New Testament itself (Hebrews 1:5) applies to Christ — yet this verse explicitly includes correction for iniquity, impossible for Christ’s own eternal Sonship. A reader who has absorbed the baseline’s son_of_god doctrine may read 7:14 as describing Christ directly and be doctrinally confused when the text turns immediately to disciplining sin. Mandatory explicit distinction required every time this verse is taught.

2. “Steadfast love” (chesed) vs. baseline “grace.” Two Critical-risk terms sitting adjacent in the reader’s mind; without explicit fencing, learners will treat them as synonyms and lose chesed’s specifically relational, covenant-prior, loyalty-in-action dimension — the term this curriculum’s fourth doctrine is built on.

3. “Throne” and the fantasy-media association. Near-universal contemporary cultural exposure to a globally dominant, cynical-power-struggle media franchise using this exact word creates a strong, silently-imported, nearly opposite frame (unstable, violently contested rule) for a passage whose entire point is God’s unilateral, stable, unconditional guarantee. High risk of confident misreading precisely because the association is so pervasive it may not register as needing correction.

4. “Covenant” applied without distinguishing human political covenants from God’s unconditional covenant with David. The same English (and Hebrew) word appears for both mutual, negotiated human treaties (chs. 3, 5) and God’s unilateral promise (ch. 7); a reader who does not track this distinction may wrongly assume God’s covenant is conditional/mutual like the human ones surrounding it in the narrative, undermining the entire first doctrine.

5. “Justice and righteousness” (8:15) vs. baseline forensic righteousness/justification. Identical English headword to two of the baseline’s Critical-risk Romans terms, but a genuinely different sense (royal governance ethics, not forensic standing by faith). High risk of typological collapse specifically because the word is not merely similar but identical in spelling and register.

6. “Sin put away” (12:13) vs. baseline justification. Real risk that David’s forgiveness is read as identical to the New Testament’s forensic justification doctrine, erasing both the passage’s own historical particularity (David still faces real consequences, 12:10-14) and the New Testament’s distinct, fuller, once-for-all doctrine.

7. “Discipline” / “the rod” (7:14-15) and contemporary parenting-method controversy. A live, emotionally charged contemporary debate (corporal punishment, associations with abuse) did not exist for the original audience and risks either alienating readers or being misapplied as a proof-text for a specific modern parenting position unrelated to the passage’s actual point (God’s relationship-preserving correction of the covenant line).

8. “Anointed” vs. capitalized “Messiah.” Risk of anachronism if 2 Samuel’s generic usage (applied even to the rejected Saul) is silently capitalized and read as the technical eschatological title, flattening the very distinction the New Testament’s own typological argument depends on.

9. “Bloodguilt” and trans-generational consequence (21:1) vs. Western individualist assumptions. Risk that contemporary readers reject or silently reinterpret the text’s plain corporate-guilt premise rather than receive it as the narrative intends, weakening the third doctrine’s honest treatment of sin’s reach beyond the individual sinner.

10. “Spirit of the LORD” (23:2) vs. baseline holy_spirit. Risk of collapsing the OT’s occasional, task-specific empowerment pattern into the NT’s fuller, universal, permanent-indwelling doctrine, obscuring real redemptive-historical development between the testaments.

---

Summary Recommendation for Phase 2

Of the gaps identified above, five terms are assessed as requiring new dedicated translation-memory entries prior to Phase 2 content generation (already flagged as priority additions in analysis/08_core_glossary.md and now confirmed here on independent gap-analysis grounds): steadfast love (chesed), house/dynasty (bayit), throne (kisse), atonement (kaphar), and father/son, Davidic (2 Samuel 7:14). All five carry Critical risk, are central to at least one of this curriculum’s five assigned doctrines, and involve either genuinely missing vocabulary or a crowded semantic neighborhood strong enough to produce confident misreading without deliberate correction. No new transliterated headwords are recommended; this curriculum’s gaps are closed through paraphrase-plus-explicit-annotation, consistent with the baseline’s own general practice.