Log in

or use your email

Search the Library

Keyword search across Doctrine Analysis, Core Glossary, Comparative Theology, and Regional Analysis. Mention a language name for the best results — e.g. "remnant burmese" or "what glossary terms conflict for burmese."

Type at least 2 characters to search.

Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Download Translation Skill

Linguistic Gap Analysis

Linguistic Gap Analysis: Exodus

0. Scope and Method

This step performs PRD Phase 1 Step 8 for the Exodus curriculum: a doctrine-by-doctrine audit of what contemporary English actually has available to carry each of the eight curriculum doctrines, where the available vocabulary is missing, degraded, or dangerously double-booked, and what strategy (retain/gloss, transliterate, paraphrase, or fence) each case requires before Phase 2 content generation begins.

As with the baseline Romans package, this is not a cross-language translation gap analysis — English is the source and destination language. The “gap” being analyzed is the distance between (a) the Hebrew concept as it functions in Exodus and (b) the nearest available contemporary English word’s actual, lived meaning for a general reader in 2026. Three baseline risk categories continue to apply (False-Friend Drift, Denominational/Tradition Contest, Obsolescence/Obscurity), joined by the two Exodus-specific categories established in 08_core_glossary.md (Pop-Culture/Franchise Collision, Sensitive Historical-Cultural Association).

This document draws directly on 08_core_glossary.md and assets/bible_term_registry.json and does not re-derive definitions already settled there; instead it organizes the same findings around the eight named doctrines, identifies where English vocabulary is genuinely missing (not just risky), and produces the ranked action list Phase 2 content generation needs.


1. Doctrine Vocabulary Matrix

