Executive Summary: James (یعقوب) Urdu Language Package

Why it matters

James is short — five chapters, 108 verses — but it lands the Urdu Bible translation pipeline in genuinely new territory. Romans and Galatians collided mainly with explicit Qur’anic denial (the crucifixion, sonship, resurrection-ahead-of-qiyamat). James’s core passage, 2:14–26 (“faith without works is dead”), introduces a third, distinct risk this pipeline has not faced before: correctly translating James’s own words, without an explicit harmonizing frame, can (a) manufacture an apparent Bible self-contradiction against Galatians’ faith-alone doctrine, or (b) read as Scripture agreeing that works secure salvation — exactly the Islamic mīzān (deeds-weighed-at-judgment) framework this whole Language Package has otherwise worked to keep distinct from Christian salvation. Getting James right is not primarily a word-choice problem; it is a discourse-level framing problem, and it governs review routing above any single term.

Key findings

• The core passage is a single, non-divisible review unit. James 2:14–26 must route to human theologian review as one discourse unit, not per-term, because the risk lives in the argument’s structure (James answers “how is faith shown genuine,” Paul answers “on what basis is a sinner declared righteous”) — not in any individual mistranslatable word.
• اعمال (“works”) is the single highest cross-document coordination risk in the entire pipeline. It is textually correct as a bare, unqualified term here, but it is also a live Islamic deeds-at-judgment technical term — the exact word the Galatians baseline spent its heaviest terms trying to keep qualified. Softening it to “good deeds” (نیک اعمال) would make things worse, not better.
• James supplies a brand-new, book-unique forbidden substitution: James 4:7’s “submit to God” sits closer to the literal root meaning of Islam than any other clause in this three-book curriculum. No fencing strategy works here — only strict avoidance of the entire س-ل-م word family.
• Three additional Critical doctrines recur outside the core passage and require the same absolute-enforcement discipline: the “law of liberty” (1:25; 2:12, compounding two independently high-risk baseline terms), the Deity/Lordship of Christ (1:1; 2:1; 5:7–8, easy to under-weight given James’s sparse narrative), and Patience and the Lord’s Return (5:7–11).
• James also contains this pipeline’s strongest positive bridges to date: orphan/widow care (1:27), Abraham as “friend of God” / Khalilullah (2:23), Job’s sabr (5:11), Elijah’s prayer (5:17–18), and “if the Lord wills” / In sha’Allah (4:15) are all genuine points of shared reverence usable pastorally, not just risks to manage.

Risks

• 35 individual terms in the James term registry carry Critical (11) or High (24) doctrine risk, on top of the baseline’s already-Critical terms (ایمان, راستباز ٹھہرایا جانا, نجات, خداوند, جلال, etc.) which are reused and, in several cases, elevated in stakes for this book.
• 16 of James’s 20 registered doctrines require human theologian review (5 Critical + 11 High); 4 require native speaker review; only 1 (Old Testament Exemplars) clears at automated review.
• بزرگ (“elders,” 5:14) collides with the live South Asian honorific for a revered Sufi saint/shrine-figure — mishandled, ordinary church leadership could be read as inviting shrine-style veneration or intercessory-mediator expectations.
• لعنت (“curse”) is reused from Galatians’ Critical divine-judicial-curse sense in a much lower-stakes human-speech context (James 3:9–10) — a concordance-style reader could wrongly import Galatians’ weight into James 3, or vice versa dilute Galatians’ weight.
• σῴζω-root verbs appear in three distinct senses within this one letter (general/1:21, physical healing/5:15, restoration-from-straying/5:20) — any conflation with each other or with baseline eternal نجات is a live drafting hazard.

Opportunities

• Frame James 2 pastorally as resolving an apparent tension rather than creating one — readers who already sense a Paul/James friction (a real question even within Christian history, e.g. the Reformation-era sola fide debate) will find a well-taught resolution unusually persuasive.
• Lean into the book’s five strongest bridge points (orphan care, Khalilullah/friend of God, Ayyub’s patience, Ilyas’s prayer, In sha’Allah parallel) as entry points for trust-building before addressing harder material (Lordship, the crucifixion’s absence-but-implication, worldliness/apostasy-adjacent material).
• Use James’s own internal repetition (دو دلا at 1:6–8/4:8; کامل across five occurrences; غریب/دولت مند across three chapters) as a teaching asset — cross-chapter consistency lets learners track the book’s recursive structure rather than experiencing it as five disconnected topics.

Recommended actions

1. Lock the discourse-level review rule for James 2:14–26 into Phase 2 tooling now, before any segment translation begins — this is a routing rule, not just a glossary entry, and must not depend on a translator remembering to check.
2. Add the two James-specific hard forbidden substitutions (جن for demons; any س-ل-م-root vocabulary for James 4:7’s “submit”) to automated validation immediately; both are single-point, zero-tolerance failures.
3. Brief theologian reviewers explicitly on the اعمال fencing strategy (keep the word bare; attach the note; never soften to نیک اعمال) so the most counter-intuitive rule in this Language Package is not accidentally “corrected” toward a seemingly safer but actually riskier phrasing.
4. Carry the کلیسیا کے qualifier as a non-droppable compound for “elders” throughout Phase 2 output — flag any segment where it appears abbreviated.
5. Sequence Phase 2 delivery so James 1:22–25 is drafted with awareness of 2:14–26’s fuller resolution already in view, even though it is translated first — an ordering risk unique to this book’s own recursive structure.

---

Full detail: 07_semantic_analysis.md, 08_core_glossary.md, 11_doctrine_analysis.md, 04_comparative_theology.md, 06_linguistic_gap_analysis.md, assets/translation_memory.json, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, 12_ai_translation_requirements.md.