Linguistic Gap Analysis — 1 Chronicles (English → Hindi)

0. Scope and Method

This analysis extends the baseline Romans/Galatians Language Package to the first Old Testament curriculum in this pipeline, 1 Chronicles (chapters 1–29), anchored at the core passage 1 Chronicles 17:1-15 (the Davidic covenant reaffirmed through Nathan’s oracle). It builds directly on 08_core_glossary.md and the updated bible_term_registry.json, and it must be read together with those artifacts. Nothing here contradicts the baseline; it identifies why each new-term decision was necessary, maps the surrounding Hindi semantic terrain, and ranks the ambiguities that most need theologian/native-speaker attention in Phase 2.

Coverage is full-book. Every chapter of 1 Chronicles was reviewed. Genealogical chapters (1–9) and administrative/roster chapters (23–27) are treated as clusters where the same handful of terms recur; narrative and doctrinal chapters (10–22, 28–29) are treated individually where they introduce new vocabulary pressure. §6 provides the chapter-by-chapter coverage ledger.

Five curriculum doctrines govern the analysis: 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.

---

1. Doctrine Vocabulary Matrix

1.1 Genealogy and the Continuity of God’s People

Available Hindi term(s)	Weakness	Recommended strategy
वंशावली (genealogy/lineage record)	Naturally read by Indian audiences through the lens of gotra/vamsha caste-lineage record-keeping, where lineage confers ritual status and rank. Chronicles’ genealogies argue the opposite: God preserves a covenant people through disruption regardless of merit or rank.	Retain वंशावली (no better native alternative exists) but attach a framing note at the first list (ch. 1) explicitly distinguishing covenant-continuity record-keeping from caste-status record-keeping. Do not let the term stand undefined at its first, most consequential occurrence.
वंश (seed/offspring/lineage)	Hindi वंश reads naturally as a collective, plural lineage (“the Davidic line”), but the Hebrew זֶרַע (zera) in 17:11 is grammatically singular, and this singular referent is what later grounds the messianic reading. The same collapse risk was already flagged for Galatians 3:16’s seed_of_abraham.	Use वंश consistently (TM-reuse from baseline seed_of_david) but flag every 1 Chronicles 17:11 occurrence for combined theologian/native-speaker review, with a note that the underlying referent is singular even though the Hindi surface form does not mark number here.
पुत्र / पिता (son/father, genealogical)	These same two words also carry the baseline’s Adoption-doctrine freight (पिता = the personal, intimate Father of Romans 8:15’s Abba). In genealogical lists, पिता simply means “ancestor of.”	Keep the genealogical sense visually and functionally distinct in surrounding prose (e.g., ”…का पिता” as ancestor-marker) from any devotional invocation of पिता as address to God, so the register difference is not blurred for the reader.
पहलौठा (firstborn)	Standard, low risk, but the text’s repeated overriding of firstborn status (David himself the youngest) needs the inheritance-rights connotation to register, or the repeated genealogical flagging of firstborns will look like mere record-keeping rather than a theological point about God’s free choice.	Retain पहलौठा; add a doctrine-level (not per-verse) note that birth-order override is a recurring election motif, tying to the baseline election entry.
बँधुआई (exile/captivity)	Purely descriptive; risks being read as national-historical trivia unless tied back to the doctrine that God’s covenant people survive even exile intact.	Retain; ensure lesson-level framing (not the term itself) carries the theological point at 5:25-26 and 9:1.

Overall assessment: No missing vocabulary here — the risk is entirely about semantic drift toward caste/lineage-status categories that are pervasive in the destination culture but theologically opposite to the doctrine being taught. Fencing notes, not new coinages, are the correct tool.

1.2 The Davidic Covenant Reaffirmed (core doctrine of 17:1-15)

