Executive Summary: Joshua → German Translation Requirements

Why it matters

Joshua is the first Old Testament, Hebrew-narrative curriculum built on this pipeline’s German Romans/NT baseline, and it introduces this language’s single most historically fraught translation problem to date: the ban (cherem/der Bann) and the divine-warrior formula (“der HERR kämpfte für Israel”) both sit adjacent to 20th-century German atrocity vocabulary (Vernichtungslager, “Gott mit uns”) in a way with no equivalent severity anywhere in the Romans-through-John baseline. The core passage (Joshua 24:14–15) additionally creates a direct lexical-family collision with this pipeline’s already-fixed Critical/High election doctrine (Erwählung), meaning a careless rendering here could quietly corrupt Reformation-era doctrine already locked in earlier books. Getting this package right protects both the safety of the German-language teaching material and the theological integrity of terms this pipeline has already committed to elsewhere.

Key findings

• Full-book coverage confirmed. All 24 chapters of Joshua are accounted for in the doctrine matrix; chapters introducing no new theological content (ch. 12; chs. 15–19 boundary lists) are explicitly logged as “reviewed — no new doctrine,” never silently omitted.
• 47 new theological terms identified beyond the 10 baseline Romans terms this book reuses exactly (Gott, Bund, Israel, Gesetz, heilig, Sünde, Beschneidung, Herr, Erwählung, Heiden).
• 23 doctrines mapped against the curriculum’s 7 assigned Bible Doctrines, each with German-specific risk notes absent from the Romans baseline.
• The cherem/Bann term is assessed as comparable in severity to this pipeline’s existing Matthew 27:25 (“his blood be on us”) requirement — the highest bar this pipeline has previously set.
• The “wählen vs. erwählen” distinction at Joshua 24:15 is a novel, book-specific safeguard with no precedent need in prior books, protecting the already-fixed Romans/Ephesians election doctrine from an unintended Arminian/decisionist misreading.

Risks

• Term-level: of 47 new Joshua-specific terms, 2 are Critical (der HERR / YHWH’s covenant name; der Bann) and 14 are High — a Critical+High total of 16 terms, each requiring mandatory human theologian review per occurrence.
• Doctrine-level: of 23 Joshua-specific doctrines, 4 are Critical and 10 are High — a Critical+High total of 14 doctrines, all routed to mandatory human theologian review; a further 9 doctrines require native speaker review, and 1 (ch. 12’s summary content) is automated-only.
• Cumulative, not just peak, risk: “der HERR” recurs in some form in essentially every chapter, and “der Bann” recurs across five non-contiguous chapters (6, 7, 8, 10, 11) — Phase 2 workflows must not treat only first occurrences as requiring full mandatory framing.
• Cross-book contamination risk: without the “wählen”/“erwählen” fence, Joshua 24:15 could be mistranslated in a way that reads as a proof-text against the Critical/High election material already fixed in the Romans and Ephesians packages.
• Register-drift risk (non-Critical but pervasive): “Erbe” (inheritance), “das Los” (lot), “die Ruhe” (rest), and “Mut” (courage) are all vulnerable to flattening toward modern secular registers (probate law, gambling, leisure, self-help) that erase their covenant-theological weight across dozens of occurrences.

Opportunities

• Joshua’s land-inheritance vocabulary (Erbe, in Besitz nehmen) offers a natural bridge to reinforce the NT inheritance language already fixed in this pipeline’s Ephesians package (Unterpfand, 1:14), strengthening cross-curriculum theological coherence for German learners moving between Old and New Testament material.
• The Rahab narrative gives this pipeline its first sustained Old Testament case study for the “inclusion of the nations by faith” theme, directly reinforcing (rather than duplicating) the grace-through-faith doctrine already Critical-tier in Ephesians 2:8-10.
• The book’s “Rest” doctrine, carefully framed as a type rather than a synonym, creates a strong teaching on-ramp to the baseline’s Rettung (salvation) doctrine and to Hebrews 3–4, positioning Joshua as a bridge book rather than an isolated OT unit.
• The Berlin Wall–adjacent positive cultural bridge already logged for Ephesians’ “dividing wall” (2:14) suggests German audiences are receptive to concrete historical-architectural typology; Joshua’s Jordan-crossing and memorial-stone material (chs. 3–4) can be taught with similar concrete, non-abstract pedagogy.

Recommended actions

1. Lock the Joshua translation_memory.json (v1) and bible_term_registry.json extensions before any Phase 2 segment processing begins, with special sign-off from a human theologian specifically on the cherem/Bann and divine-warrior-formula entries.
2. Brief every assigned theologian reviewer on the mandatory anti-misapplication framing requirement for cherem and “der HERR kämpfte für Israel” before their first review pass, using the same severity-class instructions already established for Matthew 27:25.
3. Enforce the wählen/erwählen lexical fence programmatically in Phase 2 tooling: any Phase 2 output rendering Joshua 24:15’s “choose” as “erwählen” should hard-fail validation, not merely soft-flag.
4. Never process Joshua 24:14-15 as an isolated segment — Phase 2 chunking must always include 24:2-13 in the same translation and review unit.
5. Carry forward, do not duplicate, the baseline’s Heiden caution — default to “die Völker” for Canaanite/foreign-nation narrative references throughout Joshua, reserving “Heiden” only for deliberate cross-references to the established Jew/Gentile doctrinal pairing.
6. Schedule priority theologian availability for Joshua 24 processing, since three of the book’s four Critical-risk doctrines concentrate inside sixteen verses (24:1–15).

---

Sources: analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, analysis/11_doctrine_analysis.md, analysis/04_comparative_theology.md, analysis/06_linguistic_gap_analysis.md, analysis/05_translation_landscape.md.