Linguistic Gap Analysis: 1 Chronicles (English → English)

Curriculum: 1 Chronicles 1–29 Core passage: 1 Chronicles 17:1–15 Doctrines in scope: Genealogy and the Continuity of God’s People; The Davidic Covenant Reaffirmed; Worship and the Levitical Order; Preparation for the Temple; God’s Faithfulness across Generations Baseline authority: Romans translation_memory.json / bible_term_registry.json / doctrine_risk_registry.json (all renderings and risk conventions reused exactly where they overlap; extended, never contradicted, for new terrain) Companion artifacts: analysis/08_core_glossary.md, assets/bible_term_registry.json (1 Chronicles extension)

---

0. Method and Scope Note

Because English is simultaneously the source and destination language for this pipeline, “linguistic gap analysis” here does not mean cross-language lexical mapping. It means locating, for each doctrine, where the Hebrew concept and the available stock of contemporary English words fail to line up — either because:

1. Missing vocabulary — no ordinary English word carries the full concept (e.g., chesed), forcing either a periphrastic gloss or an accepted-but-lossy single-word rendering that must be actively supplemented; or
2. Crowded semantic neighborhoods — an English word exists and is fluent, but its contemporary “neighborhood” of everyday senses (legal, corporate, fantasy-genre, sentimental, political) is so densely populated that the biblical sense gets crowded out and must be fenced off explicitly; or
3. Obsolescence — the word is rare enough in ordinary speech that it produces a comprehension gap rather than active misreading (lower risk, per baseline convention).

This analysis spans the full book, chapter 1 through chapter 29. Genealogically dense chapters that introduce no new doctrine-bearing vocabulary are noted explicitly in §5 rather than silently skipped, per the full-book-coverage mandate.

---

1. Doctrine Vocabulary Matrix

