Executive Summary — Psalms Language Package (English)

Why it matters

Psalms is the most-read, most-memorized, and most liturgically embedded book in the Bible for English-speaking audiences — and precisely because of that familiarity, it carries the highest risk in this entire pipeline of confident, unexamined misreading. Unlike Romans, where drift comes mainly from doctrinal vocabulary, Psalms adds three new risk classes on top: an invisible typographic convention (LORD/Lord) that decides who a verse is even about, a genuine lexical gap (hesed) with no adequate single English word, and a Hebrew-poetic register whose most-quoted lines (Psalm 23, Psalm 51) are worn smooth by overuse into decorative sentiment. Getting Psalm 23:1-6 — the curriculum’s theological anchor — right requires actively rebuilding meaning readers assume they already have.

Key findings

• 65 terms cataloged in the Psalms bible_term_registry.json: 11 Critical, 23 High, 22 Medium, 9 Low — roughly triple the new-term volume of the Romans baseline, driven by Hebrew poetry’s dense, image-based vocabulary (shepherd, refuge, rock, anoint, rod and staff) layered on top of every baseline term this book reuses.
• 26 doctrines mapped across all 150 psalms: 7 Critical, 10 High, 8 Medium, 1 Low — 17 of 26 doctrines (65%) require mandatory human theologian review, versus 16 of 34 in the Romans baseline, reflecting Psalms’ unusually high concentration of Messianic-prophecy, covenant, and typographic risk in a single book.
• The single highest-priority new risk is the LORD/Lord typographic distinction (small-caps LORD = YHWH; mixed-case Lord = Adonai): it is invisible in speech, easily missed on the page, and is the entire hinge of Psalm 110:1 — the most-quoted Old Testament verse in the New Testament.
• The single highest-priority lexical challenge is hesed (“steadfast love”): no English word captures its fused loyalty + love + mercy + faithfulness sense, and published English Bibles render it at least four different ways, creating real cross-translation confusion for the same underlying concept.
• Two psalms (88 and 89) end without resolution, directly countering contemporary devotional culture’s pull toward tidy endings — a doctrinal feature, not a defect, that this curriculum must protect from being silently smoothed over.

Risks

• Confident misreading, not mere unfamiliarity, dominates this book’s risk profile: “meditate” (opposite of its biblical sense), “fear of the LORD” (terror instead of awe), “wicked”/“blessed” (regional slang and social-media drift), and “Sheol” (risk of collapsing into “hell”) all produce readers who feel certain they understood correctly when they did not.
• Historically sensitive interfaith stakes: Psalms 2, 22, and 110 are the New Testament’s most heavily quoted Messianic proof-texts, and Christian fulfillment readings sit in direct, long-standing tension with Jewish tradition’s own coronation-psalm reading — this must be handled with transparency and respect, not asserted as self-evident.
• Genuine textual uncertainty carries real doctrinal weight: Psalm 22:16’s disputed reading (“pierced” vs. “like a lion”) sits at the intersection of textual criticism and a core Messianic prophecy; overstating certainty or overstating doubt both carry real cost.
• Denominational fault lines multiply beyond Romans’ four: imprecatory-psalm ethics, the Holy Spirit’s Old Testament-era presence vs. New Testament permanent indwelling, Melchizedek priesthood implications, and assurance-of-salvation stakes at Psalm 51:12 all require this curriculum to state its own position transparently rather than assume consensus.

Opportunities

• Psalm 23 and Psalm 51 are already the two most culturally embedded texts in this entire pipeline — an unmatched on-ramp for readers with no church background, provided their familiarity is actively re-engaged rather than coasted on.
• Adoption-awareness culture, contemporary refugee-crisis salience, and renewed interest in mental-health-forward “honest lament” all offer genuine, positive cultural bridges (refuge, shepherd-provision, lament-as-legitimate-prayer) not present at this strength in the Romans baseline.
• The direct bridge points already identified to the Romans baseline (Ps 32:1-2 → Romans 4:7-8; Ps 2:7/110:1 → Romans 1:3-4/8:34; Ps 51:11 → Romans 8; Ps 14:1-3 → Romans 3:10-12) let this curriculum reinforce, rather than duplicate, the pipeline’s existing doctrinal infrastructure.

Recommended actions

1. Enforce the LORD/Lord prose clarification and the fixed “steadfast love” hesed rendering as the two non-negotiable, zero-exception rules for every Phase 2 document, per 12_ai_translation_requirements.md.
2. Route all 17 theologian-review doctrines and their associated Critical/High terms through human theologian review before publication; do not allow native-speaker or automated review to substitute.
3. Preserve Psalm 88 and 89’s unresolved endings verbatim in structure and framing; flag any draft that supplies an artificial resolution for revision.
4. State this curriculum’s own transparent position on imprecatory psalms, Messianic Prophecy vs. Jewish tradition, and assurance-of-salvation-adjacent Psalm 51:12 language in every document that touches them, rather than defaulting to silence or assumed consensus.
5. Carry the assets/translation_memory.json and assets/bible_term_registry.json (Psalms extensions) into Phase 2 unmodified alongside the baseline Romans files; any newly discovered term must be added to the Psalms extension file only, never by altering baseline entries.

---

This summary synthesizes analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, analysis/11_doctrine_analysis.md, analysis/04_comparative_theology.md, analysis/06_linguistic_gap_analysis.md, assets/bible_term_registry.json, and assets/doctrine_risk_registry.json. It does not introduce new doctrinal or terminological findings beyond what those documents establish.