Linguistic Gap Analysis: 1 John (English/Greek → Urdu)

Purpose and Scope

This document executes Phase 1 Step 8 for the 1 John curriculum. It does three things the glossary (08) and term registry do not do on their own:

1. Maps each of the eight assigned doctrines against the actual available Urdu vocabulary, naming precisely where the language is rich, where it is thin, and where the “available” word is available only because it is shared with a competing theological system.
2. Separates two structurally different problems that this Language Package’s baseline document (12_ai_translation_requirements.md) already distinguishes for Urdu generally: missing vocabulary (no natural word exists, requiring paraphrase or coinage) versus crowded semantic neighborhoods (a natural word exists but sits inside, or directly beside, live Islamic theological or devotional territory and must be fenced with explicit teaching).
3. Ranks 1 John’s highest-risk ambiguities for downstream Phase 2 review routing, extending (not duplicating) the doctrine_risk_registry’s existing Critical/High tiers with book-specific reasoning.

Urdu’s governing categorical fact, inherited from the baseline and confirmed again in this book: the dominant risk type is negation (a specific, named Qur’anic verse denies the doctrine outright) rather than syncretism (a word quietly imports a different, unnamed concept). 1 John intensifies this because it is the New Testament book most saturated with exactly the three claims Qur’an 4:157 and Qur’an 112 target hardest — incarnation (4:2-3), divine sonship (2:22-23; 4:9, 15; 5:5), and, in its own way, an atoning death (2:2; 4:10) — compressed into five short chapters rather than spread across sixteen (as in Romans) or six (as in Galatians). The gap analysis below reflects that compression.

---

Part 1 — Doctrine Vocabulary Matrix

For each of the eight assigned doctrines: the Urdu terms actually available, their specific weaknesses, and the recommended handling strategy. This matrix operationalizes the glossary (08) and registry entries into deployable Phase 2 guidance.

1.1 God is Light and God is Love

Available Urdu term(s)	Weakness	Recommended strategy
محبت (muhabbat) for ἀγάπη	Rich, warm, immediately intelligible word — the opposite problem from a missing-vocabulary gap. It is fully naturalized in Islamic devotional vocabulary (al-Wadūd, Qur’an 11:90, 85:14) and Sufi maḥabbah/ʿishq. A fluent reader will supply their own theological content for what “God is love” means unless stopped.	Never let خدا محبت ہے (4:8, 16) stand as a bare predication. Every occurrence must forward-reference 4:9-10’s content (the sending and death of the Son) as the definition of the love being claimed, not an example of it. Treat as Critical, per registry.
نور (nūr) for φῶς	Same shape of problem as محبت, more acute: نور is not merely devotional vocabulary but sits inside a specific, named Qur’anic verse (24:35, Āyat an-Nūr) and a developed doctrinal-mystical tradition (Nūr Muḥammadī) in which light is treated as a quasi-substance or pre-existent created reality flowing from Muhammad.	Mandatory clarifying note at first occurrence (1:5) fencing 1 John’s content as ethical/relational (truthful confession, moral purity, functioning fellowship) rather than cosmological. Do not attempt a competing cosmological claim of any kind — sidestep the metaphysics entirely and stay inside 1 John’s own diagnostic use (1:6-7, 2:9-10: light and darkness are tested by whether one loves the brethren and confesses sin, not by any light-substance claim).
تاریکی (tārīkī) for σκότος/σκοτία	Comparatively low risk; standard moral-relational vocabulary.	Reuse directly, still framed as darkness = broken fellowship/self-deception/hatred, not a rival evil-substance.

Net assessment: this doctrine’s vocabulary is not missing — it is oversupplied by both traditions independently, which is the more dangerous condition. The gap is not lexical but framing: Urdu has no natural way to mark “this is a narrower, specific, cross-shaped claim” through word choice alone; that work must be done by mandatory annotation, not by term selection.

1.2 Fellowship with God and One Another

