Executive Summary: Psalms Spanish Language Package

Why it matters

Psalms is the most-quoted Old Testament book in the New Testament and the most devotionally used book in the Bible — Psalm 23 alone is likely the single most memorized passage in the Spanish-speaking Christian world, across Catholic and Protestant traditions alike. That popularity is exactly why the translation stakes are high: familiar words (“pastor,” “misericordia,” “Señor,” “refugio,” “confesión”) already carry strong, sometimes competing, meanings from Hispanic folk-Catholic devotional culture, Protestant/Evangelical usage, and — in the case of the divine name — a live contemporary religious-movement collision (Jehovah’s Witnesses). This package extends the Romans baseline Language Package to cover all 150 psalms without contradicting a single one of its existing conventions, while resolving a genuinely new class of terminology decisions Romans never had to face, chief among them how to render the Tetragrammaton itself.

Key findings

• 32 doctrines mapped across all five Books of the Psalter (1–150), every chapter reviewed and accounted for — either as a doctrine anchor or explicitly logged as reviewed with no new risk. Coverage is complete; nothing was silently omitted.
• 9 Critical-risk and 10 High-risk doctrines (19 total) require mandatory human theologian review — up from the Romans baseline’s 8 Critical/13 High because Psalms introduces its own new fault lines (the divine name, the Two-Lord Oracle of Psalm 110, Sheol, direct confession) on top of every Christological doctrine Romans already flagged.
• At the term level, the glossary logs 12 Critical-risk and 12 High-risk terms (24 total) requiring theologian-level enforcement, alongside 12 Medium and 4 Low-risk terms — a larger Critical/High proportion than Romans, reflecting how densely the Psalter concentrates messianic, Christological, and covenant-name vocabulary into short, highly memorized units.
• The single highest-priority open decision is the rendering of YHWH itself (600+ occurrences): this package recommends small-caps “SEÑOR” for expository text over the traditional Reina-Valera “Jehová,” to avoid a live collision with the Jehovah’s Witnesses’ non-Trinitarian movement — and flags this for client/theological board sign-off before Phase 2 begins.
• The core passage, Psalm 23:1-6, alone touches five separate Critical/High risk terms (YHWH, pastor, alma/nephesh, justicia, chesed/misericordia), making it simultaneously the curriculum’s theological anchor and its single densest concentration of translation risk.

Risks

• YHWH mis-rendering — defaulting to “Jehová” risks a live syncretism/confusion collision with Jehovah’s Witnesses; defaulting to plain “Señor” erases the Tetragrammaton’s covenant-name distinctiveness and, at Psalm 110:1, would silently destroy the New Testament’s own argument for Christ’s deity.
• Chesed flattened to pity — bare “misericordia” without the “amor fiel de pacto” gloss loses hesed’s covenant-loyalty core and risks collision with the popular “Divina Misericordia” devotional movement.
• Refuge language absorbed into Marian devotion — “refugio”/“amparo” are live, specific Catholic titles for the Virgin Mary; without disciplined referent-control, God’s own refuge doctrine can be silently read through that devotional lens.
• Confession silently sacramentalized — “confesión” defaults culturally to the Catholic sacrament; Psalm 32/51’s direct-to-God model needs explicit protection.
• Justicia register collapse — this curriculum is the first to place Romans’ forensic “justicia” and Psalms’ ethical-pathway and royal-governance “justicia” side by side for the same learners, multiplying a risk the Romans baseline only had to manage in isolation.
• Softening what Scripture does not soften — imprecatory psalms (109, 137:8-9) and Psalm 88’s unresolved lament are both vulnerable to well-intentioned but doctrinally distorting “smoothing” in devotional paraphrase.

Opportunities

• Shared devotional strength, not just risk: “el Buen Pastor,” the Reina-Valera Psalm 23 wording, and “Aleluya/Amén” are already common ground across Catholic and Protestant Spanish-speaking audiences — this package leverages that shared affection rather than treating every popular term as purely a hazard.
• Cross-curriculum reinforcement: because this package never contradicts the Romans baseline, learners moving between Romans and Psalms materials will encounter one consistent theological vocabulary, strengthening retention and trust in the material.
• A clean template for future OT curricula: the Hebrew-specific decisions made here (YHWH typography, Sheol transliteration, torah’s delight-register) establish reusable conventions the next Old Testament curriculum in this Language Package family will not need to re-litigate from scratch.

Recommended actions

1. Obtain client/theological board sign-off on the YHWH → SEÑOR (small caps) decision before Phase 2 translation begins — this is the single highest-leverage open item in the entire package.
2. Route all 19 theologian-review doctrines and 24 Critical/High terms through mandatory human theologian review in Phase 2 Step 17, with zero automated-only shortcuts for Psalm 23, 51, 1, 2, and 110.
3. Enforce the ten Psalms-specific mandatory rules in 12_ai_translation_requirements.md (YHWH, Two-Lord Oracle, chesed, Sheol, confession, refuge, shepherd register, torah register, justicia’s three registers, imprecatory/unresolved-lament completeness) at the system-prompt level for every Phase 2 segment.
4. Audit Psalm 136 and Psalm 110:1 renderings for internal consistency as a standing Phase 2 QA checkpoint, given their unique repetition- and distinction-dependent doctrinal payloads.
5. Brief native-speaker reviewers explicitly on the Marian/refuge and sacramental/confession collision risks, since these are cultural-fluency judgment calls that automated validation alone cannot catch.