Available Hindi term(s)	Weakness	Recommended strategy
घर / भवन (literal “house”); घराना / वंश (dynastic “house”)	Hindi has no single word carrying both senses at once the way בַּיִת does. The chapter’s entire rhetorical structure (David wants to build God a בַּיִת; God promises to build David a בַּיִת) depends on the pun being visible. Splitting it into two words is unavoidable but risks readers missing that it is the same word in the source.	Use घर/भवन for the temple sense and घराना/वंश for the dynasty sense, but retain बनाना (“to build”) as the verb throughout, since Hindi बनाना already carries both “construct a building” and “establish/found a family/institution” senses — this is the one surface element that CAN preserve the pun. Mandatory translator note at 17:1 (first occurrence) and again at 17:10,12 (resolution), explicitly naming the wordplay so it is not “corrected” into two unrelated verbs by a reviewer unaware of the source pun.
सदा के लिये / अनन्तकाल तक (forever, olam)	Popular Hindi religious cosmology (yuga cycles, kalpa) treats even vast time-spans as bounded and recurring. A reader could hear “सदा के लिये” as “for this age” rather than unending, linear eternity.	Retain सदा के लिये as primary rendering; add a note at 17:12,14 excluding any cyclical-epoch reading — this is unbounded, non-recurring, linear futurity.
स्थिर करना / स्थापित करना (establish, covenant sense) vs. तैयार करना (prepare, material sense)	Both render one Hebrew root (כּוּן), so Hindi loses the thematic thread linking “God establishes David’s throne forever” (ch. 17) to “David prepares materials for the house” (chs. 22, 28) as two expressions of one verb.	Accept the two-word split as necessary; compensate with an explicit cross-reference note tying the chapters together so the theological point — dynasty-building and temple-building are one divine-human enterprise — survives even though the lexical thread does not.
राज्य (kingdom, malkut)	Identical noun to the baseline kingdom_of_god (परमेश्वर का राज्य). Readers moving between this OT curriculum and the Romans/Galatians material could either (a) wrongly flatten David’s historical dynasty into the full New Testament kingdom doctrine, or (b) wrongly treat राज्य here as merely political with no theological weight, missing that 29:23 explicitly equates Solomon’s throne with “the LORD’s throne.”	Use राज्य consistently, but require a note at 17:11,14 and 29:23 that names both the historical-dynastic referent and its explicit identification with God’s own reign — continuity without collapse.
सिंहासन (throne, kisse)	सिंहासन is generic in Hindi devotional/court literature (used of any deity’s or king’s seat). Risk of the Davidic promise reading as mere royal flattery rather than a binding covenant guarantee.	Retain सिंहासन; the covenant-guarantee force must be carried by surrounding grammar/notes (परमेश्वर की वाचा के अनुसार), not by the noun itself.
सेवक (eved, “my servant David”)	Correctly kept distinct from दास/दासत्व (bondage register per the Galatians baseline) — but सेवक is also used loosely in ordinary Hindi for any employee/attendant, risking under-translation of the honorific covenant-office sense.	Retain सेवक; gloss on first occurrence (17:4) as a covenant-title of loyal, divinely-designated service, not an ordinary employment term.
मैं उसका पिता होऊँगा, और वह मेरा पुत्र होगा (davidic_sonship, 17:13)	The single highest-collision point in this doctrine: this phrase is the typological seedbed of the NT’s Critical-risk son_of_god doctrine (परमेश्वर का पुत्र), yet must NOT be rendered with that full phrase, or Solomon’s adoption formula would be theologically inflated into Christ’s unique eternal Sonship.	Render literally with पिता/पुत्र (never the fixed phrase परमेश्वर का पुत्र); mandatory theologian note explaining the Solomon-then-ultimately-Christ typological line (cf. Hebrews 1:5) and the firm boundary against collapsing the two.
यहोवा का सिंहासन (the_lords_throne, 29:23, previewed 17:14)	The clearest single verse in the book identifying a human throne with God’s own; a translator under time pressure could soften this to a mere honorific comparison (“like God’s throne”), which would blunt the doctrine entirely.	Render literally and unqualified; theologian review mandatory.

Overall assessment: This doctrine has the highest concentration of missing vocabulary (the untranslatable bayit pun; the unpreservable kun-root double sense) in the whole book, compounded by a crowded neighborhood collision at davidic_sonship with the NT Critical Sonship doctrine. Both a coinage/compensation strategy (dual-word splits with notes) and a fencing strategy (explicit non-collapse boundary) are required simultaneously.

1.3 Worship and the Levitical Order