Doctrine	Available Destination-Language Terms	Weaknesses	Recommended Strategy
Genealogy and the Continuity of God’s People	”sons of,” “descendants,” “genealogy,” “family tree,” “lineage,” “clan,” “firstborn,” “enrolled/registered”	English “family tree” and “genealogy” carry a hobbyist/ancestry-software connotation (23andMe, Ancestry.com genealogical research as a leisure pursuit) that flattens covenant-identity stakes into a genealogy-enthusiast’s curiosity project. “Sons of” misleads readers into assuming immediate parent-child pairs where the Hebrew regularly telescopes generations. “Firstborn” assumes familiarity with primogeniture inheritance customs largely absent from contemporary Western family law and experience. English has no natural equivalent for mishpachah’s land-bearing extended-clan sense; “family” defaults to the nuclear household.	Retain “genealogy,” “descendants,” “clan,” “firstborn,” “enrolled by genealogy” as fixed renderings (per glossary), but attach a standing explanatory frame at first occurrence per document: these lists are covenant-identity records, not hobbyist ancestry research, and generation-skipping is normal, not textual sloppiness. Explicitly note daughters named at points (2:16-17; 3:19; 7:15,24) are not thereby excluded from covenant standing, correcting a default assumption of an all-male list.
The Davidic Covenant Reaffirmed	”covenant,” “throne,” “kingdom,” “house,” “seed of David,” “forever,” “Father,” “anointed"	"Throne” and “kingdom” sit in a heavily fantasy-genre-saturated semantic neighborhood (epic fantasy fiction, film, games) that can reduce a real historical monarchy with binding theological guarantees to a fictional trope. “House” is genuinely ambiguous in English between “dwelling,” “temple,” and “dynasty” — precisely the three senses the Hebrew bayit deliberately activates in one wordplay across 17:1-14, a wordplay invisible unless the English rendering is held constant rather than varied for stylistic smoothness. “Forever” is hyperbole-worn from casual/sentimental overuse (“best friends forever”). “Father” risks conflation with the New Testament’s Critical-risk “Son of God” doctrine of Christ’s unique eternal Sonship.	Reuse baseline “covenant,” “Father,” “seed of David” exactly. Hold “house” to a single, unvaried rendering throughout 17:1-14 and 22:7-19, with an explicit editorial note unpacking all three senses at first occurrence rather than silently choosing one sense per verse. Explicitly restate that “forever” here is a formal covenantal guarantee, not sentimental hyperbole, and that its ultimate scope (dynastic line vs. messianic fulfillment) is clarified by later revelation. State plainly, every time “Father” appears in this typological register, that it denotes adoptive/covenantal royal sonship, not a claim of the king’s own deity — the reverse error direction from the New Testament’s own doctrine.
Worship and the Levitical Order	”priest,” “Levite,” “consecrate/sanctify,” “minister/service,” “singers,” “gatekeepers,” “by lot,” “ark of the covenant,” “tent/tabernacle"	"Priest” sits in a live denominational-contest neighborhood (Catholic/Orthodox ordained priesthood vs. Protestant priesthood-of-all-believers) without an agreed contemporary English-speaking-Christian consensus on how OT priesthood maps onto church office. “Levite” and “priest” are frequently and incorrectly used interchangeably by readers unfamiliar with the distinct hereditary classes. “Service/minister” collapses into “a church service” (the weekly event) rather than the lifelong structured vocational office the text describes. “By lot” sits inside the crowded “lottery/gambling/random luck” neighborhood, trivializing what the text presents as providential assignment. “Ark” collides directly with the vastly more culturally available “Noah’s Ark” referent.	Reuse baseline “holy”/“sanctification” family for “consecrate.” Explicitly distinguish “priest” from “Levite” at first joint occurrence (ch. 6) and state this curriculum’s own reading of the Aaronic priesthood as a distinct, non-repeatable, mediating office fulfilled in Christ, while noting the range of denominational readings without adopting all of them uncritically. Never render “ark” without the qualifying phrase “ark of the covenant” and an explicit one-line disambiguation from Noah’s Ark at first occurrence. Render “by lot” with an explicit tie to the baseline’s “providence” entry rather than leaving the gambling-adjacent English idiom unaddressed.
Preparation for the Temple	”house for the Name,” “dedicated,” “pattern,” “threshing floor,” “altar,” “census,” “atonement,” “angel of the LORD"	"Census” now denotes a routine, morally neutral administrative act in contemporary bureaucratic English, actively working against the text’s own presentation of David’s census as sinful presumption — a genuine and severe missing-context gap, not merely a crowded neighborhood. “Atonement” is both rare (obsolescence) and subject to a popular folk-etymology (“at-one-ment” = reconciliation) that quietly shifts it toward a therapeutic register, losing the judicial/sacrificial core. “Angel of the LORD” collides with a very densely populated, softened contemporary “guardian angel” neighborhood (greeting cards, cherubic imagery, benevolent spirit-guide pop culture).	Supply the theological reasoning for the census’s sinfulness explicitly (misplaced trust in military/numerical strength, and/or a self-glorifying act outside divinely sanctioned bounds) rather than leaving readers to import a neutral modern administrative frame. Flag “atonement” per the baseline’s own mandatory escalation rule for atonement/propitiation language; state both the judicial-sacrificial core and the risk of the softer folk-etymological drift. Actively restore the awe/dread register of “angel of the LORD” against the greeting-card-angel neighborhood at every occurrence in ch. 21.
God’s Faithfulness across Generations	”steadfast love,” “faithfulness,” “forever,” “the LORD reigns,” “unfaithful"	"Steadfast love” (for chesed) is a genuine missing-vocabulary case: no single English word captures covenant obligation + warmth + loyalty simultaneously, and even the two-word compound rendering is a scholarly convention unfamiliar to general readers. “Unfaithful” (for ma’al) risks being read as a vague synonym for “sinful” generally rather than the specific covenant-treachery sense that explains the exile theologically. “Faithfulness” itself, when applied to God, risks sounding like a personality trait/character compliment rather than covenant-keeping action verified across the entire genealogical and narrative record of the book.	Reuse baseline framework but do NOT default to a single word for chesed; supply the fuller range (loyal love, covenant faithfulness, merciful kindness) explicitly at each major occurrence (16:34,41; 17:13), consistent with the glossary’s Critical designation. Distinguish “unfaithful” (covenant treachery) from generic “sin” every time it explains a specific judgment (5:25; 10:13). Tie “God’s faithfulness” explicitly back to the concrete genealogical record (chs. 1-9) and the fulfilled Davidic promise (ch. 17, cf. 2 Sam. 7) as demonstrated action, not merely asserted character.