Available Urdu term(s)	Weakness	Recommended strategy
رفاقت (rifāqat) for κοινωνία [TM-REUSE]	Low risk on its own (already vetted in the baseline against امت). Its weakness in 1 John specifically is structural, not lexical: the term does not on its own carry the letter’s deliberate double axis (vertical, with the Father and Son, 1:3; horizontal, with one another, 1:7), nor its explicit condition (walking in the light).	Teach the dual-axis structure explicitly wherever 1:3 and 1:7 are handled together; رفاقت itself needs no change.
قائم رہنا / رہنا (qā’im rahnā) for μένω	This is the doctrine’s real gap. Urdu has ordinary words for “to remain/stay” (رہنا) but none that natively carries Johannine mutual indwelling (God abiding in the believer, the believer abiding in God) without either (a) sounding like mere duration/continuance, or (b) drifting, if pushed toward mystical-union vocabulary, toward Sufi wahdat al-wujūd (“unity of being”) territory where the Creator-creature distinction dissolves.	Use قائم رہنا (not bare رہنا) consistently as the anchor term, paired at first occurrence (2:6) and at the doctrinally dense cluster (4:12-16) with an explicit note: relational, covenantal, two-party communion, not ontological merger. Native speaker + theologian review at every occurrence, per glossary.
بھائی (bhā’ī) for ἀδελφός	Warm and correct, but its natural semantic neighborhood in Urdu religious discourse is crowded by ikhwān/ummah-brotherhood (universal Muslim fraternity), a concept 1 John’s “brother” does not intend (born-again family specifically, not humanity or co-religionists generally).	No substitution needed; fence with a brief note at first occurrence (2:9) distinguishing the born-again-family referent from the broader Islamic brotherhood concept, especially before 3:10-17 and 4:20-21’s diagnostic uses.

1.3 Confession and Forgiveness of Sin

Available Urdu term(s)	Weakness	Recommended strategy
اقرار کرنا (iqrār karnā) for ὁμολογέω, both senses	Not a missing-vocabulary problem but a single-verb, two-object problem: the same Urdu verb root serves both the low-risk “confess sins” (1:9) and the Critical-risk “confess Jesus is the Son of God / come in the flesh” (2:23; 4:2-3, 15; 5:1, 5). Because the verb itself carries no risk marker, a careless Phase 2 pass could treat every اقرار کرنا occurrence as uniformly low-risk.	Tag by object, not by verb, in all downstream review routing: گناہوں کا اقرار کرنا (sin-confession) routes Medium/native-speaker; Christological اقرار کرنا routes Critical/theologian automatically, regardless of surrounding sentence simplicity.
معافی / معاف کرنا (mu’āfī) for ἀφίημι/ἄφεσις	Fully naturalized, unavoidable, and doctrinally thin on its own: it is also the ordinary word for Allah’s maghfirah, granted through mercy in direct response to repentance, with no mediating atonement.	Never permit 1:9/2:12 forgiveness language to stand unanchored; every doctrinally load-bearing occurrence must trail back to 1:7/2:2’s blood-atonement ground. This is a fencing problem, not a missing-word problem — no alternative Urdu word solves it, exactly as the baseline treats نجات.
پاک کرنا (pāk karnā) for καθαρίζω	Shares the baseline’s پاک/holiness caution: risk of assimilation to Islamic ritual-purity law (ṭahāra, wuḍūʾ/ghusl), a legal-ritual category rather than a blood-atonement category.	Pair with 1:7’s “blood of Jesus” every time cleanse is doctrinally load-bearing (1:7, 1:9), not left as a stand-alone moral-improvement claim.
کفارہ (kaffārah) for ἱλασμός	Compound Critical gap. Urdu/Islamic kaffārah is a real, specific, well-known compensatory-obligation category (fasting, feeding the poor, freeing a captive, discharging a still-owed debt) — structurally different from a once-for-all, God-provided, substitutionary sacrifice covering all sin through the death of God’s own Son. It additionally presupposes the crucifixion Qur’an 4:157 denies happened. No unshared alternative exists; a coined term would be unintelligible.	Retain کفارہ (it is the only term a reader will recognize as naming this concept at all) but require the same mandatory contrastive note as the baseline’s redemption/curse entries at every occurrence (2:2; 4:10), never merely at first occurrence — this term recurs at the letter’s two most Christologically dense points.
مدافع (mudāfi’) for παράκλητος	Coined/selected specifically to avoid collision with شفاعت (intercession, baseline Medium), which in live Islamic usage centers on Muhammad’s future, permission-granted intercession at judgment. مدافع itself is a normal Urdu word (advocate/defender) with no independent theological loading, which is exactly why it was chosen — but its very unfamiliarity in a specifically Christological sense is itself a minor gap.	Introduce with a one-line functional gloss at first occurrence (2:1): “one who pleads Christ’s own righteousness on the believer’s behalf, now, before the Father” — distinguishing tense (present, finished-work-grounded) and grounds (his own atonement, not granted permission) from shafā’at.

