Log in

or use your email

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 Requirements bundle

Linguistic Gap Analysis

06 — Linguistic Gap Analysis: Hosea (English → German)

Core passage (theological anchor, not scope): Hosea 11,1-9 Doctrines in scope: God’s Steadfast Love despite Israel’s Unfaithfulness; Spiritual Adultery and Idolatry as Covenant Breaking; The Marriage Metaphor for God and His People; Judgment and Compassion Held Together; The Call to Return and Repentance Coverage mandate: This analysis spans Hosea 1–14 in full. Per the PRD’s full-book-coverage rule, chapters that introduce no new gap beyond what is already documented for an earlier chapter are noted explicitly in §6 rather than silently skipped.

Note on source language: Hosea’s source language is Biblical Hebrew (with occasional dependence on the Septuagint Greek for NT-quoted verses, e.g. Hosea 11,1 in Matthew 2,15). This is the first curriculum in this pipeline where the “original” column of every downstream artifact is Hebrew rather than Koine Greek. Several of this analysis’s gaps arise specifically from Hebrew’s morphological and root-play features (shuv/meshuvah, baʿal/baʿali/ishi) that have no German structural analogue — a qualitatively different kind of gap than the lexical-choice gaps that dominated the NT epistle and Gospel packages.


1. Doctrine Vocabulary Matrix

Each row lists the doctrine, the Hebrew key terms carrying it, the German candidate terms already in use or under consideration, the specific weaknesses of the available German vocabulary, and the recommended strategy carried forward into 08_core_glossary.md and, eventually, translation_memory.json.

1.1 God’s Steadfast Love despite Israel’s Unfaithfulness

ElementDetail
Hebrew key termschesed (חֶסֶד), rachamim/nichumim (רַחֲמִים), ahavah (אַהֲבָה), nedavah-love (14,4), rapha (heal, 14,4)
Candidate German termsGüte, Gnade, Barmherzigkeit, Erbarmen, Liebe, Treue
WeaknessesGerman’s love/kindness vocabulary is comparatively small next to Hebrew’s four semi-overlapping roots. Güte (chosen for chesed) collides with the everyday sense “kindness in general” and the commercial sense “quality/grade” (Gütesiegel, Gütezeichen), diluting the specifically covenantal, loyalty-bound character of chesed. Gnade is already Critical-risk-reserved in the baseline for χάρις (unilateral, merit-free NT grace); chesed is related but not identical — it presupposes and repeatedly survives covenant breach, whereas NT grace is prior to any covenant at all. Treue captures the loyalty component well but in secular German usage defaults to marital/employment fidelity, risking a purely human-relational register that under-plays chesed’s divine initiative. Barmherzigkeit (chosen for rachamim) can default to a formal, institutional-charity register (via its heavy use in German diakonia/Caritas vocabulary), risking loss of the visceral, “womb-warm” intensity Hosea specifically activates at 11,8.
Recommended strategyFix Güte for chesed and Barmherzigkeit/Erbarmen for rachamim, per the glossary, but attach a mandatory first-occurrence-per-unit gloss: “Güte (hebr. chesed): Gottes bundestreue, unaufgebbare Liebe” — surfacing the covenant-loyalty sense the bare German noun cannot carry alone. Never substitute Gnade for chesed without an explicit cross-doctrinal footnote distinguishing the two. Theologian sign-off required on every occurrence (6 total: 2,19; 4,1; 6,4; 6,6; 10,12; 12,6), with 6,6 flagged as the highest-priority single verse for cross-document consistency given its NT citation (Matthew 9,13; 12,7).

1.2 Spiritual Adultery and Idolatry as Covenant Breaking

