Executive Summary

Why it matters

Romans is the theological backbone of the New Testament, and Konkani presents a translation challenge unlike any other language in this pipeline: it is spoken by two genuinely distinct religious communities under one language name — a Hindu Goan population practicing Shaiva, Shakta, and Vaishnava temple devotion, and one of Asia’s oldest Christian communities, Goan Catholics, whose own centuries-old Romi Konkani (Roman-script) vocabulary already solved much of the basic Christian-terminology problem long before this Language Package existed. Treating Konkani as a single undifferentiated “Hindu-context” language, or assuming the existing Catholic vocabulary can simply be repurposed for this curriculum’s Devanagari, doctrinally-precise register, would both be mistakes this Language Package deliberately avoids.

Key findings

• The registry tracks 40 doctrines across Romans 1-16; 30 require mandatory human theologian review before any translated segment ships (7 Critical, 23 High).
• The single most unusual entry in this Language Package is देव (God): unlike Hindi’s परमेश्वर, which was chosen specifically to avoid deity-multiplicity ambiguity, Konkani’s established Bible term देव is the same generic word Goan Hindu practice uses for any individual temple deity (Shantadurga dev, Mahalasa dev). This glossary keeps देव as the settled term but requires an exclusivity marker in every doctrinally load-bearing use.
• Incarnation risk here is concretely local, not abstract: Goa’s own Mardol temple venerates Mahalasa Narayani as an avatar of Vishnu, making avatar theology a physically nearby devotional reality rather than distant cultural background.
• Evangelism and mission language carry unusually heavy historical weight in Konkani because of Goa’s documented history of coercive conversion under the Portuguese-era Goa Inquisition (established 1560); this is a substantively different sensitivity than the generic “colonial-connotation” caution applied elsewhere in this pipeline.

Risks

• God-term ambiguity: देव’s built-in multi-deity ambiguity is the single hardest problem in this glossary to fully close by word choice alone; it requires consistent contextual reinforcement rather than a clean substitute term.
• Avatar-incarnation collapse: अवतार is rejected for the same reason as in other Hindu-influenced languages, but the specific, locally sited Mahalasa Narayani/Mohini tradition at Mardol makes this risk sharper and more concrete in Goa than a generic pan-Indian description would suggest.
• Coercion-association risk: given the historical reality of Inquisition-era forced conversion, mission and evangelism vocabulary risk triggering a specific, historically grounded negative association that goes beyond ordinary “colonial baggage” caution.
• Register-collapse risk: reviewers unfamiliar with the Hindu/Catholic split could mistakenly treat this glossary’s Devanagari choices as interchangeable with Romi Konkani Catholic vocabulary, or vice versa, when the two serve different audiences and scripts entirely.

Opportunities

• Konkani has a genuine historical precedent for creative, respectful inculturation: Thomas Stephens’ 1616 Kristapurana presented the Gospel narrative in Puranic poetic form specifically to reach a Hindu audience, showing that serious doctrinal engagement with Goan Hindu literary and devotional forms has deep local roots.
• The existing Goan Catholic Christian community and its long-settled Romi Konkani vocabulary is a genuine linguistic and pastoral asset for this whole language, even though this particular Language Package’s Devanagari register does not reuse it directly.

Recommended actions

• Route every Critical and High risk segment (30 of 40 doctrines) through human theologian review before publication; do not allow automated-only review to touch these terms.
• Brief every reviewer specifically on the Hindu/Catholic audience split and on देव’s built-in ambiguity, neither of which a reviewer trained on a single-audience language’s risk categories would anticipate.
• Reuse this Language Package’s translation_memory.json for every Romans lesson in Konkani rather than re-deriving terms per document, per the two-phase pipeline design.