01 — Executive Summary: 1 Chronicles (English–Mandarin)

Why it matters

1 Chronicles reaffirms the Davidic Covenant (17:1–15) — the theological hinge connecting Israel’s genealogical continuity, Levitical worship order, and temple preparation to the New Testament’s fulfillment in Christ’s eternal Sonship, resurrection, and everlasting kingdom. Translating it into Mandarin surfaces a new class of risk the Romans baseline never had to handle: the covenant name of God (יהוה/耶和华), untranslatable Hebrew wordplay (בַּיִת, “house,” meaning temple, dynasty, and palace at once), and a head-on collision with the Mandate of Heaven (天命) — the single most deeply embedded indigenous framework for royal legitimacy in Chinese thought, which is the exact inverse of what 1 Chronicles 17 claims about God’s unconditional, non-transferable promise to David’s line.

Key findings

• 24 distinct doctrines identified across full-book coverage (chs. 1–29); 8 Critical + 12 High = 20 require mandatory human theologian review, 3 require native speaker review, 2 are automated-only.
• 70 total glossary terms carried into Phase 2 translation memory: 19 inherited exactly from the Romans baseline (神, 约, 拣选, 圣洁, 成圣, 恩典, 基督, 神的儿子, 父, 律法, 罪, 主, etc.) plus 51 new terms required by 1 Chronicles’ Hebrew register, of which 8 are Critical-tier and 15 are High-tier.
• The core passage (17:1–15) alone concentrates 6 of the book’s 8 Critical-risk doctrines: the Davidic Covenant itself, the God’s-house/David’s-house wordplay, Solomon’s covenantal sonship (vs. Christ’s eternal Sonship), the eternal throne promise, God’s steadfast covenant love (chesed), and the inspiration of Nathan’s oracle.
• Three “crowded semantic neighborhoods” recur across the whole book and must be fenced repeatedly, not once: (1) Mandate of Heaven (天命) vs. the unconditional Davidic covenant; (2) the karma/merit complex (报应, 功德, 超度) vs. covenant discipline, atonement, and freewill giving; (3) ancestor veneration (祭祖, 神主牌) vs. genealogical record-keeping and the ark of the covenant.

Risks

• Highest risk: collapsing 耶和华 (YHWH) into generic 神 or into the Romans-reserved NT term 主 — this erases the covenant-name theology that is the entire chapter’s rhetorical engine (17:2 vs. 17:4).
• Second highest risk: the lost בַּיִת (bayit) wordplay — Mandarin must split “house” into 殿/圣殿 (temple) and 家/家室 (dynasty), silently destroying the Hebrew pun that IS the passage’s argument unless a mandatory translator’s note is attached at every occurrence.
• Doctrinal self-collision risk: 儿子 (Solomon’s sonship, 17:13) and 受膏/受膏者 (David’s and Solomon’s anointing, 11:3/29:22) sit dangerously close to the Romans baseline’s reserved Critical terms 神的儿子 and 基督/弥赛亚 — every occurrence requires a mandatory distinguishing note or readers may infer Solomon shares Christ’s unique status.
• Highest pastoral-sensitivity risk: 1 Chronicles 10:13–14’s condemnation of consulting a medium (交鬼的) intersects live mediumship practices (扶乩, 问米) in many Mandarin-speaking readers’ own families; mishandled teaching risks alienation rather than instruction.
• Cumulative exposure risk: genealogical list vocabulary (chs. 1–9, roughly a third of the book) carries a diffuse but real risk of reading as ancestor-veneration record-keeping (族谱/宗谱) rather than covenant-continuity history.

Opportunities

• 1 Chronicles 17’s own internal argument (David wants to build God a house; God will build David a house instead) is a built-in teaching tool for explaining, rather than merely warning against, the Mandate-of-Heaven contrast — the text does the theological work if the wordplay note is restored.
• Saul’s death narrative (ch. 10) offers Scripture’s own explicit contrast between legitimate inquiry (求问) and illegitimate mediumship (交鬼的), giving translators and teachers a native biblical anchor rather than an imported polemic.
• The Chronicler’s distinctive redaction at 17:14 and 29:23 (“my house and my kingdom,” not “your house and your kingdom”) gives a ready-made bridge to the Romans baseline’s reserved 神的国 (kingdom of God), letting this curriculum extend the Romans Language Package’s existing kingdom theology rather than introduce a competing one.
• Reuse of 19 Romans baseline terms exactly (神, 约, 拣选, 恩典, 基督, 神的儿子, etc.) means most of the heaviest doctrinal-fencing work is already done; this curriculum’s real labor is concentrated in ~15 new High/Critical terms tightly clustered in chs. 10, 17, 21, 28–29.

Recommended actions

1. Load assets/translation_memory.json, assets/doctrine_risk_registry.json, and analysis/12_ai_translation_requirements.md (this package) together with the Romans baseline equivalents before any Phase 2 segment translation begins — never substitute one set for the other.
2. Route all 20 Critical/High doctrines and their associated Critical/High terms to mandatory human theologian review, with per-occurrence (not per-chapter) flagging for the six highest-risk items: 耶和华 boundary, 家/家室 vs. 殿/圣殿 wordplay, 儿子 (Solomon) vs. 神的儿子, 受膏者 vs. 基督, 赎罪 vs. 超度/功德, and 宝座/耶和华的国 vs. 天命.
3. Deliver the mediumship-inquiry doctrine (ch. 10) and the genealogical-register doctrine (chs. 1–9) with explicit pastoral framing guidance, not only doctrinal-accuracy guidance, given their direct intersection with readers’ living family practices.
4. Consolidate the two grace-vs-merit teaching clusters (ch. 21 atonement; ch. 29 freewill offering) into a single cross-referenced teaching unit rather than isolated footnotes, and likewise consolidate the 恩典/慈爱/爱 and 干犯/罪/报应 vocabulary fences into one early orientation unit, per analysis/06_linguistic_gap_analysis.md §7.
5. Carry all 70 glossary terms (19 inherited + 51 new) forward into Phase 2 without modification; any new term discovered during translation must be added to the 1 Chronicles translation memory (never the Romans baseline file) and flagged for theologian review if Critical or High.

---

This summary synthesizes analysis/04_comparative_theology.md, analysis/06_linguistic_gap_analysis.md, analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, analysis/11_doctrine_analysis.md, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, and assets/translation_memory.json. It does not introduce new doctrinal or terminological content.