Executive Summary — Matthew 1–28 Gujarati Translation Requirements

Why it matters

Matthew is being added to a Gujarati Bible-translation pipeline built and proven on Romans. Gujarat’s dual dominant traditions — Vaishnav/Swaminarayan bhakti Hinduism and Jainism — create dense collision risk across Matthew specifically because this Gospel is saturated with exactly the vocabulary those traditions already have strong, competing answers for: a promised king (Krishna avatars at nearby Dwarka), a path of self-attained perfection (Jain sammyak-chāritrya, kevalin/siddha), a cyclical view of time and hell (yuga theory, saṁsāra, temporary naraka), and a self-sought teacher-disciple relationship (guru-shishya paramparā). Getting this Language Package right determines whether Gujarati readers meet the real Jesus of Matthew or a syncretized stand-in.

Key findings

• 34 doctrines identified, chapter-by-chapter across the full book (1–28), anchored theologically — not scoped — by the core passage, Matthew 5:1–12 (the Beatitudes).
• 13 Critical-risk and 16 High-risk doctrines (29 of 34 total) require mandatory human theologian review; only 3 doctrines route to native speaker review and 2 to automated review alone.
• 103 terms now populate the Matthew assets/translation_memory.json: 34 inherited exactly from the Romans baseline (e.g., પરમેશ્વર, ઈસુ, ઉદ્ધાર, ન્યાયીપણું) plus 69 new terms unique to Matthew’s vocabulary.
• Of those 103 terms, approximately 23 carry Critical risk and 33 carry High risk — 56 terms (over half the glossary) require theologian-tier scrutiny on every occurrence.
• Two genuine lexical gaps surfaced during analysis and were resolved in this pass: Gehenna (ગેહેન્નાની આગ, never નરક) and Hades (હેડીસ, never પાતાળ) — both previously unaddressed because Romans never required hell-specific vocabulary.
• Matthew introduces three distinct, easily-confused Christological titles — Son of Man, Son of God, Son of David — each requiring its own fixed, non-interchangeable Gujarati rendering.
• Matthew’s characteristic phrase “kingdom of heaven” (32 occurrences) required a new compound (સ્વર્ગનું રાજ્ય) alongside the baseline’s “kingdom of God” (પરમેશ્વરનું રાજ્ય, reserved for 5 exact-phrase verses) — both name one identical reality and must never be taught as two realms.

Risks

• Worship of Christ (2:11; 8:2; 9:18; 14:33; 15:25; 28:9,17) — Critical. પૂજા (Hindu/Jain image-veneration) is the single highest-frequency substitution trap in the entire book; a Watchtower/NWT-style diminishment of worship-of-Jesus specifically would independently corrupt the Deity of Christ doctrine.
• Gehenna/Hades — Critical. The obvious native words (નરક, પાતાળ) import a temporary, cyclical hell-cosmology that directly contradicts the doctrine of final, unending judgment.
• Son of Man — Critical. Risk of flattening Daniel 7’s exalted-authority title into a bare humility-reference, erasing half of Matthew’s most load-bearing Christological claim.
• The Great Commission’s Trinitarian formula (28:19) — Critical. Must be treated as one indivisible translation unit; grammatical slip from singular “નામે” to plural would imply three separate beings.
• Righteousness’s dual sense (5:20; 6:1, 33) — Critical. Matthew stretches the baseline term ન્યાયીપણું into a lived-ethical sense that sits dangerously close to Jain self-attained conduct (સમ્યક્ ચારિત્ર્ય) if not consistently framed as grace-fruit.
• Discipleship vocabulary (શિષ્ય, શિષ્યો બનાવવા) — High, socially sensitive. Both collide with guru-shishya self-advancement models and carry live political sensitivity around religious conversion in contemporary India.
• Cult/sect renderings in circulation (Watchtower “torture stake” for cross, worship-softening for Jesus, “Jehovah” substitution) are documented as actively circulating in Gujarati and must be auto-flagged wherever back-translation matches these patterns.

Opportunities

• Matthew’s Sermon on the Mount (ch. 5–7) and the Beatitudes specifically offer strong entry points for grace-vs-merit teaching, directly answering the karma-merit economy (કર્મફળ) shared by both Hindu and Jain hearers — the vineyard-workers parable (20:1–16) and the reward doctrine (બદલો) are prime teaching texts already flagged for this purpose.
• The Great Commission’s universal scope and the Canaanite woman/centurion narratives give the curriculum natural, textually-grounded material for addressing caste- and community-based spiritual hierarchy without softening the text.
• Resolving Gehenna/Hades now (rather than leaving them as the open gaps flagged in the linguistic analysis) closes the single largest unaddressed doctrinal risk carried over from Phase 1 Step 6, ahead of Phase 2 chapters 5, 10, 11, 16, 18, and 23.
• The three-way Christological title fence (Son of Man / Son of God / Son of David) sets a reusable disambiguation pattern for future Gospel curricula (Mark, Luke, John) built on this same Language Package.

Recommended actions

1. Lock the 103-term assets/translation_memory.json for theologian sign-off before Phase 2 begins, prioritizing the ~23 Critical and ~33 High terms.
2. Route all 29 Critical/High doctrines to human theologian review per assets/doctrine_risk_registry.json; reserve native speaker review for the 3 Medium doctrines (Sabbath/Law fulfillment, Marriage/Divorce, Mercy/Compassion) and automated review for the 2 Low doctrines (Parables as Teaching Method, Genealogy/Covenant Lineage).
3. Treat Matthew 28:16–20 as a single indivisible Critical-risk translation block, not term-by-term, given the Trinitarian formula’s doctrinal density.
4. Confirm the live YouVersion version_id for IRV-GUJ before Phase 2 hyperlink generation; book code MAT, Gujarati book name માથ્થી are already fixed.
5. Add the cult/sect pattern-matching escalation rule (Part 3 of analysis/05_translation_landscape.md) to automated Phase 2 validation so any Watchtower-pattern back-translation auto-escalates regardless of assigned risk tier.
6. Carry the Gehenna/Hades resolution forward into Step 12 (this package) as newly Critical-risk, fully-specified terms — no longer open items.

---

This summary is fully consistent with analysis/11_doctrine_analysis.md, assets/doctrine_risk_registry.json, assets/bible_term_registry.json, assets/translation_memory.json, and analysis/12_ai_translation_requirements.md. Any figure cited here must match those source artifacts; update all in lockstep if revised.