Executive Summary: Joshua (English → Spanish)

Why it matters

Joshua adds a Hebrew-Vorlage/Septuagint layer to a Language Package previously built entirely on the Greek New Testament (Romans). It introduces the divine covenant name (YHWH → “Jehová”), the conquest’s most theologically loaded single term (cherem), a book-length land-inheritance vocabulary, and a proper name (Josué) that shares a root with “Jesús” but must never be confused with it. Translated carelessly, this book risks either flattening its severest claims (holy war, exclusive worship) into safe generalities, or letting its Old Testament vocabulary bleed into — and corrupt — the New Testament vocabulary the baseline Romans package already fixed for this destination language.

Key findings

• 16 doctrines tracked (7 curriculum-designated + 9 additional load-bearing doctrines surfaced across the full book): 5 Critical, 6 High, 4 Medium, 1 Low. 11 of 16 require human theologian review; 4 require native speaker review; 1 is automated-only.
• 69 total glossary terms now govern Phase 2 translation for this curriculum: 18 terms inherited exactly from the Romans baseline (reactivated with Joshua-specific cross-reference risk) plus 51 new terms this book introduces. Combined Critical+High term count requiring theologian-level enforcement: 27 (5 Critical + 22 High across the merged inherited-and-new term set).
• The core passage, Joshua 24:14-15, is the single highest concentration point of simultaneous lexical risk in the entire curriculum: the Jehová/Señor boundary, the Dios/dioses capitalization boundary, the escoger/elección complementarity question, and the exclusive-allegiance sense of “servir” all converge in two verses.
• Full-book coverage confirms every chapter contributes to at least one tracked doctrine except chs. 12 and 15-19, which are explicitly reviewed and noted as reinforcing already-registered vocabulary (heredad, límite/territorio, echar suertes) rather than introducing new terms.

Risks

• Cherem (Critical): the highest-stakes single term in the book. Risk runs in two directions at once — softening it into ordinary war vocabulary erases its judicial/consecratory character, while leaving it unexplained risks being read as a license for indiscriminate or ethnically-targeted violence, a live sensitivity given Latin America’s colonial-conquest history.
• Divine name collapse (Critical): any segment that renders YHWH as “Señor” — or vice versa, renders a New Testament κύριος-Christ reference as “Jehová” — silently erases the distinction this Language Package depends on between the Old Testament covenant name and the New Testament lordship confession (Romans 10:9).
• Rest/reposo drift (Critical): Spanish offers several fluent near-synonyms (“descanso,” “tranquilidad”) that would each read naturally in isolation but would sever the deliberate Hebrew→LXX→Hebrews 3-4 lexical chain this term exists to preserve for a future curriculum.
• Suerte fatalism collision (High): Joshua’s lot-casting narrative reactivates a word the baseline already fenced off for “providence” and “election” on fatalism grounds — the same vernacular risk resurfaces here in a new narrative context and could easily be missed without this cross-reference.
• Rahab over-softening (High, risk-inverted): unlike most glossary risks, the danger here is pastoral delicacy weakening “ramera” into a euphemism, which would blunt the doctrine’s central point that grace reaches the most socially disqualified person in Canaan through faith alone.
• Syncretism relevance (High): Joshua 23:12-13’s warning against the remaining nations’ gods becoming a “snare” has a direct, documented contemporary parallel in Espiritismo, Santería, and curanderismo practiced in parts of the Spanish-speaking world; failing to draw this connection explicitly leaves the warning inert as ancient history only.

Opportunities

• Joshua 24:14-15 as core passage gives this curriculum a natural, high-impact teaching climax: “escoged hoy a quién sirváis” directly confronts syncretistic religious layering still practiced in parts of the destination culture, making the ancient text immediately pastorally relevant rather than merely historical.
• The reposo (rest) lexical chain, if disciplined now, sets up a future Hebrews 3-4 curriculum for immediate cross-recognition by returning Spanish-speaking learners — a forward-compounding asset if consistency is maintained.
• Rahab’s inclusion narrative offers an unusually vivid, concrete on-ramp to the baseline’s faith doctrine for learners with thin Pauline/epistolary exposure, since it is narrative rather than argumentative.
• The Jehová/Señor and Dios/dioses distinctions, properly taught, give this curriculum a built-in teaching moment about the seriousness of Bible-translation tradition itself — useful catechetical content beyond the immediate doctrinal point.

Recommended actions

1. Route every occurrence of cherem, the divine name, the Shechem covenant-renewal speech (24:1-27), and the commander of the LORD’s army (5:13-15) through mandatory human theologian review before Phase 2 finalization — no exceptions.
2. Implement automated hard-validation passes (not just glossary reference) for: Jehová/Señor substitution, Dios/dioses capitalization in Joshua 22-24, “reposo” synonym drift, “arca del pacto” vs. “arca de la alianza,” and “suerte” appearing outside the fixed idiom “echar suertes.”
3. Issue explicit instructions to Phase 2 workers and downstream teaching-material authors against euphemistic softening of “ramera,” paralleling the existing baseline instruction never to soften “pecado” to “falta.”
4. Require every cherem occurrence and every application of the Joshua 23:12-13 syncretism warning to carry a mandatory teaching note (Genesis 15:16/Leviticus 18:24-25 for cherem; explicit contemporary Espiritismo/Santería/curanderismo reference for the syncretism warning) rather than leaving either as unexplained text.
5. Flag the “reposo” and “Josué/Jesús” consistency requirements to future Language Package maintainers building a Hebrews-based curriculum, since both decisions made now have direct forward dependencies outside this curriculum’s own scope.

---

This summary is fully consistent with assets/doctrine_risk_registry.json, assets/bible_term_registry.json, assets/translation_memory.json, analysis/08_core_glossary.md, analysis/11_doctrine_analysis.md, and analysis/12_ai_translation_requirements.md. No finding here overrides the baseline Romans Language Package; all baseline rulings remain fully in force.