Hebrews → Kannada Language Package: Executive Summary

Why it matters

Hebrews mounts one cumulative argument — Christ’s superiority over angels, Moses, and the Levitical priesthood, culminating in his once-for-all high-priestly sacrifice (core passage, Hebrews 9:11-28) — across all 13 chapters. For a Kannada readership, this argument runs directly through the two most theologically crowded semantic neighborhoods in the entire translation landscape: priesthood/sacrifice vocabulary (colliding with live, currently-practiced Hindu temple and Shakta ritual categories) and rest/perfection/union vocabulary (colliding with moksha, mukti, and the Lingayat Aikya-merger doctrine already fenced off in the Romans baseline). Get either wrong, and Hebrews’ central claim — a unique, finished, unrepeatable atonement — reads instead as one more excellent offering within an ongoing propitiatory economy. This package extends the Romans-baseline Language Package without altering it, giving Phase 2 translators the term-by-term and doctrine-by-doctrine guardrails this book specifically requires.

Key findings

• 27 Hebrews-specific doctrines identified and risk-tiered (10 Critical, 10 High, 6 Medium, 1 Low), all fully consistent with and never contradicting the Romans-baseline doctrine framework.
• 127 terms now populate the Hebrews translation memory: 32 inherited verbatim from the Romans package (10 Critical, 11 High, 7 Medium, 4 Low) plus 95 newly adjudicated Hebrews terms.
• Of the 95 new terms, 13 are Critical, 32 are High, and 8 more sit at the intermediate Medium-High tier (treated as High for review-routing) — meaning 53 of the 95 new terms (56%) require mandatory human theologian review before Phase 2 approval.
• Combined across both inherited and new vocabulary, 74 of the 127 total terms (roughly 58%) carry Critical, High, or Medium-High risk — a notably heavier theologian-review load than a typical epistle, driven by Hebrews’ sustained priestly/sacrificial argument.
• The core passage, Hebrews 9:11-28, is the single densest concentration in the book: 10 of the 27 doctrines either originate or reach their fullest statement within these 18 verses alone.
• All 13 chapters of Hebrews have been reviewed for full-book coverage; no chapter contributes zero new terminology, and every chapter is explicitly logged in the doctrine matrix and linguistic gap analysis even where its doctrinal load is lighter (chs. 4, 13).

Risks

• ಮಹಾಯಾಜಕ (high priest) drifting toward ಪುರೋಹಿತ/ಪುಜಾರಿ would recast Christ as one more temple ritual functionary rather than history’s unique, final priest — the single most consequential single-word failure mode in the book.
• ಪ್ರಾಯಶ್ಚಿತ್ತ (propitiation) used without ಬಲಿ inverts the doctrine entirely: ordinary Kannada usage names self-performed penance, the theological opposite of Hebrews’ God-provided, once-for-all atonement.
• ರಕ್ತ (blood) carries live ritual-collision risk (not merely historical) given Karnataka’s ongoing Shakta and village-goddess blood-offering practice — no safer word exists, so this risk must be managed entirely through mandatory recurring translator notes.
• ವಿಶ್ರಾಂತಿ (rest, chs. 3-4) is the book’s highest identity-dissolution risk, sitting closer to moksha/mukti and Lingayat Aikya-merger language than any other Hebrews term.
• Consistency failures on ಒಂದೇ ಸಲ ಎಲ್ಲಾ ಕಾಲಕ್ಕೂ (once for all), ಒಡಂಬಡಿಕೆಯ ರಕ್ತ (blood of the covenant), and ಶ್ರೇಷ್ಠ (better/superior) would silently dismantle the book’s cumulative rhetorical argument even without introducing any single wrong idea — these require automated lock-step validation, not just correct word choice.
• The four warning/apostasy passages (3:12-14; 6:4-8; 10:26-31; 12:15-17) are simultaneously the most pastorally severe and most interpretively contested material in the book; softening their graphic force for reader comfort is a standing risk flagged for mandatory theologian review at every occurrence.

Opportunities

• Kannada already has an established, non-ambiguous, safe rendering for every one of Hebrews’ highest-stakes baseline terms (ರಕ್ಷಣೆ, ಪುನರುತ್ಥಾನ, ದೇಹಧಾರಣೆ, ದೇವರ ಮಗ) — no lexical gap-filling is needed for the book’s Christological core, only disciplined reuse.
• Hebrews’ “no lasting city… a city that is to come” pilgrim theme (11:10,16; 13:14) offers a natural teaching bridge for readers already familiar with the strangers-and-exiles self-understanding common across Karnataka’s devotional traditions, provided the future, literal, personal-identity-retaining nature of the promised city is taught explicitly against both moksha-release and Aikya-dissolution horizons.
• The book’s own “once for all” argument gives curriculum writers a built-in, repeatable teaching device for distinguishing Christ’s finished sacrifice from any repeated-offering economy — an opportunity to teach the doctrine precisely where the collision risk is highest (blood, sacrifice, propitiation).

Recommended actions

1. Load assets/translation_memory.json (Hebrews) and analysis/12_ai_translation_requirements.md (Hebrews extension) alongside their Romans-baseline counterparts before any Phase 2 session; never load one without the other.
2. Route the entirety of Hebrews 9:11-28 to human theologian review as a single passage-level unit, not per-segment, given its unmatched doctrinal density (10 of 27 doctrines converge there).
3. Configure Phase 2 automated validation to hard-fail on any deviation in the four “lock identical phrase” terms (ಒಂದೇ ಸಲ ಎಲ್ಲಾ ಕಾಲಕ್ಕೂ, ಒಡಂಬಡಿಕೆಯ ರಕ್ತ, ಶ್ರೇಷ್ಠ, ಸಮೀಪಿಸು) before any human review stage, since these are consistency failures an automated check can catch cheaply.
4. Brief theologian reviewers specifically on the ὑπόστασις dual-sense split (1:3 vs. 11:1) and the purification dual-sense split (9:13 vs. 9:14) as known automated-lookup failure points requiring verse-level disambiguation.
5. Prioritize theologian review capacity toward the 53 new Critical/High/Medium-High terms and the 20 doctrines flagged for theologian review before allocating capacity to the 6 native-speaker-review doctrines and 1 automated-only doctrine.