Executive Summary — Nehemiah (English → Spanish)

Why it matters

This curriculum brings Nehemiah — a post-exilic Hebrew narrative, not a New Testament epistle — into a Language Package library anchored by Romans. That genre shift, plus Old Testament content the baseline never had to navigate (the divine name YHWH, corporate confession without priestly absolution, tithing, Sabbath, ritual purification, ethnic separation, and a joy-as-fortress doctrine), introduces translation risks structurally different from — and in several cases more severe than — anything in the Romans baseline. Getting these right determines whether Spanish-speaking learners encounter Nehemiah’s actual theology or an unintentionally syncretized, denominationally miscoded, or prosperity-gospel-flattened substitute.

Key findings

• Full-book coverage complete. All 13 chapters reviewed; chapters 3 and 7 (genealogical/administrative content) explicitly confirmed as reviewed with minimal new theological vocabulary, not silently skipped.
• 20 curriculum doctrines identified (doctrine_risk_registry.json / 11_doctrine_analysis.md): 4 Critical, 8 High, 6 Medium, 2 Low — 12 of 20 doctrines (60%) require mandatory human theologian review.
• 56 total glossary terms in force for this curriculum: 10 inherited exactly from the Romans baseline (1 Critical, 3 High, 2 Medium, 4 Low) plus 46 new Nehemiah-specific terms (4 Critical, 11 High, 16 Medium, 15 Low). Combined: 5 Critical, 14 High, 18 Medium, 19 Low — 19 of 56 terms (34%) require mandatory human theologian review at every occurrence.
• The single most consequential decision in the whole package: rejecting Reina-Valera’s traditional “Jehová” for the Tetragrammaton in favor of “el SEÑOR,” because “Jehová” now reads, to virtually every Spanish-speaking audience, as the household name of Testigos de Jehová (Jehovah’s Witnesses) — a group whose Christology directly contradicts this library’s Romans-anchored doctrine. This departs from the baseline’s own anchor register and is disclosed and defended explicitly.
• The curriculum’s doctrinal centerpiece — “el gozo del SEÑOR es vuestra fortaleza” (Nehemiah 8:10) — is a structural lexical gap: Spanish has no single word combining “joy” and “fortress,” and the path of least resistance (“felicidad,” bare “fuerza”) drains the verse into exactly the prosperity-triumphalism this passage’s actual grief-to-resolve context forbids.

Risks

• Sacramental collision: “confesar” (Neh 1:6; 9:2-3) defaults, for Catholic-heritage learners, to private priest-mediated absolution; Nehemiah’s confession is corporate, public, and unmediated.
• Cross-curriculum doctrinal bleed: “justicia/justo” in Nehemiah 9 (God’s covenant-historical righteousness) uses the identical Spanish word as Romans’ Critical-risk imputed righteousness — learners moving between curricula are the specific population at risk of conflation.
• Idiomatic collision unique to this language: “la mano de Dios” (Neh 2:8, 2:18) risks being heard through Diego Maradona’s famous 1986 “Hand of God” secular sporting idiom rather than reverent providence.
• Prosperity-gospel distortion: “diezmo” (Neh 10, 12, 13) is highly vulnerable to Latin American “siembra y cosecha” transactional teaching.
• Folk-ritual collision: “purificar/purificaron” (Neh 12-13) risks assimilation into curanderismo/Afro-diasporic “limpias” cleansing practice in parts of Latin America.
• Internal library tension: Nehemiah 13’s “se separaron de los extranjeros” stands in real doctrinal tension with this library’s own Romans-anchored Jew-Gentile unity teaching and carries added weight given regional racial-hierarchy sensitivities.
• Denominational proof-texting: Sabbath material (Neh 9, 10, 13) is live territory for Sabbatarian (Adventist/Pentecostal-splinter) argumentation.

Opportunities

• Genuine cross-tradition convergence points exist and should be leveraged pastorally: Jewish liturgical practice (Vidui, Yom Kippur, Sukkot, Shabbat) shares deeper authentic continuity with several Nehemiah doctrines than any Christian tradition’s later development, offering rich, honest comparative teaching material rather than a risk to manage.
• Catholic and Jewish practice both independently avoid vocalizing the Tetragrammaton (favoring “el Señor”/“Adonai”/“HaShem” respectively), giving this curriculum’s “el SEÑOR” convention unusually broad cross-tradition support rather than appearing as an isolated Protestant innovation.
• The Word-doctrine’s keystone clauses (8:8, 8:12) and the joy-strength doctrine (8:10) are teachable as a matched pair — comprehension produces durable, fortress-strength joy — giving the curriculum a strong, memorable, single throughline for catechesis across all 13 chapters.

Recommended actions

1. Merge assets/translation_memory.json (Nehemiah) and the extended bible_term_registry.json/doctrine_risk_registry.json into Phase 2 tooling as mandatory pre-flight loads alongside the Romans baseline, never as replacements for it.
2. Enforce automated pre-scan rejection of “Jehová” on every draft segment before human review queuing (highest-frequency, single-point-of-failure risk).
3. Route all 12 Critical/High doctrines and all 19 Critical/High terms through mandatory human theologian review per the escalation rules in 12_ai_translation_requirements.md; do not permit native-speaker-only sign-off on any of these.
4. Attach the standing disambiguation notes (confession, tithing, purification, separation, cross-curriculum righteousness, “la mano de Dios”) at every occurrence, not merely at first mention, since Phase 2 segments may be reviewed out of full-chapter sequence.
5. Proceed to Phase 2 segment translation only after confirming all four artifacts (this summary, the doctrine registry, the term registry, and the AI requirements doc) are loaded together as a single Nehemiah Language Package unit.