Available Hindi term(s)	Weakness	Recommended strategy
याजक (priest)	Correctly avoids पुजारी (Hindu temple ritual-specialist performing puja to an image), which the baseline OT-adjacent tradition already excludes. Low residual risk.	Retain याजक without further hedging; the term is already well fenced by existing Hindi Christian usage.
यहोवा की वाचा का सन्दूक (ark of the covenant)	Combines TM वाचा with सन्दूक (“chest/box”). Risk is under-translation into a merely functional storage container if सन्दूक is used without the वाचा qualifier.	Never abbreviate to bare सन्दूक; the covenant-bearing qualifier must be present at every occurrence, particularly chs. 13, 15, 16, and 17:1’s opening reference.
द्वारपाल (gatekeeper)	द्वारपाल is also the standard Sanskrit/Hindi term for the carved guardian-deity icons (dvarapalakas) flanking Hindu temple entrances — an iconographic, quasi-divine figure, not a human duty-roster office.	Retain द्वारपाल (no better term exists) but attach a clarifying note at first occurrence (ch. 9) that these are living, rostered Levitical personnel with scheduled human duties, not guardian icons.
सेवा (avodah, temple service/ministry)	सेवा is a major, living Hindu devotional category (bhakti seva — voluntary service to a deity, guru, or community, open to any devotee as a spiritual practice). The Chronicles usage is a narrower, technical term: divinely rostered, Levite-exclusive, YHWH-commanded liturgical labor.	Retain सेवा (established and unavoidable) but require a disambiguating note at chs. 23–26 distinguishing rostered Levitical office from open devotional bhakti-seva.
होमबलि (burnt offering, olah)	Direct semantic-field overlap with havan/homa, a live, frequently performed Hindu/Vedic fire-ritual for purification, blessing, or boon-seeking, typically addressed to one or more deities and repeatable at will.	Retain होमबलि (established BSI term) but mandate a translator note at every doctrinally significant occurrence (esp. 21:26, the first sacrifice on the future temple site) distinguishing a wholly-consumed offering within God’s own prescribed, exclusive sacrificial system from havan’s repeatable, multi-deity, boon-oriented logic.
वेदी (altar, mizbe’ach)	वेदी is the standard Hindi term for a Hindu ritual platform used in havan, yajna, and life-cycle ceremonies — general-purpose and reusable across deities and occasions.	Retain वेदी but require a note (21:18-26; 22:1) that this वेदी is dedicated exclusively and permanently to YHWH, marking the very site of the future temple — not a general-purpose ritual platform.
अभिषेक करना (anoint, mashach)	The single sharpest ritual collision in the book: अभिषेक is the standard term for abhishekam, the devotional Hindu practice of pouring milk/water/honey/oil over a deity’s image, a repeatable act of image-worship.	Retain अभिषेक करना (no viable substitute exists in current Hindi Christian usage) but require a mandatory translator note at every occurrence (11:3; 29:22) stating explicitly: this is God’s own act, received once, designating a specific human servant for covenant office — never a repeated devotional ritual directed at an image.
नियम के अनुसार (according to the rule, ka-mishpat)	Risk of flattening to a vague “properly,” losing the explicit contrast with ch. 13’s disastrous improvised handling of the ark.	Preserve the explicit rule/procedure sense at 15:13,15, and keep the intertextual link to ch. 13 visible in surrounding lesson material.
मेलबलि (peace offering, shelamim)	Distinct from, but easily confused with, the baseline शांति (relational peace with God).	Keep मेलबलि as the ritual-offering term; a note may clarify it celebrates/secures covenant wellbeing as a ritual act, not the same category as शांति’s relational-psychological sense.
चिट्ठी डालना (lot-casting, goral)	Superficial resemblance to fortune-telling/divination practices, and adjacent to (though distinct from) भाग्य/किस्मत fatalism already forbidden by the baseline election/providence entries.	Frame explicitly as a God-trusted scheduling mechanism for an already-chosen priesthood, not a means of discovering hidden fate.

Overall assessment: This is the single most crowded semantic neighborhood in the entire book. Nearly every load-bearing worship term (अभिषेक, वेदी, होमबलि, सेवा, द्वारपाल) has a live, active Hindu ritual-practice homonym or near-homonym. There is no missing-vocabulary problem here — Hindi has abundant vocabulary — the problem is the opposite: an oversupply of terms already saturated with non-biblical ritual meaning. The strategy throughout is fencing via mandatory translator notes, not substitution or coinage.

1.4 Preparation for the Temple

Available Hindi term(s)	Weakness	Recommended strategy
यहोवा का भवन (house of the Lord) vs. मन्दिर	मन्दिर is the single strongest Hindu-association word in the book — it denotes the physical Hindu temple building, typically housing one or more deity images for darshan and puja. Using it for God’s house risks assimilating the whole “preparation for the temple” narrative arc into a familiar Hindu temple-construction/consecration schema.	Default to भवन (यहोवा का भवन) throughout; reserve मन्दिर only where narrative clarity absolutely requires the “temple” gloss, and only with accompanying material distinguishing it from a Hindu मन्दिर’s multiple-deity image-worship function.
निवासस्थान (tabernacle, mishkan)	Must not be rendered मन्दिर at this narrative stage; the entire theological point of 17:5 is that God chose mobility (tent) over a fixed shrine before Solomon’s temple — collapsing this into “temple” vocabulary erases the point the passage is making.	Retain निवासस्थान (or तम्बू for the concrete tent) strictly for the pre-temple, mobile-dwelling stage; never मन्दिर here.
नमूना / रचना (pattern/design, tavnit)	Adjacent risk to यंत्र, a sacred geometric ritual diagram in Hindu/Tantric tradition believed to carry independent mystical potency. If the temple “pattern” is rendered with any यंत्र-adjacent vocabulary, readers could infer the blueprint itself is spiritually powerful.	Use नमूना/रचना (architectural blueprint sense only); the plan is authoritative because it is divinely given, not because the diagram itself possesses independent sacred power — this distinction should be explicit in surrounding material at 28:11-19.
विश्राम (rest, menuchah)	Must be kept distinct from the baseline शांति (relational, salvific peace with God) — here it names a historical, political condition (freedom from war) that is the precondition for temple-building, not a spiritual state per se.	Retain विश्राम; do not substitute शांति even where the English glosses both as “peace/rest.”
स्वेच्छाबलि (freewill offering, nedavah)	Risk of assimilation into ongoing devotional daan/offering practice (a recurring, merit-oriented giving pattern in Hindu religious life) rather than being read as the one-time, project-specific, joyful contribution the text describes.	Note at 29:5-9,14 that this is a bounded, non-repeating, non-merit-generating contribution to a specific God-initiated project.
यह सब तेरे ही हाथ से मिला है (everything from your hand, 29:14,16)	Not a lexical gap but a theological anchor-phrase; risk is under-translating its force into a generic politeness formula (“thank you for your gifts”) rather than a doctrinal statement undercutting all human-merit claims over the offering.	Preserve as a full clause, not compressed; flag alongside the baseline grace/works escalation trigger, since the theological logic (even our giving originates in God’s prior giving) parallels — without being identical to — the baseline अनुग्रह doctrine.

