Executive Summary: James (Persian Language Package Extension)

Why it matters

James is a practical, ethics-dense letter — faith and works, wisdom, speech, wealth, prayer, patience — and that practicality is exactly what makes it harder, not easier, to translate safely into Persian. Its vocabulary sits closer to the most densely populated regions of Iranian Shia devotional and Sufi-mystical language (نفس, دنیا, تسلیم, حکمت, شفاعت, ظهور) than Romans’ more forensic-soteriological vocabulary did. The letter’s central argument — that living faith inevitably produces works — is also the single highest cross-document risk in this entire pipeline: it reuses the Romans baseline’s exact justification compound (عادل شمرده شدن) in a different sense, directly adjacent to Iran’s two independent deeds-weighing cultural defaults (Islamic mizan, Zoroastrian Chinvat Bridge). Get this wrong, and James 2:24 will read as scripture endorsing exactly the works-based framework the gospel confronts.

Key findings

• Full-book coverage complete. All 5 chapters of James have been analyzed verse-by-verse (core passage, James 2:14-26) and chapter-by-chapter (full letter); no chapter was silently omitted.
• 9 curriculum doctrines map to 17 discrete doctrine-risk entries, and — unlike Romans, which had a mix of tiers — 100% of James’s 17 doctrines are Critical or High risk (7 Critical, 10 High, 0 Medium, 0 Low), all routed to mandatory human theologian review.
• Combined James + inherited-Romans translation memory totals 89 enforced terms: 22 Critical, 33 High, 30 Medium, 4 Low. 55 of 89 terms (62%) are Critical or High risk, requiring theologian-level scrutiny at every occurrence.
• The single highest risk in the curriculum is the Romans-James justification harmony: James 2:21-25 reuses عادل شمرده شدن (justification) and عدالت محسوب‌شده (imputed righteousness) verbatim from the Romans baseline, but in a demonstrative/vindicating sense rather than Romans’ forensic sense — every occurrence requires a mandatory attached harmonization note or the two curricula will appear to contradict each other.
• Two Shia-specific collision points are newly acute in James beyond what Romans already flagged: (1) ظهور, the natural-instinct Persian word for Christ’s return (parousia, 5:7-8), is Twelver Shia eschatology’s own technical term for the Hidden Twelfth Imam’s reappearance; (2) تسلیم (submit to God, 4:7) is the literal etymological root of “Islam” itself.
• Two genuine vocabulary gaps (not merely crowded terms) were identified: “image of God” (شبیه خدا, James 3:9) has no positive existing doctrinal content in mainstream Persian Islamic theology (tanzih avoidance), and horizontal believer-to-believer confession (اعتراف کردن, 5:16) has no indigenous precedent distinct from either Catholic sacramental confession or Islamic tawbah.
• Persian has a genuine linguistic asset in James 1: a clean existing lexical split between آزمایش (God-permitted testing) and وسوسه (temptation to sin) — one of the few places in this curriculum where Persian’s vocabulary is more precise than the risk requires, rather than less.

Risks

• Highest risk (Critical): Faith and Works / Justification Harmony (James 2:14-26) — an unflagged occurrence of عادل شمرده شدن is a doctrinal failure, not a stylistic one.
• Critical: Wisdom from Above (حکمت/نفسانی collapsing into Sufi philosophical/ascetic categories); Prayer and Healing (نجات/قیامت bleeding into شفا/برخیزانیدن); Mutual Intercessory Prayer (شفاعت echoing Karbala/Hussein devotion); Patience and the Lord’s Return (ظهور/Mahdi displacement); Deity and Lordship of Christ in James (the compact, easily-overlooked 2:1 statement).
• High: Worldliness vs. Friendship with God (تسلیم’s Islam-etymology risk); Favoritism and the Poor (وارث reengaging the adoption/sarparasti civil-law collision); Taming the Tongue (جهنم’s shared-destination-different-basis risk; شبیه خدا’s content gap); Confession and Restoration; Origin of Sin and Temptation; True and Pure Religion (دین’s din-e-Islam weight); Oaths and Truthful Speech (pervasive Imam-invoking oath culture).
• Process risk: because every James doctrine routes to theologian review, Phase 2 throughput planning must budget for a proportionally larger review queue than Romans’ mixed-tier profile allowed.

Opportunities

• Reuse, don’t reinvent. 24 baseline Romans terms transfer into James with zero lexical change, only extended notes — translation memory consistency is preserved by design, and the Isaac/Ishmael, Job/Ayyub, Elijah/Elyas shared-prophet bridges give real, positive points of contact to build teaching on.
• Persian’s testing/temptation split (آزمایش/وسوسه) is a rare case where the destination language is already better-equipped than the source-risk requires — worth highlighting in translator training as a model of what “good” looks like elsewhere in the curriculum.
• رحمت (mercy) and قرب-adjacent “draw near to God” are genuine devotional bridges (Bismillah’s ar-Rahman ar-Rahim; Sufi qorb) that can be leveraged for warmth and resonance, provided each is explicitly grounded in Christ’s atoning work rather than left as an unexamined shared truism.

Recommended actions

1. Lock the mandatory Romans-James harmonization note (analysis/08_core_glossary.md Part C) into every Phase 2 segment touching James 2:14-26 before any batch translation begins; treat its absence as a hard validation failure, not a warning.
2. Enforce the ظهور-avoidance and تسلیم-qualifying-clause rules as automated pre-submission checks (per analysis/12_ai_translation_requirements.md), not reviewer-discretion guidelines, given how easily both terms could slip in via translator fluency bias.
3. Route 100% of James Phase 2 output to human theologian review per assets/doctrine_risk_registry.json; do not apply Romans’ native-speaker-only or automated-only tiers anywhere in this book.
4. Commission a short supplementary explainer (for translator/reviewer onboarding) on the two newly-surfaced content gaps — image of God (3:9) and horizontal confession (5:16) — since these require constructed positive teaching, not merely careful word choice.
5. Confirm with the destination platform, before batch processing, the citation convention for یعقوب (James) alongside رومیان (Romans), and verify all Genesis cross-references (پیدایش ۱۵:۶؛ پیدایش ۲۲) render consistently across both curricula.