DoctrineAvailable English Term(s)Weakness(es)Recommended Strategy
The Exodus as Redemption”redeem,” “redemption,” “deliver,” “rescue""Redeem” is captured almost entirely by commercial/transactional usage (coupons, loyalty points, gift cards) in contemporary English; “deliver/deliverance” is safer but flatter, losing the kinship dimension of ga’al; two distinct Hebrew verbs (ga’al, padah) are both flattened into one English wordRetain “redeem/redemption” as primary term (established Bible-translation vocabulary) but require mandatory explicit clarification on first substantive use per document distinguishing (1) the commercial false-friend, (2) the kinsman-redeemer sense (ga’al), and (3) the paid-ransom-substitute sense (padah); use “kinsman-redeemer” as a compound gloss where the distinction is load-bearing (6:6, 15:13 vs. 13:13-15)
Passover and Substitutionary Atonement”Passover,” “blood,” “lamb,” “substitute,” “atonement""Passover” is a living, present-tense Jewish festival, not merely an ancient artifact — English has no word that lets a Christian curriculum discuss it without either sounding like it is teaching about a dead ritual or unintentionally supersessionist; “blood” is trivialized by horror-media and clinical/medical usage; “lamb” is aestheticized (Easter-card cuteness)Transliterate/retain “Passover” untranslated as a proper noun (no viable English substitute exists) with mandatory framing distinguishing the ongoing Jewish observance from the curriculum’s Christological reading (1 Cor 5:7); retain “blood” and “lamb” with explicit de-trivializing context rather than substituting euphemism (“the sacrifice,” “the offering”) which would soften the text’s own bluntness
The Character and Name of God (I AM)“I AM,” “the LORD,” “God,” “Yahweh”/“YHWH”English has no native equivalent for the dynamic, self-existent force of the Hebrew verb “to be” behind Ehyeh Asher Ehyeh; “I AM” collides directly with contemporary self-affirmation-culture “I am ___” statements; “LORD” (small caps convention) is typographically invisible without explicit teachingRetain “I AM WHO I AM” as the primary rendering (established English Bible-translation tradition) with mandatory reversal-of-agency clarification on every substantive use; retain the LORD/Lord typographic convention but explicitly teach it rather than assume readers notice small capitals; offer “YHWH” transliteration in teaching notes (not published devotional text) as a precision aid
The Mosaic Covenant and Law”law,” “covenant,” “commandment,” “statute""Law” imports a modern litigious/civil-code frame that partially helps but risks flattening a relational covenant into a bare legal contract; “covenant” is captured by real-estate/contract law in ordinary usage; “commandment” is stable but “Ten Commandments” is captured by the 1956 DeMille filmRetain “law” and “covenant” (established terms) with the baseline’s required relational-not-merely-legal clarification; retain “Ten Commandments” as the standard rendering but explicitly name and set aside the film association before doctrinal teaching, per the “Abba”/ABBA precedent in the baseline
The Tabernacle and God’s Presence”tabernacle,” “dwell,” “sanctuary,” “presence,” “glory""Tabernacle” is a near-archaic word outside religious use, and its dominant contemporary association for many American readers is the Mormon Tabernacle Choir, an unrelated LDS institution; “glory” is nearly inverted in casual usage (“glory days,” “a glory hound”)Retain “tabernacle” (no viable modern substitute carries the “dwelling place” etymology as cleanly) with mandatory disambiguation from the LDS institutional association; retain “glory” with explicit restoration of its radiant/weighty sense, anchored to Exodus 40:34-35 as a consistency anchor verse parallel to the baseline’s treatment of Romans 8:28
Deliverance from Bondage to Sin”bondage,” “slavery,” “service,” “freedom”English cannot preserve the single Hebrew root (avodah) that spans forced slavery and willing worship without either sounding like a euphemism for continued bondage (“service to God”) or losing the wordplay altogether; “slavery” vocabulary carries the full, painful weight of the transatlantic slave trade for contemporary American readersUse context-dependent rendering (“slavery/bondage” for Egypt, “service/worship” for God) per the existing glossary decision, but name the wordplay explicitly every time both senses appear in the same passage rather than translating around it silently; explicitly honor the positive resonance of this narrative in African American Christian tradition (spirituals, Civil Rights usage) as a genuine asset, not only a risk to manage
Moses as Mediator and Deliverer”mediator,” “intercession,” “deliverer,” “prophet""Mediator” is stable but abstract/legalistic in ordinary usage (a divorce mediator, a labor-dispute mediator) and needs re-anchoring to a personal, relational sense; “intercession” is rare/formal (obsolescence) but has no serious competing meaning, a mild assetRetain “mediator” and “intercession” (established terms) with explicit narrative anchoring to Moses’ concrete acts (32:11-14, 32:30-32, 33:12-16) rather than abstract definition alone; use Moses’ own reluctance (3:11, 4:1, 4:10, 4:13) as the concrete illustration correcting “calling”/“called” false-friend drift already flagged in the baseline
Holiness and the Fear of the Lord”holy,” “holiness,” “fear of the LORD,” “reverence,” “awe""Fear” defaults to anxious dread in contemporary usage, with no single available English word carrying the composite sense (reverential awe + trust + love) that yir’ah requires; “holy” survives mainly in negative idiom (“holier-than-thou”) or content-free exclamation (“holy cow”) per the baselineRetain “fear of the LORD” as the primary rendering (do not substitute a softer synonym like “respect,” which loses too much weight, or a purely reverential gloss like “awe” alone, which loses the volitional/obedience dimension) with mandatory composite-sense clarification on every substantive use, anchored concretely to Exodus 14:31’s fear-produces-faith sequence

2. Missing Vocabulary: Concepts with No Adequate Single English Word

