Linguistic Gap Analysis — Ephesians (Urdu Language Package)
0. Purpose and Method
This document identifies where established Urdu Bible vocabulary is sufficient, where it is absent (missing vocabulary), and where it is present but overcrowded by competing meanings from Islamic theology, Sufi devotional tradition, or South Asian folk religion (crowded semantic neighborhoods). It extends the Romans/Galatians baseline translation_memory.json and the Ephesians 08_core_glossary.md without contradicting either. Every recommendation below either (a) confirms reuse of an existing baseline term, (b) formalizes a new term already proposed in 08_core_glossary.md/bible_term_registry.json, or (c) adds a gap-analysis-specific recommendation (fencing language, transliteration decision, or escalation) not yet made explicit elsewhere.
Framing carried forward from 12_ai_translation_requirements.md: Urdu’s dominant risk pattern is negation (a specific Qur’anic verse denies a specific doctrine — crucifixion, sonship) rather than syncretism (a fluent word smuggling in an unwanted cosmology), though Ephesians introduces several genuine syncretism-pattern risks not present in Romans/Galatians (most notably mystery vs. ghayb/kashf, and union with Christ vs. wahdat al-wujud). This analysis treats both patterns explicitly per doctrine.
1. Doctrine Vocabulary Matrix
For each of the nine curriculum doctrines: available Urdu terms, their specific weaknesses, and the recommended handling strategy.
1.1 Salvation by Grace through Faith
| Available Urdu terms | Weakness | Recommended strategy |
|---|
| فضل (grace), ایمان (faith), نجات (salvation) — [BASELINE] | فضل is unambiguous but must stay visibly distinct from new term رحمت (mercy, 2:4) within the same short span (2:4-8), or the two-step Greek argument (ἔλεος → χάρις) collapses into one generic “God is kind” idea. نجات’s shared-word/two-mechanism risk (see baseline) is sharpened, not repeated, by Ephesians 2:8’s perfect tense (“you have been saved”) — Islamic soteriology structurally cannot make this claim before judgment. | Reuse فضل, ایمان, نجات exactly. Render 2:8’s perfect tense with an unambiguous Urdu perfect (“نجات پا چکے ہو,” not a simple past or aorist-flavored “نجات پائی”) and attach a mandatory contrastive note on assurance every time 2:8 is cited. Keep رحمت (2:4) and فضل (2:5, 8) typographically and syntactically separated (do not let one clause carry both words interchangeably). |
| اعمال (works, unqualified, 2:9); نیک اعمال (good works, 2:10) | Missing-vocabulary problem, not crowded-neighborhood problem, in this specific case: Urdu has no unqualified word for “human deeds of any kind” that does not simultaneously activate the mizan (deeds-weighed-at-judgment) frame, because اعمال is that frame’s technical vocabulary. Galatians could fence this by anchoring to “works of the [Mosaic] law” (شریعت کے اعمال); Ephesians 2:9 gives Paul’s unqualified ἔργα, removing that fence. | Do not insert an artificial “law-works” qualifier not present in the Greek (this would soften Paul’s actually broader claim). Instead, fence procedurally: 2:9 and 2:10 must never be translated, quoted, or cross-referenced independently of one another in any lesson material — always as a single unit (اعمال excluded as basis in v.9, نیک اعمال affirmed as fruit in v.10). Mandatory theologian review per existing registry entries works_unqualified and good_works. |
| مرے ہوئے (dead, 2:1, 5); فطرتاً غضب کے فرزند (children of wrath by nature, 2:3) | These are missing-vocabulary gaps filled by compound phrases, since Urdu has no single word for “spiritually incapacitated from birth, prior to any act” that does not sound either merely metaphorical (weak) or medical (sick). فطرتاً (by nature/by birth) is the load-bearing word and is the exact grammatical negation-point against fitrah. | Retain compound phrasing exactly as recorded in 08_core_glossary.md/registry. Never substitute a single adjective. فطرتاً must never be dropped or softened to a temporal “later became” reading. Mandatory theologian review, every occurrence. |
| خوشبودار قربانی (fragrant sacrifice/offering, 5:2) | Crowded neighborhood: قربانی is extremely familiar Urdu/Islamic vocabulary (Eid al-Adha sacrifice, Ibrahim/Isma’il narrative), which is a genuine bridge (sacrificial logic is shared ground) but risks being heard as commemorative/symbolic rather than substitutionary-atoning, since Islamic qurbani does not carry a once-for-all atonement-for-sin function. | Reuse the term but never present it without explicit teaching that this قربانی actually atones (removes guilt before God once for all), unlike the commemorative Eid sacrifice. Automatic theologian-review flag inherited from the baseline crucifixion/atonement escalation rule. |
1.2 Election and Predestination in Christ
| Available Urdu terms | Weakness | Recommended strategy |
|---|
| خدا کا انتخاب (election) — [BASELINE]; پہلے سے مقرر کیا گیا (predestined, NEW); اپنی مرضی کی خوشی کے مطابق (purpose/good pleasure of his will, NEW) | Crowded neighborhood, not missing vocabulary: تقدیر (taqdir) is the single most natural Urdu word an average reader will reach for when reading Ephesians 1:4-11, since Ephesians piles up election + predestination + purpose-of-will language more densely in five verses than anywhere in Romans. The baseline’s existing taqdir-avoidance strategy (never substitute; engage directly in supporting material) is stress-tested by this density, not merely repeated. | Reuse the three baseline/new compound terms exactly, never تقدیر as a substitute for any of them. Because of the density, recommend a single dedicated supporting-material sidebar specifically for 1:3-14 (not deferred to a general Providence note as in Romans) directly engaging the Ash’ari/Mu’tazila qadar debate and distinguishing it from Ephesians’ narrower claim (God’s gracious choice of believers for salvation and adoption, not a claim about universal cosmic determinism of every event). |
| مہر لگانا (sealed, NEW); بیعانہ (guarantee/pledge, NEW) | Missing-vocabulary gap filled well: بیعانہ is a precise, familiar Urdu commercial-legal term (earnest money/down payment) with no competing religious sense — a genuine linguistic asset here, rare in this package. | Reuse as recorded. Use بیعانہ’s very ordinariness pastorally: it gives assurance-of-salvation teaching a concrete, legally binding image the reader already trusts in daily transactions — worth foregrounding in 1:14 teaching notes as a positive bridge, not merely a risk to fence. |
1.3 The Church as the Body of Christ
| Available Urdu terms | Weakness | Recommended strategy |
|---|
| کلیسیا (church), بدن (body, NEW), سر (head, NEW) | Missing-vocabulary decision already made correctly in 08_core_glossary.md: بدن (body) is deliberately not جسم, since جسم already carries the established “sinful flesh/nature” sense from the Galatians baseline. This is the single clearest example in Ephesians of a term needing its own dedicated word specifically to avoid crowding an existing baseline word. | Confirm and lock بدن vs. جسم vs. ایک تن (5:31, marriage) as three permanently distinct lexical items, never interchanged. Recommend a translator’s note at first occurrence of each explaining why three different words render three different senses of body/flesh across the letter — this triple distinction is unique to Ephesians among this pipeline’s curricula and should be flagged for glossary-training material, not left implicit. |
| ہیکل (temple, NEW); کونے کا پتھر (cornerstone, NEW) | Low risk; ہیکل safely reused from OT-temple usage. | No change needed; confirm never مسجد. |
| بھرپوری (fullness, NEW) | Crowded neighborhood risk unique to this doctrine: 1:23’s “fills all in all” risks a wahdat al-wujud (unity-of-being)-adjacent pantheistic misreading in Urdu religious-literary register, where “fullness/filling” language is a recognized Sufi devotional trope for the dissolution of creature into Creator. | Every occurrence of بھرپوری applied to Christ/God must carry or reference an explicit Creator/creature-distinction note. Do not let 1:23, 3:19, and 4:13 be taught in isolation from each other — their combined sense (Christ’s own completeness; being filled with God’s fullness; growing toward Christ’s fullness) is relational and participatory, never ontological merger. |
1.4 Unity of Jews and Gentiles in One New Humanity
| Available Urdu terms | Weakness | Recommended strategy |
|---|
| غیر قوموں (Gentiles), اسرائیل (Israel), عہد (covenant), وعدہ (promise) — [BASELINE] | No new weakness beyond baseline; reuse exactly. | Confirm reuse; never کافر, never ummah-framing (per baseline universal_scope_of_gospel and unity_of_jews_and_gentiles doctrine notes). |
| درمیان کی دیوار (dividing wall, NEW); ایک نیا انسان (one new man/new humanity, NEW) | The single most important missing-vocabulary decision in this doctrine: Urdu has a ready-made word for “a single people transcending prior ethnic/tribal division” — امت (ummah) — which is closer in surface meaning to Paul’s “one new man” than almost any other false-friend in this entire package, because ummah genuinely is a supersessionist unity-concept (transcending Arab/non-Arab, tribal identity) in Islamic self-understanding. This is a crowded semantic neighborhood, not a missing-vocabulary problem: the available word is dangerously close, not absent. | Never use امت for ایک نیا انسان under any circumstance (this extends, with much sharper stakes, the baseline’s general fellowship/church avoidance of امت). Every occurrence of “one new man” must explicitly anchor the ground of this new humanity to union with the specific crucified-and-risen Christ (2:14-16), not merely to shared new identity — the mechanism, not just the result, is what differs from ummah. Mandatory theologian review. |
| ساتھ کے وارث (fellow heirs, NEW) | Low risk; extends established وارث cleanly. | No change needed. |
1.5 The Mystery of Christ Revealed
| Available Urdu terms | Weakness | Recommended strategy |
|---|
| راز (mystery, NEW) | The sharpest crowded-semantic-neighborhood problem in the entire letter, colliding with two separate established Islamic vocabulary categories simultaneously: (1) الغیب (al-ghayb, “the unseen”) — knowledge the Qur’an states is reserved to Allah alone and withheld from humanity (Qur’an 27:65); راز used carelessly could sound like a claim to forbidden, unlawfully-accessed knowledge; (2) عرفان/کشف (‘irfan/kashf) — Sufi esoteric knowledge attained through spiritual discipline by an elite (a wali or pir), which راز could equally sound like if framed as something Paul “achieved” rather than received. Ephesians’ μυστήριον is the theological inverse of both: sovereignly disclosed, openly, to all believers, through ordinary apostolic preaching. | No better single Urdu word exists than راز; the fix is framing, not lexical substitution (structurally identical to the baseline’s own son_of_god pattern: the word is not the problem, the unflagged claim is). Mandatory explicit clarifying frame at first occurrence in every document (“a raaz that was hidden but is now openly told to everyone, not a secret kept from people or a knowledge only a few holy people can reach”). Mandatory theologian review, every occurrence, per registry. |
| دلیری اور رسائی (access/boldness, NEW) | Genuine positive-contrast term: direct, unmediated access to God, no priestly or intercessory gatekeeper required. | Reuse as recorded; actively teach the contrast with salat’s formal, mediated approach and with Islamic intercession doctrine (Muhammad’s future intercession) rather than treating this only as a risk to manage — it is one of this letter’s clearest apologetic opportunities. |
| انتظام / امانت داری (stewardship, NEW) | Low risk. | No change. |
1.6 Spiritual Warfare and the Armor of God
| Available Urdu terms | Weakness | Recommended strategy |
|---|
| فضا کی طاقت کا حاکم (prince of the power of the air, NEW); حکمرانیاں / اختیارات / تاریکی کے حکمران / شریر روحانی طاقتیں (principalities/powers, NEW) | Genuine shared-ground doctrine, not a missing-vocabulary gap — Islamic cosmology has fully developed categories (شیطان Shaitan, ابلیس Iblis, جن jinn) affirming real personal spiritual evil, arguably the richest point of structural agreement anywhere in this Language Package. The risk is therefore over-mapping, not absence: a reader may assume one-to-one equivalence with jinn-affliction folk categories, importing an entire live exorcism-and-amulet practice framework Ephesians does not address. | Teach on Ephesians’ own narrative terms (an organized hierarchy, already defeated at the cross, subject to Christ’s exalted lordship, 1:21) without either denying the real overlap or asserting full equivalence. Recommend native-speaker cultural review (not only theological) given active folk-Islamic jinn-affliction practice in Urdu-speaking communities — this is one of the few places in the package where a cultural-context reviewer’s input is as load-bearing as a theologian’s. |
| خدا کی پوری زرہ بکتر (armor of God, NEW) | Missing-vocabulary risk on the offensive-weapon side: Urdu military/religious register has an extremely charged available word for righteous struggle — جہاد (jihad) — immediately adjacent in meaning-space to “spiritual warfare,” “struggle” (πάλη), and “sword.” This is a crowded neighborhood of the highest stakes: unlike ummah or taqdir, جہاد carries live contemporary geopolitical and legal connotations in Urdu-speaking contexts. | جہاد is not on any approved list and must be treated as an absolute forbidden substitution, on par with کافر and اسلام in the baseline’s forbidden list — recommend promoting this to the Language Package’s forbidden-substitution list at the next translation_memory.json version increment. کشمکش (wrestling/struggle) and پوری زرہ بکتر (full armor) must carry the passage’s own explicit restraint: the only offensive item named is “the word of God” (6:17); no other martial vocabulary should be introduced even for literary color. |
| روح کی تلوار، یعنی خدا کا کلام (sword of the Spirit = word of God, NEW) | Low-medium; but see above. | Reuse as recorded; connect explicitly to baseline inspiration_of_scripture doctrine note distinguishing Scripture from the Qur’an’s own final-revelation claim. |
1.7 Household Codes and Christ-Centered Relationships
| Available Urdu terms | Weakness | Recommended strategy |
|---|
| تابع ہونا (mutual submission, NEW); سر (headship, NEW) | Direct structural collision, not merely a shared-vocabulary risk: Surah an-Nisa 4:34’s qawwamun (“men are the protectors/maintainers of women”) is a live, well-known, comparably structured household-authority text. This is Ephesians’ equivalent of Galatians’ circumcision problem — a currently practiced, actively taught framework, not a historical curiosity. | 5:21 (mutual submission) must never be separated from or subordinated to 5:22-33 in translation unit boundaries — always rendered and taught as one continuous unit so that the mutual frame governs the wife-specific instruction that follows. 5:23’s سر must never appear without 5:25’s self-sacrificial-death definition attached in the same teaching unit. The base translation itself must not stage a direct comparison with 4:34 (per baseline’s Hagar/Sarah-style rule: comparative engagement belongs in supporting doctrinal material, never the translated text). Mandatory theologian review, entire unit 5:21-33. |
| ایک تن (one flesh, NEW) | See §1.3 above (fencing against جسم). | Confirm distinct lexical choice; translator’s note at first occurrence. |
| غلام / مالک (bondservants/masters, NEW) | Live social-realia risk (contemporary domestic and bonded labor in South Asia), not a purely lexical one. | Never politicize toward a named community; teach the passage’s relativizing logic (a shared heavenly Master, 6:9) with explicit application to modern employer-employee ethics, per 08_core_glossary.md. مالک must remain visibly distinct from the divine title خداوند in every sentence where both could appear (e.g., 6:5-9’s own text). |
1.8 Gifts for Building Up the Church
| Available Urdu terms | Weakness | Recommended strategy |
|---|
| رسول (apostle), نبی (prophet) — [BASELINE]; مبشر (evangelist, NEW); چرواہا (pastor, NEW); معلم (teacher, NEW) | معلم is a crowded-neighborhood risk: ustadh/‘alim (the authoritative religious-law teacher) is a well-established, socially weighty office in Urdu-speaking Muslim communities, carrying an expectation of durable, hierarchical, near-permanent authority over a student’s religious formation — structurally similar to the Galatians baseline’s paidagogos caution but here applied to a positive, ongoing New Testament office rather than a temporary, expiring one, which makes the fencing job harder (the NT teacher is not temporary, but is nonetheless not an independent authority parallel to the ulama). | Frame every occurrence of معلم under Christ’s own headship and the fivefold gifts’ shared, interdependent equipping purpose (4:11-13), never as an independent authority structure. Distinguish explicitly: unlike paidagogos, this office does not expire, but unlike ‘alim, it has no independent doctrinal authority apart from and unaccountable to the whole body. |
| مہر لگانا / روح سے بھر جانا / روح القدس کو غمگین کرنا (sealed / filled / grieved, NEW) | All three inherit the baseline روح القدس Critical risk (Qur’anic ruh al-qudus/Jibreel identification). | Recommend that 4:30 (“grieve not the Spirit”) and 5:18 (“be filled with the Spirit”) be specifically flagged in teaching material as the letter’s strongest available texts for teaching the Spirit’s full personhood, since both verbs presuppose a relational, willing, personal Agent incompatible with an impersonal-force or created-angel reading. |
1.9 Walking in Newness of Life
| Available Urdu terms | Weakness | Recommended strategy |
|---|
| چلنا / چال چلن (walk/conduct, NEW) | Genuine, low-risk bridge point with Islamic سیرت/صراط (“path,” as in Sirat al-Mustaqim, the “straight path” of Surah al-Fatihah) — a rare case in this package of helpful overlap rather than dangerous overlap. | Reuse as a positive bridge; keep the New Testament sense explicit in supporting teaching (a Spirit-empowered pattern of life flowing from a completed salvation already received, not a path walked toward earning standing before God — the reverse sequence from the sirat/mizan framework). |
| پرانا انسان / نیا انسان (old man/new man, NEW); اتار دینا / پہن لینا (put off/put on, NEW) | Low-medium; standard clothing-metaphor vocabulary. | No change; connect explicitly in teaching to corporate ایک نیا انسان (2:15) per 08_core_glossary.md. |
| نور کے فرزند / تاریکی کے فرزند (children of light/darkness, NEW); نور کا پھل (fruit of light, NEW) | Low-medium; parallels established روح کا پھل singular-fruit framing. | No change. |
2. Missing Vocabulary vs. Crowded Semantic Neighborhoods — Summary Table
This table separates the two distinct gap types the PRD requires be distinguished, since they call for opposite remediation strategies (coin/compound a new term vs. fence an existing term).
2.1 True Missing Vocabulary (no adequate single Urdu word exists; compound phrase or new coinage required)
| Concept | Gap | Resolution |
|---|
| τέκνα φύσει ὀργῆς (children of wrath by nature) | No single word for “condition inherited from birth, prior to any act, deserving judgment” | فطرتاً غضب کے فرزند (compound; فطرتاً is the irreplaceable load-bearing word) |
| νεκρός (spiritually dead, total incapacity) | No word for “spiritually dead” distinct from “weak” or “sick” | مرے ہوئے, always with the surrounding clause “trespasses and sins” attached, never standing alone |
| ἔργα (unqualified works, 2:9) | No word for “human deeds in general” that avoids activating the mizan frame | No substitute exists; fence procedurally (see §1.1) rather than lexically |
| συζωοποιέω/συνεγείρω/συγκαθίζω (made alive/raised/seated with Christ) | No single verb for participatory positional union; Urdu must use three separate compound verbs | مسیح کے ساتھ زندہ کیا / ساتھ اٹھایا / ساتھ بٹھایا (triad, always kept together as a unit) |
| πλήρωμα applied to a Person (fullness) | No word distinguishing “God’s active personal fullness/presence” from generic “completeness” | بھرپوری, always with explicit Creator/creature-distinction framing attached |
| παρρησία/προσαγωγή (bold, direct, unmediated access) | No single word capturing both boldness and unmediated approach together | دلیری اور رسائی (compound pair) |
2.2 Crowded Semantic Neighborhoods (an available Urdu word exists but is already claimed by a competing framework; fencing/framing required, not coinage)
| Urdu term | Competing occupant of the semantic space | Fencing strategy |
|---|
| اعمال / نیک اعمال | Mizan (deeds weighed at judgment, qiyamat) | Never quote 2:9 apart from 2:10; never insert artificial law-qualifier |
| راز | (1) الغیب — withheld/forbidden knowledge; (2) عرفان/کشف — elite-attained esoteric knowledge | Mandatory disclosure-not-withholding, all-not-elite framing note at first occurrence |
| بھرپوری | Wahdat al-wujud (Sufi unity-of-being) | Explicit Creator/creature distinction every occurrence |
| ایک نیا انسان | امت (ummah, transcending-tribal-division community) | Never render/gloss via ummah; always anchor to union with the crucified/risen Christ specifically |
| سر / تابع ہونا | Qur’an 4:34 qawwamun household-authority framework | 5:21 and 5:22-33 always one translation unit; 5:23 and 5:25 always one teaching unit |
| معلم | Ustadh/‘alim (durable religious-law-teaching authority) | Frame under Christ’s headship and shared, interdependent fivefold-gift equipping |
| خدا کی پوری زرہ بکتر / کشمکش | جہاد (jihad) | جہاد treated as forbidden substitution; only offensive item is “the word of God” |
| حکمرانیاں / اختیارات (principalities/powers) | جن / شیطان / ابلیس (jinn/Shaitan/Iblis folk cosmology) | Teach on Ephesians’ own narrative terms; avoid one-to-one feature mapping; native cultural-context review recommended |
| خوشبودار قربانی | Qurbani (Eid al-Adha commemorative sacrifice) | Distinguish commemorative-symbolic from substitutionary-atoning function every occurrence |
| رحمت / فضل | Rahmat (Allah’s mercy operating within the mizan framework) | Keep the two Urdu words visibly distinct within 2:4-8 so ἔλεος/χάρις remain separable |
| نجات | Najat (mercy-weighed-against-deeds at qiyamat) | Explicit contrastive note wherever doctrinally load-bearing, sharpened here by 2:8’s perfect tense |
| خدا کا انتخاب / پہلے سے مقرر کیا گیا | تقدیر (taqdir, Ash’ari/Mu’tazila qadar debate) | Never substitute; dedicated 1:3-14 sidebar given unusual doctrinal density |
3. Transliteration vs. Paraphrase Decisions
Per the baseline’s transliteration standards, the following table records Ephesians-specific decisions not already fixed by the baseline proper-noun table.
| Source term | Decision | Rationale |
|---|
| ἀρραβών (guarantee/pledge) | Paraphrase using existing Urdu commercial-legal vocabulary (بیعانہ), not transliteration or coinage | An exact, familiar, non-religious Urdu legal term already exists; transliterating a Greek loanword here would sacrifice real clarity for no gain. |
| μυστήριον (mystery) | Paraphrase using راز, not transliteration (e.g., not “میسٹیریان”) and not substitution with غیب/کشف vocabulary | Transliteration would be unintelligible to the reading-level target audience; the native word راز is correct but requires framing, not replacement (see §1.5, §2.2). |
| ἀγάπη / πανοπλία / other Greek technical terms in the armor unit | Paraphrase throughout, no transliteration | Consistent with established pipeline practice; the armor list is meant to be immediately visualizable in the reader’s own language, not marked as foreign technical vocabulary. |
| Ἀββά (Abba, inherited from Romans baseline, not textually present in Ephesians but relevant to the Father doctrine at 1:2-3, 17; 2:18; 3:14; 4:6) | Retain baseline’s transliteration decision (ابّا) wherever cross-referenced | Consistency rule; no new decision needed, flagged here only to confirm no divergence. |
| Ἐφεσίοις (book name, Ephesians) | Transliterate per Urdu Bible Society convention: افسیوں (Afsiyõ) | Follows the same convention pattern as رومیوں (Romans) and گلتیوں (Galatians) already fixed in the baseline; must be added to the Cross-Reference Preservation Rules at the next 12_ai_translation_requirements.md revision. |
| Proper names newly appearing in Ephesians (none beyond baseline: no new named individuals requiring a fresh transliteration decision beyond Paul, already فیPaulus/پولس) | No new decision required | Ephesians introduces no new proper names requiring transliteration beyond the existing baseline table (Paul, David not present, etc.). |
| πνευματικῆς πονηρίας / κοσμοκράτορες (spiritual forces of evil, cosmic rulers) | Paraphrase with a fenced descriptive compound, not a single transliterated or Islamic-cosmology loanword | See §2.2; borrowing جن/شیاطین vocabulary directly would import unwanted one-to-one mapping; a descriptive Urdu compound (شریر روحانی طاقتیں, تاریکی کے حکمران) keeps the concept native to the passage’s own terms. |
General rule confirmed for this letter: Ephesians requires almost no new transliteration decisions beyond the baseline table — its translation-strategy center of gravity is overwhelmingly paraphrase-with-fencing (crowded neighborhoods) and compound-phrase coinage (missing vocabulary), not transliteration. This is a different profile from, e.g., Galatians’ heavier reliance on retained technical terms (paidagogos → نگہبان as a functional paraphrase, similarly).
4. Ranked List of Highest-Risk Ambiguities in Ephesians
Ranked by combined severity (doctrinal centrality × collision specificity × likelihood of silent mistranslation), for review-routing prioritization in Phase 2.
- مسیح کے ساتھ زندہ کیا / ساتھ اٹھایا / ساتھ بٹھایا (2:5-6) — union-with-Christ language that must resist a wahdat al-wujud ontological-merger reading while simultaneously carrying the full baseline crucifixion/resurrection-denial risk (Qur’an 4:157) in its background. Two Critical risks stacked in two verses.
- فطرتاً غضب کے فرزند (2:3) — direct textual collision with fitrah; the single most specific negation-point in Ephesians, structurally parallel to the baseline’s treatment of Sonship of Christ.
- اعمال (2:9) separated from نیک اعمال (2:10) — highest-probability silent mistranslation risk in the whole letter, because both halves are individually easy to render correctly while the pairing (which is where the doctrine actually lives) is the part most likely to be lost in segment-by-segment processing.
- سر / تابع ہونا (5:21-33) — direct structural collision with Qur’an 4:34; risk of the mutual-submission frame (5:21) being silently dropped or treated as a separate unit from the wife-specific instruction, inverting Paul’s argument.
- راز (1:9; 3:3-9; 5:32; 6:19) — double collision (ghayb-withholding and kashf-attainment); high recurrence across the letter increases exposure if the first-occurrence framing note is not carried forward to later occurrences.
- ایک نیا انسان (2:15) — the ummah false-friend; among the most fluent-sounding, most easily unflagged mistranslations in the package because the surface meaning is unusually close to the correct one.
- خدا کی پوری زرہ بکتر / کشمکش (6:10-17) — جہاد-adjacency; risk is less about doctrinal content and more about register, where a translator reaching for vivid martial vocabulary could inadvertently introduce forbidden terminology with serious real-world consequences.
- بھرپوری (1:23; 3:19; 4:13) — pantheism-adjacent misreading risk, compounded by occurring three times with three different grammatical subjects (Christ fills; believers are filled with; believers grow toward), each requiring separate but consistent handling.
- خوشبودار قربانی (5:2) — atonement/crucifixion-denial risk wearing the deceptively familiar clothing of Eid qurbani vocabulary, raising the likelihood a reviewer treats it as low-risk shared vocabulary rather than flagging it.
- پہلے سے مقرر کیا گیا / اپنی مرضی کی خوشی کے مطابق (1:5, 9, 11) — taqdir-adjacency at unusually high density (three occurrences in seven verses), raising cumulative exposure even though each individual term is independently well-fenced.
- حکمرانیاں / اختیارات (6:12, cf. 2:2, 1:21) — jinn/Shaitan over-mapping risk; distinct from ranking #7 in that the danger here is excessive equivalence-claiming by well-meaning teachers rather than vocabulary borrowing.
- معلم (4:11) — ustadh/‘alim permanent-authority reading; lower doctrinal stakes than items above but high likelihood of unreflective use given how embedded the word’s religious-authority connotation already is in everyday Urdu.
- مالک vs. خداوند (6:5-9 alongside 6:9’s “your Master and theirs”) — risk of the two titles blurring within the same short passage, diluting Lordship’s exclusive divine weight.
- ایک تن vs. جسم vs. بدن (5:31 vs. throughout) — low doctrinal stakes per single occurrence, but high cumulative risk of translator drift across a long document if the three-way distinction is not actively enforced segment-by-segment.
- دلیری اور رسائی (3:12) — lowest risk on this list, included because it is the letter’s clearest positive apologetic opportunity and is therefore at risk of being under-taught (treated as merely safe rather than actively leveraged) rather than mistranslated.
The following gap-analysis findings should be formalized as explicit rule additions at the next translation_memory.json / 12_ai_translation_requirements.md version increment (beyond the term-level entries already staged in 08_core_glossary.md):
- Add جہاد to the CRITICAL FORBIDDEN SUBSTITUTIONS list (armor/spiritual-warfare context), alongside کافر, اسلام, دعوت/تبلیغ, اللہ, bare عیسیٰ.
- Add a procedural pairing rule (not just a term rule): Ephesians 2:9 and 2:10 must never be translated, cached, or reviewed as independent segments — flag at the segmentation stage, before translation begins, not only at validation.
- Add افسیوں to the Cross-Reference Preservation Rules book-name table.
- Add a triple-fence rule for جسم / بدن / ایک تن requiring an automated same-document consistency check flagging any cross-substitution among the three.
- Add native-culture cultural-context review (distinct from theologian and native-speaker linguistic review) as a fourth review track specifically for 6:12’s principalities/powers unit, given live folk-Islamic jinn-affliction practice — this may require a routing category not yet present in
doctrine_risk_registry.json’s three-tier review_routing field.
This analysis extends but does not alter any baseline translation_memory.json entry. All new-term recommendations above are already reflected in 08_core_glossary.md and assets/bible_term_registry.json; this document’s contribution is the explicit missing-vocabulary/crowded-neighborhood classification, the transliteration-vs-paraphrase rationale, and the cross-doctrine risk ranking required for Phase 2 review routing.