Executive Summary — Malachi (German Destination Language)

Why it matters

Malachi closes the Hebrew canon with a covenant-lawsuit oracle that is short (4 chapters) but doctrinally dense throughout — every chapter carries load-bearing vocabulary. For a German-speaking audience, this book concentrates an unusual cluster of high-stakes, destination-language-specific collision risks: a mandatory Tetragrammaton typography rule (HERR vs. Herr) that most output formats cannot preserve without explicit workarounds; a tithing doctrine that collides head-on with Germany’s Kirchensteuer system; and a marriage/divorce passage (2:16) sitting on a genuine Hebrew textual crux that intersects Germany’s live Catholic/Protestant confessional divide. Getting this book’s German package right protects five curriculum doctrines and sets binding precedent (HERR typography, curse-term fencing, Bote/Engel disambiguation) that future OT curricula in this pipeline will inherit.

Key findings

• 50 new German theological terms identified across all 4 chapters (none omitted), plus 17 baseline Romans-package terms inherited exactly for reuse or deliberate contrast.
• 13 Critical-risk + 14 High-risk new terms (27 of 50, 54%) require mandatory human theologian review before Phase 2 release — concentrated in the core passage (Maleachi 3:1-4) and its immediate surroundings.
• 26 doctrines documented across the full book, with the registry recording 10 Critical + 10 High = 20 doctrines requiring theologian review, 6 requiring native-speaker review, and 1 (the prophetic-oracle genre marker) sufficient for automated review alone.
• Two German-forced disambiguations exist that the Hebrew original does not require: the HERR/Herr typographic split (Tetragrammaton vs. adon) and the Bote/Engel lexical split (mal’akhi vs. mal’akh habb’rit) — both concentrated in Malachi 3:1, the core passage’s opening verse.
• Three distinct Hebrew curse-terms (arur, cherem, and the baseline’s inherited NT anathema) all pressure-test the same German word family (“verflucht/Fluch/Bann”) and must be fenced apart, not merged.
• No missing vocabulary — German has adequate words for nearly every Hebrew concept in this book; the dominant risk is overcrowded, competing vocabulary requiring disciplined fencing rather than new-term invention (per analysis/06_linguistic_gap_analysis.md).

Risks

• Format fragility (Critical): the HERR/Herr distinction is typographic; any plain-text, audio, or accessibility-formatted output that drops case will silently answer an open theological question about the identity of “the messenger of the covenant.”
• Kirchensteuer collision (Critical): German readers may assume the state church tax already fulfills, or has bureaucratically superseded, the biblical tithing exhortation (3:8-12) — comparable in severity to the baseline’s existing Heil/Nazi-era caution.
• Divorce-crux mishandling (Critical): Malachi 2:16 is a genuine scholarly translation crux; resolving it silently in either direction pre-empts a live Catholic/Protestant pastoral disagreement in Germany.
• Automated glossary mismatch (High, procedural): pipeline automation may default “gentiles/nations” (goyim, 1:11) to the baseline’s pre-loaded “Heiden” rather than this curriculum’s deliberate “Völker” divergence.
• Curse-vocabulary convergence (High): without explicit fencing, translators will likely default all three curse-terms to “verflucht/Fluch,” erasing genre distinctions (liturgical fraud vs. total destruction vs. apostolic anathema) the curriculum must teach.
• Antisemitism-adjacent sensitivity (High): the Coming Messenger/Elijah material (3:1; 4:5-6) has both a Christian fulfillment reading and a live, still-awaited Jewish reading; teaching material must present both accurately per this pipeline’s existing Juden/Heiden discipline.

Opportunities

• Strong cross-pipeline anchors already exist: Elijah/John the Baptist (Matthew 11:14; 17:10-13) and “my messenger” (Mark 1:2) are already Critical-risk entries in this pipeline’s NT baseline registry — Malachi’s package can cite them directly rather than building forerunner typology from scratch.
• Positive cultural bridge: German hymnody’s long-standing “Sonne der Gerechtigkeit” tradition (4:2) gives teaching material a ready-made devotional entry point, provided it is framed as interpretive tradition rather than the text’s sole original sense.
• Diakonia/Caritas resonance: the social-justice catalogue of 3:5 (oppression of the hired worker, widow, orphan) connects naturally to Germany’s shared Protestant/Catholic charitable-service tradition already flagged for Matthew 25:40.
• Reusable governance pattern: the fencing discipline developed here (crowded-neighborhood management over new-term coining) is lower-cost to apply to future OT books than the NT baseline’s vocabulary-invention challenges were.

Recommended actions

1. Lock HERR/Herr typography enforcement into every Phase 2 output pipeline stage, including a mandatory spoken/written gloss requirement for non-typographic formats, before any Malachi segment ships.
2. Commission a standing theologian-authored Zehnte/Kirchensteuer distinguishing note for reuse across every lesson touching 3:8-12, rather than drafting ad hoc per lesson.
3. Draft the mandatory dual-reading translator’s note for Malachi 2:16 now, in advance of Phase 2, so no derivative teaching material can silently adopt one confessional reading.
4. Add an automated pre-flight check that flags any attempt to render goyim (1:11) as “Heiden” rather than “Völker,” given the high probability of default-glossary mismatch.
5. Route all 20 theologian-review doctrines and 27 Critical/High-risk terms through mandatory human theologian sign-off before Phase 2 batch translation begins; do not allow native-speaker-only review to substitute for any of them.
6. Reuse this book’s curse-term fencing (verflucht/Bann) and Bote/Engel disambiguation pattern as the template for any future OT prophetic-book curriculum in this pipeline.

---

This summary is consistent with assets/doctrine_risk_registry.json, assets/bible_term_registry.json, assets/translation_memory.json, and analysis/11_doctrine_analysis.md (all Malachi versions, German destination language). Any future update to term or doctrine counts must be reflected here simultaneously.