ElementDetail
Hebrew key termszenunim/zenut (זְנוּנִים), naʾaph (נאף), Baʿal (בַּעַל), baʿali/ishi wordplay, ʿatsabbim (idols), daʿat Elohim (knowledge of God)
Candidate German termsHurerei, Ehebruch, Untreue, Baal, Götzenbilder, Erkenntnis Gottes
WeaknessesHurerei is available and lexically exact but sits in a crowded register: contemporary colloquial German has largely retired the word to either archaic-biblical or crude-vulgar registers, with no comfortable “neutral formal” middle ground — translators will be tempted toward the gentler Untreue, which erases the sexual-covenantal shock the Hebrew intends. Baal as a bare transliteration risks defaulting, for a biblically low-literacy reader, to a generic “an idol” rather than the specific rival deity whose name is also an ordinary Hebrew word for “husband/lord” — the wordplay depends on this double identity, which German has no equivalent single word for. Erkenntnis Gottes risks collapsing into the German academic-theological sense of “religious/theological knowledge” (propositional, historisch-kritisch) rather than Hosea’s relational-experiential sense, a risk the baseline already flags for inspiration_of_scripture but which is sharper here because daʿat is Hosea’s own centerpiece indictment term (4,1.6; 6,6).
Recommended strategyRetain Hurerei at full crude force (never softened to Untreue) per the baseline’s precedent of preserving Paul’s own deliberate crudeness (Dreck, Philippians 3,8). Keep Baal transliterated, never generalized to “Götze,” with an explicit note that the same word functions as an ordinary noun for “husband/lord” — see §4 and §5 for the wordplay’s dedicated handling. Gloss Erkenntnis Gottes on first occurrence per unit as Beziehungswissen (“relational knowing”), explicitly distinguished from doctrinal/informational knowledge.

1.3 The Marriage Metaphor for God and His People

ElementDetail
Hebrew key termsʾerastikh (betroth, 2,19-20), Gomer (proper name), teshvi li (“remain mine,” 3,3), chevlei adam/avotot ahavah (cords of love, 11,4), ʿol (yoke, 11,4)
Candidate German termsverloben, Braut, Bräutigam, Ehe, Bund
WeaknessesVerloben in contemporary German denotes a casual, easily-dissolved modern engagement, considerably weaker than the ancient Near Eastern betrothal it renders — a real register mismatch, since Hosea 2,19-20’s fourfold repetition (“ich will dich mir verloben… in Gerechtigkeit und Recht, in Güte und Erbarmen… in Treue”) is meant to land as an unbreakable four-part covenant oath, not a tentative modern promise. German’s rich marriage vocabulary (Braut, Bräutigam, Hochzeit) exists and is well-established from NT usage (Ephesians 5; Revelation 19,7 in the wider pipeline) but is not automatically activated by Hosea’s own vocabulary, which more often uses covenant/legal terms (berit, Bund) than explicit bridal terms outside chs. 1–3 and 14. Readers may therefore fail to connect Hosea’s marriage narrative (chs. 1–3) to its covenant-theology payoff (chs. 4–14) without explicit signposting.
Recommended strategyRender ʾerastikh as verloben, but require teaching material (not the base translation) to gloss it explicitly as ein unauflösliches Bundesversprechen (“an indissoluble covenant promise”), guarding against the softer modern sense. Maintain Bund consistently (reused from baseline) as the connective tissue linking the marriage narrative of chs. 1–3 to the covenant-lawsuit material of chs. 4–14, with explicit cross-referencing notes rather than leaving the two registers to stand as separate topics.

1.4 Judgment and Compassion Held Together

