Log in

or use your email

Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Download Requirements bundle

Executive Summary

01 Executive Summary — Daniel (English → Mandarin)

Why it matters

Daniel is going into Mandarin on top of an already-proven Romans Language Package — but Daniel is not a low-risk extension. Its core passage (7:9-14) puts the single most theologically loaded phrase in the Old Testament — “one like a son of man” — directly into the hands of Mandarin translators, one keystroke away from a Critical-risk collision with the baseline’s Christological vocabulary. Get the fencing wrong once and a lesson can flatten Christ’s unique divine-human kingship into either a generic human figure or an imperial title (天子) with none of the same meaning. This curriculum requires the tightest cross-chapter lexical discipline of any book processed so far.

Key findings

  • 26 doctrines analyzed, full book, chs. 1–12. No chapter contributes zero load-bearing content; every chapter is confirmed reviewed in 11_doctrine_analysis.md.
  • 6 Critical + 14 High = 20 doctrines require mandatory human theologian review (per doctrine_risk_registry.json); 5 more require native speaker review; only 1 is automated-only.
  • At the term level, the Daniel-specific glossary adds 9 Critical and 18 High risk items on top of the baseline Romans terms already governing this space (per 08_core_glossary.md) — nearly 60 new or extended glossary entries total.
  • Daniel’s risk profile is structurally different from Romans’s. Romans risk clusters around single-term collisions with Buddhist merit-theology and Confucian virtue-ethics. Daniel adds a second, distinct risk class: three-way Christological title collisions (人子 / 神的儿子 / 好像神的儿子) and mandatory cross-chapter consistency (the same Mandarin word must recur identically across chapters for the text’s own internal argument — e.g., 事奉 across chs. 3/6/7, 小角 across chs. 7/8/11, 权柄 across chs. 2/4/7).
  • The Mandate-of-Heaven (天命) family of concepts is the single most pervasive collision risk in this book, touching Sovereignty, Providence, Son of Man, and the Ancient of Days doctrines simultaneously — more diffuse than any single collision risk documented in the Romans baseline.

Risks

  1. Critical — Christological title collapse. 人子 (Daniel 7:13) confused with baseline 神的儿子, or either confused with the pagan king’s 好像神的儿子 (Daniel 3:25), would either erase Christ’s humanity, erase his deity, or falsely imply a Trinitarian claim in a polytheistic king’s mouth.
  2. Critical — Messianic Promise dilution. 受膏者 (Daniel 9:25-26) read as a lesser figure than 基督, or drifting toward 弥勒 (Maitreya), directly undermines the Messianic Promise doctrine inherited from the baseline.
  3. Critical — over-translation of 七十个七. Encoding a single eschatological interpretive scheme into the translation itself would make a doctrinal ruling the source text does not make.
  4. Critical — apocalyptic-genre collapse into cyclical historiography. 治乱循环 (the dynastic order-chaos-order pattern), Buddhist kalpa cycles, and Hindu yuga cycles all pull Daniel’s linear, terminating prophecy toward a repeating-cycle misreading — the single highest-diffusion risk in the book.
  5. High — fatalism drift in Daniel 4. “The Most High gives the kingdom to whomever he wills” is this book’s most fatalism-vulnerable sentence; 天意/命运/天命 substitution would invert the chapter’s entire polemic against Nebuchadnezzar’s pride.
  6. High — worship-boundary erosion. 跪拜 (coerced idol-prostration, ch. 3) bleeding into 敬拜 (exclusive God-directed worship) would blur the martyrdom stakes that anchor Faithfulness under Persecution.

Opportunities

  • Reuse, don’t reinvent. 19 baseline Romans terms (神, 圣灵, 复活, 基督, 约, 荣耀, 神的国, 耶稣, 神的儿子, 救恩, 恩典, 神的护理, 预言, 先知, 主, 神的大能, 大卫, 父, 以色列) transfer to Daniel with zero new coinage — CUV’s century of settled usage does the heavy lifting.
  • The Old Testament wisdom-versus-divination polemic (chs. 2, 4, 5) is a strong evangelistic bridge for a Mandarin audience saturated with folk fortune-telling practice (占卜, 算卦, 算命先生) — the text itself, not just the translation, makes the apologetic case.
  • Daniel 9’s confession/prayer pattern maps unusually closely onto existing Jewish and even some Islamic ritual-prayer forms (per 04_comparative_theology.md), offering a strong comparative-teaching anchor without doctrinal compromise.
  • The book’s own internal cross-referencing (小角 across three chapters, 事奉 across three chapters) gives Phase 2 QA a built-in self-check: if the same term isn’t identical across the flagged chapters, that is itself a reliable, automatable error signal.
  1. Merge assets/translation_memory.json (Daniel) with the baseline Romans file before any Phase 2 run — never process Daniel segments against the Daniel file alone.
  2. Add a mandatory cross-chapter consistency validation pass (documented in 12_ai_translation_requirements.md) checking 事奉, 小角/角, 权柄, 永不败坏的国, and 那行毁坏可憎的 after all twelve chapters are translated, before Doctrinal Fidelity Review.
  3. Route all 20 theologian-review doctrines and every occurrence of the 9 Critical terms through human theologian review with zero exceptions — do not allow automated approval even when a segment “looks routine” (court-narrative chapters 1, 2, 5, 6 still carry Critical-tier vocabulary in places).
  4. Require the mandatory disambiguation note on every occurrence (not just non-obvious ones) for the six highest-collision-density terms: 人子, 好像神的儿子, 圣神的灵, 受膏者, 至高者的圣民, 七十个七.
  5. Brief native-speaker reviewers explicitly on the 天命/天意/命运 family before they review any Daniel 4, 7, or Sovereignty-doctrine segment — this is the single most pervasive, and most easily missed, collision risk in the curriculum.

End of 01_executive_summary.md.

Library content is free and openly licensed under CC BY-NC-SA 4.0 — share and adapt it for non-commercial use, with attribution to tri-bible.ai.

Give feedback

How would you rate this page?

0 / 500 words