01 Executive Summary — Matthew 1–28 (English → Manipuri)

The bottom line: Matthew can be translated into Manipuri (Meiteilon, Bengali script) using the Romans baseline’s proven dual-tradition method, but Matthew’s narrative density — a virgin birth, angelic visitations, homage-paying, exorcisms, a radiant transfiguration, a bodily resurrection, a final judgment scene — turns what were largely abstract vocabulary risks in Romans into concrete, behaviorally visible syncretism risks that this curriculum’s Phase 1 artifacts now name and fence explicitly.

---

Why it matters

• Manipuri believers and seekers live inside two simultaneously active, non-Christian religious systems — Gaudiya Vaishnavism (majority Meitei religious identity, Krishna-Radha devotion via the Ras Lila tradition) and Sanamahism (indigenous religion under active revival, centered on Sanamahi, Pakhangba, and the Umang Lai) — not a single fading “Hindu background.”
• Matthew is the most doctrinally dense and narratively concrete book yet processed for this language pair: it stages the Incarnation, worship of Christ, exorcism, kingship, and final judgment as literal events, each with a ready cultural analogue in Manipuri religious life that must be actively distinguished, not just glossed.
• Getting this wrong has lived consequences: the small, currently pressured Meitei Christian minority is this curriculum’s real first audience, not a hypothetical one.

Key findings

• 100 terms are now recorded in translation_memory.json for Matthew: 47 inherited verbatim from the Romans baseline plus 53 new terms this book introduces (Beatitudes vocabulary, Son of Man, Son of David, Kingdom of Heaven, baptism, Gehenna, Great Commission vocabulary, and more).
• Of those 100 terms, 40 are Critical risk and 36 are High risk — 76 terms (76%) require human theologian review at every occurrence; 19 are Medium (native speaker review); only 5 are Low (automated review).
• 30 doctrines are tracked in doctrine_risk_registry.json; 19 Critical + 9 High = 28 doctrines (93%) require human theologian review; only 2 (Sabbath and the Law; Prayer) route to native speaker review. Zero doctrines are Low risk — reflecting Matthew’s unusually concentrated Christological, eschatological, and ecclesiological content.
• The core passage, Matthew 5:1-12, sits at the single highest-density risk point in the whole book: its central word “blessed” (9 occurrences) must never render as ধন্য, the Vaishnava devotee’s merit-adjacent blessedness from Krishna’s favor — a one-word failure at the curriculum’s theological anchor would corrupt its entire doctrine of unconditioned divine favor.
• One term’s risk tier was deliberately elevated from the Romans baseline: “church” (কলিসিয়া) moves from Medium to Critical, because Matthew 16:18 and 18:17 are the founding texts for the Church-and-Discipline doctrine block.

Risks

• Highest-severity ambiguity: খুরুমজবা (προσκυνέω, “worship/homage”) directed at Jesus spans ordinary royal courtesy and full temple-image veneration in ordinary Meitei usage; every one of its 8 Matthean occurrences is flagged Critical.
• Highest behavioral-syncretism risk: বাপ্তিস্মা (baptism) narrates an actual physical rite that invites direct visual comparison with Vaishnava river-bathing (snana) and Sanamahi purification washing.
• Highest lexical-collision risk: bare থাওয়াই (“spirit”) sits at the intersection of the core passage (“poor in spirit,” 5:3) and the populated Sanamahi ancestral/Umang Lai spirit-world; it must never appear unqualified.
• Highest doctrinal-cosmology collision: গেহেন্না (Gehenna) must never be rendered নরক, which presumes temporary punishment before rebirth — directly contradicting Gehenna’s finality; repeated at six locations.
• Ongoing framing risk: the Great Commission and disciple-making vocabulary must be actively defended against being heard as a colonial-coded missionary project (given real regional history) or as guru-śiṣya devotional recruitment (given live Vaishnava bhakti-lineage practice).

Opportunities

• Matthew’s genealogy and “Son of David” material, and Meitei culture’s own strong emphasis on royal/clan (yumnak) lineage, give this curriculum a natural, if carefully bounded, point of resonance for teaching the Davidic covenant — provided the Pakhangba-descent royal-divine framework is explicitly distinguished rather than assumed compatible.
• The vineyard-workers parable (Matthew 20:1-16) is the clearest illustrative text in either curriculum for teaching grace-apart-from-merit against the live bhakti-responsive কৃপা framework — a strong candidate for a flagship teaching unit.
• This is the first Language Package to document Sanamahism and Vaishnavism as two distinct, simultaneously live systems rather than folding both into one “Hindu-majority” backdrop — a reusable methodological asset for any future Manipuri curriculum.

Recommended actions

1. Route all 76 Critical/High terms and 28 Critical/High doctrines to human theologian review before Phase 2 segment translation begins; do not allow automated-only approval for any of this material.
2. Prioritize theologian review time using the ranked ambiguity list in 06_linguistic_gap_analysis.md Part D, starting with προσκυνέω/worship, baptism, and bare থাওয়াই.
3. Confirm three provisional renderings with a Manipuri-speaking theologian before wide deployment: covenant (ৱারেপ্পা), the Peter/rock wordplay (পিতর/নুংশিত্), and the Son of Man title’s contextual glossing strategy.
4. Load both this package’s translation_memory.json and the Romans baseline’s for any combined-curriculum deployment, and never re-derive a divergent rendering for a term the two books share.
5. Brief every reviewer on both live traditions explicitly — a reviewer trained only on Vaishnava-Hindu risk categories will miss Sanamahism-specific risks (maibi trance-possession, Umang Lai veneration, the Puya Meithaba’s shaping of attitudes toward sacred text) that this curriculum’s demon, spirit, and worship vocabulary depend on getting right.

---

This summary synthesizes 06_linguistic_gap_analysis.md, 07_semantic_analysis.md, 08_core_glossary.md, 11_doctrine_analysis.md, 12_ai_translation_requirements.md, assets/translation_memory.json, assets/bible_term_registry.json, and assets/doctrine_risk_registry.json. Load alongside those documents for full supporting detail.