1.4 Love for the Brethren as Evidence of New Birth

Available Urdu term(s)	Weakness	Recommended strategy
محبت / محبت کرنا, reused from §1.1	No additional lexical gap; the risk here is tonal/ethical rather than referential — 1 John uses this vocabulary as a diagnostic test with a blunt negative verdict (4:20: professed love of God + hatred of a brother = جھوٹا, liar).	Preserve the bluntness. Do not soften جھوٹا or the conditional structure of 3:17/4:20 to reduce honor/shame social friction, per the baseline’s general anti-dilution rule.
موت سے زندگی میں منتقل ہونا for the 3:14 assurance clause	This is a constructed compound, not a single lexical item — English/Greek has no single-word equivalent either, so this is a shared, not Urdu-specific, gap.	Treat as a fixed liturgical-style phrase once coined; keep it identical wherever the letter’s assurance material (3:14; cf. 5:13) is cross-referenced.
قابیل / ہابیل for Κάϊν/Ἄβελ	No gap — shared proper names with the Qur’an’s own parallel account (5:27-31), differing somewhat in emphasis.	Low-friction; a brief note on the narrative-detail differences is optional, not mandatory.

1.5 The Incarnation and Antichrist

This is the doctrine cluster with the fewest true vocabulary gaps and the highest framing stakes in the entire book — the terms are all already settled in the baseline; the work is entirely in annotation discipline.

Available Urdu term(s)	Weakness	Recommended strategy
مجسم ہونا [TM-REUSE] for “come in the flesh” (4:2-3)	No lexical gap. The weakness is historical-directional: 1 John 4:2-3 was originally aimed at a docetic denial of Christ’s real humanity (opposite error-direction from Islamic theology’s typical denial of his deity while affirming his humanity). A flattened teaching note that treats “the error 1 John opposes” and “the error a Muslim reader is likely to hold” as the same thing will mislead in both directions.	Name both error-directions explicitly and separately every time 4:2-3 is taught: (a) the ancient docetic denial of real humanity, which the verse directly refutes; (b) the reader’s own likely instinct, denial of deity while affirming humanity, which the verse’s wider letter-context (2:22-23; 5:5) refutes. Do not conflate the two into one generic “some people deny this” statement.
خدا کا بیٹا / اکلوتا بیٹا [TM-REUSE / extended]	No lexical gap; اکلوتا was specifically selected over any phrase implying literal generation. The risk is entirely in omission — every occurrence without the mandatory note reopens the Qur’an 112:3 collision.	Treat the eternal-not-begotten annotation as non-negotiable at every occurrence in this book, not just at “introduction” points — 1 John repeats the confession five separate times (2:22-23; 4:9, 15; 5:5, 10, 20), each one a fresh occasion for the collision to surface unmitigated if the note is skipped.
مخالفِ مسیح for ἀντίχριστος	The true gap: no existing Urdu/Islamic vocabulary names this specific Johannine concept (a present, diffuse, doctrine-denying spirit already active, 4:3) without reader expectation snapping instead to دجال, a fully developed, well-known, future, single-figure eschatological narrative (defeated by the returning ʿĪsā). This is a false-friend gap: the expected word exists and is wrong.	مخالفِ مسیح (transparent compound, not a loanword) is correct and should stand as the primary rendering. Mandatory note at first occurrence (2:18) naming the دجال expectation directly and distinguishing it structurally (present/diffuse/plural “antichrists” already at work vs. future/singular/climactic figure) rather than hoping the reader will not import it unprompted.
مسح (mas’h) for χρῖσμα	Minor gap: shares its root transparently with مسیح (Masīh), which is instructive but also means an unprepared reader could either (a) miss the connection entirely or (b) over-read it as implying believers become “little messiahs.”	Brief note at first occurrence (2:20) affirming the shared root deliberately (believers derivatively share in Christ’s anointing by the Spirit) while immediately fencing against any elite/esoteric-gnosis reading (2:20 explicitly says “all of you,” not a spiritual elite).