Unlike most of the terms already logged in 08_core_glossary.md and the term registry (which have an available English word carrying risk), the following concepts have no single adequate English word at all and require structural compensation (compound phrases, retained transliteration, or explanatory paraphrase) rather than mere clarification of an existing word.

  1. Ga’al vs. padah (two redemption verbs, one English word). English “redeem” cannot carry both the kinsman-based, relational redemption of ga’al and the paid-ransom-substitute sense of padah. Strategy: compound gloss — “redeem (as a kinsman)” / “redeem (by a substitute payment)” — used consistently wherever the distinction is doctrinally load-bearing (Exodus 6:6, 15:13 vs. 13:13-15).

  2. Pasach vs. avar (the Passover wordplay itself). No single English verb pair reproduces the Exodus 12:12-13 wordplay in which God “passes through” (avar) Egypt in judgment while “passing over” (pasach) the blood-marked households. Most English translations collapse both into “pass over” or “pass through” interchangeably. Strategy: this is the core passage’s central theological hinge and must be surfaced as an explicit two-verb teaching point, not solved by word choice alone — recommend a dedicated explanatory sidebar in every document treating Exodus 12:1-14, since no lexical fix suffices.

  3. Chazaq / kashah / kabed (three “harden” verbs, one English word). English has no equivalent three-way distinction; “harden” must do triple duty. Strategy: cannot be fixed lexically; requires an explicit note (not a different word choice) stating that the Hebrew varies where the English does not, alongside the required denominational-transparency statement on the sovereignty/responsibility question.

  4. Avodah spanning slavery and worship. Already addressed in the doctrine matrix above; flagged again here because it is a genuine missing-word problem, not merely a risky-word problem — English simply does not have one word that means both “forced slave labor” and “devoted worship service.”

  5. Chesed’s composite sense. “Steadfast love,” the registry’s chosen rendering, is a compound phrase precisely because no single English noun (not “love,” not “mercy,” not “loyalty,” not “kindness” alone) carries chesed’s full sense of reliable, promise-keeping, covenant-bound loyalty. This compound should be treated as a fixed technical phrase, not varied stylistically across documents.

  6. The self-revelation formula (34:6-7) as a unit. No single English phrase captures “merciful and gracious, slow to anger, abounding in steadfast love and faithfulness” plus the justice clause as a single lexical item; it must remain a full compound formula, treated as an anchor text (see Section 4 below), not shortened for stylistic variety.

  7. Kapporet (“mercy seat”/“atonement cover”). Neither available English rendering is fully adequate: “mercy seat” sounds like generic furniture to a contemporary reader with no religious background; “atonement cover” is clearer in function but obscure and clinical-sounding. Strategy: use “mercy seat (the atonement cover)” as a compound first-use rendering, explaining both function and location together, since the object is genuinely doctrinally dense and no single English phrase carries both dimensions.

  8. Eved ivri (“Hebrew servant/bondservant”) as a legally distinct status. English “servant,” “slave,” and “bondservant” do not map cleanly onto the ancient Near Eastern legal category of a term-limited, rights-bearing indentured laborer with mandatory seventh-year release. Strategy: this is a structural gap requiring explanatory paraphrase (“a fellow Israelite working off a debt for a limited term, with a guaranteed release date and legal protections — not the chattel slavery familiar from later history”) rather than a better single word, because no single word exists.


3. Crowded Semantic Neighborhoods Requiring Fencing

Several English words are being asked to do doctrinal work in Exodus while already carrying strong, unrelated meanings from elsewhere in the same curriculum, from the baseline Romans register, or from broader contemporary culture. These require explicit “fencing” — a stated boundary distinguishing the intended sense from its neighbors — rather than a change of word choice, since the words themselves are the correct, established renderings.