Overall assessment: The central decision here is almost entirely about restraint: avoiding the single most tempting and most dangerous available word (मन्दिर) in favor of a less vivid but doctrinally safer default (भवन). This is a fencing decision, not a vocabulary-gap decision.

1.5 God’s Faithfulness across Generations

Available Hindi term(s)	Weakness	Recommended strategy
यहोवा (YHWH, the covenant name)	This is a genuinely missing category in the NT-keyed baseline: Romans/Galatians never needed to distinguish the covenant personal name from the generic Elohim/God noun, because Greek κύριος/θεός do not carry the same distinction as pointedly as Hebrew יהוה vs אֱלֹהִים. 1 Chronicles uses יהוה over 500 times, and the personal-name theology (a God who reveals himself by name, binds himself by promise, and is faithful across generations specifically as this named God) is the doctrinal core of “God’s Faithfulness across Generations.”	Introduce यहोवा as a new Critical-risk transliterated proper name (see §4), kept visibly distinct from परमेश्वर in surrounding prose and notes, even though both refer to the one true God. Never allow यहोवा to be silently normalized to परमेश्वर in translation — the personal-name theology would be lost.
करुणा (chesed, steadfast covenant love)	करुणा is a major, actively cultivated Hindu/Buddhist ethical virtue — a generalized, self-cultivated compassion practiced toward all beings as a spiritual discipline. Chesed is the opposite kind of thing: God’s own freely-given, relationally-anchored, covenant-specific loyalty to a particular covenant partner (the house of David), guaranteed never to be withdrawn as it was from Saul.	Retain करुणा (established BSI rendering; no better option) but require a mandatory translator note at every doctrinally load-bearing occurrence (16:34,41; 17:13) distinguishing covenant-bound divine loyalty from a generalized, self-cultivated compassion virtue.
दर्शन (prophetic vision, chazon, 17:15)	दर्शन is the same Hindi word already explicitly rejected by the Galatians-era baseline for ἀποκάλυψις/“revelation,” precisely because it denotes a devotee’s mystical or ritual sight of a deity (temple darshan, guru darshan) — an attainment reachable through the worshipper’s own devotional practice.	Retain दर्शन (no adequate substitute exists for “night-vision/prophetic communication”) but require the identical mandatory note the baseline already established for this exact collision: this दर्शन is God’s own sovereign, verbal disclosure to his prophet, not the worshipper’s attained sight of the divine.
परमेश्वर का वचन / यहोवा यों कहता है (word of God; prophetic messenger-formula)	Risk of softening into “a thought/idea occurred to the prophet,” especially since 17:2-4 contrasts Nathan’s own sincere-but-merely-human counsel with the LORD’s actual word that immediately follows and corrects it.	Preserve the contrast structure explicitly; render the messenger-formula identically at every occurrence throughout the book so its recognizability as a marker of verbatim divine speech is not diluted.
सामर्थ्य / महिमा / संप्रभुता (power/glory/sovereignty, doxological cluster, 29:11-12)	Individually low-to-medium risk (all TM-reused from the baseline), but as a hymnic cluster they risk drifting toward Hindu stotra-praise register, where a deity’s cosmic attributes (greatness, power, glory, victory, splendor) are enumerated in a very similar five-fold pattern.	Retain each TM term exactly (never शक्ति for power); flag the cluster as a unit for native-speaker review to ensure the hymnic register remains recognizably addressed to the one covenant God, not assimilated wholesale into a generic Sanskritic praise-poem form.