1.6 Assurance of Salvation and Eternal Life

Available Urdu term(s)	Weakness	Recommended strategy
ابدی زندگی [TM-REUSE]	No gap; already established.	Reuse exactly; anchor to نجات continuity per baseline rule.
نجات دہندہ (najāt dahindā) for σωτήρ, extended from baseline	Carries forward the full نجات/mizan contrast (see baseline salvation entry) at a single, unusually concentrated point: 4:14’s “Savior of the world” combines the Critical salvation-mechanism contrast with a universal-scope claim in one clause.	Treat 4:14 as a compound-risk verse requiring both the salvation contrastive note and the universality note (do not reframe “of the world” via ummah/kafir categories) simultaneously — flag for theologian review even though each individual term is independently already flagged elsewhere.
دلیری / اعتماد (dilerī / e’timād) for παρρησία	Genuine and instructive gap-of-contrast rather than a translation problem: Urdu supplies adequate words for “confidence/boldness,” but the disposition itself — settled, present-tense confidence about one’s final standing before God — has no natural devotional home in the target culture’s dominant religious framework, where such confidence before the mīzān-weighing is often viewed as presumptuous.	Do not try to soften this into a more modest-sounding Urdu register to avoid seeming presumptuous by local religious standards — that would blunt the doctrine. Teach explicitly as a respectful, named point of contrast (per baseline’s assurance_of_salvation framing), not an oversight to smooth over.
خدا کے فرزند (Khudā ke farzand) for τέκνα θεοῦ, deliberately distinct from خدا کا بیٹا	No lexical gap — فرزند was specifically selected as a different word family from بیٹا to prevent bleed-through into the Son of God collision.	Enforce as an absolute non-interchange rule (see Consistency Rules in 08); flag any Phase 2 draft that uses بیٹا for believers anywhere in 1 John as an automatic error, not a stylistic variant.
نئے سرے سے پیدا ہونا for γεννάω ἐκ τοῦ θεοῦ	The single largest true vocabulary gap in this entire book. English/Greek itself uses ordinary begetting-language (γεννάω) applied metaphorically to ordinary believers; Urdu has no periphrasis-free way to say this that does not either (a) sound like literal divine procreation applied to many humans (worse than the Son of God problem, because it is pluralized and applied to ordinary people) or (b) lose the “God-originated new life” sense entirely if flattened to a generic “became a believer.”	The periphrastic نئے سرے سے پیدا ہونا (“to be born anew”) is a genuine, deliberate translation solution, not a stopgap — retain it as the fixed rendering at all five occurrences (2:29; 3:9; 4:7; 5:1, 4, 18) with mandatory annotation every time, at the same priority tier as Son of God. This is a paraphrase-over-literalism decision that should not be revisited without full theologian sign-off.
عدالت کا دن (adālat kā din) for ἡμέρα τῆς κρίσεως	Not missing vocabulary but a fencing problem against the wrong baseline term: قیامت is available, fluent, and would be the naturally reached-for word — but the baseline has already reserved قیامت specifically for Christ’s own resurrection with its own distinguishing note, and reusing it here would blur that earlier, hard-won distinction.	Enforce عدالت کا دن as the fixed alternative specifically to protect قیامت’s existing baseline meaning; this is an inter-book consistency safeguard, not merely a 1 John-local choice.

1.7 Overcoming the World