ElementDetail
Hebrew key termscharon af (fierceness of anger, 11,9), nehpakh libi (heart recoils, 11,8), kemo-shachal (like a lion, 13,7-8), cherev (sword, 11,6), yemei ha-pekudah (days of punishment, 9,7)
Candidate German termsZorn, Glut meines Zorns, Herz kehrt sich um, Löwe, Schwert, Heimsuchung
WeaknessesGerman theological register has historically split this material into two poles that Hosea deliberately refuses to separate: (a) a strong Lutheran-orthodox “Zorn Gottes” (wrath of God) vocabulary, well attested in classical hymnody and confessional writing, and (b) a contemporary, more liberal-theological and broadly secular-culture discomfort with divine-wrath language at all, tending to translate it away into psychologized or metaphorical terms. A German rendering that leans too far toward (a) risks losing 11,8-9’s climactic mercy; leaning too far toward (b) risks losing 11,9’s genuine “Glut meines Zorns,” turning judgment into mere rhetorical flourish. Heimsuchung (days of punishment) carries a helpful dual visitation/punishment sense (as in Luke 1,68) but must be disambiguated from any positive-visitation reading elsewhere in the pipeline.
Recommended strategyPreserve both poles explicitly at every occurrence rather than resolving the tension in translation; mandatory theologian pairing note requiring judgment-language segments and compassion-language segments within the same pericope (esp. 11,5-9 as a single unbroken unit) to be reviewed together, never separately. Do not substitute a softened synonym for Zorn in 11,9; do not omit or soften Barmherzigkeit/Erbarmen in the same verse’s second half.

1.5 The Call to Return and Repentance

ElementDetail
Hebrew key termsshuv (שׁוּב, return/repent), meshuvah (מְשׂוּבָה, apostasy — same root), rapha (heal)
Candidate German termsumkehren, Buße, Abwendung, Abfall, heilen
WeaknessesUmkehren is the correct choice (see baseline extension in 08_core_glossary.md) but is also the ordinary secular German verb for a U-turn (traffic), a reversed decision, or a change of mind in any non-religious context — without sufficient co-text, a given occurrence may register to a low-biblical-literacy reader as merely “changing one’s mind” rather than covenantal repentance. It must also be kept visibly distinct from Buße, already fixed in the baseline’s Matthew-package extension for metanoia — the two must not be silently merged into a single undifferentiated “repentance” concept, since Hosea’s shuv carries a concrete spatial “turning/reversing direction” sense tied to the marriage metaphor’s “leaving/returning” logic that metanoia’s more inward “change of mind” sense does not foreground. German additionally has no root-family that mirrors the Hebrew shuv/meshuvah pun (turning-back vs. turning-away sharing one root) — umkehren and Abwendung/Abfall look and sound unrelated, silently erasing Hosea 11,7’s tragic wordplay unless a note supplies it.
Recommended strategyFix umkehren identically at every occurrence (20+ instances across chs. 2, 3, 5, 6, 7, 11, 12, 14) — a book-wide consistency requirement more demanding than any single-occurrence term elsewhere in this pipeline, since the rhetorical unity of the whole book depends on the German reader perceiving one repeated appeal. Attach a standing footnote at the term’s introduction distinguishing it from Buße. Supply an explicit translator/teaching note at 11,7 (and again at its resolution, 14,4) surfacing the shuv/meshuvah root-pun that German cannot reproduce natively.

2. Missing Vocabulary Inventory

These are gaps where German simply has no lexical item — not even an imperfect one — doing the work the Hebrew does natively. Paraphrase and footnoting, not term selection, are the only available strategies.