Overall assessment: This doctrine contains the book’s one true missing-vocabulary gap (a personal divine name requiring new transliteration decisions never needed in the NT-keyed baseline) alongside its most acute reused-collision risk (दर्शन, already flagged once before in this pipeline for the identical reason, now recurring in a different book).

---

2. Missing Vocabulary vs. Crowded Semantic Neighborhoods

2.1 Genuinely Missing Vocabulary (no adequate Hindi lexical item exists)

Concept	Why it is missing	Resolution adopted
בַּיִת (bayit) house/dynasty double meaning	No single Hindi noun spans “physical building” and “household/dynasty” the way the Hebrew does.	Split into घर/भवन (building) and घराना/वंश (dynasty), compensated by retaining बनाना as the shared verb and mandatory cross-referencing translator notes (§1.2).
כּוּן (kun) root’s establish/prepare double sense	Hindi has no single verb spanning “establish a covenant-throne forever” and “prepare building materials.”	Split into स्थिर करना/स्थापित करना (covenant sense) and तैयार करना (preparation sense), compensated by a cross-reference note (§1.2).
The personal covenant name יהוה, distinct from the generic אֱלֹהִים	The baseline package, being NT-keyed, never needed a Hindi rendering for this distinction; Hindi Christian usage typically collapses both into परमेश्वर.	New transliteration यहोवा introduced (Critical risk), deliberately kept visually and functionally distinct from परमेश्वर throughout — see §4.
Grammatical singular/plural distinction carried by זֶרַע (zera) at 17:11	Hindi वंश does not obligatorily mark number, and naturally reads as collective.	Retain वंश (TM-consistent with baseline seed_of_david) with a mandatory flag for combined theologian/native-speaker review, noting the underlying singular referent — parallel to the already-documented Galatians 3:16 seed-of-Abraham problem.
נָגִיד (nagid) vs. מֶלֶךְ (melek) — divine designation vs. dynastic inheritance	Hindi राजा covers both without distinction; there is no common word isolating “ruler by direct divine appointment” as opposed to “king by hereditary right.”	Render nagid with प्रधान/अधिपति and melek with राजा, keeping the two visibly distinct so 17:7’s contrast (God took David from the sheep pasture to be nagid, not merely inheriting a throne) is not lost.

2.2 Crowded Semantic Neighborhoods Requiring Fencing (Hindi has abundant vocabulary, but all of it is already claimed by non-biblical religious meaning)

These are the inverse problem: not absence of vocabulary but oversupply of vocabulary already saturated with Hindu (occasionally Buddhist) ritual, devotional, or cosmological meaning. Each requires a fence — a mandatory translator note restricting the term’s biblical sense and excluding its dominant cultural sense — rather than a substitute term, because no unsaturated alternative exists.

Term	Crowded neighbor concept	Fence required
अभिषेक करना (anoint)	Abhishekam — ritual pouring of substances over a deity image, repeatable devotional act	Note: one-time, God-initiated designation of a human office-holder, never a repeated image-ritual
वेदी (altar)	Havan/yajna ritual platform, general-purpose, multi-deity	Note: dedicated exclusively and permanently to YHWH
होमबलि (burnt offering)	Havan/homa fire ritual, repeatable, boon-oriented, multi-deity	Note: wholly consumed offering within God’s own exclusive prescribed system
सेवा (temple service/ministry)	Bhakti seva — open, self-directed devotional service	Note: divinely rostered, Levite-exclusive liturgical office
द्वारपाल (gatekeeper)	Dvarapalaka — carved guardian-deity icon	Note: living, rostered human Levitical officers
मन्दिर (temple, restricted use)	Hindu temple building housing deity images for darshan/puja	Default avoided in favor of भवन; used only with clarifying material when unavoidable
दर्शन (prophetic vision)	Darshan — devotee’s mystical/ritual sight of a deity, attainable through devotion	Note: God’s own sovereign disclosure to the prophet, not devotee-attained sight (already fenced once in the Galatians package for the same word)
करुणा (steadfast love/chesed)	Karuna — self-cultivated universal compassion virtue (Hindu/Buddhist)	Note: God’s own covenant-bound, relationally-anchored loyalty, not a generalized cultivated disposition
वंशावली (genealogy)	Gotra/vamsha caste-lineage record-keeping conferring status/rank	Note: covenant-continuity record, not caste-status record
राजा / सिंहासन (king/throne)	Devotional/court literature’s generic royal-divine register	Note: covenant-accountable kingship under YHWH, not self-sufficient royal divinity
नमूना/रचना (pattern/design)	Yantra — sacred geometric diagram with independent mystical potency	Note: authoritative because divinely given, not independently sacred
भूत-प्रेत का माध्यम (medium/necromancer, ‘ov)	Live occult spirit-consultation and tantric practice	Pastoral, non-sensationalizing note; the text condemns the practice decisively
चिट्ठी डालना (lot-casting)	Divinatory fate-discovery adjacent to भाग्य/किस्मत (already forbidden by baseline)	Note: God-trusted scheduling mechanism, not fate-discovery