Available Urdu term(s)	Weakness	Recommended strategy
دنیا (dunyā) for κόσμος	Unavoidable and correct lexically, but organizes reality along a different axis than Johannine κόσμος. Islamic ethical discourse pairs dunyā against ākhirah (this life vs. the next life) — a temporal axis. 1 John’s κόσμος is organized along a moral/spiritual axis (the present fallen system in active rebellion against God, vs. life and truth from God), cutting across, not aligned with, the dunyā/ākhirah pairing.	This is a genuine conceptual gap disguised as a lexical non-gap. Do not assume دنیا self-evidently carries 1 John’s sense; make the axis-difference explicit in any teaching material touching 2:15-17, and note the productive (but not identical) resonance with Sufi zuhd (detachment from worldly attachment) as a bridge, while flagging that the two systems still answer different questions.
غالب آنا / فتح (ġhālib ānā / fatḥ) for νικάω/νίκη	No gap in ordinary vocabulary for “victory/overcome” — the gap is a forbidden-neighbor problem: the most tonally adjacent, martially-flavored Urdu-Islamic register for “spiritual struggle/victory” is جہاد, a specific, loaded technical term (in some usages, armed struggle) that would import an effort-based, and potentially militant, connotation exactly backward from 5:4-5’s own grammar (victory already accomplished through faith, appropriated by trust).	جہاد is absolutely forbidden here (extends the doctrine_risk_registry’s forbidden-substitution logic to a new term not previously flagged in the Romans/Galatians baseline). غالب آنا/فتح alone, always tied explicitly to 5:4-5’s faith-grounding, not personal exertion.
جسم کی خواہش, زندگی کا غرور for the 2:16 triad	No new gaps; both extend already-vetted baseline terms (جسم/flesh caution).	Reuse per baseline caution against body-negation asceticism readings.
بت (but) for εἴδωλα	No lexical gap; genuine, differently-defined overlap with shirk (Trinity and Christ’s Sonship are themselves classified by Islamic theology as shirk) makes 5:21’s abrupt closing command land with unusual force for this audience.	Do not let this be read as an easy, low-friction closing verse; flag for native-speaker-plus-theologian review specifically because of what the letter has just spent four chapters affirming (Christ’s Sonship) immediately before commanding avoidance of idolatry — the juxtaposition itself needs pastoral framing.

1.8 Testing the Spirits

Available Urdu term(s)	Weakness	Recommended strategy
روحوں کو پرکھنا for δοκιμάζετε τὰ πνεύματα	No lexical gap; the risk is grammatical/referential — روح alone is structurally identical to the first half of روح القدس (Holy Spirit), and a careless construction could visually or grammatically suggest the Holy Spirit is among the “spirits” subject to testing.	Enforce روح alone (never a construction beginning like or abbreviating روح القدس) for the generic plural “spirits” in 4:1 and the singular contrastive “spirit of truth/error” in 4:6. This is a syntax-level fencing rule, not merely a glossary entry.
روحِ حق / روحِ گمراہی for πνεῦμα τῆς ἀληθείας / πνεῦμα τῆς πλάνης	Low risk on their own.	Reuse as constructed; keep visually and grammatically distinct from روح القدس per above.
موت کا باعث گناہ for ἁμαρτία πρὸς θάνατον	Genuine interpretive gap present even in the source text (scholars disagree on referent); the Urdu-specific risk is a false-analogy gap — Islamic jurisprudence supplies a ready-made, well-known major/minor sin taxonomy (kabīrah/ṣaghīrah) that a reader will likely reach for to make sense of this otherwise difficult category.	Do not map onto kabīrah/ṣaghīrah. Read strictly within 1 John’s own letter-context (apparent reference to settled, unrepentant apostasy/denial of Christ, consistent with 2:19’s departure-language), and flag the interpretive uncertainty itself rather than resolving it falsely via the Islamic taxonomy’s clean categories.
شریر / ابلیس for ὁ πονηρός	No gap; genuinely shared demonological ground.	Low-risk; ابلیس available as an optional specific-reference variant.
حکم / بے شریعتی for ἐντολή and ἀνομία	حکم: no gap, but must not be conflated with شریعت (baseline High-risk Mosaic-Law term). بے شریعتی: shares شریعت’s root and thus its full baseline caution, applied here to 1 John’s own definition of sin generically (3:4), not Torah-specifically.	Keep حکم tied to Christ’s specific relational directives (belief + love, 2:3-8; 3:22-24), never expanded into a legal system. Anchor بے شریعتی to 1 John’s own definition of sin as rebellion against God’s moral order, explicitly distinguished from both شریعت-as-Mosaic-Law and from any implied claim about Islamic sharīʿah as a system.

