Linguistic Gap Analysis: 2 Corinthians

Purpose and Scope

This document performs PRD Phase 1 Step 8 for 2 Corinthians: it analyzes the Urdu language’s structural capacity (or incapacity) to carry each of this letter’s eight target doctrines, distinguishes missing vocabulary (no adequate Urdu term exists at all) from crowded semantic neighborhoods (an Urdu term exists but is already claimed, in whole or part, by a specific rival theological system and needs deliberate fencing), records transliteration-vs-paraphrase decisions, and ranks the letter’s highest-risk ambiguities for review-routing purposes.

This analysis inherits the baseline’s categorical finding (12_ai_translation_requirements.md): Urdu’s dominant risk pattern is direct negation — a specific, named Qur’anic verse explicitly contradicts a specific Romans/Galatians/2 Corinthians doctrine — rather than the diffuse syncretism risk documented for the Hindu-context languages in this pipeline. 2 Corinthians intensifies this pattern in two new ways not yet seen at this density in Romans/Galatians:

1. The core passage itself (5:11-21) is the single densest concentration of Critical-tier negation risk in the entire curriculum to date — reconciliation, non-imputation of sin, the incarnational premise (“God was in Christ”), and the katallagē/hamartia exchange formula (“made him to be sin… that we might become the righteousness of God”) all sit within eleven verses, each individually colliding with Qur’an 4:157 (crucifixion denial) and Qur’an 4:171/5:72-75 (deity/sonship denial).
2. 2 Corinthians introduces the letter’s own distinctive crowded-neighborhood problem: توبہ (tawbah/repentance) and فردوس (Firdaus/paradise) are not merely adjacent to Islamic doctrine, as most Romans/Galatians terms are — they are specific, independently theorized technical terms within Islamic theology proper, structurally identical in kind to the baseline’s روح القدس and نجات entries. This raises the number of “shared-word-two-mechanisms” terms requiring the heaviest review tier from two (نجات, ایمان) in the baseline to at least five across the full curriculum.

---

Section 1 — Doctrine Vocabulary Matrix

For each of the eight curriculum doctrines: available Urdu terms, their weaknesses, and the recommended strategy. Terms already fixed in translation memory are marked [TM-FIXED] and must not be altered; new terms proposed in 08_core_glossary.md are marked [PROPOSED].

1. Reconciliation with God

Available Urdu term	Weakness	Recommended strategy
صلح (ṣulḥ) [TM-FIXED, Romans 5:1]	Names the forensic result (peace achieved), not the reconciling act. Using it for καταλλαγή would flatten 5:18-20’s active, ongoing “ministry of reconciliation” into a static state.	Reserve صلح for peace-as-result; do not reuse for reconciliation-as-act.
معافی (mu’āfī, forgiveness)	Names only guilt-removal; risks assimilation to Islamic maghfirah (mercy-weighed-against-deeds), already flagged in the baseline’s justification entry.	Reject as primary rendering; may appear as a component idea but never as the headword.
مصالحت (muṣālaḥat) [PROPOSED, Critical]	No inherent weakness as a lexical item — a genuine, dignified Urdu/Persian word for reconciling two estranged parties, sharing the ص-ل-ح root with صلح for doctrinal continuity. Risk is entirely in ensuring it is taught as God’s own initiating act, not a mutual negotiation between equals.	Adopt as the fixed rendering. Mandatory clarifying note at first occurrence: God is the reconciler, humanity the reconciled, not two parties meeting halfway (this differs structurally from ordinary مصالحت disputes, e.g. family/tribal reconciliation, where both sides typically concede something).

Gap classification: Missing vocabulary, now filled. No single existing TM-FIXED term covered the reconciling-act sense; مصالحت closes a genuine lexical gap rather than displacing a crowded term.

2. New Creation in Christ

Available Urdu term	Weakness	Recommended strategy
نئی مخلوق (na’ī makhlūq) [TM-FIXED, Galatians 6:15]	None significant; already proven in Galatians. Risk is entirely about consistency and about not flattening the creation-level ontological claim into ordinary moral self-improvement vocabulary (اصلاح, “reform/improvement,” or بہتری, “betterment”).	Reuse identically at 2 Cor 5:17. This is the doctrine’s anchor verse for the whole curriculum; render byte-for-byte the same as the Galatians occurrence.
اصلاح / بہتری (reform / betterment)	Both describe self-directed moral improvement, precisely the reading Paul’s “new creation” language excludes.	Forbidden substitutions for this doctrine specifically — flag if either appears near 5:17 in draft translation.
صورت بدلنا / تبدیل ہونا (transformed) [PROPOSED, Medium]	Adjacent but distinct: 3:18’s μεταμορφόω is progressive Spirit-work, while 5:17’s καινὴ κτίσις is a decisive, punctiliar new-creative act. Conflating the two verbs blurs an important tense/aspect distinction.	Keep the two lexically separate in all teaching material: نئی مخلوق for the decisive new-creation status; صورت بدلنا/تبدیل ہونا for the ongoing transformation process.

