Executive Summary
Executive Summary
Leviticus → German | TRI Phase 1 Translation Requirements
Format: Smart Brevity. Core passage: Leviticus 16:1–34 (The Day of Atonement). Full scope: Leviticus 1–27, all chapters reviewed.
Why it matters
Leviticus gives German learners the Old Testament’s most concentrated picture of substitutionary atonement — and hands the translation team the single riskiest German-specific term collision in this entire pipeline to date. German coined the word “Sündenbock” directly from Luther’s own rendering of Leviticus 16, and that word has since fully secularized into an idiom for unjustly blaming an innocent person — the exact theological opposite of the divinely ordained, ritually authorized substitution the text describes. Get this chapter’s terminology and framing right, and the curriculum delivers a uniquely powerful bridge from Old Testament ritual to New Testament atonement Christology already established elsewhere in this pipeline (Romans 3:25, 1 Peter 1:19). Get it wrong, and German readers will hear the opposite of what Leviticus 16 says.
Key findings
- 27 of 27 chapters reviewed; full-book coverage confirmed. No chapter silently omitted; each is either a doctrine’s primary locus or an explicitly logged continuation.
- 8 curriculum doctrines mapped to 27 total doctrine entries in the risk registry (the 8 core doctrines plus supporting sub-doctrines required for full-book coverage), of which 11 are Critical-risk and 8 are High-risk — 19 of 27 doctrines (70%) require mandatory human theologian review, versus 8 requiring native-speaker review and 1 automated-only.
- ~94 Leviticus-specific terms registered in the term registry, of which 13 are Critical-risk and 23 are High-risk — 36 terms (38%) require mandatory theologian review, on top of roughly 40 inherited Romans-baseline terms reused exactly per pipeline discipline.
- Two doctrines carry uniquely acute, current-events-level German collision risk with no equivalent severity anywhere else in this pipeline: the Day of Atonement (the term “Jom Kippur” is simultaneously the theological name and the name of the 1973 Yom Kippur War, tied to Germany’s Staatsräson commitment to Israel) and the Scapegoat (near-total secularization of “Sündenbock”).
- Jewish tradition’s continuing, non-superseded observance of Yom Kippur, Shabbat, and kashrut is the most frequent point of interpretive divergence across this doctrine set; teaching material must name this explicitly rather than presenting Christian fulfillment as the only lens.
Risks
| Risk | Severity | Nature |
|---|---|---|
| ”Sündenbock” secularization | Critical | Total semantic inversion (unjust blame vs. divine ordination); every occurrence needs restorative framing, not a footnote |
| ”Jom Kippur” / 1973 war collision | Critical | Live geopolitical association, not a closed historical one |
| Sühne/Versöhnung conflation | Critical | Flattens forensic, blood-mediated atonement into generic relational reconciliation |
| Rein/unrein vs. heilig blending | Critical | German purity-idiom moralizes a Hebrew ritual-cultic category |
| ”Freiheit ausrufen” (Jubilee) assimilation | Critical | Concrete debt/land/slave-release sense lost to Germany’s dense general “Freiheit” associational field |
| ”Gnadenthron” cross-tradition divergence | Critical | Genuine Luther-classical vs. Luther-2017 vs. Einheitsübersetzung disagreement |
| ”Aussatz” stigma history | High | Medieval German social-exclusion history not coextensive with tsara’at |
| ”Fremde”/ger migration-politics sensitivity | High | Contemporary asylum/migration discourse could overshadow the text’s own historical-experiential logic |
| ”Friedensopfer” vs. “Heilsopfer” | High | A careless default to the Einheitsübersetzung’s term reintroduces the baseline’s Nazi-era “Heil” contamination risk |
| Threefold sin-vocabulary flattening | Medium (pervasive) | Sünde/Schuld/Übertretung collapse without deliberate translator discipline |
Opportunities
- Reuse, don’t reinvent. ~40 baseline Romans terms (Gnade, Gerechtigkeit, Freiheit, Heiliger, Bund, Israel, etc.) transfer directly, cutting new-term risk surface and reinforcing cross-book doctrinal continuity for learners already exposed to the Romans/Galatians/Ephesians material.
- “Gnadenthron” recovers Reformation memory. Choosing Luther’s classical rendering for kapporet over the flatter modern alternatives actively strengthens the Romans 3:25 typological connection already embedded in German devotional habit.
- The two-goat and two-bird rites (chs. 14, 16) teach as one unit. This internal biblical parallel gives German teaching material a built-in, textually grounded way to explain substitution before the “Sündenbock” secularization problem has to be confronted head-on.
- Named, credited Jewish interpretive priority (Hillel and Akiva on Leviticus 19:18) strengthens rather than weakens the curriculum’s credibility with a biblically literate audience and models the historical honesty this pipeline already practices for Matthew 23 and 27:25.
Recommended actions
- Route all Leviticus 16 segments as a matched theologian-review batch, not distributed individually — the chapter’s Critical-term density (mercy seat, atone, scapegoat, Azazel, bear-away, Day of Atonement name) requires interpretive coherence across the whole passage, not term-by-term sign-off in isolation.
- Mandate restorative framing text, not a parenthetical gloss, for every “Sündenbock” occurrence — treat this as a structural teaching-material requirement, per
06_linguistic_gap_analysis.md§5–6. - Fix and lock three verbatim cross-document phrases now, before Phase 2 begins: the four-times-repeated “be holy” refrain, the Leviticus 19:18 love-neighbor command (must match this pipeline’s Matthew 22:39 / Romans 13:9 / Galatians 5:14 renderings exactly), and the Leviticus 17:11 life-in-the-blood rationale.
- Brief every reviewer on the “das tausendjährige Reich” / “Jom Kippur” class of live historical-political collision risk before Phase 2 launch, distinct from and in addition to standard doctrinal review training.
- Load
assets/translation_memory.json(Leviticus) andanalysis/12_ai_translation_requirements.mdtogether for every Phase 2 segment; neither is sufficient alone given how many Leviticus terms require both fixed-string enforcement AND structural framing guidance beyond what a glossary entry can carry.
Full detail: 04_comparative_theology.md (cross-tradition analysis), 06_linguistic_gap_analysis.md (vocabulary gap strategy), 07_semantic_analysis.md (verse-by-verse Hebrew original-language study), 08_core_glossary.md (term register), 11_doctrine_analysis.md (full doctrine matrix and chapter coverage), assets/doctrine_risk_registry.json, assets/bible_term_registry.json, assets/translation_memory.json.