Linguistic Gap Analysis
Linguistic Gap Analysis — Matthew (English → Urdu)
0. Scope and Method
This analysis extends the baseline Romans/Galatians Language Package to the Gospel of Matthew (chapters 1–28) without contradicting any established rendering. Every term below has been checked against the baseline translation_memory.json first; only genuinely new Matthean vocabulary is analyzed fresh. Matthew’s overall risk profile inherits the baseline’s central finding — Urdu’s dominant hazard is direct negation (a specific, named Qur’anic claim explicitly contradicting a specific Matthean claim) rather than diffuse syncretism — but Matthew adds a second, distinct hazard class not prominent in Romans/Galatians: structural-parallel collision, where Urdu’s available vocabulary for a Matthean concept is also the precise technical term of a parallel Islamic institution (juristic authority, zakat categories, divine-name vocabulary, ritual purity law). This is a different failure mode from “the word means something false” — here the word is exactly right in form and invites a false equivalence in function. Sections 2 and 3 exist specifically to fence this second hazard class, which the baseline’s four Romans/Galatians documents encountered only sporadically (e.g. شریعت, رسول) but which recurs constantly across Matthew’s teaching material (chs. 5–7, 15, 16, 18, 23).
Full-book coverage note: every chapter of Matthew (1–28) has been reviewed for terminology gaps. Chapters producing no new terminology beyond what is already tabulated below (6, 8, 9, 14, 19 [beyond one_flesh_marriage, already covered], 20 [beyond ransom_for_many, already covered]) are recorded as reviewed, no new gap at the end of Section 1.
1. Doctrine Vocabulary Matrix
For each of the nine curriculum doctrines: the candidate Urdu term(s) available in the language, their specific weaknesses, and the recommended handling strategy. Risk tiers match doctrine_risk_registry.json conventions.
1.1 The Kingdom of Heaven
| Candidate term | Weakness | Recommended strategy |
|---|---|---|
| آسمان کی بادشاہی (literal “kingdom of the heavens”) | Risks being heard spatially (a kingdom located in the sky) or conflated with جنت (paradise, the afterlife reward) | ADOPT as primary rendering, but require a standing clarifying note at first occurrence per chapter-group: “آسمان” here is reverential circumlocution for God’s own name/rule (matching Jewish avoidance of the divine name), not a place. Teach as strictly synonymous with baseline’s خدا کی بادشاہی. |
| خلافت / خلافتِ الٰہیہ (caliphate/divine-caliphate) | Politically loaded in South Asian Muslim discourse (historical Ottoman/Mughal khilafat, contemporary khilafat-restoration movements); would import a territorial-political program Matthew’s “kingdom” does not intend | REJECT outright as a rendering; flag explicitly in teaching notes so translators are not tempted toward it as a “more dynamic” option. |
| مُلک / سلطنت (generic kingdom/realm) | Too flat; loses the reign/rule sense in favor of a bounded territory | Retain بادشاہی (already baseline-fixed for kingdom_of_god) as the noun; do not substitute مُلک or سلطنت. |
Doctrine-level strategy: Treat آسمان کی بادشاہی and خدا کی بادشاہی as one referent throughout Matthew; introduce the synonymy explicitly at 3:2/4:17 and reinforce at each major discourse shift (chs. 5, 13, 18, 25).
1.2 Jesus as the Promised Messiah and Son of David
| Candidate term | Weakness | Recommended strategy |
|---|---|---|
| مسیح | Shared Qur’anic title (al-Masīḥ), but without Matthew’s Davidic-covenant, atoning-death, or divine-sonship content | REUSE baseline term; every occurrence must carry the standing note that Matthew’s content exceeds the Qur’anic Isa al-Masih. |
| داؤد کا بیٹا | Could be misread as either (a) a bare genealogical fact needing no theological weight, or (b) conflated with خدا کا بیٹا if translators are careless | NEW term, keep strictly distinct in form from خدا کا بیٹا; use consistently for the royal-messianic title, reserving خدا کا بیٹا only for the eternal-Sonship claim. |
| مسیحا (a less common Urdu variant spelling) | Non-standard; would create unnecessary inconsistency against the established مسیح | REJECT; do not introduce spelling variants. |
Gap identified: Urdu has no single word carrying “royal Davidic heir who is also eternally divine” — this must remain a two-term system (داؤد کا بیٹا + خدا کا بیٹا), deliberately held apart until Matthew 22:41-45 itself argues for their convergence. Do not pre-collapse the two terms for translation convenience.
1.3 Fulfillment of Old Testament Prophecy
| Candidate term | Weakness | Recommended strategy |
|---|---|---|
| پوری ہونا (fulfilled) | Adequate lexically, but recurrence (~17x) creates risk of being read as a generic literary refrain rather than a load-bearing doctrinal claim if translators vary the wording for “freshness” | Fix پوری ہونا / پوری ہوئی as the invariant rendering for πληρωθῇ at every occurrence; do not vary for stylistic reasons. |
| تعبیر / تشریح (interpretation/exposition) | Could be used loosely for “fulfillment” in casual Urdu but wrongly suggests Matthew is offering a creative reading rather than reporting an accomplished historical event | REJECT as a substitute for پوری ہونا. |
| نبوت کی تکمیل (completion of prophecy) | Acceptable as a doctrine-label gloss (used in doctrine_risk_registry as “fulfillment_of_prophecy”), but too formal/abstract for running narrative text | Reserve for doctrine-summary headings only; use پوری ہونا in the translated text itself. |
Structural risk unique to this doctrine: Islamic prophetology reads the entire prophetic sequence as pointing toward a final prophet (khatam an-nabiyyin). Matthew’s fulfillment-formula readers may unconsciously map “fulfilled in Jesus” onto that same forward-pointing structure and then ask “so what about the one who came after him?” This is not solved by word choice; it requires an explicit teaching note (see baseline’s fulfillment_of_prophecy doctrine entry) at first occurrence (1:22) and at the discourse-level summary (5:17).
1.4 The Authority of Jesus’ Teaching
| Candidate term | Weakness | Recommended strategy |
|---|---|---|
| اختیار | Also names a muftī’s derived, consensus-grounded interpretive authority (a live, structurally parallel Islamic legal category) | ADOPT، but require an explicit contrastive note at 7:29 (first occurrence) distinguishing Jesus’ inherent, self-grounded authority from derived, tradition-grounded juristic authority. |
| قوت / طاقت (force/strength) | Loses the “right to act,” legitimacy sense entirely; reduces to raw power | REJECT as a substitute for اختیار. |
| حکمرانی (dominion/rule) | Overlaps with بادشاہی (kingdom) vocabulary; would blur two distinct Matthean concepts (Jesus’ teaching-authority vs. the Kingdom’s reign) | REJECT for this specific sense. |
Crowded-neighborhood note: اختیار sits in the same semantic and social space as فتویٰ (fatwa), اجماع (scholarly consensus), and علماء کا اختیار (the authority of religious scholars) — all live, contemporary Urdu-Islamic-discourse terms. This is the single most crowded neighborhood in the Authority doctrine and must be fenced at every major occurrence (7:29; 9:6,8; 21:23-27; 28:18), not only the first.
1.5 Righteousness Exceeding the Pharisees
| Candidate term | Weakness | Recommended strategy |
|---|---|---|
| راستبازی | Baseline forensic term; Matthew’s ethical overtone (5:20’s “exceeding”) risks being read as abandoning the forensic sense altogether in favor of pure performance-righteousness | REUSE baseline term; explicitly teach both senses (received status AND resulting conduct) coexisting, verse by verse. |
| نیکی (goodness/virtue) | Purely ethical, no forensic/legal-standing content at all; would silently convert 5:20 into a bare morality contest | REJECT as primary; already rejected at the baseline level for the same reason. |
| تقویٰ (piety/God-consciousness) | Names an achieved spiritual-ethical disposition through obedience — exactly the “same merit system, higher score” reading 5:20 must avoid | REJECT; already rejected at baseline level. |
Gap identified: there is no single Urdu word that simultaneously carries “declared right standing” and “resulting exceeding conduct” — this is not solvable lexically and requires doctrinal scaffolding (see baseline’s righteousness_exceeding entry) rather than a better word.
1.6 The Church and Church Discipline
| Candidate term | Weakness | Recommended strategy |
|---|---|---|
| کلیسیا | Baseline term; safe as a proper institutional noun, but 16:18/18:17’s founding and disciplinary weight is not carried by the noun alone | REUSE baseline term; risk tier elevates to High specifically at 16:18/18:17 per the doctrine registry, requiring explicit teaching rather than a different word. |
| باندھنا / کھولنا (bind/loose) | Functions in a linguistic space nearly identical to حلال/حرام declaration and فتویٰ authority | ADOPT literal rendering (no natural Urdu synonym exists that avoids this overlap), but fence explicitly: content and source of authority (apostolic, Christ-delegated, church-exercised) differ sharply from juristic derivation from Qur’an/hadith/consensus. |
| اُمّت (community) | Explicitly rejected at baseline level for “church” and “fellowship”; equally inapplicable here | REJECT. |
Gap identified: Urdu has no institutional-authority vocabulary for “the gathered church exercising Christ-delegated discipline” that does not also evoke Islamic juristic-authority structures. This is unavoidable overlap in form, requiring content-level fencing, not a vocabulary substitute.
1.7 The Great Commission
| Candidate term | Weakness | Recommended strategy |
|---|---|---|
| تمام قوموں (all nations) | None significant; correctly signals universal, Israel-inclusive scope, distinct from غیر قوموں | ADOPT for 28:19 specifically; do not use غیر قوموں here even though it is elsewhere the baseline default for ἔθνη. |
| بشارت کی خدمت (mission/gospel-service) | Baseline term; safe, but risk is not in this word — it is in how the Commission is applied pastorally | REUSE; apply baseline’s evangelism-sensitivity caution (proselytization’s real social/legal weight) with maximum care given this is the New Testament’s most explicit missionary mandate. |
| دعوت / تبلیغ | Specific Islamic missionary technical terms | REJECT — already baseline-forbidden; doubly important here given the prominence of this passage. |
| باپ اور بیٹے اور روح القدس کے نام پر (Trinitarian formula) | Concentrates three baseline Critical terms in one memorized liturgical line | See Section 4 (highest-risk ambiguities) — no lexical fix exists; grammatical singularity (“the name,” not “the names”) must be preserved without exception. |
1.8 Judgment and the End of the Age
| Candidate term | Weakness | Recommended strategy |
|---|---|---|
| قیامت (as end-of-age referent generally) | Already baseline-flagged Critical for Christ’s own resurrection; reused here for the general end-time consummation risks blending the two distinct senses (Christ’s own past resurrection vs. the still-future general judgment day) if not disambiguated | Use دنیا کا خاتمہ / زمانے کا اختتام for συντέλεια τοῦ αἰῶνος (end of the age) and reserve قیامت strictly for resurrection contexts, per the Matthew glossary’s existing distinction; do not let the two blend. |
| جہنم / دوزخ | Genuine bridge words (shared with Qur’anic jahannam) — the rare case of real common ground on the existence of final judgment | ADOPT as shared vocabulary, but the criterion (relationship to Christ, not mīzān deeds-weighing) must be taught explicitly every load-bearing occurrence. |
| مِیزان (scales, deeds-weighing) | A precise, technical Islamic eschatological term for the judgment mechanism itself | REJECT as a rendering for any Matthean judgment vocabulary; reserve only as a comparative-teaching reference point when explicitly contrasting mechanisms (e.g. sheep_and_goats, 25:31-46). |
| روح القدس کی گستاخی (blasphemy against the Holy Spirit) | Names an unforgivable sin structurally parallel in function (an unforgivable-sin category exists in both systems) but not in content to Qur’anic shirk | NEW term; teach the two unforgivable-sin claims (12:31-32 vs. Qur’an 4:48,116) as distinct systems, never conflated. |
1.9 Discipleship and the Cost of Following Jesus
| Candidate term | Weakness | Recommended strategy |
|---|---|---|
| اپنی صلیب اٹھانا (take up one’s cross) | Full crucifixion-collision weight (Qur’an 4:157) plus a personal-identity discipleship demand | REUSE root صلیب; never soften to a generic “carry your burdens” idiom, which would lose the specific, historically loaded image. |
| شاگرد (disciple) | Safe; the correct fenced alternative to مرید | ADOPT; never مرید (imports Sufi pir-murid master-disciple institution with oath, spiritual lineage, and intercessory mediation — an entire unwanted institutional import). |
| بہتوں کے بدلے اپنی جان دینا (ransom for many) | Double collision: presupposes the crucifixion AND asserts a substitutionary mechanism separately denied (Qur’an 6:164; 17:15; 53:38) | NEW term; see Section 4, ranked #2. Never فدیہ. |
| تلوار (sword, 10:34) | Risk of false-parallel association with جہاد sword imagery even though the term itself is unremarkable | Teach explicitly as metaphor for household division, never literal violence, and note the false-parallel risk for reviewers even though no different word is needed. |
Chapters reviewed with no new terminology gap beyond what is already tabulated in this document or the Matthew core glossary/registry: 6 (Lord’s Prayer vocabulary already covered under Kingdom/Father baseline terms; almsgiving/fasting material uses standard, low-risk vocabulary), 8–9 (healing narratives use standard vocabulary; authority already covered at 8:9; 9:6,8), 14 (worship_of_christ already covered at 14:33), 19 (beyond one_flesh_marriage, already covered; divorce material uses standard شریعت-adjacent vocabulary with no new gap), 20 (beyond ransom_for_many, already covered; the vineyard parable’s اجر/انعام tension is already covered under the “reward” entry).
2. Missing Vocabulary vs. Crowded Semantic Neighborhoods
Matthew’s terminology gaps fall into two structurally distinct categories requiring different remediation strategies.
2.1 Genuinely Missing Vocabulary (no adequate Urdu term exists)
These require paraphrase, compound construction, or borrowed/transliterated form rather than a single-word substitution, because no existing Urdu word — safe or unsafe — covers the concept:
| Concept | Why no single term exists | Strategy adopted |
|---|---|---|
| Justification’s forensic “declared righteous” sense applied at the Kingdom-ethics level (5:20) | Urdu’s ethical vocabulary (نیکی, تقویٰ) and forensic vocabulary (راستبازی) do not naturally combine into one word carrying both senses simultaneously | Compound teaching, not compound word: retain راستبازی and add explicit doctrinal scaffolding per occurrence. |
| Daniel 7’s “Son of Man” as concealed exalted-dominion title | No Urdu idiom carries both “ordinary human being” and “cosmic judge receiving eternal dominion” simultaneously; ابنِ آدم (the only close cognate) carries neither sense in Qur’anic usage | Literal calque انسان کا بیٹا + mandatory Daniel 7 explanatory note at first and climactic occurrences. |
| Substitutionary, vicarious atonement bearing another’s specific penalty (20:28; 26:28) | No Urdu word for “payment” carries load-bearing, one-time, uniquely sufficient substitution without either (a) compensatory-payment-still-owed logic (فدیہ) or (b) generic self-sacrifice language losing the penal substitution | Retain چھڑایا/چھٹکارا (baseline root) in expanded phrase form (بہتوں کے بدلے اپنی جان دینا); never compress to a single word. |
| Trinitarian grammatical singularity (“the name,” not “names,” shared by three Persons) | Urdu grammar permits either singular or plural possessive constructions here; the doctrinal requirement (singularity) is not enforced by Urdu grammar automatically | Fix the exact phrase باپ اور بیٹے اور روح القدس کے نام پر as invariant; forbid pluralization at the translation-memory level. |
2.2 Crowded Semantic Neighborhoods (too many available terms, each importing an unwanted parallel institution)
These require fencing — selecting one term and explicitly excluding its neighbors — rather than searching for a missing word:
| Neighborhood | Competing terms present in ordinary Urdu | Fence applied |
|---|---|---|
| Religious teaching-authority | اختیار (Jesus’ inherent authority) vs. فتویٰ / اجتہاد / اجماع (derived juristic authority) | اختیار retained; explicit note at 7:29 distinguishing inherent vs. derived authority. |
| Legal-scholarly office | شریعت کے معلم (Matthew’s scribes) vs. فقیہ (Islamic jurisprudential scholar) | فقیہ explicitly rejected as default; شریعت کے معلم adopted to avoid implying commentary on Islamic religious scholarship. |
| Binding/permitting declarations | باندھنا / کھولنا (apostolic church authority) vs. حلال / حرام (Islamic legal categories) | Retained (no alternative exists) but fenced with explicit source-and-content contrast note at 16:19 and 18:18. |
| Economic-spiritual poverty | روح کے مسکین (spiritual poverty, 5:3) vs. مسکین as the technical zakat-recipient category (Qur’an 9:60) | Compound retained (روح کے مسکین, never bare مسکین) with mandatory clarifying note distinguishing spiritual posture from economic/zakat category. |
| Human virtue vs. divine attribute-name | نرم دل (preferred, 5:5) vs. حلیم (one of the 99 names of Allah, al-Ḥalīm) | نرم دل / فروتن adopted as primary; حلیم permitted only as secondary gloss subject to reviewer judgment, never as the sole rendering. |
| Achieved spiritual perfection/station | کامل (Matthew’s “be perfect,” 5:48) vs. الانسان الکامل (Sufi “perfected human” honorific, sometimes applied devotionally to Muhammad) | کامل retained but immediately anchored to its own context (unstinting, indiscriminate love) to prevent drift toward a station-attainment reading. |
| Ritual purity/dietary law | ناپاک کرنا (“defiles,” 15:11) vs. حلال/حرام dietary law and ṭahāra ritual-purity system | Retained but explicitly scoped to the Pharisaic hand-washing controversy; never generalized into a verdict on dietary law as a category. |
| Reward/merit vocabulary | انعام (gift-continuous-with-grace, preferred) vs. اجر (technical mīzān deeds-weighed reward) | انعام adopted as default; اجر permitted only where the text itself argues against merit (e.g. the vineyard parable, ch. 20), case-by-case theologian review required. |
| Repentance | توبہ — retained despite being the precise technical Islamic term, because no viable alternative exists that Urdu readers will recognize as “repentance” at all | Retained (structurally identical situation to the baseline’s نجات treatment); every load-bearing occurrence requires the response-to-grace vs. merit-generating-act contrast. |
| Mourning/lament | غمگین (preferred) vs. ماتم کرنا (ritualized public lamentation strongly associated with Shi’a Muharram processions) | غمگین/تسلی پائیں گے adopted; ماتم کرنا explicitly excluded to avoid an unrelated ritual-mourning association. |
| Astrologer-figures (2:1) | مجوسی (also names Zoroastrians historically) vs. منجّم (astrologer, more precise) | One term to be selected consistently in Phase 2; both flagged, neither silently interchanged. |
3. Transliteration vs. Paraphrase Decisions
The following table records, for each newly identified Matthew term requiring a form-decision, whether the recommended strategy is transliteration (retain the source-language sound-form), paraphrase/compound (construct an Urdu descriptive phrase), or established-equivalent reuse (an existing Urdu/Christian-Bible-tradition word already carries the concept adequately).
| Term | Decision | Rationale |
|---|---|---|
| Immanuel (1:23) | Transliteration + gloss: عمانوایل (خدا ہمارے ساتھ) | Proper name retains recognizability as a name while the parenthetical gloss carries the doctrinal content; paraphrase alone would lose the name’s own identity as a title Matthew is citing from Isaiah. |
| Hosanna (21:9,15) | Transliteration: ہوشعنا | A liturgical acclamation, not a concept; Urdu Christian Bible tradition already transliterates such exclamations (cf. baseline’s آمین, ہلelویاہ). |
| Gehenna (5:22 etc.) | Established-equivalent reuse: جہنم / دوزخ | Genuine existing Urdu/Islamic vocabulary already names this concept; transliterating “Gehenna” (جہنا/گیہنا) would be unrecognizable and would forfeit real, useful common ground on the existence of final judgment. |
| Abba-pattern intimacy address to the Father | Not directly recurring in Matthew’s text (contrast Romans 8:15) but the same transliteration principle applies if it appears in study-note cross-references | Follow baseline’s ابّا transliteration precedent if referenced. |
| Son of Man (ὁ υἱὸς τοῦ ἀνθρώπου) | Paraphrase/calque: انسان کا بیٹا | Transliteration is impossible (this is a title, not a proper name); the existing near-cognate ابنِ آدم is explicitly rejected because it is itself a live Qur’anic phrase with a different, non-messianic sense — a calque using different vocabulary (انسان rather than آدم) is required precisely to avoid false recognition. |
| Ransom for many (λύτρον ἀντὶ πολλῶν) | Paraphrase (expanded phrase): بہتوں کے بدلے اپنی جان دینا | No single word carries the substitutionary-payment sense without either commercial (فدیہ) or generic-sacrifice connotations; the expanded phrase makes the substitution and its beneficiaries (“for many”) both explicit. |
| Trinitarian baptismal formula (28:19) | Established-equivalent reuse of three baseline terms combined: باپ اور بیٹے اور روح القدس کے نام پر | Each component term is already fixed at baseline; the task here is not new vocabulary but strict grammatical-form preservation (singular “name”). |
| Talents (τάλαντα, 25:14-30) | Paraphrase: سونے کی تھیلیاں (“bags of gold”) | Direct transliteration (تالنت) would be unrecognizable and lose the parable’s monetary-stakes sense entirely; Urdu Bible tradition favors descriptive rendering here over borrowed unit-names. |
| Phylacteries (φυλακτήρια, 23:5) | Paraphrase: تعویذ کی ڈبیاں (“amulet-boxes”) | تعویذ alone risks the folk-Islamic amulet association noted in Section 2; the fuller phrase anchors the concept to Deuteronomy 6:8’s literal small boxes rather than a general amulet practice. |
| Magi (μάγοι, 2:1) | Established-equivalent reuse (with caution): مجوسی / منجّم | Both are recognized existing Urdu words; no transliteration needed, but a single consistent choice must be fixed in Phase 2 given مجوسی’s additional Zoroastrian association. |
| Ēli Ēli, lema sabachthani (27:46) | Transliteration + immediate gloss: اِیلی اِیلی، لَما شبقتنی (میرے خدا، میرے خدا، تُو نے مجھے کیوں چھوڑ دیا) | Matthew itself preserves the Aramaic and then glosses it in Greek; the Urdu translation must mirror this two-step structure (transliterated cry, then translated meaning), matching the source text’s own method. |
| Woe (οὐαί, ch. 23) | Established-equivalent reuse: افسوس / ہلاکت ہے | Standard Urdu prophetic-judgment idiom; no transliteration or new coinage needed. |
General principle applied: transliteration is reserved for (a) proper names, (b) liturgical exclamations already transliterated elsewhere in the Urdu Christian Bible tradition, and (c) cases (like 27:46) where the source text’s own bilingual structure must be preserved. Paraphrase is required wherever a title or theological claim (Son of Man, ransom for many) has no safe single-word Urdu equivalent, particularly where the nearest-sounding or nearest-meaning existing word is itself a live, differently-freighted Islamic technical term.
4. Ranked List of Matthew’s Highest-Risk Ambiguities
Ranked by combined severity (doctrinal centrality × collision specificity × recurrence) and consistent with doctrine_risk_registry.json Critical-tier routing. All items below require mandatory human theologian review at every occurrence per the baseline’s escalation rules, extended by the Matthew-specific additions this Language Package will formalize in 12_ai_translation_requirements.md.
-
Trinitarian baptismal formula (28:19) — concentrates three baseline Critical entries (Father, Son, Holy Spirit) into one memorized, liturgically central line; grammatical singularity (“the name”) is not automatically enforced by Urdu grammar and must be manually fixed. Single highest-priority item in the entire Matthew package.
-
Ransom for many (20:28) / new covenant institution words (26:26-28) — double collision: presupposes the crucifixion (Qur’an 4:157) AND asserts a substitutionary penalty-bearing mechanism separately and explicitly rejected in principle (Qur’an 6:164; 17:15; 53:38, “no soul shall bear the burden of another”). No other term in this package carries two independent, separately-sourced Qur’anic negations at once.
-
My God, my God, why have you forsaken me (27:46) — engages the historicity of the crucifixion, the mystery of the Trinity (the Son forsaken without the Godhead dividing), and the deepest pastoral delicacy of any single utterance in the Gospel; no lexical fix mitigates this, only careful annotated teaching.
-
Worship of Jesus (προσκυνέω, 2:2,8,11; 14:33; 28:9,17) — every occurrence is an implicit deity-of-Christ claim; سجدہ/پرستش-register vocabulary directed at a human figure is recognized by Muslim readers as shirk-adjacent. Distinct from, but compounding, the existing Son of God risk.
-
Son of Man (ὁ υἱὸς τοῦ ἀνθρώπου) throughout — the single most easily mistranslated recurring title in the book: the “safe-looking,” phonetically closest Urdu phrase (ابنِ آدم) is a live Qur’anic phrase with the opposite risk profile (it flattens rather than conceals a divine-dominion claim). A one-word substitution error here would silently erase Daniel 7 from roughly a dozen passages.
-
Fulfill the Law (πληρῶσαι τὸν νόμον, 5:17) and the Antitheses (5:21-48) — Jesus’ claim to personal authority to complete and reinterpret revealed Law has no parallel in Islamic prophetology’s treatment of Isa, and collides with sharī’ah’s self-understanding as complete and fixed through Qur’an/hadith; this is a structural claim, not a word-choice problem.
-
Keys of the kingdom / bind and loose (16:19; 18:18) — linguistically and functionally parallel to fatwā-issuing and ḥalāl/ḥarām declaration; the overlap is in form, not content, and requires explicit source-of-authority fencing at every occurrence, not a different word (none exists).
-
Take up one’s cross (10:38; 16:24) — carries the full baseline crucifixion-collision weight plus a personal-identity discipleship demand placed on every individual reader, raising both doctrinal and real-world social/safety stakes (cf. baseline’s apostasy/persecution-risk pastoral doctrine).
-
Poor in spirit / meek (5:3, 5) — the Beatitudes’ opening two terms sit directly against precise, technical Islamic vocabulary (مسکین as a zakat category; حلیم as a divine name); mishandling either at the Sermon’s very first verses would corrupt the interpretive frame for the entire core passage (Matthew 5:1-12).
-
Authority (ἐξουσία) applied to Jesus (7:29 and throughout) — the crowds’ own comparison (“not as their scribes”) is Matthew’s explicit invitation to contrast inherent vs. derived authority; اختیار’s overlap with muftī/fatwā-authority vocabulary makes this comparison land differently for an Urdu reader than for Matthew’s original audience unless fenced explicitly.
5. Summary and Handoff
This analysis identifies two structurally distinct linguistic-gap categories for Matthew — genuinely missing vocabulary requiring paraphrase/compound construction (Section 2.1), and crowded semantic neighborhoods requiring explicit fencing rather than a substitute word (Section 2.2) — and ranks the ten highest-risk ambiguities for mandatory theologian review (Section 4). These findings should be read alongside analysis/08_core_glossary.md (term-by-term rendering decisions) and will inform the Matthew-specific additions to 12_ai_translation_requirements.md (forbidden substitutions, escalation rules, and system-prompt extensions) to be drafted in the next Phase 1 step. No recommendation in this document contradicts any baseline Romans/Galatians translation_memory.json entry.