Linguistic Gap Analysis
06 — Linguistic Gap Analysis: 2 Kings
Destination Language: German
Purpose and Method
This document executes PRD Phase 1 Step 8 for the 2 Kings curriculum. It builds directly on the semantic groundwork already laid in 08_core_glossary.md and the extended bible_term_registry.json entries, but performs a distinct analytical task: rather than cataloging what each term should be rendered as, it diagnoses why German as a destination language creates translation difficulty for this specific book, and prescribes strategy at the doctrine level.
Four analytical lenses are applied, per the PRD Step 8 mandate:
- Doctrine Vocabulary Matrix — for each of the six curriculum doctrines, what German vocabulary is available, what is structurally weak about it, and what strategy Phase 2 must follow.
- Missing Vocabulary vs. Crowded Semantic Neighborhoods — where German has no natural word (a gap requiring coinage or periphrasis) versus where German has too many competing senses crowded onto one word (requiring a “fence” — an explicit disambiguating convention).
- Transliteration vs. Paraphrase Decisions — for proper nouns, technical cultic vocabulary, and idiom, which strategy is correct and why.
- Ranked Ambiguity List — the specific highest-risk points of confusion in this letter, ordered by severity, anchored to the core passage (2 Kings 17:1-23) but spanning the whole book per the full-coverage mandate.
This analysis inherits and does not contradict the baseline Romans Language Package. Every baseline-fixed term (Gott, Bund, Gesetz, Sünde, Herr, Glaube, Prophet, Weissagung, Israel, David, Heiden) is treated here as a constraint, not a free variable — the task is to determine how the 2 Kings material interacts with, extends, or creates friction against those fixed choices.
1. Doctrine Vocabulary Matrix
| Doctrine | Available German Vocabulary | Structural Weaknesses | Recommended Strategy |
|---|---|---|---|
| Covenant Judgment and the Exile | Bund (baseline), Gericht, Zorn, verwerfen, wegführen, Exil, Verbannung, vor seinem Angesicht wegtun | German legal vocabulary (Gericht, Urteil) risks sounding like impersonal court process rather than a wronged covenant partner’s relational response; “Exil” alone is historically neutral (used equally of political refugees, economic emigrants) and drains the covenant-curse force unless anchored; “Zorn Gottes” sits between a rich Lutheran hymnic tradition (which takes it seriously) and a modern liberal-theological instinct to psychologize it away | Use Bund consistently (never substitute a bare “Vertrag,” which is transactional/commercial); reserve Exil for section headings/summaries only, using wegführen / in die Verbannung führen for the theologically load-bearing verbal statements of the judgment itself; require explicit “personal, relational, judicially-proportionate” framing note wherever “Zorn” occurs |
| Prophetic Ministry and Miraculous Power (Elijah and Elisha) | Prophet (baseline), Mann Gottes, Wunder, Zeichen, Geist, wieder lebendig werden | ”Wunder” (miracle) is theologically thin in contemporary secular German usage — often trivialized to “medical miracle” (Wunderheilung) or advertising language (“Wundermittel”); “Geist” for the prophetic-empowering ruach risks bleeding into the baseline’s fully personal, Trinitarian Heiliger Geist doctrine if not qualified; “auferstehen” MUST NOT be used for Elisha’s revival miracles | Prefer concrete, narrative-anchored language over the abstract noun “Wunder” where possible (e.g., name the specific act: Heilung, Vermehrung, Wiederbelebung); qualify “Geist” as dein Geist / der Geist, der auf Elija war in these OT-functional-empowerment contexts rather than bare “der Heilige Geist”; enforce wieder lebendig werden, never Auferstehung, as an absolute rule at every occurrence (4:34-35; 8:1-6; 13:21) |
| The Fall of Israel and Judah as Covenant Consequence | Sünde (baseline), Götzen, Baal, Kulthöhen, tat, was dem HERRN missfiel, Same-formula language | German colloquial “Sünde” is trivialized (diet/dessert usage, per baseline note) at exactly the doctrine that most needs its full covenantal weight; the recurring regnal-evaluation formula requires lexical fixity across ~35 occurrences, which is a discipline risk (translators drift toward natural variation for readability) rather than a vocabulary-availability gap | Mandate a single, locked German formula for “did evil in the sight of the LORD” applied without stylistic variation across all 35+ occurrences, explicitly overriding the normal stylistic instinct toward varied phrasing; pair every “Sünde” occurrence in ch. 17 exposition with explicit generational/national-scale framing to resist colloquial-trivialization drift |
| God’s Patience through Repeated Prophetic Warning | ermahnen (baseline, wrong register), bezeugen, warnen, Seher, hören und gehorchen | The baseline’s existing “ermahnen” is calibrated for New Testament pastoral encouragement/admonition and is too gentle for the Hebrew legal-covenantal “he’id” (formal witnessed warning); German “hören” alone (without an obedience-gloss) reads as mere auditory perception, losing the Hebrew shama’s built-in obedience component | Introduce bezeugen / warnen as a distinct, non-baseline term reserved for this formal covenant-lawsuit warning sense, explicitly distinguished in teaching notes from “ermahnen”; always gloss “hören” as hören und gehorchen in accusatory covenant contexts |
| Josiah’s Reforms and the Rediscovered Law | Gesetz (baseline), Buch des Gesetzes, Bund, Kulthöhen entfernen, sein Herz war weich | ”Gesetz” in German theological discourse is saturated with the Pauline/Lutheran “Gesetz und Evangelium” dialectic (per baseline note); 2 Kings uses the word in its plain historical-narrative Mosaic-document sense, and readers steeped in Romans/Galatians material from this same pipeline may unconsciously import the law-versus-grace antithesis where it does not belong | Explicit teaching-note requirement: every occurrence of das Buch des Gesetzes in the Josiah material must carry a brief disambiguating note that this is the concrete Mosaic covenant document being rediscovered as history, not a rhetorical foil for grace — while still permitting the legitimate forward connection to the baseline’s Romans doctrine of law’s role in exposing sin |
| Hope amid Judgment | Rest/Überrest, vertrauen auf den HERRN, der lebende Gott, eine tägliche Zuteilung | German has no single term carrying “restrained, non-triumphalist hope” — “Hoffnung” alone risks sounding either falsely upbeat (contradicting the book’s severe judgment content) or, if under-emphasized, disappearing entirely beneath the judgment material; there is a genuine register gap between full eschatological hope-vocabulary (too strong for this book’s understated ending) and mere historical footnote (too weak) | Deliberately calibrate register down from the fuller NT hope-vocabulary already fixed in this pipeline (e.g., avoid borrowing intensity from Romans 8’s assurance language); render the book’s closing image (25:27-30) with restrained, factual narrative German that lets the theological weight emerge from the reader’s own inference rather than the translation’s adjectives |
2. Missing Vocabulary vs. Crowded Semantic Neighborhoods
2.1 Missing Vocabulary (German Has No Clean Native Equivalent)
These are concepts where German simply lacks a single word carrying the full Hebrew semantic load, requiring periphrasis, compounding, or a fixed multi-word formula rather than a single lexeme.
| Concept | Why German Has No Single Word | Resolution Strategy |
|---|---|---|
| gillulim (contemptuous idol-term, “dung-things”) | German “Götze” is already a fixed, mildly derogatory loanword-adjacent term but carries none of the Hebrew’s specific scatological insult; no German word replicates that register | Accept Götzen as the best available approximation (already fixed in registry) but supply an explanatory footnote at first occurrence (17:12) naming the Hebrew’s literal contempt, so the argument (idols are refuse, not rivals) is taught even though the word itself cannot carry it |
| hevel-wordplay (“became empty by worshipping emptiness”) | German has no single root that functions as both noun (“emptiness/vanity”) and verb (“to become empty”) with natural theological register, matching Hebrew hevel’s flexibility | Construct a fixed paired phrase using one root on both sides — sie liefen der Nichtigkeit nach und wurden selbst nichtig — rather than importing two unrelated German words that would sever the wordplay |
| chozeh vs. navi (seer vs. prophet, a doubled office-term for rhetorical comprehensiveness) | German “Seher” exists but is under-used in contemporary religious register (associated more with folklore/fortune-telling in secular usage) compared to the robust, stable “Prophet” | Retain Seher deliberately despite its secular-register risk, because using “Prophet” for both terms erases the historian’s rhetorical device of doubling; add a brief translator note distinguishing this from folk-fortune-telling associations |
| pi-shenayim beruchakha (firstborn double-inheritance idiom applied to spiritual empowerment) | German inheritance-law vocabulary (Erbteil, Erbrecht) does not carry a natural devotional-spiritual extension the way the Hebrew idiom does | Render literally as doppelter Anteil deines Geistes and supply the inheritance-custom background explicitly in teaching material rather than seeking a native German idiom that does not exist |
| the aruchah “daily portion” epilogue (25:30) — an ancient royal-court maintenance allowance, not a modern salary/pension/welfare payment | Modern German administrative/financial vocabulary (Rente, Gehalt, Unterhalt) imports anachronistic bureaucratic connotations | Use the deliberately plain, non-technical eine tägliche Zuteilung rather than any modern financial-administrative term, preserving ancient-court register |
2.2 Crowded Semantic Neighborhoods (Too Many Competing Senses on One German Word — Require Fencing)
A “fence” here means an explicit, documented convention — typographic, contextual gloss, or reserved-term discipline — that prevents one German word’s multiple senses from bleeding into each other across this curriculum.
| German Word | Competing Senses Crowded Onto It | Fence Required |
|---|---|---|
| Herr | (1) baseline’s fixed NT Kyrios-confession title (Romans 10:9); (2) the ordinary everyday German title “Mr.” (Herr Müller); (3) OT’s divine-name YHWH, occurring ~380 times in this book alone; (4) Baal’s own etymological meaning (“lord, master, husband”) | Mandatory typographic fence: OT YHWH renders as small-caps/full-caps HERR per Luther 2017/Einheitsübersetzung convention, never plain “Herr.” Baal is never translated as a common noun (always the transliterated proper name). Any teaching material cross-referencing 2 Kings’ HERR-formula with Romans 10:9’s Herr-confession requires mandatory theologian review to keep the two typographically and conceptually distinct. |
| Heiden / Völker | (1) baseline’s Romans missionary-inclusion sense (Unity of Jews and Gentiles, positive valence); (2) 2 Kings’ judgment/dispossession sense (goyim as objects of covenant curse for idolatry, negative valence); (3) plain ethnic-descriptive sense (resettled foreign populations, 17:24, neutral valence) | Fence by lexical choice, not typography: reserve bare Heiden for contexts explicitly echoing the Romans missionary doctrine; use die Völker / die heidnischen Völker for 2 Kings’ judgment-oracle sense (17:8, 11, 15, 26-41); use plain Völker or fremde Völker for the neutral ethnic-descriptive resettlement sense (17:24). Mandatory theologian review flag wherever OT and NT “nations” material is taught side by side. |
| Gesetz | (1) baseline’s Pauline law/grace dialectical foil (Galatians, Romans); (2) 2 Kings’ plain historical-narrative Mosaic covenant document (the rediscovered scroll, ch. 22) | Contextual-note fence: every occurrence in the Josiah material requires a brief note establishing the plain historical-document sense before any legitimate forward connection to the Pauline dialectic is drawn; never let the two senses merge silently. |
| fürchten | (1) ordinary emotional dread; (2) OT’s positive reverential-worship sense (“Gottesfurcht”); (3) the syncretism-diagnosis sense (“feared the LORD, yet served their own gods,” 17:33, 41) — where “fear” names allegiance, not emotion | Gloss fence: never leave “fürchten” bare in a worship-allegiance context; always expand to verehrten or fürchteten und verehrten so the reader cannot default to the emotional-dread reading. |
| Bund | (1) the underlying covenant relationship itself (theological constant); (2) specific historical renewal ceremonies (11:17; 23:1-3) as one-time public events | Contextual fence, not lexical: no separate word is needed, but teaching material must distinguish “the covenant” (ongoing relationship, singular theological referent) from “a covenant-renewal ceremony” (a specific datable liturgical event) so students do not think the covenant was repeatedly re-created rather than repeatedly reaffirmed. |
| Geist | (1) baseline’s fully personal, Trinitarian Heiliger Geist; (2) 2 Kings’ OT functional-empowerment sense (Elisha’s “double portion,” 2:9; the Spirit that “was upon” Elijah) | Gloss fence: never render 2:9 as a bare, unqualified reference that could be silently equated with full NT pneumatology; always retain the possessive/functional framing (“dein Geist,” “der Geist, der auf Elija war”) and note doctrinal continuity-without-identity explicitly. |
| Auferstehung / auferstehen | (1) baseline’s Critical-risk, singular, eschatological resurrection of Christ; (2) any temptation to describe Elisha’s revival miracles (4:34-35; 8:1-6; 13:21) using the same root | Absolute lexical fence: “Auferstehung” is permanently reserved for the baseline’s Christological doctrine. 2 Kings’ revival miracles use only wieder lebendig werden. This is a zero-tolerance rule, not a stylistic preference. |
| salben / Messias | (1) baseline’s Critical-risk Messianic Promise doctrine, fulfilled exclusively in Jesus; (2) 2 Kings’ ordinary royal-designation anointing (Jehu, 9:6; earlier kings) | Fence by doctrine-label discipline: the verb salben is shared, but 2 Kings’ royal anointings must never be characterized in teaching material as “messianic” in the baseline’s technical sense; flag explicitly wherever both senses could be juxtaposed (e.g., teaching material tracing the anointing motif across the whole Old Testament into the New). |
| Vorsehung / Zorn (God’s providence/anger) | Enlightenment-era deist German philosophical usage treats both as impersonal cosmic forces or abstract principles (already flagged in the baseline for “Vorsehung”) | Framing fence: every occurrence of judgment/anger language in the ch. 17 exposition must explicitly affirm personal, relational, covenant-partner anger — a specific response to a specific documented breach — rather than an impersonal deist “cosmic justice” mechanism. |
3. Transliteration vs. Paraphrase Decision Log
This section records, term by term, whether the correct destination-language strategy is (a) transliteration/proper-noun retention, (b) established-lexeme translation, or (c) periphrasis/paraphrase, with the reasoning for each decision.
| Term | Strategy | Reasoning |
|---|---|---|
| Baal | Transliterate (proper noun, never translated as common noun) | Translating “Baal” as “Herr” (its literal etymological sense) would create a catastrophic, unintended legitimacy-transfer with the fixed divine title; transliteration as a bare proper name neutralizes this risk while preserving historical specificity. |
| YHWH (Tetragrammaton) | Established-convention rendering, not transliteration | German Bible tradition (Luther 2017, Einheitsübersetzung) does not transliterate the Tetragrammaton but uses the typographically distinguished HERR; this curriculum follows that convention rather than introducing a novel transliteration (“Jahwe”), which would break continuity with the destination culture’s dominant Bible translation tradition per the baseline’s own governing rule. |
| Gillulim / Pesilim / Atsabbim (three distinct Hebrew idol-terms) | Established-lexeme translation with differentiation, not transliteration | Transliterating three obscure Hebrew terms would be unreadable and pedagogically useless for a German audience with no Hebrew background; instead, three distinct German phrases (Götzen / geschnitzte Bilder / Götzenbilder) preserve the fact of lexical variety (the historian’s comprehensiveness argument) without requiring Hebrew literacy. |
| Asherah | Transliterate the proper/technical name, translate the referent in gloss | ”Aschera” is retained as the established German Bible transliteration (both for the goddess and, by extension, her cult-object); paired with the gloss “Kultpfahl” to clarify the physical referent for readers unfamiliar with the term. |
| Sefer ha-Torah / “Book of the Law” | Established-lexeme translation, not transliteration | Reuses baseline Gesetz; no transliteration value exists here since this is a Hebrew common-noun phrase, not a proper name, and the baseline’s Gesetz rendering is already fixed and must not be varied. |
| Aruchah (“daily portion,” 25:30) | Paraphrase, not transliteration or single-word translation | No single German word captures this ancient royal-court maintenance-allowance concept without anachronistic administrative connotations (see Section 2.1); a plain descriptive phrase is required. |
| Chozeh (“seer”) | Established-lexeme translation (Seher), not transliteration | A native German word exists and should be used rather than either transliterating the Hebrew or collapsing into “Prophet” (see Section 2.1 discussion of the doubling device). |
| Ben ha-Nevi’im (“sons of the prophets”) | Paraphrase / established compound, not literal word-for-word translation | A literal “Söhne der Propheten” would mislead German readers toward biological sonship; the institutional-guild sense requires the compound Prophetenjünger/Prophetenschüler, which is paraphrase-as-clarification rather than literal transliteration of the Hebrew idiom. |
| Proper names (Elija, Elisa, Hiskia, Josia, Manasse, etc.) | Established German Bible transliteration forms, per Table 4 of the glossary | Consistency with existing German Bible tradition (per the baseline’s own transliteration standards section) takes priority over phonetic closeness to Hebrew; these forms are not open variables. |
| Pi-shenayim beruchakha (“double portion of your spirit”) | Literal translation, not paraphrase | Unlike aruchah, this idiom translates comprehensibly enough word-for-word (doppelter Anteil deines Geistes) that literal rendering plus a brief explanatory note is preferable to a fully paraphrased alternative, which would lose the inheritance-law texture entirely. |
| Massoretic regnal-evaluation formula (“did evil/right in the sight of the LORD”) | Fixed established-lexeme formula, locked across all occurrences | Neither transliteration nor free paraphrase is appropriate; this is a case requiring maximum lexical rigidity — the same German words every time — because the repetition itself, not merely the content, is the theological argument. |
4. Ranked List of Highest-Risk Ambiguities
Ranked by combined severity (doctrinal consequence if mistranslated) and probability (how easily a translator or reviewer could plausibly get it wrong given German’s specific semantic terrain). All items are anchored where possible to the core passage, 2 Kings 17:1-23, with book-wide cross-references noted.
Rank 1 — HERR (YHWH) vs. Herr (Kyrios/“Mr.”) typographic collapse
Where: Every verse of the core passage (17:1-23 contains the divine name over a dozen times) and ~380 times book-wide. Risk: If a translator, editor, or downstream formatting pipeline silently normalizes “HERR” to “Herr” (a very easy accidental error in automated pipelines, style-sheet defaults, or copy-paste operations), the entire chapter’s covenant-lawsuit argument — addressed to and about the specific covenant God, not a generic honorific — collapses into ambiguous, flattened prose indistinguishable from ordinary narrative address. Given that German has no protective secondary honorific (unlike languages that lend “Lord” a reserved liturgical register distinct from everyday address), this is the single highest structural risk in the whole book. Mitigation: Automated post-translation validation must specifically scan for lowercase “Herr” in OT narrative segments and flag for correction; this is a mechanically checkable rule and should be enforced at the validation-rules layer, not left to reviewer discretion alone.
Rank 2 — “verwerfen” wordplay integrity (17:15 / 17:20)
Where: 2 Kings 17:15 (“they rejected his statutes… and his covenant”) and 17:20 (“the LORD rejected all the seed of Israel”). Risk: This is the chapter’s central theological mirror: Israel’s rejection of the covenant becomes the LORD’s judicial rejection of Israel. If a translator uses two different German verbs (e.g., “verachten” at v.15 and “verwerfen” at v.20, or vice versa) for stylistic variety — a very natural German-prose instinct — the deliberate structural argument (this judgment is the precise legal mirror of Israel’s own act) becomes invisible to the German reader. Mitigation: Lock verwerfen at both poles; explicitly flag in the translator brief that stylistic variation is forbidden here, overriding the normal preference for varied vocabulary in literary German prose.
Rank 3 — “die Völker/Heiden” bleed-through between OT judgment sense and NT missionary sense
Where: 2 Kings 17:8, 11, 15, 26-41 (goyim as objects of judgment) versus the baseline’s fixed Romans usage (Heiden as objects of gospel inclusion). Risk: Given this pipeline’s own documented plan to teach Romans and 2 Kings within the same overall curriculum ecosystem, and given Germany’s acute historical sensitivity to any rhetoric that could be heard as ranking or condemning whole peoples, an inconsistent or careless German rendering could either (a) import Romans’ positive inclusion-framing backward into 2 Kings’ judgment-oracle in a way that blunts the passage’s actual argument, or (b) import 2 Kings’ judgment-framing forward onto Romans’ missionary objects in a way that sounds like ethnic condemnation. Both directions of bleed-through are serious. Mitigation: Enforce the Section 2.2 fence (die Völker / die heidnischen Völker for judgment sense; bare Heiden reserved for missionary sense) with mandatory theologian review flag wherever both testaments are taught in adjacent material.
Rank 4 — “Sünde” colloquial trivialization at exactly the passage bearing the most doctrinal weight
Where: 2 Kings 17:7, 17:21-22 (cumulative national sin as the stated cause of exile). Risk: The baseline already documents this risk for Romans, but the risk is structurally worse here: Romans’ theological argument survives even if a reader momentarily thinks of “Sünde” as a minor lapse, because the letter’s larger argument (grace, justification) recontextualizes it. In 2 Kings 17, the trivialized reading directly undermines the passage’s entire rhetorical strategy, which depends on the reader feeling the cumulative, generational, exile-causing weight of the term. A reader accustomed to “das ist doch keine Sünde” (colloquial: “that’s not really a big deal”) register will radically underestimate the chapter’s severity. Mitigation: Explicit teaching-note framing accompanying every occurrence in ch. 17 exposition material, naming the cumulative/generational/national scale explicitly rather than relying on the word alone.
Rank 5 — “Zorn” register mismatch (Lutheran-devotional vs. modern-liberal-theological instincts)
Where: 2 Kings 17:18 (“the LORD was very angry with Israel”) — the chapter’s judicial climax.
Risk: German-speaking readers arrive with genuinely divergent theological formation: pietist/confessional Lutheran readers may take “Zorn Gottes” with full seriousness (a genuine asset here), while readers formed by more liberal 20th-century German Protestant theology (which has often worked to reinterpret or de-emphasize divine wrath language) may instinctively soften the translation or its exposition. Both instincts, left unchecked, distort the passage: the first risks caprice-reading, the second risks explaining the wrath away entirely.
Mitigation: Mandatory theologian-authored framing note holding together “genuine personal anger” AND “proportionate judicial conclusion of a documented case” as inseparable, per the bible_term_registry.json entry for very_angry_anaph.
Rank 6 — “vor seinem Angesicht wegtun” (removed from his sight) losing its relational-presence force
Where: 2 Kings 17:18, 17:23 (inclusio) and echoed at 25:9. Risk: A translator seeking natural German idiom might reach for a simpler “er verstieß sie” (he cast them out) or “er verbannte sie” (he banished them), both of which are grammatically smoother but lose the “Angesicht” (face/presence) vocabulary that makes clear this is a withdrawal of relational divine presence, not merely a change of geography. This is precisely the theological point of “exile” that distinguishes it from ordinary deportation. Mitigation: Lock the full phrase vor seinem Angesicht wegtun at both v.18 and v.23, resisting the natural editorial instinct toward a shorter, smoother alternative.
Rank 7 — “wieder lebendig werden” vs. “Auferstehung” boundary discipline
Where: Book-wide (4:34-35; 8:1-6; 13:21), not within the core passage itself, but doctrinally adjacent via the “Prophetic Ministry and Miraculous Power” curriculum doctrine that sits alongside the core passage. Risk: Although the core passage does not itself contain a revival miracle, curriculum material teaching 2 Kings as a whole will inevitably juxtapose the Elisha revival narratives with the book’s Christological/eschatological horizon. Any accidental lexical overlap with the baseline’s fixed, Critical-risk “Auferstehung” doctrine would blur a distinction Christian theology has always insisted on: Christ’s resurrection is unique, bodily-glorified, and eschatologically final; Elisha’s revivals are temporary returns to ordinary mortal life. Mitigation: Treat as an absolute, zero-tolerance lexical rule (see Section 2.2) rather than a stylistic preference, given its adjacency to core-passage teaching material.
Rank 8 — “Gesetz” register contamination from this pipeline’s own Romans/Galatians material
Where: 2 Kings 17:13, 17:34, 17:37 (within the core passage itself) and ch. 22 (Josiah’s rediscovered scroll). Risk: Because this same translation pipeline has already produced extensive Romans and Galatians material establishing “Gesetz” within the Pauline law/grace dialectic, students and even translators moving between curricula may unconsciously read 2 Kings 17’s “Gesetz” through that dialectical lens, when the chapter’s own argument is a plain historical claim (Israel possessed, and disregarded, Mosaic covenant instruction) rather than a statement about law’s relationship to grace. Mitigation: Explicit disambiguating note at first occurrence in the core-passage exposition, distinguishing the plain historical-narrative sense from the Pauline dialectical sense while still permitting a legitimate, clearly-labeled forward connection.
Rank 9 — “verehrten andere Götter” vs. bare “fürchteten” (fear/worship allegiance disambiguation)
Where: 2 Kings 17:7 (within the core passage) and the syncretism-diagnosis passages (17:33, 41). Risk: Contemporary German “fürchten” primarily signals emotional dread; without an explicit worship/allegiance gloss, readers may parse 17:7’s accusation as merely “they were afraid of other gods” (a psychological claim) rather than the actual accusation, “they gave other gods the reverence-allegiance owed exclusively to YHWH” (a covenant-loyalty claim). Mitigation: Enforce the Section 2.2 gloss-fence at every occurrence; never permit bare “fürchteten” to stand unglossed in this specific sense.
Rank 10 — Baal/Herr etymological collision in homiletic material
Where: Book-wide wherever Baal is named (not within 17:1-23’s own text, but frequently adjacent in teaching material summarizing the northern kingdom’s apostasy that ch. 17 indicts). Risk: A well-meaning but theologically careless teacher or curriculum writer might be tempted to build a homiletic point on the fact that “Baal” literally means “lord” — drawing a rhetorical parallel to “Herr” that could, if mishandled, suggest some kind of linguistic legitimacy-transfer or false equivalence between the two. Mitigation: Explicit standing instruction in all teaching material (already present in bible_term_registry.json) that this etymological fact is historical-linguistic information only, never a homiletic wordplay opportunity, and must never imply legitimacy-transfer.
5. Summary Recommendations for Phase 2 Enforcement
- Typographic discipline is non-negotiable. The single highest-risk item in this entire analysis (Rank 1) is mechanical, not interpretive — it can and must be caught by automated validation rules, not left to translator judgment alone.
- Lock all repeated formulas. The regnal-evaluation formula, the “removed from his sight” inclusio, and the “verwerfen” wordplay all require lexical rigidity that runs against the normal German-prose instinct toward stylistic variety. This must be an explicit, stated override in the Phase 2 system prompt, not assumed.
- Fence, don’t merge, crowded neighborhoods. Herr/HERR, Heiden/Völker, Gesetz, fürchten, Geist, and Auferstehung each require an explicit, documented convention preventing cross-contamination with either the baseline’s NT doctrine or this book’s own internal distinct senses.
- Where German lacks a word, use fixed periphrasis, not ad hoc translator choice. The aruchah, hevel-wordplay, and ben ha-nevi’im cases all require a single agreed multi-word rendering repeated consistently, not independent case-by-case translator decisions that could produce inconsistent renderings across chapters.
- Calibrate the “Hope amid Judgment” doctrine’s register deliberately downward from the fuller assurance-vocabulary already established elsewhere in this pipeline’s Romans material — this book’s hope is real but restrained, and the translation must not artificially inflate its emotional register to match Romans 8.
This analysis feeds directly into Phase 1 Step 9 (terminology decision log) and Phase 1 Step 11 (doctrine risk registry construction) for the 2 Kings curriculum, and must be loaded alongside 08_core_glossary.md before any Phase 2 segment translation begins.