Executive Summary: Titus (English → Ndebele)

Why it matters: Titus concentrates more Critical-risk doctrine per verse than almost any other NT letter — the deity of Christ (2:13), regeneration by the Spirit (3:5), and salvation by grace apart from works (3:3-7) all converge in eight verses that form this curriculum’s core passage. Ndebele’s traditional religious structure — uNkulunkulu approached only through amadlozi (ancestral spirits) — is the same mediated-access risk the Romans baseline already documents, but Titus adds three new flashpoints unique to this letter: a Greek grammatical construction naming Jesus as God outright, a “new birth” concept with no native lexical equivalent, and church-office vocabulary (elder, overseer, master) that collides head-on with customary Ndebele authority structures.

Key findings:

• 15 doctrines identified across the full book (Titus 1:1–3:15, no chapter skipped); 4 rated Critical, 7 rated High — 11 of 15 doctrines require mandatory human theologian review.
• 32 glossary terms are tagged Critical or High risk (11 Critical, 21 High) across the translation memory, more than double the number of new terms introduced by Romans at a comparable analysis stage, reflecting Titus’s doctrinal density despite its short length.
• The single highest-stakes rendering decision in the entire package is Titus 2:13’s Granville Sharp construction (“our great God and Savior Jesus Christ”), which must use Ndebele apposition syntax to avoid a two-persons misreading — this has no precedent requirement in the Romans baseline.
• Regeneration (παλιγγενεσία, Titus 3:5) is a genuine lexical gap: Ndebele has no native word for a one-time, non-cyclical spiritual “new birth” distinct from literal birth, reincarnation-adjacent concepts, or joining the amadlozi. The proposed coinage “ukuzalwa kutsha” requires sustained teaching-note support, not a lexical fix alone.
• “Elder” (πρεσβύτερος) and “master” (δεσπότης) each collide with existing, positively-loaded Ndebele vocabulary — customary clan eldership (abadala) and, if mishandled, the reserved title iNkosi — requiring compound-qualifier and absolute-prohibition safeguards respectively.

Risks:

• Using bare “umdala” instead of the mandatory compound “umdala webandla” would silently import customary lineage-based or ancestral-consultation authority into the biblical elder office.
• A single lexical slip rendering “abanumzana” (household master, 2:9) as “iNkosi” would breach the Romans baseline’s Critical reservation of that title for Christ alone.
• Inconsistent rendering of “umsindisi” (Savior) across its six occurrences (shared by Father and Son) would fracture Paul’s deliberate shared-identity argument without any single verse-level error being individually obvious.
• Conflating “ukuzalwa kutsha” (regeneration) with “ukuvuka kwabafileyo” (resurrection) or with amadlozi-joining would collapse two distinct, non-interchangeable doctrines into one.
• Mishandling Titus 3:9’s rejection of “genealogies” risks either offending Ndebele clan/ancestry identity or under-translating Paul’s actual, narrower target (lineage as spiritual-authority claim).

Opportunities:

• Ndebele kinship vocabulary (uBaba, ukutholwa njengomntwana, and the new “indlalifa,” heir) gives Titus 3:7’s heirship language strong, positive cultural resonance when taught alongside the baseline’s adoption doctrine.
• The letter’s household-code structure (2:1-10) maps naturally onto Ndebele family and household values, provided each customary-authority term is explicitly fenced per the forbidden-substitution list.
• Titus’s “sound doctrine” health metaphor (imfundiso ephilileyo) offers a vivid, teachable image once introduced with a dedicated explanatory note at its first occurrence (1:9).

Recommended actions:

1. Carry forward all 66 new Titus terms and 19 reused baseline terms into Phase 2 translation_memory.json exactly as recorded in this package, with no ad hoc substitutions permitted.
2. Mandate native-speaker back-translation testing specifically for the Titus 2:13 apposition rendering before any Phase 2 segment using it is finalized.
3. Route all 11 Critical/High doctrines (per assets/doctrine_risk_registry.json) through human theologian review; route the 3 Medium doctrines to native speaker review; the 1 Low doctrine may proceed on automated review only.
4. Apply the extended forbidden-substitution list in analysis/12_ai_translation_requirements.md at every Phase 2 pre-flight check, with particular vigilance on the Savior-title consistency and regeneration/resurrection distinction checks.