---

2. Missing Vocabulary vs. Crowded Semantic Neighborhoods

2.1 Missing Vocabulary (no adequate single English word exists)

These require periphrastic glossing every time, not a one-word fix:

Hebrew term	Gap	Why no English word suffices
chesed (steadfast love)	Severe	Combines legal/relational obligation, active loyalty, and warm affection in one word; English forces a choice among “love” (loses obligation), “mercy” (loses warmth), “faithfulness” (loses affection), or “kindness” (loses covenant weight).
ma’al (unfaithful/trespass)	Moderate	English “unfaithful” or “sin” both under-specify the specifically covenantal betrayal-of-trust sense that Chronicles uses to explain concrete historical judgments (exile, Saul’s death).
nagid (ruler/designated leader)	Moderate	No English word distinguishes divinely designated leadership (prior to full royal installation) from hereditary succession or popular election; “ruler,” “prince,” “leader” each default to one of the wrong frames.
tabnit (temple pattern, “by the Spirit”)	Mild	English “pattern”/“blueprint” is serviceable alone, but the accompanying claim of revelatory origin (“by the Spirit,” 28:12) has no natural single-word English equivalent that keeps both the architectural and revelatory senses simultaneously active.
avodah (cultic service/ministry)	Mild	English “service” or “ministry” alone cannot hold together the term’s full range from manual/slave labor to consecrated lifelong liturgical office; the single Hebrew root’s breadth is lost either way.

2.2 Crowded Semantic Neighborhoods (a fluent English word exists but competing senses dominate)

These require active fencing — explicit exclusion of the dominant competing sense — rather than a vocabulary substitution:

English word	Competing occupants of the neighborhood	Fencing required
house	dwelling/real estate; “House” as legislative body; “on the house” (idiom); TV genre (“house drama”)	Fence against “temple” and “dynasty” collapsing into mere “residence”; hold the word constant across 17:1-14 so the reader can see all three senses Paul… [Chronicles] deliberately layers.
kingdom / throne	fantasy fiction, film, gaming franchises; “throne” also toilet-humor idiom in casual speech	Fence against fictional-realm connotations; state plainly this is a real historical monarchy with binding, still-unfolding theological consequences.
election / chosen	political voting (dominant, near-total)	Reuse baseline fencing language exactly; ch. 28’s dense stacking of election vocabulary (28:4-6,10) requires the correction repeated at high frequency, not stated once and assumed to carry forward.
census	routine government/statistical administration (dominant, neutral)	Fence hardest of all entries in this table: readers must be told this specific census carried moral weight the modern administrative act categorically does not.
angel	guardian-angel/greeting-card imagery; “on my shoulder” idiom; horror/fantasy “dark angel” tropes	Fence against sentimentalized protector imagery; restore the awe/dread, judgment-bearing dimension.
atonement	folk-etymology “at-one-ment” (reconciliation, therapeutic “healing a relationship”)	Fence against draining the judicial/sacrificial core; this triggers the baseline’s mandatory theologian-review escalation rule.
by lot	lottery, gambling, random luck	Fence against “random chance” and connect explicitly to providence.
ark	Noah’s Ark (dominant cultural referent for readers with limited church background)	Never leave “ark” unqualified; always “ark of the covenant” with a one-line disambiguation on first occurrence per document.
servant	historical chattel slavery, contemporary labor-rights discourse	Fence as an honor-title (“my servant David,” 17:4,7), explicitly distinguishing from social bondage.
priest	denominational-contest neighborhood (Catholic/Orthodox ordained office vs. Protestant priesthood-of-all-believers)	Not a false-friend problem but a live contested-meaning problem; state this curriculum’s reading transparently, per baseline denominational-transparency convention.
vision	corporate “vision statement,” personal-development “life vision”	Fence against self-authored strategic planning; restore externally-given, prophetic-revelatory sense.
name (“make a name,” 17:8)	self-achieved fame/branding (dominant secular idiom)	Fence against self-achievement; the greatness of David’s name is God’s sovereign gift, reversed agency exactly parallel to the baseline’s “calling” note.