GapHebrew FeatureWhy German Has No EquivalentMitigation
baʿali / ishi wordplayOne Hebrew word (baʿal) serves simultaneously as “husband/lord” and the proper name of the rival godGerman “Baal” (proper name, borrowed/transliterated) and “Mann/Herr” (husband/lord) are lexically unrelated; no German word carries both sensesRender literally as the shift from “mein Baal” to “mein Mann,” with a mandatory explanatory footnote in every occurrence of teaching material (Hosea 2,16-17) — treat the loss of the pun itself, not just its content, as the thing requiring compensation
shuv / meshuvah root-pun”Return” (שׁוּב) and “turning-away/apostasy” (מְשׂוּבָה) share one Hebrew root, so Israel’s sin is literally “the turning that mirrors the turning it refuses to make”umkehren (return) and Abwendung/Abfall (apostasy) are unrelated word families in GermanStanding teaching note at 11,7 and 14,4 surfacing the wordplay explicitly; cannot be solved lexically
Theologically-loaded proper names (Jesreel, Lo-Ruhama, Lo-Ammi, Beth-Awen)Hebrew names that are simultaneously ordinary personal/place names AND full theological sentencesGerman transliteration of a proper name carries none of its Hebrew semantic content automaticallyMandatory paired gloss at every occurrence: name + parenthetical meaning (already adopted in 08_core_glossary.md); never leave as a bare untranslated proper noun
Four-way Hebrew love/loyalty vocabulary (chesed, rachamim, ahavah, nedavah-love) mapped onto a comparatively smaller German lexical fieldHebrew maintains four semi-distinct roots across this doctrinal field; German’s core options (Liebe, Güte, Barmherzigkeit, Treue, Gnade) do not cleanly partition the same wayFixed one-to-one mapping per term (§1.1) plus mandatory glosses; accept that some semantic nuance is structurally, not just lexically, unrecoverable
qara (Exodus-calling sense) vs. NT effectual callingHebrew qara covers a broad “summon” semantic field; the baseline’s German berufen/Berufung was fixed specifically for the NT soteriological senseNo separate German verb exists for “corporate-historical divine summons out of slavery” distinct from “individual salvific calling”Explicit sense-disambiguation note wherever taught alongside Romans 8,28-30 material; reuse rief for the narrative-historical instance (11,1) rather than Berufung the noun, to reduce the risk of doctrinal conflation
rapha (heal) vs. ga’al (redeem/ransom) vs. yasha’ (save) — three distinct Hebrew soteriological-adjacent rootsHosea uses all three (11,3/14,4 heal; 13,14 ransom; implicit yasha’ throughout) with distinct nuances (restoration-from-brokenness; commercial buy-back; deliverance)German’s heilen, erlösen, retten map reasonably well one-to-one, but the baseline’s existing Rettung/Erlösung/Heil three-way tension (already Critical-risk in the Romans package) now gains a fourth adjacent term (heilen) requiring fencing — see §3

3. Crowded Semantic Neighborhoods Requiring Fencing

Where §2 catalogues genuine absences, this section catalogues the opposite risk: German words already carrying multiple, competing theological jobs in this pipeline, such that a translator or reviewer could plausibly, but wrongly, substitute one job’s term for another’s.

3.1 “Herr” / HERR neighborhood — now the most crowded in the entire pipeline

Three distinct referents now compete for the same surface form:

  1. Herr — ordinary German “Mr.” (no baseline protection exists; flagged Critical since Romans 10,9)
  2. Herr — the NT Christological confession, “Jesus ist Herr” (Romans 10,9; Philippians 2,11)
  3. HERR (small capitals) — the OT covenant name YHWH, occurring ~45 times in Hosea alone, a density far exceeding any single NT document already in the pipeline

Fencing strategy: The small-capital typographic convention (already standard in Lutherbibel/Einheitsübersetzung) must be treated as load-bearing, not decorative. Any teaching format that cannot preserve small capitals (plain text, audio script, subtitle, screen-reader output) must carry an explicit reviewer note flagging the loss of this distinction, given that Hosea’s own central wordplay (2,16-17, “mein Baal” → “mein Mann”) already trades on exactly this kind of husband/lord/master ambiguity — collapsing HERR into ordinary “Herr” in the same book that stages this precise confusion as its central metaphor is a uniquely self-defeating error for this specific curriculum.

3.2 “Geist” neighborhood

  • Heiliger Geist — the third Person of the Trinity (baseline, Critical)
  • ein Geist der Hurerei (ruach zenunim, Hosea 4,12; 5,4) — a metaphorical internal disposition, NOT the Holy Spirit