Crowded WordCompeting Senses in PlayFencing Required
”Redeem”(a) ga’al kinsman-redemption, (b) padah ransom-substitute, (c) commercial coupon/loyalty-point redemption (dominant contemporary sense), (d) baseline Romans NT theological senseFence (c) out explicitly every time; fence (a) and (b) apart from each other per Section 2 above; note continuity with, not identity to, the baseline’s NT usage
”Cover”(a) kapporet’s atoning “cover,” (b) generic English “cover” (a lid, a blanket, insurance coverage)Fence out generic senses; anchor to the specific atoning function
”Ark”(a) Ark of the Covenant (aron, a chest), (b) Noah’s Ark (tevah, an unrelated Hebrew word, a boat), (c) Raiders of the Lost Ark franchiseFence (b) and (c) out explicitly and immediately on first use — this is a compounded, high-traffic confusion requiring the strongest possible fencing language
”Tabernacle”(a) mishkan, God’s dwelling place, (b) Mormon Tabernacle Choir (LDS institution)Fence (b) out explicitly on first use; supply the “dwelling” etymology as a positive replacement association
”Plague”(a) negef/magepah, personal judicial act, (b) post-pandemic naturalistic disease-outbreak usage, (c) casual trivialized usage (“a plague of tourists”)Fence (b) and (c) out; restore personal, targeted, judicial framing
”Fear”(a) yir’ah’s composite reverence+trust+love, (b) anxious dread (dominant contemporary sense), (c) baseline’s general caution about obedience-adjacent virtues being culturally suspectFence (b) out; do not substitute a softer synonym; use 14:31’s sequence (deliverance → fear → faith) as the fencing anchor
”Glory”(a) kavod’s radiant, weighty divine presence, (b) nostalgic “glory days,” (c) pejorative “glory hound”Fence (b) and (c) out; anchor to 40:34-35
”Covenant”(a) brit’s relational promissory bond, (b) real-estate/contract-law “restrictive covenant” (dominant contemporary legal sense, per baseline)Fence (b) out; note continuity with baseline’s Romans treatment
”Jealous”(a) qanna’s positive covenant-exclusivity claim, (b) near-universally pejorative contemporary usage (insecurity, possessiveness)Fence (b) out explicitly; supply a positive analogy (marital fidelity, not envy)
“An eye for an eye”(a) the original legal principle of proportional limitation on retaliation, (b) the now-dominant idiom for unlimited escalating vengeanceFence (b) out; this is a case where the idiom has inverted the original meaning, requiring active correction rather than passive reliance on the phrase
”Ten Commandments”(a) the covenant stipulations of Exodus 20:1-17, (b) the 1956 Cecil B. DeMille filmFence (b) out on first use in any teaching context
”Idol”(a) pesel, a prohibited manufactured cult object, (b) secularized “teen idol”/“American Idol” usageFence (b) out; note the commandment covers images of the true God, not only images of false gods
”Manna”(a) man, daily-dependence miraculous provision with built-in limits, (b) secularized idiom “manna from heaven” for any unearned windfallFence (b) out; restore the daily-trust and no-hoarding dimensions
”Cherubim”(a) keruvim, fearsome guardian/throne-bearing figures, (b) chubby winged-baby “cherub” imagery (Valentine’s Day)Fence (b) out explicitly; this is a near-total inversion, not a partial drift
”Serve/service”(a) avodah as worship-directed purpose of the Exodus, (b) avodah as the forced labor Israel is delivered from, (c) generic contemporary “service” (customer service, military service)Fence (c) out; explicitly name that (a) and (b) share the same Hebrew root as the doctrinal point itself, not a translation accident to be smoothed over

4. Transliteration vs. Paraphrase Decisions

Per the baseline’s convention of retaining established Bible-translation vocabulary rather than inventing novel English terms, the following decisions govern Phase 2 content generation:

