Matthew — urdu
TRI knowledge bundle for Matthew (urdu).
Executive Summary
Executive Summary — Matthew (English → Urdu)
Why it matters
Matthew is the first Gospel added to this Urdu Language Package family, and it concentrates the pipeline’s defining hazard — direct Qur’anic negation, not diffuse syncretism — more densely than Romans or Galatians did individually. The core passage (Matthew 5:1-12, the Beatitudes) opens the whole curriculum by naming the poor in spirit, the meek, and peacemaking “sons of God” in the same breath the book will later use to claim Jesus is the Son of God, the Son of Man, and the one worshipped, crucified, and raised. Getting Matthew right in Urdu means teaching genuine common ground (qiyāmat, jahannam, tawbah, the virgin conception) honestly alongside the sharpest points of contested claim (the crucifixion, Qur’an 4:157; substitutionary atonement, Qur’an 6:164; the Trinity and Sonship, Qur’an 112) — never blurring either side of that line.
Key findings
- 109 total glossary terms now govern Matthew translation: 46 inherited unchanged from the Romans/Galatians baseline, plus 63 new terms this book introduces.
- 70 of those 109 terms carry Critical or High doctrine risk (27 Critical + 43 High), mandating human theologian review at every occurrence.
- At the doctrine level, Matthew’s
doctrine_risk_registry.jsonrecords 16 Critical-risk doctrines and 15 High-risk doctrines — 31 doctrines total requiring mandatory human theologian review — plus 6 Medium-risk doctrines requiring native speaker review. Zero doctrines in the entire book are Low risk. - Two entirely new Critical concentration points exceed anything in Romans/Galatians: the Trinitarian baptismal formula (Matthew 28:19), which stacks three separately-Critical baseline terms (Father, Son, Holy Spirit) into one memorized liturgical clause; and the ransom-for-many saying (Matthew 20:28) plus its Last Supper echo (26:26-28), which layers a second, independently-sourced Qur’anic negation (rejection of vicarious penalty-bearing, Qur’an 6:164/17:15/53:38) on top of the standing crucifixion-historicity collision.
- Matthew introduces a new hazard class absent from Romans/Galatians: structural-parallel collision, where the correct Urdu word for a Matthean concept (اختیار for authority; باندھنا/کھولنا for binding-and-loosing; مسکین for “poor”) is also the exact technical term of a parallel Islamic institution (fatwā-issuing juristic authority; ḥalāl/ḥarām declaration; the zakat-recipient category). This requires fencing, not substitution.
Risks
- Highest risk in the entire Language Package family: Matthew 28:19’s Trinitarian formula and Matthew 20:28/26:26-28’s double-collision ransom language. Both require dedicated, standalone theologian-review flags — neither may be silently folded into the general crucifixion-review rule.
- Core-passage-specific risk: three of the Beatitudes’ opening terms (روح کے مسکین, “poor in spirit”; حلیم-adjacent “meek”; خدا کے بیٹے, “sons of God”) sit directly against precise, technical Islamic vocabulary at the very first verses a learner will encounter — mishandling any of the three corrupts the interpretive frame for the whole curriculum.
- Son of Man mistranslation risk: the single most easily and silently corrupted title in the book. The phonetically closest Urdu phrase (ابنِ آدم) is itself a live, flatly generic Qur’anic phrase; using it instead of انسان کا بیٹا would erase Matthew’s concealed Daniel 7 divine-authority claim from roughly a dozen passages without triggering any obvious translation error.
- Pastoral/safety risk: the Great Commission (28:18-20), the cost-of-discipleship material (10:1-42; 16:24-26), and the church-discipline procedure (18:15-20) all carry real social, familial, and in some jurisdictions legal consequences for Urdu-speaking readers; doctrinal content must never be softened, but application must always be framed as personal, patient witness and privately-held conviction, never public confrontation.
Opportunities
- Genuine, usable bridges exist and should be led with, not avoided: the virgin conception (Qur’an 19:20-21), the shared name Yunus/Jonah, the shared existence of a final judgment and hell (jahannam), the shared concern about hypocritical public piety (riyā’), and the Persian-origin word خدا itself. Leading with honest common ground before naming divergence is both accurate and pastorally effective, especially for Judgment and the End of the Age.
- The Beatitudes as curriculum anchor offer an unusually warm, invitational entry point (مبارک’s genuine everyday familiarity, e.g. “Eid mubārak”) if taught with care to keep the eschatological force of God’s own verdict intact rather than flattening it into casual well-wishing.
- A single, disciplined glossary now exists spanning three books (Romans, Galatians, Matthew), giving Phase 2 translators a stable, cross-referenced enforcement database and reducing the risk of inconsistent terminology as the curriculum library grows.
Recommended actions
- Route all 31 Critical/High-risk doctrines and all 70 Critical/High-risk terms through mandatory human theologian review before any Phase 2 segment is marked approved; do not allow automated-only or native-speaker-only clearance for any of these.
- Treat Matthew 28:18-20 and Matthew 20:28/26:26-28 as standalone, dedicated review blocks — never merge their sign-off with the general crucifixion-narrative review of chapters 26-27.
- Apply the fencing strategy (retain the correct term, explicitly exclude its Islamic-institutional neighbor) documented in
06_linguistic_gap_analysis.mdSection 2.2 at every occurrence of اختیار, باندھنا/کھولنا, مسکین, حلیم, and اجر — these require notes, not new words. - Load
translation_memory.jsonv3,bible_term_registry.json, anddoctrine_risk_registry.json(Matthew-extended) plus the updated12_ai_translation_requirements.mdbefore any Phase 2 Matthew segment is processed. - Brief all reviewers on the categorical distinction this package draws between negation risk (a named Qur’anic counter-claim) and structural-parallel-collision risk (a correct word inviting a false institutional equivalence) — the two require different remediation strategies and neither should be treated as the other.
This document completes Phase 1, Steps 9-11 for the Matthew curriculum. See assets/translation_memory.json, analysis/12_ai_translation_requirements.md, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, and analysis/11_doctrine_analysis.md for full supporting detail.