Gap classification: No gap — baseline term transfers cleanly. Risk is entirely about protecting an already-solved term from erosion by nearby near-synonyms.

3. Suffering and Comfort in Ministry

Available Urdu term	Weakness	Recommended strategy
تسلی (tasallī, comfort) [PROPOSED, High]	Shares its verbal root (پارا-… via نصیحت کرنا) with the baseline’s “exhort” entry, but تسلی’s own sense (console) and نصیحت’s sense (admonish/build up) diverge sharply — both translate the same Greek root παρακαλέω/παράκλησις depending on context. Real risk is sense-selection error per occurrence, not a competing theological system.	Adopt تسلی as the default rendering for the consolation sense (1:3-7; ch. 7); retain نصیحت کرنا [TM-FIXED] strictly for the admonish/build-up sense elsewhere in the curriculum. Flag every occurrence of the root in 2 Corinthians for sense-check before applying either term.
مصیبت (muṣībat, affliction) [PROPOSED, Medium]	Standard word, but carries a strong vernacular association with fatalistic, undeserved-calamity framing (e.g., “muṣībat aa gayī,” a disaster befell [someone], often used with resigned/passive connotation). This risks undercutting the letter’s purposive framing of suffering (comfort flows from affliction toward a purpose).	Use مصیبت but pair consistently with purposive framing language (تسلی، مقصد) in surrounding text; avoid isolated bare occurrences in doctrinal summary material.
دکھ / تکلیف (participatory suffering) [PROPOSED, Medium]	Both are generic hardship words; neither carries an inherent “shared with Christ” (koinōnia-of-suffering) sense on its own.	Anchor explicitly to 1:5’s “share/participate in Christ’s sufferings” language every time; do not let دکھ/تکلیف stand alone as if synonymous with مصیبت.
مسیح کا تختِ عدالت (judgment seat of Christ) [PROPOSED, High, borderline Critical]	No existing Urdu term for a believers’-only reward tribunal distinct from final judgment; nearest cultural analogue is the qiyamat/mizan framework, which is a different mechanism (all humanity, deeds weighed to determine salvation itself).	Coin the compound phrase; mandatory contrastive note every occurrence distinguishing this from mizan-style salvation-determining judgment (5:10).

Gap classification: Mixed. تسلی/نصیحت is a crowded neighborhood (shared root, sense-collision risk) requiring fencing by context; مسیح کا تختِ عدالت is a missing vocabulary gap filled by compound-coining.

4. The New Covenant versus the Old

Available Urdu term	Weakness	Recommended strategy
شریعت (sharī’at) [TM-FIXED]	Already flagged in the baseline as High risk: shared vocabulary with Islam’s own comprehensive legal-theological term for the whole body of Allah’s revealed law. 2 Corinthians 3 intensifies this because the letter-versus-Spirit contrast (3:6) sounds, if mishandled, like a categorical verdict against written law/revelation as such.	Reuse شریعت only where the Mosaic covenant specifically is meant (as per baseline law_and_grace note); never let 3:6’s “letter kills” stand unqualified near شریعت without the Mosaic-specificity anchor.
حرف / روح (letter/Spirit) [PROPOSED, High]	حرف (letter, literally “a written character/word”) is a comparatively safe, narrow term with no direct Islamic-technical competing sense, but its pairing with روح in a law-critique context creates collision risk by association with شریعت, not by حرف’s own meaning.	Adopt حرف / روح as the fixed pair; always co-occur with an explicit gloss: “the Mosaic covenant’s written code, not written revelation or religious law in general.”
عہد (ahd, covenant) [TM-FIXED]	None on its own (already a genuine bridge word per the baseline, cf. Qur’an 7:172’s primordial covenant). Risk is entirely in the new/old contrast requiring نیا / پرانا modifiers to be unambiguous.	Reuse عہد; render “new covenant” as نیا عہد [reused-extended], consistently distinguished from a bare, unmodified عہد.
نقاب / پردہ (veil) [PROPOSED, Medium-High]	THE SHARPEST crowded-neighborhood problem in this doctrine: پردہ/purdah names a live, socially central Muslim (and broader South Asian) female modesty-veiling practice. Exodus 34’s veil is Moses’ own literal face-covering used typologically for hardened spiritual perception — an entirely different referent that nonetheless shares the identical Urdu vocabulary.	Mandatory clarifying note at first occurrence (3:13) stating explicitly this refers to Moses’ face-veil in Exodus 34, not a comment on veiling practice generally. Native speaker + theologian co-review for every occurrence in ch. 3.
جلال (glory) [TM-FIXED]	None new; already a genuine, safe shared-vocabulary bridge (Allah as Dhu’l-Jalali). Risk is volume (ch. 3 uses جلال roughly ten times in eleven verses) diluting the “always anchor to Christ/God” discipline through sheer repetition.	Reuse جلال; flag ch. 3 for a dedicated consistency pass ensuring every occurrence retains an explicit divine referent, not a floating abstract-radiance reading.