---

Part 2 — Missing Vocabulary vs. Crowded Semantic Neighborhoods

The matrix above surfaces two structurally distinct kinds of gap. Separating them clearly matters because they require opposite remedies: a missing-vocabulary gap is fixed by coining a periphrasis or compound and then holding it fixed; a crowded-neighborhood gap cannot be fixed by word choice at all and must be fenced by mandatory annotation instead.

2.1 True missing vocabulary (periphrasis/coinage required, no natural single term exists)

Concept	Why no natural term exists	Solution adopted
γεννάω ἐκ τοῦ θεοῦ applied to believers	Ordinary Urdu begetting-vocabulary (پیدائش/جننا) taken literally would assert plural human divine procreation — worse than any existing Islamic taboo language, not merely adjacent to one.	نئے سرے سے پیدا ہونا (periphrasis: “born anew”), fixed, always annotated.
μένω, the Johannine mutual-indwelling sense	Ordinary Urdu “stay/remain” (رہنا) under-carries reciprocal divine-human indwelling; pushing toward stronger union-vocabulary risks a wahdat al-wujūd reading.	قائم رہنا, fixed, with an explicit relational-not-ontological note.
παράκλητος, Christ’s present legal-advocacy sense	شفاعت is already occupied by a different (future, permission-based) doctrine; no unoccupied native word for “present advocate grounded in one’s own finished righteousness” exists.	مدافع, a functionally neutral coinage-by-selection, glossed at first occurrence.
ἡμέρα τῆς κρίσεως, distinct from Christ’s resurrection	قیامت is the natural word but is already committed elsewhere in this Language Package.	عدالت کا دن, fixed substitute, explicitly to protect the prior baseline commitment.
The 3:14 “passed from death to life” assurance clause	No single Urdu (or English/Greek) word covers a completed, one-time transfer between two moral-spiritual states.	Fixed compound phrase موت سے زندگی میں منتقل ہونا.

2.2 Crowded semantic neighborhoods requiring fencing, not substitution

These are cases where Urdu vocabulary is not missing — often it is unusually rich and immediately available — but every available word already has a settled home in Islamic theology or Sufi devotional practice, meaning the fluent reader’s first, unprompted association will not be 1 John’s intended one.

Term	Crowded neighbor(s)	Fencing required
محبت (love)	al-Wadūd; Sufi maḥabbah/ʿishq	Anchor every doctrinal use to 4:9-10’s cross-shaped content
نور (light)	Āyat an-Nūr (24:35); Nūr Muḥammadī	Mandatory ethical-not-cosmological clarifying note
معافی (forgiveness)	maghfirah (unmediated divine pardon)	Anchor to 1:7/2:2’s blood-atonement ground every load-bearing use
کفارہ (propitiation)	kaffārah (compensatory-payment discharge of an owed obligation)	Mandatory contrastive note at every occurrence (2:2; 4:10), not just first
پاک کرنا (cleanse)	ṭahāra ritual-purity law	Pair with “blood of Jesus” language every load-bearing use
شفاعت-adjacent مدافع (advocate)	shafā’at, esp. Muhammad’s future intercession	Distinguish tense and grounding explicitly at introduction
بھائی (brother)	ikhwān/ummah universal brotherhood	Brief note distinguishing born-again family from broader fraternity
رفاقت (fellowship)	ummah (rejected per baseline already)	No new fencing needed; baseline rejection already covers this
دنیا (world)	dunyā/ākhirah temporal axis	Explicit axis-difference note wherever 2:15-17 is taught
غالب آنا/فتح (overcome)	جہاد (forbidden neighbor)	Absolute prohibition on جہاد-adjacent vocabulary
مخالفِ مسیح (antichrist)	دجال (specific, well-known, structurally different narrative)	Mandatory distinguishing note naming دجال directly
مسح (anointing)	root-shared with مسیح; adjacent to Sufi maʿrifah/gnosis elitism	Fence against elite-endowment reading; stress “all of you” (2:20)
بت (idols)	shirk (differently defined — includes Trinity/Sonship in Islamic theology)	Direct comparative-theology engagement at 5:21, not silent avoidance
عدالت کا دن (day of judgment)	yaum al-qiyāmah/yaum ad-dīn	Anchor Christian confidence in Christ specifically, not shared eschatological expectation alone
موت کا باعث گناہ (sin unto death)	kabīrah/ṣaghīrah taxonomy	Read within letter’s own apostasy-context; do not map onto the Islamic taxonomy