Structural observation: Section 1.3 (Worship and the Levitical Order) accounts for the majority of crowded-neighborhood terms in the book. This is expected — cultic vocabulary is precisely where two active sacrificial/ritual religious systems (biblical Israelite worship and living Hindu ritual practice) share the most surface-level phenomenological overlap (altars, offerings, anointing, priesthood, sacred architecture) while differing sharply in underlying theology (one God, one exclusive system, no image, no repeatable boon-transaction). Phase 2 review routing should weight this doctrine’s segments toward mandatory theologian/native-speaker double review accordingly.

---

3. Transliteration vs. Paraphrase Decisions

Term	Decision	Rationale
יהוה → यहोवा	Transliterate (new to this curriculum)	Preserves the personal-name distinction from generic परमेश्वर; a paraphrase (“the LORD” → प्रभु) would collide with the baseline’s own Critical-risk प्रभु entry (Christ’s Lordship) and erase the name/title distinction Hebrew itself makes.
מָשַׁח → अभिषेक करना	Retain established loanword/paraphrase (not transliteration; अभिषेक is itself a Sanskrit-derived Hindi verb, not a Hebrew transliteration)	No Hebrew transliteration exists in Hindi Christian tradition for this verb; the established BSI paraphrase is retained despite its ritual-collision risk because no safer alternative exists (see §2.2 fence).
בְּרִית → वाचा	Retain established paraphrase (TM reuse)	Already fixed in the baseline; no change needed.
כֹּה־אָמַר יְהוָה → यहोवा यों कहता है	Paraphrase, fixed formula	Functions as a recognizable messenger-formula; must be rendered identically every time, not varied stylistically.
מִשְׁכָּן → निवासस्थान (not तम्बू alone, not मन्दिर)	Paraphrase, restricted register	Coined/selected specifically to avoid मन्दिर’s temple-association at the pre-temple narrative stage; तम्बू reserved for the concrete tent-object sense.
לֵוִי → लेवीय	Transliterate	Established, low-risk proper-tribal-name transliteration; no viable paraphrase exists or is needed.
כֹּהֵן → याजक	Retain established paraphrase	Already distinguished from पुजारी in Hindi Christian tradition; no transliteration needed or desirable.
שׁוֹעֵר → द्वारपाल	Retain established paraphrase despite iconographic collision	No transliteration option; paraphrase is unavoidable, fenced by note (§2.2).
חָזוֹן / חִזָּיוֹן → दर्शन	Retain established paraphrase despite devotional collision	No transliteration option (this is not a proper name); fenced by mandatory note, consistent with the identical decision already made once in the Galatians package for ἀποκάλυψις.
חֶסֶד → करुणा	Retain established paraphrase	Established BSI rendering; transliteration is not applicable to a common noun of this kind; fenced by note.
עֶבֶד (David’s servant-title) → सेवक	Retain established paraphrase, explicitly not दास	Preserves the honorific covenant register against the bondage register the Galatians baseline reserves for दास/दासत्व.
נָגִיד → प्रधान / अधिपति	Paraphrase, deliberately distinct from राजा	No transliteration option; the paraphrase is chosen specifically to preserve a distinction Hindi does not otherwise mark.
תַּבְנִית → नमूना / रचना	Paraphrase	Avoids यंत्र-adjacent transliteration or coinage that would import independent mystical connotation.
אֲרוֹן בְּרִית־יְהוָה → यहोवा की वाचा का सन्दूक	Compound paraphrase, no transliteration	The sacred-object designation must remain fully descriptive (वाचा + सन्दूक); a bare transliteration of “ark” has no established Hindi form and would obscure the covenant content.
אָמֵן (Amen)-type liturgical items (not present as a distinct new term here, cross-referenced)	Transliterate (TM reuse: आमीन)	Consistent with baseline; no OT-specific liturgical transliterations beyond יהוה were required in this book.

General principle applied throughout: Transliteration is reserved for (a) proper names (persons, tribes, places) and (b) the newly-required personal divine name יהוה, where a paraphrase would either not exist or would erase a source-language distinction. Paraphrase is used for all common nouns and technical/cultic vocabulary, even where paraphrase creates a crowded-neighborhood collision, because Hindi genuinely lacks unsaturated alternatives for nearly all cultic vocabulary in this book (§2.2). No new coinages (invented compound neologisms) were judged necessary or advisable; all decisions draw on existing, attested Hindi vocabulary, disambiguated by translator notes rather than invented terminology.

---

4. Ranked List of Highest-Risk Ambiguities