Gap classification: نقاب/پردہ is the doctrine’s standout crowded neighborhood case — arguably the single most acute cultural-connotation (as opposed to theological-negation) risk newly introduced by this book.

5. Sincerity and Apostolic Authority

Available Urdu term	Weakness	Recommended strategy
رسول (apostle) [TM-FIXED]	Already flagged: risk of being read through the Quranic scripture-bearing messenger-prophet paradigm (culminating in Muhammad as “seal of the prophets”). 2 Corinthians raises the stakes because Paul is defending his apostleship against rivals — a defense that could inadvertently read as a claim to Quranic-style prophetic finality if the office is not carefully bounded.	Reuse رسول; every defense-of-apostleship passage (chs. 10-12) should carry the standing baseline clarifying note about Christ-commissioned apostleship being distinct from Quranic prophetic revelation.
سفیر (safīr, ambassador) [PROPOSED, High]	A genuinely neutral diplomatic-envoy word with no specific competing Islamic technical loading — but because it is neutral, it risks under-conveying the weight of 5:20’s claim (Christ himself entreating through Paul). A courier/low-stakes-messenger reading would undersell the passage.	Adopt سفیر; mandatory native-speaker check that register conveys sovereign-delegated authority (a king’s envoy, not a postal courier); consider a strengthening modifier (e.g. “مسیح کی طرف سے سفیر,” “ambassador on Christ’s behalf”) at first occurrence.
فخر (fak͟hr, boasting) [PROPOSED, High]	Genuinely dual-valence in ordinary Urdu (neutral pride vs. sinful arrogance), and Paul’s own usage swings between condemning boasting “in appearance” and commanding boasting “in the Lord” within the same discourse (chs. 10-12) — this is a Pauline ambiguity, not merely a translation problem, but Urdu’s own dual-valence compounds it.	No single fixed gloss; require every occurrence to be tagged with its valence (legitimate/illegitimate) in the segment cache, and prefer disambiguating modifiers (خداوند میں فخر, “boasting in the Lord” vs. ظاہری فخر, “boasting in externals”) over a bare فخر wherever the immediate context does not make the valence self-evident.
خالص نیت / خلوص (sincerity) [PROPOSED, Medium]	ἁπλότης’s two senses (motive-sincerity at 1:12; generosity at chs. 8-9) share one Greek root but must not share one Urdu gloss, or the two doctrines (Sincerity/Authority vs. Generosity/Giving) blur together.	Fix خالص نیت/خلوص for the motive sense only; use فراخدلی/خلوص دلی سے دینا for the generosity sense (see Doctrine 6). Track both under a single “haplotēs-dual-sense” flag in translation memory notes.

Gap classification: فخر is this doctrine’s crowded neighborhood — not because of Islamic-theological collision but because of Urdu’s own pre-existing dual valence intersecting with Paul’s own genuinely double usage. This is a source-text ambiguity compounded by target-language ambiguity, requiring per-occurrence tagging rather than a single fixed gloss.

6. Generosity and Grace in Giving

