Obadiah → German: Executive Summary

Why it matters

Obadiah is the shortest book in the Hebrew Bible — 21 verses, one chapter — but it is doctrinally dense and carries the highest concentration of German-specific historical-sensitivity risk yet encountered in this pipeline. Its core passage (1:15–21) delivers four load-bearing doctrines — judgment on pride and violence, a universalized Day of the Lord, God’s justice for the oppressed, and the climactic confession that the kingdom belongs to the Lord — through vocabulary (the Tetragrammaton, “handed over,” “nations,” “kingdom”) that collides directly with terms already fixed in the German-language Romans baseline. Getting this book right requires not just accurate Hebrew-to-German translation but active fencing of Obadiah’s own vocabulary away from superficially similar baseline NT terms, plus one non-negotiable historical-sensitivity protocol with no precedent elsewhere in the pipeline except the Matthew 27:25/Matthew 23 rules.

Key findings

• Full-book coverage confirmed. All 21 verses reviewed across six rhetorical sections (superscription/judgment announcement, certainty of Edom’s fall, undoing of Edom’s wisdom/might, the specific indictment, the Day of the Lord hinge, and the restoration/kingdom climax). No verse range was silently skipped.
• 34 book-specific terms and 9 inherited baseline terms are now fixed in assets/translation_memory.json v1.
• 9 doctrines are fully documented in assets/doctrine_risk_registry.json v1 and analysis/11_doctrine_analysis.md: 4 core curriculum doctrines plus 5 supporting doctrines (Divine Authority of the Prophetic Word; Fraternal Betrayal and Kinship Obligation; Handing Over the Vulnerable to Destruction; Restoration and Covenant Land Inheritance; Lex Talionis and Divine Retribution).
• One irreducible German-specific lexical/historical gap exists with no clean resolution: Obadiah 1:14’s “handed over” (hisgir) must render as “ausliefern”/“preisgeben,” both of which carry direct Nazi-era deportation/betrayal resonance in German. This is flagged as the single highest-sensitivity term in the entire curriculum.
• Five crowded semantic neighborhoods require active fencing so Obadiah’s Hebrew-oracle vocabulary is not silently harmonized with the German Romans baseline’s NT-calibrated vocabulary: Herr/HERR (Tetragrammaton typography), Heiden/Völker (nations), Gerechtigkeit (justice vs. justification), Reich Gottes/Königsherrschaft (kingdom climax), and Stolz/Hochmut (pride).

Risks

Risk	Severity	Term-level flag count
Term-level Critical risk	9 terms (day_of_the_lord, divine_name_tetragrammaton, pride, violence, handed_over, holy_mountain, holy_status, saviors_deliverers, kingdom_of_the_lord)	Mandatory theologian review, every occurrence
Term-level High risk	6 terms (sovereign_lord_adonai_yhwh, nations_goyim, brother_jacob, drink_cup_of_wrath, remnant_escape, judge_rule)	Mandatory theologian review
Term-level Critical + High combined	15 of 34 book-specific terms (44%)	—
Doctrine-level Critical risk	5 of 9 doctrines	Mandatory theologian review
Doctrine-level High risk	2 of 9 doctrines	Mandatory theologian review
Doctrine-level Critical + High combined	7 of 9 doctrines (78%) require human theologian review; remaining 2 require native speaker review; 0 are automated-only	—
Single highest-severity item	Obadiah 1:14 “handed over” — Nazi-era deportation-verb resonance	Non-negotiable mandatory theologian-authored framing, every use, no exceptions

No doctrine in this curriculum is rated Low risk or eligible for automated-only review — a materially higher review burden than the Romans baseline package, driven by Obadiah’s compressed length (every verse is doctrinally load-bearing) and its unusually acute German historical-sensitivity profile.

Opportunities

• Genuine OT-to-NT vocabulary bridges exist and should be surfaced pedagogically rather than hidden: “Gerettete” (1:17) and “Retter” (1:21) are deliberately built on the same root as the baseline’s “Rettung,” giving German learners a visible etymological link between Obadiah’s remnant/deliverer language and later NT salvation vocabulary — taught typologically, never as direct identification.
• The Berlin Wall / dividing-wall cultural bridge documented for Ephesians 2:14 has a structural cousin here: Obadiah’s Mount Zion/Mount Esau antithesis and its territorial reversal (1:17, 19–21) can draw on Germany’s own post-1989 reunification vocabulary of restoration and reversal, if handled with the same historical-distancing discipline already required for “Exil”/“die Verbannten.”
• The Petra/Sela identification (1:3) is a concrete, visitable-UNESCO-site anchor that can meaningfully build OT geographic literacy for a low-literacy German audience, turning a translation risk into a teaching asset.
• German’s own proverbial tradition (“Hochmut kommt vor dem Fall”) gives “Hochmut” cultural resonance beyond a bare dictionary choice, strengthening rather than merely satisfying the doctrinal requirement.

Recommended actions

1. Adopt assets/translation_memory.json v1 and analysis/12_ai_translation_requirements.md v1.28 as binding before any Phase 2 Obadiah segment translation begins.
2. Route all 7 Critical/High doctrines and both remaining Medium doctrines’ theologian-review-escalation triggers (per assets/doctrine_risk_registry.json) through human theologian review; confirm zero segments are approved via automated-only review for this book.
3. Enforce the Tetragrammaton small-capitals “HERR” convention mechanically across all six occurrences (1:1, 4, 8, 15, 18, 21) as a standalone validation check, independent of doctrinal content review.
4. Require the mandatory theologian-authored anti-misuse framing note on every use of Obadiah 1:14, with zero exceptions, before any teaching material containing that verse is published.
5. Brief all translators and reviewers explicitly on the five crowded-semantic-neighborhood fencing rules (Herr/HERR, Heiden/Völker, Gerechtigkeit, Reich Gottes/Königsherrschaft, Stolz/Hochmut) before assignment, given that this book shares a translator/reviewer pool with the Romans-through-John packages and harmonization errors are the most likely failure mode.