Fencing strategy: German’s mandatory capitalization of all nouns removes any capitalization-based disambiguation cue that might exist in other target languages. Every occurrence of “Geist” in a non-Trinitarian sense in Hosea must carry an explicit qualifying phrase (“ein Geist der Hurerei,” never a bare “der Geist”) and a first-occurrence teaching note distinguishing it from Trinitarian language.

3.3 “Steadfast love” neighborhood: Güte / Gnade / Barmherzigkeit / Treue

Four near-synonymous German nouns now sit in close semantic proximity, each already earmarked for a distinct referent:

  • Gnade = χάρις, unilateral NT grace (baseline, Critical)
  • Güte = chesed, OT covenant loyalty-love (this package, Critical)
  • Barmherzigkeit/Erbarmen = rachamim, visceral compassion (this package, Critical)
  • Treue = a candidate but explicitly rejected default for chesed (risks flattening to secular fidelity)

Fencing strategy: Translation memory must record all four with explicit “do not substitute for” cross-references to each other, not merely a positive definition each. Phase 2 automated translation must treat any occurrence of “Gnade” appearing where the source Hebrew is chesed as an automatic validation failure requiring reviewer escalation (parallel to the baseline’s existing “verdiente Gerechtigkeit” forbidden-substitution check).

3.4 “Salvation/healing/redemption” neighborhood: Rettung / Erlösung / Heil / heilen

The baseline already documents a three-way tension (Rettung / Erlösung / Heil, the last flagged for Nazi-era contamination) for sōtēria. Hosea adds a fourth, morphologically adjacent term: heilen (“to heal,” rapha, 11,3; 14,4), which is uncomfortably close in both spelling and sound to the contaminated Heil.

Fencing strategy: Explicitly document that heilen (verb, “to heal a wound/brokenness”) is not a euphemistic backdoor reintroduction of the avoided noun Heil — the two are etymologically related but must be treated in Phase 2 QA as distinct, permitted (heilen) versus caution-flagged (Heil), items. A validation rule should specifically check that heilen is not silently expanded into a Heil-adjacent phrase.

3.5 “Israel” neighborhood

Already flagged in the baseline for its Staatsräson-driven modern-nation-state conflation risk; Hosea sharpens this because its Israel is specifically the 8th-century-BC Northern Kingdom, distinct from the united-monarchy Israel of the Davidic-covenant material and from the exilic/post-exilic Israel of Romans 9–11. Fencing strategy: every occurrence in teaching material should carry an explicit historical-scope qualifier (“das Nordreich Israel unter Hosea”) to prevent silent conflation across three distinct biblical-historical referents that the bare proper noun “Israel” cannot itself distinguish.

3.6 “Erkenntnis” neighborhood

Erkenntnis Gottes (daʿat Elohim, relational knowing) sits close to the German academic-theological register’s historisch-kritische Erkenntnis (critical-scholarly knowledge), a register the baseline already flags as a live risk for inspiration_of_scripture. Fencing strategy: never let “Erkenntnis Gottes” stand without the Beziehungswissen gloss on first occurrence per teaching unit.


4. Transliteration vs. Paraphrase Decision Log