Available Urdu term	Weakness	Recommended strategy
فضل (grace) [TM-FIXED]	None new. Risk is entirely about keeping giving framed as grace’s fruit, not an independently meritorious human virtue that could be read as a good-deed-in-the-mizan contribution.	Reuse فضل; every giving-doctrine passage should retain an explicit “God working generosity in the giver” frame, echoing the baseline’s grace-versus-works discipline.
بونا اور کاٹنا (sow and reap) [TM-FIXED, Galatians 6:7-8]	Already flagged in Galatians as mizan-adjacent; reapplication to material generosity (9:6) intensifies the risk because “you reap what you sow” is proverbially close to karma/mizan folk-reasoning in everyday Urdu speech, independent of any specific verse.	Reuse exactly; mandatory reminder that the acting agent is the personal, generous God who multiplies seed (9:10), not an impersonal cosmic law of reciprocity.
فراخدلی / خلوص دلی سے دینا (generosity) [PROPOSED, Medium]	See ἁπλότης dual-sense caution above (Doctrine 5).	Keep visually and lexically separate from خالص نیت/خلوص (sincerity sense); do not let the shared Greek root justify a shared Urdu gloss.
برابری (equality/fairness) [PROPOSED, Medium]	برابری in contemporary Urdu political discourse can carry connotations of enforced socio-economic equality (a live, debated concept in South Asian political rhetoric) that Paul’s voluntary-mutual-sufficiency point does not intend.	Frame consistently as voluntary, mutual sufficiency among believers (no one lacks while another has abundance), not redistribution ideology; flag for native speaker review if paired with any contemporary economic-justice vocabulary in surrounding lesson material.
کفایت (sufficiency) [PROPOSED, Low-Medium]	Minor risk of a Stoic self-sufficiency reading (autarkeia’s classical philosophical sense) if translated without a divine-source qualifier.	Pair with “خدا کی طرف سے” (from God) at first occurrence to keep the source explicit.

Gap classification: No missing vocabulary; the doctrine is well-served by existing/reused terms. The main task is fencing بونا اور کاٹنا against folk-karma reasoning and fencing برابری against contemporary redistribution-politics readings.

7. Power in Weakness

Available Urdu term	Weakness	Recommended strategy
کمزوری (kamzorī, weakness) [PROPOSED, Medium]	Not a theological-collision risk but a cultural-values risk: South Asian honor-culture, shared broadly across Muslim, Hindu, and Christian communities in the region, prizes strength/status/izzat (honor) and treats weakness as something to conceal, not something to boast in. Paul’s paradox (boasting in weakness) runs directly against this value system.	Retain کمزوری plainly; do not soften it to a more face-saving euphemism. Teaching material must explicitly name and address the honor-culture collision as a cultural challenge distinct from (though occurring alongside) the letter’s theological-negation risks.
خدا کی قدرت (power of God) [TM-FIXED]	Genuinely safe, shared divine-attribute vocabulary (Allah as al-Qadir) — the one doctrine in this letter where baseline vocabulary is low-friction.	Reuse freely; note the partial positive bridge value for teaching (both traditions affirm all power belongs to God alone), while flagging that the specific Pauline paradox — boasting in one’s own weakness as the very locus where that power operates — has no exact parallel and must not be assumed already understood.
صلیب / مصلوب (cross/crucified) [TM-FIXED]	Already the baseline’s highest-priority escalation term. 13:4’s compound (“crucified in weakness… lives by God’s power”) stacks THREE Critical-tier baseline terms in one clause (crucifixion, resurrection/life, power), making it the single most doctrinally dense sentence in the Power-in-Weakness doctrine.	Reuse صلیب/مصلوب exactly; render the full compound as a single reviewed unit, not word-by-word, to preserve the paradox’s rhetorical unity. Mandatory theologian review, equal priority to 5:14-15 and 5:21.
جسم میں کانٹا (thorn in the flesh) [PROPOSED, Medium-High]	جسم (flesh) is already TM-fixed from Galatians with its own caution against نفس substitution (Sufi nafs-discipline risk). “Thorn in the flesh” as a literal-sounding phrase risks a folk-medical/physical-ailment-only reading, losing the spiritual-humbling purpose.	Retain جسم میں کانٹا but pair with 12:7’s stated purpose clause (to keep Paul from becoming conceited) in any teaching gloss, so the phrase is not read as merely describing a physical health condition.

Gap classification: No missing vocabulary. This doctrine’s central challenge is cultural values fencing (honor-culture strength-bias) rather than lexical gap or theological negation — a genuinely different category from most of this letter’s risks, worth flagging explicitly for pastoral framing in Phase 2/3 material.

