Titus — vietnamese
TRI knowledge bundle for Titus (vietnamese).
Executive Summary
01 Executive Summary — Titus (English → Vietnamese)
Why it matters
Titus packs an unusually dense concentration of Critical-tier doctrine into a short, practical letter — and does so in a destination language whose dominant cultural traditions (Mahayana Buddhism, Confucian ethics, ancestor veneration) offer false-friend vocabulary for nearly every one of them. The core passage (Titus 2:11–3:8) alone contains all 3 Critical-risk doctrines identified for the whole book. Getting this letter’s vocabulary right — and fencing it with the required teaching notes — is the difference between Vietnamese readers hearing the gospel of grace and hearing a repackaged version of merit-accumulation or cyclical rebirth.
Key findings
- 21 doctrines mapped across all 3 chapters (full-book coverage confirmed, no verse range silently omitted): 3 Critical, 9 High, 6 Medium, 3 Low.
- 115 terms now tracked in the Titus-extended
translation_memory.json: 19 inherited unchanged from the Romans baseline, 96 newly introduced by Titus. - 26 terms carry Critical or High doctrine-risk requiring mandatory human theologian review at every occurrence: 9 Critical (christ, savior, good_works, regeneration, works_of_righteousness, plus baseline-inherited salvation, holy_spirit, god, jesus) and 17 High (epiphany, training, godliness, redeem, submit, servant, heir, mercy, elder, overseer, sound_doctrine, love_agape, divisive_person, plus baseline-inherited grace, righteousness, justification, father).
- 12 of the 21 doctrines require mandatory human theologian review; 6 require native speaker review; 3 are automated-review-only (matching
doctrine_risk_registry.json’s risk_summary exactly). - One term — παλιγγενεσία (“regeneration,” rendered sự sinh lại, Titus 3:5) — is flagged as the single greatest syncretism risk in the entire curriculum, because its literal “again-birth” sense superficially parallels tái sinh, a live term for Buddhist rebirth within saṃsāra.
- One grammatical construction — Titus 2:13’s “our great God and Savior Jesus Christ” — carries the letter’s clearest deity-of-Christ argument and depends on Vietnamese sentence structure preserving a single-referent reading that Greek grammar (Sharp’s rule) guarantees but Vietnamese syntax does not automatically preserve.
Risks
- Regeneration ↔ rebirth collision (Critical). Sự sinh lại (3:5) must never be rendered tái sinh/đầu thai/luân hồi. This is the highest-stakes single substitution risk in the whole Language Package to date.
- Good works ↔ merit accumulation collision (Critical). Việc lành (2:14; 3:8, etc.) sits inside the same “việc” root as ἔργα ἐν δικαιοσύνῃ (3:5, explicitly excluded from salvation) — readers can collapse Paul’s two directions (works commended as fruit vs. works excluded as ground) into one undifferentiated idea unless every occurrence is fenced.
- Deity-of-Christ grammar loss (Critical). Titus 2:13 and 3:4/3:6’s dual application of Cứu Chúa to Father and Son could be misread as naming two figures rather than affirming Christ’s full deity.
- Elder/overseer institutional collision (High). Giám mục imports Vietnamese Roman Catholic diocesan-bishop expectations; trưởng lão imports Confucian seniority-by-age authority — both distort a qualification-based congregational office.
- Submission-to-authority hierarchy collision (High). Vâng phục risks being absorbed into Confucian tam cương’s absolute, identity-defining hierarchy rather than Titus’s voluntary, gospel-motivated, provisional framing.
- Sound doctrine genericization (High). Đạo lành risks being heard as “one wholesome moral path among many” given the proverbial “đạo nào cũng dạy làm lành.”
- Christian love collision (High). Bare ái carries Buddhist taṇhā/craving connotations opposite in direction to commanded, cultivated ἀγάπη.
Opportunities
- A century of settled Vietnamese Protestant Bible vocabulary (ân điển, sự cứu rỗi, Đức Chúa Trời, Đức Thánh Linh) transfers into Titus without modification, giving translators a strong, non-ambiguous foundation for roughly one-sixth of the book’s load-bearing terms.
- Titus’s own internal structure — three parallel “appearing” statements (2:11 grace, 2:13 glory, 3:4 kindness) and the paired 3:5/2:14+3:8 grace-works statements — gives Phase 2 reviewers a built-in cross-check: each occurrence can be validated against its structural sibling for consistency.
- The letter’s practical, household-and-leadership focus (elders, submission, family roles) creates strong teaching opportunities to positively contrast grace-grounded identity with — rather than simply warn against — Confucian filial/hierarchical categories that Vietnamese readers already deeply understand.
- Vietnam’s living tradition of legend about deified ancestors and folk heroes (e.g., Thánh Trần) offers a ready-made, respectful illustrative analogy for explaining Paul’s rejection of “myths” (1:14; 3:9) without requiring translators to invent a foreign frame of reference.
Recommended actions
- Load the Titus-extended
translation_memory.json,bible_term_registry.json, anddoctrine_risk_registry.json— never the Romans-only baseline alone — before any Phase 2 Titus segment processing. - Route all 12 Critical/High-risk doctrines and all 26 Critical/High-risk terms to mandatory human theologian review; do not permit automated-only approval for any occurrence of sự sinh lại, Cứu Chúa, việc lành, or những việc công bình chúng ta đã làm.
- Enforce the mandatory translator-note requirement (every occurrence, not first-occurrence-only) for the five highest-priority fenced terms: regeneration, savior/deity-of-Christ grammar, good works vs. works-of-righteousness, sound doctrine, and elder/overseer.
- Carry the updated
12_ai_translation_requirements.md(Titus extension) into every Phase 2 worker’s system prompt alongside the Romans baseline prompt, not as a replacement for it. - Prioritize back-translation and reviewer capacity toward Titus 2:11–3:8, which contains 5 of the 21 doctrines at their densest concentration and all 3 Critical-tier doctrines in the book.
This summary is consistent with, and does not alter, the risk tiers fixed in doctrine_risk_registry.json and the term-level detail recorded in assets/translation_memory.json and assets/bible_term_registry.json.