---

3. Transliteration vs. Paraphrase Decisions

Because destination = source = English, “transliteration” here concerns whether to (a) retain a Hebrew-derived loanword/technical term as-is, (b) supply an English paraphrase/gloss, or (c) use a fixed hybrid (established English rendering + standing explanatory note). Decisions below extend, and must not contradict, the baseline’s own transliteration choices (e.g., baseline retains “Abba” transliterated; renders charis as “grace,” not a transliteration).

Term	Decision	Rationale
YHWH → “the LORD” (small capitals)	Fixed hybrid: retain the traditional English small-capitals convention, not a transliteration (“Yahweh”/“YHWH”)	The small-capitals convention is the working convention of virtually every major English Bible translation this curriculum’s audience will have encountered (including the site’s own NLT citation standard); switching to a transliterated “Yahweh” would create needless discontinuity with the reader’s existing Bible and with the baseline’s own “Lord” (kyrios) entry. Must be actively taught as God’s personal covenant name at first occurrence (17:1), not assumed already understood via the typographic convention alone.
chesed → “steadfast love”	Paraphrase/gloss, not transliteration	A theological loanword (“chesed”) would be opaque to a general audience with no Hebrew background; “steadfast love” is the most widely recognized English Bible-translation-tradition rendering and should be retained, but always with the fuller explanatory range supplied per §1 above rather than left to stand alone.
Levi / “Levite”	Retain as an established English loanword	”Levite” is already fully naturalized in English Bible vocabulary across all major translation traditions; no better paraphrase exists, and the term is stable enough to function as a fixed technical term needing only brief functional definition, not replacement.
kohen / “priest”	English gloss, not transliteration	”Priest” is the universal English Bible-translation-tradition rendering; a transliteration would be needlessly opaque. The risk here is denominational contest over meaning, not lexical unfamiliarity, so the fix is explanatory framing, not a different word.
mashach / “anointed”	English gloss with explicit typological note	Retain “anointed” (not “Messiah”) for the generic verb’s lower-case royal-installation sense in 11:3 and 29:22, reserving capitalized “Messiah” for the baseline’s distinct eschatological entry; state the shared root and genuine (but not identical) typological relationship explicitly rather than silently merging or silently separating the two.
bayit / “house”	English gloss, held deliberately constant	Discussed in §2.1; a single fixed English word is required precisely so the wordplay remains visible, rather than translating contextually to “palace,” “temple,” or “dynasty” as smoother English style might otherwise favor.
goral / “by lot”	English gloss with providence cross-reference	No transliteration tradition exists for this term in English Bible usage; the fix is fencing against the “lottery” neighborhood (§2.2), not a different word choice.
tamid / “continually”	English gloss	Low risk; standard rendering, no transliteration warranted.
Proper names (David, Israel, Solomon, etc.)	Retain standard established English Bible-translation forms	Per baseline convention for proper names; no new decision required.

General principle: transliteration (retaining a Hebrew loanword) is reserved for terms already fully naturalized in the English Bible-translation tradition (“Levite,” proper names) or where no English word exists at a workable register (none identified as requiring fresh transliteration in this book — unlike the baseline’s “Abba,” 1 Chronicles supplies no comparable case). All other new-to-this-curriculum terms receive an English gloss plus explicit fencing/explanatory apparatus, consistent with the baseline’s own strong preference for glossed English terms over transliterated loanwords wherever an adequate English rendering exists.

---

4. Ranked List of Highest-Risk Ambiguities (1 Chronicles)