8. Genuine versus False Apostleship

Available Urdu term	Weakness	Recommended strategy
جھوٹے رسول (false apostles) [PROPOSED, High]	Built on TM-fixed رسول; risk is ensuring “false” is understood as false by gospel-distortion and self-serving method, not “false” in the sense of lacking a scripture-bearing office comparable to Muhammad’s — a Quranic criterion Paul is not using.	Reuse رسول baseline caution explicitly here; pair “false” language with concrete behavioral markers from the text (self-commendation, financial exploitation, ch. 11) rather than an abstract office-legitimacy claim alone.
نور کا فرشتہ (angel of light) [PROPOSED, Medium-High]	نور carries devotional resonance in some South Asian Islamic mystical/Sufi traditions (Nur Muhammadi-adjacent concepts of primordial prophetic light). Satan’s disguise-as-light-being in 11:14 risks unintended resonance with that separate devotional category if under-contextualized.	Keep the verse’s deceptive-disguise point explicit and foregrounded; do not let نور stand as an isolated, admirable image detached from the disguise/deception frame.
دوسرا یسوع (another Jesus) [PROPOSED, Critical]	Compounds two risks simultaneously: (a) the baseline’s یسوع-vs-عیسیٰ distinction already carries high interpretive weight; (b) “another/different Jesus” in 11:4 is a first-century intra-church rival distortion, wholly unrelated to the later Qur’anic prophet-Isa, but an Urdu reader unfamiliar with that history could easily misread the phrase as directly engaging Isa.	Mandatory clarifying note at every occurrence distinguishing the two entirely separate historical/theological contexts (first-century rival teaching vs. seventh-century Quranic prophetology) — this note is more urgent here than almost anywhere else in the curriculum because the surface phrase invites exactly the misreading the baseline’s Jesus-naming convention was designed to prevent.
خدا کی طرف سے سرگرم محبت (godly jealousy) [PROPOSED, High — connotation]	غیرت (the natural, idiomatic Urdu word for “jealousy”) carries heavy South Asian honor-culture baggage (family/tribal honor, and in extreme application, honor-based violence) entirely absent from Paul’s pastoral-protective meaning. This is the doctrine’s standout connotation risk, parallel in severity to نقاب/پردہ above but arising from a different mechanism (honor-culture association, not Islamic-doctrinal specificity).	Adopt the descriptive phrase خدا کی طرف سے سرگرم محبت as primary; if غیرت must be used for stylistic/idiomatic reasons in any derivative material, require a mandatory clarifying note every time. Native speaker cultural review required regardless of which option is chosen.

Gap classification: Mixed. دوسرا یسوع is a compounded ambiguity (theological-historical, not lexical); خدا کی طرف سے سرگرم محبت is a crowded-neighborhood substitution (avoiding غیرت’s honor-culture connotation entirely, rather than fencing it).

---

Section 2 — Missing Vocabulary vs. Crowded Semantic Neighborhoods

2.1 Missing Vocabulary (no adequate existing Urdu term; new coinage/compound required)

These terms have no existing Urdu word or fixed phrase adequate to the doctrine, requiring the glossary’s proposed new compounds:

Concept	Gap	Resolution
Reconciliation (as active, God-initiated ministry, not merely resultant peace)	صلح names only the result	مصالحت (new root-family extension)
Non-imputation of sin (forensic non-crediting, not weighed-against-deeds)	No Urdu term names “not counting” as a discrete forensic act	شمار نہ کرنا (descriptive compound)
Judgment seat of Christ (believers’-only reward tribunal, distinct from salvation-determining judgment)	No cultural or lexical analogue; nearest neighbor (qiyamat/mizan) is a different mechanism entirely	مسیح کا تختِ عدالت (coined compound, mandatory contrastive note)
Ambassador (Christ-delegated envoy, distinct from apostle)	رسول is already claimed for a different, founding-authority office	سفیر (borrowed but doctrinally under-loaded diplomatic term, requires strengthening)
Judgment-seat-adjacent “arrabōn” guarantee-deposit image	No existing Urdu financial/legal metaphor was previously fixed for this in the baseline	ضمانت (guarantee/pledge, already a natural Urdu legal-financial term — low risk, genuine gap filled cleanly)
Tent/body metaphor (skēnos, temporary dwelling)	خیمہ exists as ordinary vocabulary but was not previously anchored to this specific eschatological body-metaphor use	خیمہ (adopted directly; low gap severity)