Ranked by combined severity (doctrinal centrality × collision likelihood × review burden), for Phase 2 routing priority within this curriculum:

1. यहोवा vs. परमेश्वर collapse. If a translator or reviewer unfamiliar with this book’s specific requirement silently normalizes every יהוה to परमेश्वर, the entire “God’s Faithfulness across Generations” doctrine loses its personal-name anchor. Highest risk because it can happen invisibly, term-by-term, without any single dramatic mistranslation flagging it.
2. בַּיִת (house/dynasty) wordplay loss at 17:1-15. The core passage’s entire argumentative structure depends on readers perceiving that “house” shifts meaning mid-chapter. A translator working segment-by-segment without the cross-referencing note could easily render two unrelated, disconnected statements.
3. davidic_sonship (17:13) bleeding into son_of_god. The single highest risk of doctrinal inflation in the book: rendering “he shall be my son” with anything resembling the fixed Critical phrase परमेश्वर का पुत्र would wrongly assert Solomon’s (or by extension any human’s) co-equal divine Sonship with Christ.
4. अभिषेक करना (anoint) read as image-ritual. Given अभिषेक’s overwhelming primary association with abhishekam in everyday Hindi religious usage, any occurrence without its mandatory note risks being read as devotional ritual performed toward David/Solomon as toward a deity-image, rather than God’s own one-time act of office-designation.
5. दर्शन (prophetic vision, 17:15) read as devotee-attained sight. This is a recurrence of a risk the pipeline has already documented once (Galatians’ ἀποκάλυψις); its reappearance here in a different grammatical form (a night-vision report rather than an apostolic commissioning) makes it easy to overlook that the same fence is required.
6. करुणा (chesed) flattened to generic compassion. Because करुणा is a celebrated ethical virtue in the destination culture, translators may be tempted to let its warm cultural resonance stand unqualified, quietly losing the covenant-specificity (this steadfast love is bound to David’s house particularly, and unconditionally, unlike its withdrawal from Saul).
7. वेदी/होमबलि/सेवा cluster (chs. 21-26) read through a havan/bhakti-seva lens. Individually High risk; compounded because these terms cluster densely across the Levitical-order chapters, multiplying the chance that at least one occurrence escapes its mandatory fencing note during batch processing.
8. राज्य (kingdom) doctrinal conflation with NT kingdom_of_God. Risk runs in both directions: under-translating (treating David’s राज्य as merely political, missing 29:23’s explicit identification with यहोवा का सिंहासन) and over-translating (treating every occurrence as already the full NT kingdom doctrine, erasing the historical particularity of the Davidic dynasty).
9. वंश (zera) singular/plural collapse at 17:11. A subtle grammatical-argument risk, lower profile than the items above but directly parallel to a documented prior failure mode (Galatians 3:16); worth flagging precisely because its low visibility makes it easy to miss without the note.
10. मन्दिर temptation throughout chs. 22, 28-29. Because मन्दिर is shorter, more natural-sounding, and more immediately recognizable to readers than यहोवा का भवन, there will be constant stylistic pressure across the temple-preparation chapters to use it; this is a sustained risk across many segments rather than a single high-stakes verse.
11. सदा के लिये (olam, forever) heard as bounded epoch. Lower risk than items above because the surrounding covenant-promise language usually supplies sufficient context, but worth monitoring particularly at 17:12,14 where the promise’s unending force is the entire point.
12. भूत-प्रेत का माध्यम (medium/necromancer, 10:13) sensationalized or normalized. Risk is pastoral-tone rather than doctrinal-content: mishandling could either alarm readers unnecessarily or inadvertently legitimize consultation practices the text condemns outright.
13. गिनती करना (census, ch. 21) treated as intrinsically sinful. Because counting/numbering is morally neutral elsewhere in the administrative chapters (23-27), a reviewer could wrongly generalize ch. 21’s specific judgment (self-reliant pride) into a blanket statement against record-keeping as such.

---

5. Cross-Cutting Recommendations for Phase 2

1. All Critical and High-risk terms identified in this analysis must be loaded into translation_memory.json and bible_term_registry.json before segment translation begins (already staged in the accompanying 08_core_glossary.md and updated bible_term_registry.json; this document supplies the rationale trail for that staging).
2. Mandatory translator notes are the primary fencing mechanism in this book, more so than in the Romans/Galatians baseline, because Old Testament cultic vocabulary sits far closer to the destination culture’s living ritual practice than most New Testament epistolary vocabulary did. Phase 2 tooling should treat “requires mandatory note” as a distinct, trackable flag alongside risk tier, not merely folded into the Critical/High risk categories.
3. Worship and the Levitical Order (chs. 9, 13, 15-16, 21-26) should be weighted for double review (theologian + native speaker) given the density of crowded-neighborhood collisions documented in §2.2, exceeding what risk tier alone would suggest for some individually Medium-tier terms (e.g., द्वारपाल, चिट्ठी डालना) that become higher-stakes in combination.
4. The core passage (17:1-15) should be treated as a single reviewed unit, not segmented term-by-term, because at least three of its key decisions (bayit wordplay, davidic_sonship boundary, zera singular/plural) depend on cross-verse coherence that segment-level review could miss.