Ranked by combined severity of (a) how confidently readers will supply a wrong sense, and (b) doctrinal weight of the passage affected. Top tier requires mandatory human theologian review per baseline escalation convention.

1. “House” (bayit), 1 Chronicles 17:1-14 / 22:7-19 — The entire theological turn of the core passage (David wants to build God a house; God instead promises to build David a house) depends on English readers perceiving one word carrying three senses at once. Silent stylistic variation would destroy the chapter’s central rhetorical device. Highest risk in the book.
2. “Chosen” / election (bachar), 1 Chronicles 28:4-6, 10 — Near-total contemporary capture by the political-voting frame (per baseline Critical designation), compounded here by unusually dense stacking of election vocabulary in a single chapter, demanding repeated, not single, correction.
3. “Steadfast love” (chesed), 16:34, 41; 17:13 — Genuine missing-vocabulary problem; any single English word under-delivers, and readers may not notice the loss since the word “sounds” adequately covered.
4. “Census” (paqad/mispar), 21:1-6 — The single sharpest values-collision in the book: contemporary administrative culture treats counting people as routine and virtuous (transparency, planning), while the text treats this specific census as sinful presumption. Highest risk of readers actively rejecting or silently overriding the text’s own moral verdict rather than merely missing nuance.
5. “Atonement” (kaphar), ch. 21 (implicit); sacrificial system generally — Triggers the baseline’s own mandatory theologian-review escalation rule; compounded by the folk-etymology drift toward a therapeutic-reconciliation sense.
6. “The LORD” (YHWH) vs. “Lord” (baseline) — Not itself a false-friend in the same way, but a structural risk: most readers do not know or notice the small-capitals convention exists at all, so the entire covenant-name theology of the book (as opposed to a mere title of respect) can pass unnoticed unless explicitly taught at 17:1.
7. “Father” (typological royal sonship), 17:13 — Real risk of conflation with the New Testament’s Critical-risk Son of God doctrine; the error here runs in the opposite direction from most of this registry (readers might over-read deity into David’s line rather than under-reading it).
8. “Angel of the LORD,” ch. 21 — Contemporary softened “guardian angel” imagery is a near-total cultural takeover for most readers, working directly against this text’s judgment-bearing, plague-inflicting agent.
9. “Servant” (eved), 17:4, 7 — Post-slavery cultural sensitivity risks readers resisting or misreading positive servant-language as demeaning rather than as the honor-title the text intends.
10. “Priest” vs. “Levite,” ch. 6 and throughout 23-27 — Denominational-contest risk plus a real conflation risk (readers treating the two classes as interchangeable), undermining the structural logic of the whole Levitical-order doctrine.
11. “By lot” (goral), chs. 24-26 — Crowded-neighborhood risk (gambling/lottery) directly undercutting the providence doctrine this book depends on to explain how appointments were made without favoritism.
12. “Ark [of the covenant],” chs. 13, 15-17 — Noah’s-Ark collision risk is severe for readers with limited church background, though easily fenced with a consistent one-line disambiguation.
13. “Forever” (olam), 16:15; 17:12 — Hyperbole-worn word risks readers under-weighting a formal covenantal guarantee as casual sentiment.
14. “Vision” (chizzayon), 17:15 — Corporate “vision statement” neighborhood risks flattening prophetic revelation into a self-authored strategic plan, undercutting the doctrine of inspired, externally-given revelation this verse anchors.
15. “Kingdom” / “throne,” ch. 17, 28 — Fantasy-genre saturation risk; ranked lower than the above because context (explicit historical narrative, genealogical anchoring) does more independent disambiguating work than for terms like “election” or “census.”

---

5. Full-Book Chapter Coverage Log

Every chapter reviewed for doctrine-bearing and gap-relevant vocabulary. Chapters contributing no new terms beyond those already logged in §1–§4 or the companion glossary are marked “reviewed, no new gap-relevant vocabulary.”