---

Part 3 — Transliteration vs. Paraphrase Decisions

1 John forces more transliteration-vs-paraphrase decisions per chapter than any other book in this Language Package to date, because its Christological confessions are so densely repeated. The governing principle, extending the baseline: transliterate/retain a shared term only where the shared recognition itself is doctrinally useful and the risk is manageable by annotation; paraphrase (build a transparent Urdu compound) wherever the available loanword’s competing content cannot be safely annotated around.

Term	Decision	Reasoning
μονογενής (4:9)	Paraphrase: اکلوتا بیٹا, not a transliterated technical term	No Greek-derived loanword exists in Urdu religious register for this; a literal begetting-construction would be far worse than paraphrase. اکلوتا (“unique, one-of-a-kind”) carries the needed sense without asserting generation.
ἀντίχριστος (2:18, 22; 4:3)	Paraphrase, not transliteration or borrowed-Islamic-equivalent: مخالفِ مسیح	Transliterating “antichrist” directly would be unintelligible to most readers; borrowing دجال (the tempting “equivalent”) would import a wrong, structurally different narrative. The transparent Urdu compound “opponent of the Messiah” is safer than either extreme.
ἱλασμός (2:2; 4:10)	Retain the shared Arabic-derived term کفارہ, heavily fenced	Here transliteration/retention is preferred over paraphrase specifically because no paraphrase would be more intelligible — کفارہ is the only word a reader will recognize as naming “atoning payment for sin” at all. The risk is managed by mandatory contrastive annotation, not by avoiding the word.
χρῖσμα (2:20, 27)	Translate with the cognate root مسح, not a fresh coinage	Deliberately keeping the مسیح-root visible is a rare case where shared-root recognition is doctrinally useful (believers share derivatively in Christ’s own anointing) rather than merely risky, provided it is fenced against elitist over-reading.
γεννάω ἐκ τοῦ θεοῦ	Paraphrase: نئے سرے سے پیدا ہونا, never a literal-begetting construction	See Part 2.1; literal transliteration is not even at issue here (there is no Greek loanword route), but the same logic that would forbid transliterating a dangerous loanword applies to forbidding a dangerously literal native construction.
παράκλητος (2:1)	Paraphrase: مدافع, deliberately NOT the transliterated “پیراکلیت” sometimes seen in academic contexts, and NOT شفاعت	A transliteration would be opaque to the target reading level (Class 8-10 per the baseline’s reading-level target); شفاعت would import the wrong doctrine. مدافع is a plain, intelligible Urdu word repurposed with a glossing note.
Ἀβαδδών / proper names generally (Cain, Abel, etc.)	Transliterate in established Christian Urdu forms	Standard baseline practice; no new decision required — قابیل/ہابیل, already shared with the Qur’an’s own transliteration tradition.
θεός, Ἰησοῦς, υἱὸς θεοῦ	Retain baseline transliteration/rendering choices exactly (خدا, یسوع, خدا کا بیٹا)	No new decision; 1 John introduces no reason to revisit these settled baseline choices, only to apply them with unusually high repetition-density (see Part 4).

---

Part 4 — Ranked List of 1 John’s Highest-Risk Ambiguities

Ranked by combined severity (doctrinal centrality × collision explicitness × repetition frequency in this specific letter). All items below require, at minimum, human theologian review per the doctrine_risk_registry conventions; ranking determines review priority sequencing within Phase 2, not exemption from review.