2.2 Crowded Semantic Neighborhoods (existing Urdu term(s) already claimed, wholly or partly, by a rival system; require fencing, not coinage)

These are the analysis’s highest-value findings, because the risk is not absence of vocabulary but contested ownership of vocabulary:

Urdu term	Rival claimant	Nature of the crowding	Fencing strategy
نقاب / پردہ (veil)	Islamic female modesty-veiling practice (purdah), a live, socially central, non-theoretical practice (unlike, say, an abstract doctrine)	Cultural-practice crowding, not doctrinal-negation crowding — Moses’ Exodus 34 face-veil and the purdah practice share identical vocabulary but have zero conceptual overlap	Mandatory clarifying note at first occurrence; treat as a live practice-adjacent term requiring the same care given to ختنہ (circumcision) in the Galatians baseline
غیرت (jealousy, natural gloss for zēlos)	South Asian honor-culture family/tribal-honor concept, with extreme-application association to honor violence	Cultural-values crowding	Avoid as primary rendering; substitute descriptive phrase (خدا کی طرف سے سرگرم محبت)
توبہ (repentance)	Islamic theology’s own precisely theorized tawbah doctrine (independent merit-transaction within the mizan/mercy framework)	Doctrinal-mechanism crowding, structurally identical to نجات/ایمان	No viable alternative exists; mandatory contrastive teaching every occurrence, same tier as نجات
فردوس (paradise)	A specific, named tier of Jannah in Islamic eschatology with independent theological content (levels, inhabitants, hadith description)	Doctrinal-content crowding, structurally identical to روح القدس	Mandatory framing note every occurrence; theologian-discretion alternative (خدا کی حضوری کا باغ) available to reduce (not eliminate) collision
اس دنیا کا خدا (god of this age — applied to Satan)	The baseline’s own reserved-word convention: خدا is deliberately kept exclusive to the true God throughout this Language Package	Reserved-word-integrity crowding (a unique category: the “rival claimant” here is the Language Package’s own prior convention, not an external religious system)	Mandatory bracketed clarifying note, or theologian-selected alternative اس جہان کا حاکم
فخر (boasting)	Not a rival religious system but Urdu’s own inherent dual valence (neutral pride vs. sinful arrogance), compounded by Paul’s own genuinely dual usage	Lexical-ambiguity crowding (source and target ambiguity stacking)	Per-occurrence valence tagging; disambiguating modifiers preferred over bare فخر
نور (light, in “angel of light”)	South Asian Sufi/devotional Nur Muhammadi-adjacent light-theology	Devotional-resonance crowding	Keep disguise/deception frame explicit and dominant in context
جہاد/قتال-adjacent vocabulary (avoided entirely in weapons_of_warfare)	Live regional religious-political discourse around armed conflict	Political-resonance crowding (avoidance strategy, not fencing an occupied term)	Use only generic جنگ کا اسلحہ; explicitly avoid any جہاد-root vocabulary; mandatory non-literal metaphor note
شریعت (used narrowly for Mosaic law in 3:6ff)	Islam’s own comprehensive legal-theological term	Already flagged in baseline; 2 Corinthians 3 intensifies via the letter/Spirit contrast’s apparent (but not actual) blanket law-critique	Reuse baseline fencing (Mosaic-specificity anchor); do not extend the letter/Spirit contrast beyond the Mosaic covenant in any teaching gloss

Observation: 2 Corinthians roughly doubles the count of acute cultural-connotation crowding cases (پردہ, غیرت, نور, جہاد-avoidance) compared to Romans/Galatians, in addition to carrying forward and intensifying the doctrinal-mechanism crowding cases (توبہ, فردوس joining نجات/ایمان/روح القدس). This letter therefore requires proportionally more native-speaker cultural review relative to theologian doctrinal review than either baseline book, even though its Critical-tier doctrinal count (driven by the core passage) is also higher.

---

Section 3 — Transliteration vs. Paraphrase Decisions