TermDecisionRationale
YHWHHybrid: transliterate-as-convention via small-capital HERR (not a phonetic transliteration but the fixed German Bible-tradition orthographic marker)Matches Lutherbibel/Einheitsübersetzung convention exactly; a true phonetic transliteration (“Jahwe”) would break with 500 years of German Bible-translation tradition and reduce liturgical/devotional recognizability
Baal (בַּעַל)Transliterate (Baal / die Baale)Proper name of a specific historical deity; paraphrasing to “Götze” erases both the historical referent and the 2,16-17 wordplay
baʿali / ishi wordplayHybrid: transliterate the proper name within a paraphrased explanatory clause + mandatory footnoteNo single-word solution exists (see §2); this is the pipeline’s clearest case requiring compensatory apparatus rather than a lexical choice
Gomer, Ephraim, Jacob, Egypt, Assyria, Admah, Beth-AvenTransliterate, per established German Bible proper-name conventions (Gomer, Ephraim, Jakob, Ägypten, Assyrien, Adma, Beth-Awen)Standard practice; low risk beyond the historical-background glosses already noted in 08_core_glossary.md
Jezreel, Lo-Ruhamah, Lo-AmmiTransliterate + mandatory paraphrase gloss (never transliterate alone)These names ARE the theological content of their respective oracles (1,4-9); a bare transliteration silently deletes the point of the naming
chesedParaphrase only (Güte) — no transliteration attemptedUnlike Abba (retained untranslated in the NT baseline for its felt intimacy), chesed has no established German-Bible-tradition transliterated form; German Bible tradition has always translated it, never transliterated it
shuvParaphrase only (umkehren) — no transliteration attemptedSame rationale; a common Hebrew verb with deep German-Bible-tradition translation precedent, not a proper noun or untranslatable interjection
Amen, Halleluja, Abba (where reused from Hosea’s Aramaic/Hebrew-adjacent NT citations)Transliterate, per existing baseline conventionNo change from baseline; Hosea itself does not add new instances of these specific terms but the convention must remain identical if cross-referenced

General decision rule for this package: Transliterate proper nouns (people, places, the divine name’s typographic convention, the specific deity Baal); paraphrase common nouns and verbs, even at the cost of losing root-play, supplementing the loss with mandatory explanatory apparatus rather than inventing artificial German neologisms or loanwords that have no basis in the existing German Bible-translation tradition.


5. Ranked List of Highest-Risk Ambiguities

Ranked by combined weight of (a) doctrinal centrality, (b) likelihood of translator/reviewer error, and (c) severity of consequence if mistranslated. Items 1–5 are drawn directly from the core passage (Hosea 11,1-9); items 6–15 are the highest-risk items from the rest of the book.