TermDecisionRationale
PassoverRetain untranslated (proper noun)No English paraphrase exists; the word is already the standard English Bible-translation and cultural term; paraphrasing it would be both unnecessary and disrespectful to its status as a living festival name
I AM WHO I AMRetain established English rendering; do not paraphraseThis is the historic English Bible-translation rendering (KJV through NLT lineage); paraphrase (e.g., “I am the self-existent one”) sacrifices the text’s own deliberately repetitive, declarative form for a theologian’s summary
LORD (small caps) / LordRetain the typographic convention; add mandatory explanatory note, do not silently drop itBaseline already establishes this convention for Romans; Exodus is where the convention’s stakes are highest (Exodus 3, 6) since this is the name’s origin narrative
YHWHTransliterate in teaching/footnote material only; do not use in published devotional textPer this Language Package’s citation and register conventions (see baseline), published material defaults to standard English Bible-translation wording (NLT); YHWH transliteration is a precision tool for teacher-facing material, not reader-facing text
Ga’al / padahDo not transliterate; use compound English glosses (“kinsman-redeem” / “ransom-redeem”)Transliterating obscure Hebrew roots would add jargon without aiding comprehension for a general audience; compound glosses solve the missing-vocabulary problem identified in Section 2 more directly
ChesedDo not transliterate; retain “steadfast love” as a fixed compound renderingAlready established in the term registry; transliteration would create an unnecessary new vocabulary item when a stable English compound already functions well
Mishkan (tabernacle)Retain “tabernacle”; do not transliterate the Hebrew and do not substitute a modern paraphrase like “sacred tent""Tabernacle” is deeply embedded in English Bible-translation tradition and carries its own “dwelling” etymology once explained; a paraphrase like “sacred tent” would lose this etymological teaching opportunity and the King James-lineage familiarity that supports cross-reference recognition (John 1:14)
Aron habrit (Ark of the Covenant)Retain “Ark of the Covenant”; do not paraphrase to avoid the pop-culture collisionAvoiding the term entirely (e.g., substituting “covenant chest”) would sacrifice recognizability and cross-reference value; the correct strategy is explicit fencing (Section 3), not avoidance
KapporetUse compound rendering “mercy seat (the atonement cover)”; do not choose only oneNeither established English option alone is adequate (Section 2, item 7); presenting both together, once, on first use, resolves the gap without requiring a novel coinage
Eved ivriParaphrase with an explanatory clause; do not rely on “servant” or “bondservant” aloneNo single English word carries the specific legal status; per Section 2 item 8, explanatory paraphrase is required
Ehyeh Asher EhyehProvide both renderings side by side on first use: “I AM WHO I AM” / “I WILL BE WHAT I WILL BE”The Hebrew imperfect verb form genuinely supports both a present-tense and future-tense reading; per the baseline’s Ambiguity Handling rule, note the range rather than silently picking one
Karan panav (Moses’ radiant face)Retain “his face was radiant/shone”; do not transliterate; include the Vulgate “horned” mistranslation as an explicit historical aside, not a live rendering optionThis is a documented historical translation error with ongoing art-historical consequences (Michelangelo’s Moses), valuable as a teaching illustration of translation drift itself, but must not be presented as a live rendering choice

5. Ranked List: Highest-Risk Ambiguities for This Curriculum