Term	Decision	Rationale
مصالحت (reconciliation)	Native Urdu/Persian vocabulary, NOT transliterated from Greek	A genuine, dignified existing word exists; transliterating katallagē would be unintelligible and unnecessary.
سفیر (ambassador)	Native vocabulary, not transliterated	Standard diplomatic loanword already fully naturalized in Urdu; no transliteration needed.
توبہ (repentance)	Native (Arabic-derived, fully naturalized) vocabulary	No transliteration option meaningfully avoids the collision (see baseline نجات precedent: the risk is in the concept, not the word-form); paraphrase into a multi-word compound was considered and rejected as unnatural and unrecognizable to readers.
فردوس (paradise)	Retained as the primary rendering, WITH a theologian-discretion paraphrase alternative (خدا کی حضوری کا باغ)	Unlike توبہ, an alternative paraphrase genuinely reduces (if not eliminates) the collision here because Paul’s own referent (a visionary “third heaven” experience) is unusual enough that a descriptive paraphrase remains intelligible without requiring the reader to already know the word. Decision: retain فردوس as default per established Bible-translation-tradition precedent, but authorize the paraphrase as a reviewer-selected escape valve — a decision not extended to توبہ, where no such valve exists.
ضمانت (guarantee/pledge, arrabōn)	Native vocabulary (legal/financial term), not transliterated	Ordinary Urdu legal-financial vocabulary already carries the exact “earnest deposit” sense needed; no gap.
طِطُس (Titus), اخیہ (Achaia), مکِدُنیہ (Macedonia), تیمتھیس (Timothy)	Transliterated, following established Urdu Christian Bible proper-name forms	Proper names have no translation option; transliteration is the only correct approach, per baseline transliteration standards.
بلیعال (Beliar)	Transliterated WITH a mandatory identifying gloss (“a name for Satan”)	Obscure proper name unlikely to be independently recognized; transliteration alone would be opaque without the gloss.
مسیح کا تختِ عدالت (judgment seat of Christ)	Paraphrase/compound, NOT transliterated (bēma has no viable transliterated form in Urdu)	Greek bēma is architecturally specific (a raised judicial platform) with no Urdu loanword tradition; a descriptive compound is the only workable option.
اس دنیا کا خدا / اس جہان کا حاکم (god of this age)	Paraphrase, deliberately avoiding a transliteration-adjacent shortcut	No transliteration would help here; the problem is a reserved-word collision (خدا’s exclusivity convention), which only a wording change, not a foreign-word import, can address.

General principle observed: Transliteration is reserved for proper names and truly untranslatable architectural/cultural specifics (bēma). Doctrinal-mechanism-crowded terms (توبہ, فردوس) are NOT resolved by transliteration — importing a Greek-transliterated alternative (e.g., a hypothetical “matanoia” loanword) would be unintelligible to readers and would not remove the underlying conceptual collision, which lives in the doctrine, not the word-form. This confirms the baseline’s own categorical finding: Urdu’s problem is negation/collision of content, not absence of vocabulary, and transliteration is therefore a weak tool against this letter’s sharpest risks.

---

Section 4 — Ranked List of Highest-Risk Ambiguities in 2 Corinthians

Ranked by combined severity (doctrinal centrality × collision directness × review burden). All rank 1-6 items require mandatory human theologian review of every occurrence; items below that line require native speaker review with theologian co-review where marked.

1. 2 Corinthians 5:21 — “made him to be sin… that we might become the righteousness of God” (اُسے ہمارے لیے گناہ بنا دیا / راستبازی). The letter’s single densest doctrinal compound: presupposes the crucifixion Qur’an 4:157 denies, states a substitutionary status-exchange with no parallel category in Islamic individual-deeds soteriology, and uses the baseline’s own Critical-tier راستبازی term in its salvific (not ethical) sense. Highest-priority item in the entire book.

2. 2 Corinthians 5:18-20 — the reconciliation/non-imputation/ambassador cluster. Three new Critical/High terms (مصالحت, شمار نہ کرنا, سفیر) load-bear the letter’s title doctrine simultaneously, compounding lexical-gap risk (new coinages, unproven in extended Phase 2 use) with doctrinal-negation risk (mizan-framework contrast).

3. 2 Corinthians 13:4 — “crucified in weakness… lives by God’s power.” Stacks three baseline Critical terms (صلیب/مصلوب, قیامت-family life/resurrection language, خدا کی قدرت) in one clause; the paradox’s rhetorical unity must survive translation as a single reviewed unit, not a word-by-word assembly.

4. 2 Corinthians 5:19 — “God was in Christ” (خدا مسیح میں تھا). The most compressed possible statement of the incarnation/deity-of-Christ collision in the entire curriculum to date — six Urdu words carrying the full weight of the baseline’s Critical incarnation and deity_of_christ doctrine notes.