Chapters	Coverage status
1–2	Reviewed. Genealogy doctrine vocabulary established (“sons of,” “firstborn,” “clan”); no further new gap categories beyond §1 Genealogy row.
3	Reviewed. David’s own line enumerated; reinforces “seed of David” / dynastic continuity vocabulary already logged; no new gaps.
4–5	Reviewed. “Clan,” “enrolled by genealogy,” “unfaithful” (ma’al, 5:25) all logged in §1–§2; no additional new gap-relevant vocabulary.
6	Reviewed. “Levite,” “priest,” “pasture lands” — priest/Levite denominational-contest and conflation risk logged in §2.2 and §4 (#10).
7–8	Reviewed, no new gap-relevant vocabulary beyond established genealogical formulae.
9	Reviewed. “Enrolled by genealogy,” “gatekeepers” logged; reinforces continuity doctrine; no new gap categories.
10	Reviewed. “Unfaithful” (Saul’s death, 10:13) and “inquire” (darash, negative use) reinforce §1 God’s Faithfulness row; no new gap categories.
11–12	Reviewed. “Anointed” (11:3), “mighty men,” “covenant” (11:3) logged; fantasy-genre “throne/kingdom” risk anticipated here narratively though the term itself concentrates in ch. 17 and 28.
13	Reviewed. “Ark [of the covenant]” (Noah’s-Ark collision risk, §2.2/§4 #12) and “wrath of the LORD” logged.
14	Reviewed. “Inquire” (darash, positive use, David) reinforces contrast with ch. 10; no new gap categories beyond what’s logged.
15–16	Reviewed. “Consecrate,” “singers,” “minister,” “the LORD reigns,” “continually,” “steadfast love” (first major occurrence, 16:34,41) — the chesed missing-vocabulary problem (§2.1, §4 #3) is anchored here.
17	Core passage. All top-tier ambiguities converge here: “house” (§4 #1), “the LORD”/YHWH convention (§4 #6), “Father” (§4 #7), “servant” (§4 #9), “seed of David,” “forever,” “vision” (§4 #14), “kingdom/throne” (§4 #15), “steadfast love” (17:13). This chapter carries the single highest concentration of ranked risks in the book and anchors the Davidic Covenant Reaffirmed doctrine.
18–20	Reviewed. “Gave victory” (yasha) logged as related to but distinct from baseline “salvation”; military-deliverance register requires explicit distinguishing per glossary, not a new gap category beyond that already logged.
21	Reviewed. “Census” (§4 #4), “angel of the LORD” (§4 #8), “altar,” “atonement”-adjacent logic (§4 #5), “threshing floor” — second-highest concentration of ranked risks after ch. 17, anchoring Preparation for the Temple.
22	Reviewed. “House for the Name of the LORD” (compound risk of “house” + “name”), “rest/peace,” “be strong and courageous” logged; reinforces Preparation for the Temple doctrine.
23–27	Reviewed. “Service/ministry” (avodah), “by lot” (§4 #11), “prophesy with instruments,” “captains” logged; anchors Worship and the Levitical Order doctrine’s organizational vocabulary.
28	Reviewed. “Chosen”/election (§4 #2, top-tier), “pattern,” “Spirit” (ruach, continuity/discontinuity care with baseline Holy Spirit entry), “wholehearted” logged; second-highest concentration of Critical-risk terms after ch. 17.
29	Reviewed. “Freewill offering,” “glory,” “riches and honor” (doxology cluster, direct source of the Lord’s Prayer’s closing doxology) logged; closes out God’s Faithfulness across Generations and Worship doctrines.

Conclusion: The gap analysis confirms that this curriculum’s highest-risk terrain clusters overwhelmingly around the core passage (ch. 17) and its immediate doctrinal neighbors (ch. 21’s temple-preparation narrative and ch. 28’s election/Spirit language), while the genealogical chapters (1–9) carry real but lower-intensity, more evenly distributed gaps concentrated in missing extended-kinship vocabulary rather than false-friend collisions. This distribution should directly inform Phase 2 review-routing priority: chapters 17, 21, and 28 warrant the most concentrated human theologian attention; the genealogical chapters warrant native-speaker review focused on consistent handling of telescoped generations and inclusive covenant-standing language.