Executive Summary: 2 Samuel Portuguese Translation Requirements

Why it matters

2 Samuel 7:1-17 — the Davidic Covenant — is the Old Testament hinge on which the New Testament’s messianic claims turn (Luke 1:32-33; Acts 2:30; Hebrews 1:5). Translating it into Portuguese for a curriculum aimed primarily at Brazilian learners means doing something the existing Romans (New Testament) Language Package never had to do: render the Hebrew covenant name of God, a Hebrew term for covenant loyalty with no Portuguese one-word equivalent, and a royal father-son adoption formula that a careless translation could accidentally turn into a false Trinitarian claim. Brazil’s religious landscape — the world’s largest Kardecist Spiritist population, alongside a Catholic-majority culture and fast-growing Evangelical movements — makes several of this book’s central terms (steadfast love, anointed one, eternal throne, providence) live theological fault lines, not academic footnotes.

Key findings

• This curriculum requires a wholly new Critical-risk system absent from the baseline: the YHWH (“SENHOR”)/Adonai (“Senhor”) divine-name case distinction, needed because 2 Samuel’s Hebrew text — unlike Romans’ Greek text, which uses κύριος uniformly — distinguishes God’s personal covenant name from a generic title on nearly every page.
• חֶסֶד (chesed) has no baseline equivalent and no natural Portuguese one-word match. The standardized coined rendering “amor leal” must appear identically at every occurrence (7:15; 9:1,3,7; 15:21; 22:51) or the doctrine “God’s Steadfast Love despite Human Failure” loses its terminological backbone for the learner.
• “Messias” and “ungido” must be split by capitalization. Every 2 Samuel occurrence of anointing (Saul, David) uses lowercase “ungido”; capitalized “Messias” is reserved exclusively for the fulfilled New Testament figure, converging explicitly only at 22:51/23:1.
• 2 Samuel 7:14’s “father”/“son” language requires the sharpest new guardrail in this package: it must render as lowercase “pai”/“filho,” never the baseline’s capitalized “Pai”/“Filho de Deus,” or a royal-adoption metaphor becomes a false direct christological claim.
• The word “aliança” (covenant) never occurs in the core passage itself — 2 Samuel 7:1-17 implies the covenant; 2 Samuel 23:5 names it explicitly. Every lesson must teach both passages together.
• Full-book coverage (chs. 1-24) surfaces 17 total doctrines extending the 5 named curriculum doctrines, and 65 total glossary terms (23 inherited exactly from the Romans baseline, 42 new to this book).

Risks

• 21 Critical-risk and 18 High-risk terms (39 of 65 total, ~60%) require human theologian-level enforcement in Phase 2 — concentrated overwhelmingly in three convergence passages: 2 Samuel 7:1-17 (the core passage), 22:51-23:5 (the book’s own doctrinal bridge), and 24:1-25 (providence and atonement resolved together).
• 12 of 17 doctrines (Critical: 5, High: 7) require mandatory human theologian review; the remaining 5 (Medium) require native speaker review. No doctrine in this curriculum is automated-review-only.
• The single highest silent-failure risk is anachronistic conflation of Old Testament “justiça” (royal/social governance, 8:15; 22:21,25) with Romans’ forensic soteriological “justiça” — no typographic marker distinguishes the two senses; only a teaching note can, and an inattentive AI pass could import Romans’ sola fide argument backward into David’s song without anyone noticing a lexical error occurred.
• Kardecist Spiritism collision risk recurs across five separate doctrines (Messianic Hope, Steadfast Love, Consequences of Sin, Providence, Inspiration of Revelation) — more doctrines than any other rival framework touches in this book, confirming the baseline’s assessment that this is the defining interpretive risk for the Brazilian destination culture.

Opportunities

• 2 Samuel 9 (David’s chesed to Mephibosheth) offers a built-in, textually native illustration of doctrine #4 (Steadfast Love) — the same term, “amor leal,” models the divine promise at the human level, giving Portuguese-speaking learners a concrete narrative anchor for an otherwise abstract theological term.
• Nathan’s own self-corrected premature opinion (7:3, immediately reversed in 7:4-5) is a ready-made pastoral tool for teaching discernment against Kardecist psicografia claims, without requiring an imported illustration.
• The etymological link between “estabelecer/firme” (ne’eman) and “Amém” — already retained untranslated in the Romans baseline — gives this curriculum a natural teaching bridge connecting Old and New Testament assurance vocabulary.
• Because 21 of this book’s 65 glossary terms are inherited exactly from the Romans baseline, roughly a third of Phase 2 enforcement work reuses infrastructure already validated in production, reducing net new translation-memory risk despite the book’s Old Testament complexity.

Recommended actions

1. Load assets/translation_memory.json (2 Samuel) and assets/bible_term_registry.json (2 Samuel) alongside, never in place of, the Romans baseline files before any Phase 2 segment work begins.
2. Route every segment touching 2 Samuel 7:1-17, 22:51-23:5, or 24:1-25 to human theologian review as a single unit, even when technically sub-segmented, per the doctrine-convergence finding in 11_doctrine_analysis.md.
3. Enforce the Divine Name (SENHOR/Senhor) case rule and the chesed→“amor leal” rule as the two highest-priority automated validation checks for this curriculum, ahead of all other Medium/Low checks, given their volume and doctrinal centrality.
4. Require a mandatory (not optional) translator note at six fixed locations: 7:1-13 (casa wordplay), 7:14 (pai/filho lowercase), 8:15 and 22:21,25 (justiça OT/NT distinction), 12:13-14 (forgiveness/consequence pairing), 22:51/23:1-5 (Messianic convergence), and 24:1 (providence tension with 1 Chronicles 21:1).
5. Proceed to Phase 2 segment translation only after confirming all 65 terms in the 2 Samuel translation memory have been cross-checked against the Romans baseline for non-contradiction, per the completeness mandate already satisfied in Steps 6-9.

---

See analysis/06_linguistic_gap_analysis.md, analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, analysis/11_doctrine_analysis.md, and analysis/04_comparative_theology.md for full supporting detail behind every finding above.