5. 2 Corinthians 5:14-15 — “one died for all… all died” (ایک سب کے لیے مرا). Corporate/representative substitutionary death language; presupposes the historical crucifixion at full Qur’an 4:157 collision force, with the added complexity of the corporate “all died” claim, which has no ready analogue in an individual-accountability framework (cf. baseline universal_human_accountability caution).

6. 2 Corinthians 12:2-4 — paradise / third heaven (فردوس). Ranked here rather than higher because, unlike items 1-5, the risk is conceptual crowding (a shared, independently theorized term) rather than direct negation — serious enough for mandatory theologian review, but categorically different in kind and slightly lower in centrality to the letter’s core argument than the 5:11-21 cluster.

7. 2 Corinthians 7:9-10 — repentance (توبہ) and godly/worldly grief. Equal in shared-term-mechanism severity to نجات/ایمان, but ranked below the crucifixion-cluster items because the collision, while real and requiring mandatory contrastive teaching, is a parallel-mechanism risk (two systems both using the word for a change-of-heart-toward-God event) rather than a direct denial risk (one system asserting an event the other flatly says did not happen).

8. 2 Corinthians 3:13-16 — the veil (نقاب/پردہ). Highest-ranked cultural-connotation (as opposed to doctrinal-negation) risk in the book; ranked here because mishandling risks a serious, unnecessary social-offense reading (appearing to comment on a female modesty practice) even though the underlying theological content (spiritual dullness in reading the old covenant) is comparatively low-friction on its own.

9. 2 Corinthians 4:4 — “god of this age” (اس دنیا کا خدا). Ranked here as a unique reserved-word-integrity risk: the danger is not collision with Islamic theology per se but self-inflicted erosion of the Language Package’s own خدا-exclusivity convention, established precisely to protect items 1, 4, and 5 above.

10. 2 Corinthians 11:2-4 — “another Jesus” and “godly jealousy.” Two distinct but co-located risks in adjacent verses: دوسرا یسوع’s risk of being misread against the Qur’anic Isa (a compounded historical-theological ambiguity), and غیرت’s honor-culture connotation risk (a cultural-values crowding case). Ranked lower than items above because both are manageable through fencing (clarifying notes; substitute phrasing) rather than requiring the heaviest possible doctrinal defense.

11. 2 Corinthians 3:6 — letter and Spirit (حرف/روح) paired with شریعت. Ranked here because the risk, while real (an apparent-but-not-actual blanket law-critique), is narrower in scope than the items above and is already substantially mitigated by the baseline’s existing law_and_grace fencing conventions carried forward from Galatians.

12. 2 Corinthians 5:10 — judgment seat of Christ (مسیح کا تختِ عدالت). Ranked last among the theologian-mandatory tier because, while doctrinally adjacent to the mizan/qiyamat framework, its content (believers’-only reward evaluation, not salvation-determining) is comparatively more self-contained and easier to fence with a single consistent contrastive note than the items above, which each carry irreducible, verse-specific negation force.

---

Section 5 — Summary Recommendations for Phase 2 Handoff

1. Load all 08_core_glossary.md proposed terms into an updated translation_memory.json before Phase 2 begins, per the baseline’s Pre-flight Checklist; this analysis confirms none of the proposed renderings duplicate or contradict existing baseline entries.
2. Escalate the core passage (5:11-21) as a single reviewed unit, not as five or six independently reviewed segments, given the density and interlocking nature of its Critical-tier terms (items 1, 2, 4, 5 above all occur within eleven verses).
3. Distinguish two categories of review burden explicitly in Phase 2 routing: (a) doctrinal-negation risk (theologian-mandatory, e.g., crucifixion/reconciliation/incarnation cluster) and (b) cultural-connotation risk (native-speaker-mandatory with theologian co-review where flagged, e.g., veil, jealousy, honor-culture weakness framing). This letter is the first in the curriculum where category (b) reaches a volume comparable to category (a), and Phase 2 review-team staffing should reflect that.
4. Treat توبہ and فردوس as promotions to the baseline’s highest shared-term-risk tier, formally joining نجات, ایمان, and روح القدس as the curriculum’s structurally hardest terms — same-word-two-mechanisms cases with no viable alternative wording, requiring contrastive teaching rather than lexical substitution.
5. Flag پردہ (veil) for a dedicated pastoral-framing note in lesson material, separate from the standard translator-note mechanism, given the practice-adjacent (not merely doctrine-adjacent) nature of the risk.