Ranked by combined severity (confidence of misreading × doctrinal centrality × frequency of occurrence in the core passage and curriculum doctrines), highest risk first. All entries below are Critical or High tier in assets/bible_term_registry.json; this ranking sequences them for Phase 2 prioritization and human-theologian review scheduling.

  1. “Passover” itself (Exodus 12:1-14, the core passage). Highest rank because it combines Critical doctrinal centrality (the curriculum’s own anchor passage), Sensitive Historical-Cultural Association (a living Jewish festival), and the compounded risk of supersessionist error if handled carelessly. Every other risk in this list is subordinate to getting this one right first.
  2. The pasach/avar wordplay (Exodus 12:12-13). Ranked second because it is the literal mechanism of the core passage’s theology and is the single most structurally invisible gap in this entire analysis — no word choice alone can fix it; failure here undermines comprehension of substitutionary atonement at its narrative root.
  3. “Blood” (Exodus 12:7, 13, 22-23). Ranked third: Critical false-friend drift from horror/entertainment and clinical usage, occurring at the exact center of the core passage, directly underlying the doctrine “Passover and Substitutionary Atonement.”
  4. “I AM WHO I AM” (Exodus 3:14). Ranked fourth: Critical false-friend collision with contemporary self-affirmation culture is a near-total reversal of agency, and this is the curriculum’s dedicated doctrine (“Character and Name of God”), though it occurs less frequently in the core passage itself than items 1-3.
  5. “Redeem” (ga’al/padah collapse). Ranked fifth: Critical false-friend drift (commercial redemption) affecting the doctrine “The Exodus as Redemption” throughout the whole book, compounded by the missing-vocabulary problem of two Hebrew verbs sharing one English word.
  6. “Harden(ed) [heart]” (Exodus 4-14). Ranked sixth: Critical denominational contest compounded by a three-Hebrew-verbs-into-one-English-word collapse; high doctrinal stakes for “Character and Name of God” but somewhat lower frequency within the core passage itself than items above.
  7. “Ark of the Covenant.” Ranked seventh: Critical, compounded pop-culture collision (Noah’s Ark homophone confusion plus the Indiana Jones franchise), but occurs later in the book (ch. 25 onward) rather than in the core passage, lowering its immediate priority relative to Passover-adjacent terms.
  8. “Bondage/slavery/service” (avodah). Ranked eighth: Critical Sensitive Historical-Cultural Association with the highest pastoral-sensitivity stakes in the registry, but its central doctrinal payload (freedom-for-worship) is slightly less concentrated in the core passage itself than items 1-6.
  9. “Election” / “treasured possession” (Exodus 19:5-6). Ranked ninth: Critical false-friend drift (political-voting capture) carried over from the baseline; high stakes for denominational transparency but a single concentrated occurrence rather than a recurring thread through the core passage.
  10. The self-revelation formula (Exodus 34:6-7). Ranked tenth: Critical denominational-contest risk (mercy clause eclipsing justice clause under therapeutic-culture pressure) with the OT’s richest theology-proper payload, but located well outside the core passage’s immediate scope.
  11. “Glory of the LORD filled the tabernacle” (Exodus 40:34-35). Ranked eleventh: Critical curriculum-capstone anchor verse, but as the book’s concluding rather than core passage, its priority for the immediate core-passage-anchored curriculum is lower than items above, though it remains mandatory for full-book coverage.
  12. “Tabernacle” (Mormon Tabernacle Choir collision). Ranked twelfth: Critical pop-culture collision, but the underlying doctrine (“Tabernacle and God’s Presence”) is addressed structurally across many later chapters, giving more opportunities to correct the association than the single-passage risks above.
  13. “Fear of the LORD” (yare/yir’ah). Ranked thirteenth: Critical false-friend drift (dread vs. reverent awe) with strong doctrinal weight (“Holiness and the Fear of the Lord”) and a valuable concrete anchor at 14:31, but somewhat mitigated by the fact that “fear” is at least a familiar word requiring recalibration rather than wholesale unfamiliarity.
  14. “I am the LORD” recognition formula (Ani YHWH). Ranked fourteenth: Critical cross-reference anchor (Romans 9:17) recurring frequently through the plague narrative, but its risk is more about under-noticing a repeated formula than active misreading, slightly lowering its severity relative to items above.
  15. “Without blemish” (tamim, Exodus 12:5). Ranked fifteenth: High false-friend drift (cosmetic triviality vs. sacrificial qualification standard) occurring directly within the core passage; ranked below the Critical-tier core-passage terms above it but above other High-tier terms located outside the core passage.
  16. “Sign” (ot, Exodus 12:13). Ranked sixteenth: High denominational-contest risk (objective marker vs. subjective feeling of assurance) occurring within the core passage, directly relevant to the baseline’s assurance-of-salvation transparency requirement.
  17. “The destroyer” (mashchit, Exodus 12:13, 23). Ranked seventeenth: High false-friend drift (impersonal-plague framing vs. personal commissioned agent) within the core passage, but lower doctrinal centrality than blood/sign/blemish above.
  18. “Steadfast love” (chesed). Ranked eighteenth: High false-friend drift (narrowing to “mercy”) with broad thematic importance but no single concentrated occurrence within the core passage itself.
  19. “An eye for an eye.” Ranked nineteenth: High false-friend drift (idiom inversion) with strong illustrative value for “Mosaic Covenant and Law” but located in case law outside the core passage.
  20. “Hebrew bondservant” (eved ivri). Ranked twentieth: High Sensitive Historical-Cultural Association requiring careful legal-distinction framing, but a single-passage occurrence (21:2-6) outside the core passage’s immediate scope.

Escalation note: Items 1-14 above all carry Critical risk tier in bible_term_registry.json and require mandatory human theologian review at every occurrence per this curriculum’s escalation rules, consistent with the baseline Romans package’s routing conventions; items 15-20 carry High risk tier and require human theologian review with slightly lower prioritization urgency. Phase 2 content generation should sequence review resources according to this ranking, front-loading review capacity on Exodus 12:1-14 (items 1, 2, 3, 15, 16, 17) before proceeding to full-book coverage of the remaining chapters.


This document extends 08_core_glossary.md and assets/bible_term_registry.json, both of which remain the enforced source of record for individual term definitions and risk tiers. This gap analysis governs Phase 2 sequencing and review-resource allocation; it does not supersede the glossary’s term-level rulings.

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.

Give feedback

How would you rate this page?

0 / 500 words