---

6. Full-Book Chapter Coverage Ledger

Chapters	Primary doctrine(s) touched	New vocabulary pressure	Status
1–9	Genealogy and the Continuity of God’s People	वंशावली, वंश, पुत्र/पिता, पहलौठा, बँधुआई, कुलपति, सीमा, विनती करना (Jabez), विश्वासघात करना (5:25), द्वारपाल (9), याजक (6), लेवीय (6)	Reviewed; vocabulary tabled in §1.1 and glossary
10	God’s Faithfulness across Generations (Saul’s downfall, contrast)	विश्वासघात करना, भूत-प्रेत का माध्यम	Reviewed; tabled §1.5, §2.2
11	The Davidic Covenant Reaffirmed (background); Worship	वाचा (Hebron kingship), अभिषेक करना, शूरवीर	Reviewed; tabled §1.2, §1.3
12	—	No new load-bearing vocabulary; reuses ch.11 register (mighty men)	Confirmed reviewed, no new terms
13	Worship and the Levitical Order	यहोवा की वाचा का सन्दूक, परमेश्वर का क्रोध (Uzzah)	Reviewed; tabled §1.3
14	—	No new load-bearing vocabulary; narrative continuation	Confirmed reviewed, no new terms
15	Worship and the Levitical Order	नियम के अनुसार, अपने आप को पवित्र करना, गायक	Reviewed; tabled §1.3
16	Worship and the Levitical Order; God’s Faithfulness	महिमा, करुणा (16:34,41), धन्यवाद	Reviewed; tabled §1.3, §1.5
17	The Davidic Covenant Reaffirmed (core passage); God’s Faithfulness	घर/भवन/घराना/वंश wordplay, स्थिर करना, सदा के लिये, राज्य, सिंहासन, सेवक, प्रधान/अधिपति, राजा, चराना, न्यायी/अगुवे, मिटा देना, नाम, रोपना, निवासस्थान, तम्बू, देवदार, वंश (offspring), पिता…पुत्र (davidic_sonship), यहोवा, सेनाओं का यहोवा, परमेश्वर का वचन, यहोवा यों कहता है, दर्शन	Fully reviewed in depth; §1.2 and §1.5 primary focus of this document
18	Preparation for the Temple (background)	भेंट/कर, अर्पित करना	Reviewed; tabled §1.4
19–20	—	No new load-bearing vocabulary; military narrative reusing existing register	Confirmed reviewed, no new terms
21	Preparation for the Temple; Sin/Judgment (background to doctrine)	गिनती करना, महामारी, यहोवा का स्वर्गदूत, वेदी, होमबलि, मेलबलि	Reviewed; tabled §1.3, §1.4, §2.2
22	Preparation for the Temple	यहोवा का भवन/मन्दिर decision, विश्राम, तैयार करना	Reviewed; tabled §1.4
23–26	Worship and the Levitical Order	दल/विभाग, चिट्ठी डालना, भण्डार/कोष, भविष्यद्वाणी करना (musical), सेवा	Reviewed; tabled §1.3
27	—	No new load-bearing vocabulary; administrative roster reusing existing register	Confirmed reviewed, no new terms
28	Preparation for the Temple; Election	परमेश्वर का चुनाव, सम्पूर्ण हृदय से, नमूना/रचना, आत्मा (in revelation), स्थिर करना/तैयार करना	Reviewed; tabled §1.2, §1.4, §1.5
29	Preparation for the Temple; God’s Faithfulness (climax)	स्वेच्छाबलि, यह सब तेरे ही हाथ से मिला है, अभिषेक करना (Solomon/Zadok), यहोवा का सिंहासन, महानता/सामर्थ्य/महिमा/विजय/वैभव (doxological cluster)	Reviewed; tabled §1.2, §1.4, §1.5

Every chapter of 1 Chronicles has been examined. Chapters 12, 14, 19, 20, and 27 introduce no new load-bearing theological vocabulary beyond terms already tabled elsewhere in this analysis and are noted here explicitly per the full-book coverage mandate, not silently omitted.

---

This analysis must be read together with 08_core_glossary.md, the updated bible_term_registry.json, and doctrine_risk_registry.json for this curriculum. All Critical and High-risk items identified above require human theologian review before Phase 2 segment translation begins, per the Pre-flight Checklist in 12_ai_translation_requirements.md.