RankAmbiguityPassageWhy It Is High-Risk
1chesed rendered as Güte vs. silently drifting to GnadeBook-wide; esp. 6,6; 2,19; 11 (thematically)The single highest-priority lexical decision in the whole curriculum (per 08_core_glossary.md); a silent drift to Gnade would retroactively blur the Romans-package’s carefully guarded Gnade/works distinction by importing a covenant-conditioned OT concept into a term reserved for unconditioned NT grace
2”Mein Herz kehrt sich in mir um” — divine mutability questionHosea 11,8Core-passage climax; over-reading risks a doctrine of genuine divine emotional volatility; under-reading risks flattening the verse into rhetorical decoration, losing the book’s most theologically exposed statement of divine anguish
3”Denn ich bin Gott und nicht ein Mensch” — doctrine of God’s unchanging natureHosea 11,9The verse’s own resolution of #2; if softened or paraphrased loosely, the load-bearing logical connection between God’s ontological difference from humans and his covenant restraint is lost
4baʿali / ishi wordplayHosea 2,16-17Untranslatable pun (see §2, §4); without a mandatory footnote, German readers cannot access the exegetical point that Israel must abandon language hearable as Baal-devotion even when nominally addressed to YHWH
5”Mein Sohn” (11,1) — typological bridge to Matthew 2,15Hosea 11,1Sits directly beside the baseline’s Critical-risk Sohn Gottes doctrine (eternal, co-equal divine Sonship); flattening corporate-Israel-as-son into a direct identity claim with Christ’s unique Sonship, or conversely denying any typological connection at all, are both live misreadings requiring an explicit theologian-authored bridging note
6HERR (small capitals) typographic loss in non-typeset formatsBook-wide, ~45 occurrencesGiven #4’s wordplay, this book is uniquely unable to absorb the collapse of YHWH into ordinary “Herr” without compounding, rather than merely repeating, an existing baseline caution
7shuv consistency across 20+ occurrencesChs. 2, 3, 5, 6, 7, 11, 12, 14The book’s rhetorical unity as a single escalating covenant appeal depends on one fixed German rendering throughout; any variation (e.g., alternating “umkehren” with “zurückkehren” or “sich bekehren”) breaks a structural feature of the whole book, not just a single verse
8Hurerei crudeness vs. moralizing the historical GomerChs. 1–3; recurring 4,12-14; 5,3-4; 6,10Two opposite failure modes: softening the term erases the metaphor’s shock; alternatively, teaching material may drift into biographical moralizing against Gomer as an individual sinner, losing the corporate-national referent that is the entire point of the enacted sign
9”Wie Adam haben sie den Bund gebrochen” — Adam as person vs. place nameHosea 6,7Genuine, unresolved textual-critical ambiguity; silently resolving it in either direction (rather than flagging transparently) misrepresents the state of scholarship to the reader
10”Ich will sie erlösen vom Tode… Tod, wo sind deine Plagen?” — promise vs. further threatHosea 13,14Directly quoted by Paul (1 Korinther 15,55) as unambiguous resurrection triumph, yet the Hebrew syntax genuinely supports a threat-reading in its original context; the cross-testamental reception history must not be allowed to silently overwrite transparent disclosure of the OT exegetical debate
11Jezreel’s dual meaning across 1,4 and 1,11/2,22-23Hosea 1,4; 1,11; 2,22-23If the name is glossed only once (at first occurrence, with the judgment sense), the deliberate later reversal to the restoration sense is lost; both glosses are required at their respective locations
12Lo-Ruhamah / Lo-Ammi left as bare transliterationsHosea 1,6.9; reversed 1,10; 2,23As in #11 — these are not merely proper names but complete theological sentences; omitting the gloss at any occurrence (including the reversal) breaks the naming-oracle’s rhetorical logic
13”Wie ein Löwe” vs. the tender parent of 11,1-4Hosea 13,7-8 vs. 11,1-4The deliberate shock of the juxtaposition (same God, radically different register) is itself the theological content; softening either image to reduce the apparent tension defeats the book’s own rhetorical strategy
14”Die Glut meines Zorns” in a wrath-averse contemporary German theological climateHosea 11,9; cf. 8,5Risk of the term being quietly reduced to a metaphor for “disappointment” in teaching material shaped by contemporary liberal-theological discomfort with divine wrath language, undermining the very tension the doctrine “Judgment and Compassion Held Together” requires
15”Ich will sie frei und aus freiem Willen lieben” (14,4) as an OT/NT bridge conceptHosea 14,4Useful pedagogically as a bridge to Gnade, but must not be presented as lexically or historically identical to χάρις — a plausible but doctrinally imprecise shortcut likely to appear in teaching material unless explicitly guarded against

6. Full-Book Coverage Checklist

Per the PRD’s full-book-coverage mandate, every chapter is accounted for below. Chapters contributing no new gap beyond what is already documented above are stated explicitly.

