1 Chronicles — portuguese
TRI knowledge bundle for 1 Chronicles (portuguese).
Executive Summary
Executive Summary: 1 Chronicles → Portuguese Language Package
Why it matters
1 Chronicles extends the Romans Language Package into Old Testament covenant history, anchored in the core passage 1 Chronicles 17:1–15 — the reaffirmation of the Davidic covenant. This book carries the single highest-stakes new doctrinal collision in the entire pipeline to date: 1 Chronicles 10:13 names consulting a medium as the covenant treason that cost Saul the kingdom, directly confronting mainstream Kardecist Spiritist mediunidade, a mainstream and organized practice among tens of millions of Brazilians. Getting this book’s translation and doctrinal framing right is not a peripheral concern — it is a direct engagement with the destination culture’s dominant non-Christian religious framework, extending the same Kardecism-aware rigor the baseline Romans package established.
Key findings
- 71 total glossary terms now govern Phase 2 translation of this curriculum: 14 inherited exactly from the baseline Romans
translation_memory.json(e.g., Deus, Pai, aliança, Messias, santos) and 57 newly introduced by this book’s full-book analysis (chs. 1–29). - Of the 57 new terms, 5 are Critical risk (house/casa’s triple wordplay, the covenantal father/son pairing, “forever”/eternal throne, médium/necromante, Satanás), 13 are High risk, 26 are Medium risk, and 13 are Low risk — combined with the 14 inherited terms (4 Critical, 5 High, 2 Medium, 3 Low), the full glossary carries 9 Critical and 18 High risk terms requiring absolute or near-absolute enforcement in Phase 2.
- The extended
doctrine_risk_registry.jsondocuments 22 total doctrines across the five curriculum themes: 5 Critical, 7 High, 8 Medium, 2 Low — 12 doctrines require mandatory human theologian review, 8 require native speaker review, and 2 are automated-review-sufficient. - All 29 chapters of 1 Chronicles were reviewed for doctrinal load; no chapter was silently omitted. Chapters 4, 7, 8, 19, 20, 23, 24, 26, and 27 are explicitly logged as contributing no doctrinal load beyond doctrines already tabled elsewhere.
- The core passage (17:1–15) alone converges five distinct Critical/High doctrines: the Davidic covenant, covenantal sonship typology, the eternal throne, chesed/covenant loyalty, and prophetic revelation — making it the single densest risk cluster in the book.
Risks
- Critical: “Médium/necromante” (10:13) is the ordinary, respected Portuguese term for a mainstream Kardecist religious practitioner; a softened or merely antiquarian translation would erase the text’s own covenant-treason verdict against a live, organized rival practice.
- Critical: “Casa” (bayit) carries a triple wordplay (palace/temple/dynasty) across 17:1–15 that Portuguese preserves lexically but does not disambiguate automatically — losing referent-tracking here damages the core passage itself.
- Critical: The covenantal “Pai/filho” language of 17:13 sits directly against the baseline’s Critical “Filho de Deus” doctrine; conflating Solomon’s adoptive sonship with Christ’s eternal ontological Sonship would corrupt either this verse’s historical meaning or Christ’s unique Sonship.
- Critical: “Satanás” (21:1) is exposed to depersonalization into “energia negativa” under Brazilian folk-spiritual/New Age discourse, and to inaccurate conflation with unrelated Afro-Brazilian spirit categories.
- Critical: “Para sempre” (‘ad olam) applied to the Davidic throne is the OT seed of Christ’s eternal messianic reign (Luke 1:32–33); softening to a finite-duration phrasing severs this book’s central promise from its NT fulfillment.
- High: “Sacerdote” must never be rendered “padre” (imports anachronistic Roman Catholic parish-clergy categories); “chesed” has no single-word Portuguese equivalent and must use a fixed two-term compound; “peregrinos e forasteiros” (29:15) risks assimilation to Kardecist/Hindu reincarnational readings of human transience.
Opportunities
- Portuguese is lexically well-positioned: no true untranslatable gaps were identified in this book (unlike some other language pairs in this pipeline) — every core Hebrew term has a settled Almeida-tradition equivalent, so the translation task is about doctrinal fencing and mandatory notes, not vocabulary invention.
- The book’s genealogical and Levitical-order material offers a natural, low-risk on-ramp (13 Low-risk new terms, 2 Low-risk doctrines, automated review sufficient) for early Phase 2 batch processing before tackling the core passage and its converged Critical-risk cluster.
- 1 Chronicles’ explicit, textually direct confrontation with mediumship (ch. 10) gives this curriculum unusually strong, built-in apologetic and pastoral value for its primary Brazilian audience — an opportunity the Language Package can lean into rather than soften.
Recommended actions
- Route all segments touching the core passage (17:1–15) and the five doctrines it converges to mandatory human theologian review before Phase 2 sign-off — no automated or native-speaker-only approval path.
- Enforce the Critical forbidden-substitution list (casa referent-tracking, Pai/filho distinction, para sempre, médium/necromante, Satanás) at the validation-gate level in Phase 2, not merely as style guidance.
- Load both the baseline Romans and the 1 Chronicles
translation_memory.jsonfiles together for every Phase 2 session; never process this curriculum against the baseline file alone. - Prioritize theologian review capacity for the 12 Critical/High doctrines flagged for human review before allocating reviewer time to the 8 native-speaker-routed doctrines or the 2 automated-only doctrines.
- Carry forward the “médium/necromante” and “Satanás” fencing notes into any downstream homiletic or small-group discussion materials generated from this Language Package, since the risk here is pastoral and cultural, not merely lexical.
Prepared per PRD Phase 1, Step 11. Cross-references: assets/translation_memory.json, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, analysis/11_doctrine_analysis.md, analysis/12_ai_translation_requirements.md.