1. Confession of the Son of God / Christ come in the flesh (2:22-23; 4:2-3, 15; 5:1, 5, 10, 20) — the letter’s own explicit test of true faith is also the single sharpest collision point with tawhid (Qur’an 4:48, 4:116, 112:3) and with the crucifixion denial (Qur’an 4:157) simultaneously, and it recurs five to seven times depending on how boundaries are drawn. No other book in this pipeline compresses this much Critical-tier repetition into this little text.

2. “Born of God” applied to ordinary believers (2:29; 3:9; 4:7; 5:1, 4, 18) — arguably harder pastorally than #1 precisely because it is not about Christ’s unique status but generalizes begetting-language to many ordinary humans; a careless literal rendering would read as a stranger and more expansive claim than the Son of God title alone.

3. Propitiation/κfārah compound risk (2:2; 4:10) — the single term in this book carrying two independently Critical risks at once (a different soteriological mechanism than Islamic kaffārah, plus the upstream crucifixion-denial presupposition), appearing at the letter’s argumentative hinge points.

4. “God is love” / “God is love” as essential nature, not mere attribute (4:8, 16) — uniquely dangerous because it feels like the most exportable, ecumenically “safe” line in the whole letter, and is therefore the line most likely to be quoted or excerpted without its 4:9-10 defining content attached.

5. Antichrist vs. Dajjāl false-friend substitution (2:18, 22; 4:3) — not a doctrinal collision in the same register as items 1-4, but a high-probability reader-side misreading that could silently import an entire wrong eschatological narrative if the distinguishing note is omitted even once.

6. Forgiveness/cleansing left unanchored to the blood of Christ (1:7, 9; 2:2, 12) — lower drama than items 1-3 but higher frequency of occurrence and higher risk of being handled casually by a Phase 2 pass precisely because گناہ/معافی vocabulary feels so ordinary and low-friction on the surface.

7. “Overcome the world” rendered with jihad-adjacent register (2:13-14; 4:4; 5:4-5) — a forbidden-substitution risk rather than a doctrinal-content risk, but flagged this high because the failure mode (militarized victory-language) would actively distort the passage’s own faith-not-effort grammar, not merely under-communicate it.

8. μένω/“abide” drifting toward ontological-merger register (2:6; 4:12-16) — lower collision explicitness than items 1-4 (no single named Qur’anic counter-verse), but real risk of a different kind of doctrinal error (collapsing the Creator-creature distinction) if handled loosely, especially in the core passage’s climactic 4:12-16.

9. Confidence/assurance language normalized away from its contrastive force (2:28; 3:21; 4:17; 5:14) — risk here is dilution rather than collision: translators accustomed to softening confident-sounding claims for politeness may inadvertently blunt 1 John’s deliberately bold register.

10. “Day of judgment” bleeding into the reserved قیامت slot (4:17) — lowest-severity item on this list in doctrinal terms, but included because an inter-book consistency failure here would retroactively undermine the Romans-baseline’s carefully constructed قیامت/resurrection distinction, a cross-document risk unique to this position in the ranking.

---

Summary for Phase 2 Handoff

• All [TM-REUSE] terms from the baseline translation_memory.json/bible_term_registry.json are confirmed unchanged and load first.
• All [NEW] 1 John terms from 08_core_glossary.md are confirmed consistent with this gap analysis’s recommended strategies; no term recommendations in this document contradict the glossary.
• The périphrasis decisions in Part 3 (اکلوتا بیٹا, مخالفِ مسیح, نئے سرے سے پیدا ہونا, مدافع) are to be treated as fixed upon promotion to the updated translation_memory.json, not subject to per-segment re-litigation in Phase 2.
• The ranked ambiguity list in Part 4 should directly inform Phase 2 Step 16-17 review queue ordering: items 1-4 first into the human theologian queue, items 5-6 next, items 7-10 following, all before any Medium/Low-tier segment processing begins for this book.

This document must be loaded alongside 08_core_glossary.md, the baseline translation_memory.json, bible_term_registry.json, doctrine_risk_registry.json, and 12_ai_translation_requirements.md before any Phase 2 segment translation of 1 John begins.