Chapter(s)New Gap Contributed?Disposition
1Yes — Jezreel, Lo-Ruhamah, Lo-Ammi naming-oracle gaps (§5 #11-12)Fully documented above
2Yes — baʿali/ishi wordplay (§5 #4); betrothal register mismatch (§1.3); Hurerei crudeness (§5 #8)Fully documented above
3Yes — qanah (redeem/buy back) commercial metaphor; “remain mine” fidelity periodDocumented in 08_core_glossary.md; no additional gap beyond concrete-metaphor discipline already established in the baseline (Schuldschein/Lösegeld precedent)
4Yes — daʿat Elohim (§1.2, §3.6); ruach zenunim “spirit of whoredom” (§3.2); Beth-Awen wordplayFully documented above
5Yes — “pride of Israel” self-testimony image; continues shuv usage (5,4; 5,15)No new gap category beyond §1.5’s shuv consistency requirement
6Yes — chesed citation (6,6, §1.1 #1 priority); Adam/covenant textual ambiguity (§5 #9)Fully documented above
7No new doctrinal gap beyond continued shuv usage (7,10.16) and two minor domestic similes (cake not turned, silly dove) already catalogued in 08_core_glossary.md as Low risk with no fencing requiredReviewed; no new entry needed
8Yes — sowing/reaping intensification (§baseline cross-reuse, documented in bible_term_registry.json); calf-idols/Exodus-32 echoNo new gap category; reuses existing baseline säen/ernten fencing discipline
9Yes — kavod/Herrlichkeit disambiguation (national honor vs. divine glory, §3.5-adjacent); “days of punishment” HeimsuchungFully documented in §1.4 and §3
10Yes — luxuriant vine (John 15 contrastive bridge, non-lexical); continued calf-idol imageryNo new gap category beyond §1.2’s idolatry vocabulary
11Core passage. Yes — the single densest concentration of gaps in the book: beni typological sonship (§5 #5), qara/Exodus-calling disambiguation (§2), cords-of-love/yoke tenderness imagery, nehpakh libi (§5 #2), charon af (§5 #14), qadosh/Holy One paradox, ki El anokhi ve-lo ish (§5 #3), “like a lion” anticipation (paired with ch. 13)Fully documented above; this chapter is the analytical center of the entire document
12Yes — Jacob/wrestling-with-God typological allusion (Genesis 32 cross-reference gloss need)Documented in bible_term_registry.json; no new fencing category beyond existing low-OT-literacy gloss discipline already established throughout the baseline package
13Yes — “like a lion” (§5 #13); ransom from Death exegetical debate (§5 #10); “no God besides me” exclusivity claim (parallel to, but historically distinct from, John 14,6’s NT exclusivity claim — must be kept categorically separate in teaching material)Fully documented above
14Yes — climactic resolution: ohavem nedavah “I will love them freely” (§5 #15); rapha/heilen resolution of 11,3 (§3.4); restoration imagery cluster (dew/lily/Lebanon, Low risk, concrete-imagery discipline only)Fully documented above

Conclusion: All 14 chapters are accounted for. Twelve of fourteen chapters contribute at least one new gap category; chapters 7 and 10 are explicitly noted as reviewed-with-no-new-gap rather than silently omitted, per the mandate.


7. Summary Recommendations Carried Forward to Phase 2

  1. Fix all Critical-risk terms exactly as recorded in 08_core_glossary.md / bible_term_registry.json; no Phase 2 worker may improvise an alternative for chesed, shuv, the divine name typography, or any of the naming-oracle terms.
  2. Build automated validation checks (parallel to the baseline’s “verdiente Gerechtigkeit” and “Heil” checks) specifically for: Gnade-for-chesed substitution; Heil-adjacent expansion of heilen; loss of HERR small-capital typography; pluralization or softening errors in the naming-oracle glosses.
  3. Mandate theologian review for every occurrence of the 15 ranked ambiguities in §5, with the core-passage items (#1–5) requiring the highest review priority in the Phase 2 Step 17 routing queue.
  4. Supply standing footnote/teaching-note infrastructure for the four genuinely untranslatable features identified in §2 (baʿali/ishi pun; shuv/meshuvah root-pun; theologically-loaded proper names; the four-way love/loyalty vocabulary split) — these cannot be solved by term selection alone and must be treated as a documentation requirement, not a translation-memory entry.
  5. Carry the fencing rules of §3 into the AI system prompt (Phase 1 Step 12) as explicit forbidden-substitution and disambiguation-required rules, extending the existing baseline categories rather than replacing them.

This analysis extends, and nowhere contradicts, the baseline Romans Language Package for German. All baseline term renderings (Israel, Bund, Gott, Herr, heilig, Sohn Gottes, Herrlichkeit, berufen/Berufung, Prophet, säen/ernten, Gnade, Rettung, Erlösung, Buße) remain fixed as recorded there and are referenced here only for boundary-marking (fencing) purposes, never for redefinition.

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