Executive Summary: The Epistle of James (English → Hebrew)

The big picture: James translates into Hebrew unusually well at the vocabulary level — richer native resources than most target languages — but carries the highest doctrinal-collision density of any curriculum in this pipeline so far, concentrated in one chapter (2) and one closing chapter (5).

---

Why it matters

James 2:14–26 sits closer to a live Hebrew-speaking reader’s own theological categories than almost any other NT passage: emunah is already praxis-oriented in Jewish self-understanding, so James’s “faith without works is dead” risks being heard as agreement with a mitzvot-observance framework, when in fact James is answering a different question (“is this profession genuine?”) than Romans (“how is a sinner declared righteous?”). Get this wrong and the curriculum either manufactures a false Bible contradiction or accidentally re-opens the Galatians/Acts 15 works-of-the-law controversy the New Testament itself resolved. Everything else in James — the tongue, wealth, patience, healing, confession — inherits genuine, positive Hebrew/Jewish resonances (lashon hara, the Akedah, teshuvah, Yom Kippur’s Vidui) that are assets, not obstacles, if handled deliberately.

Key findings

• 27 doctrines identified across the full letter (chapters 1–5, full-book coverage, no chapter skipped): 9 Critical, 8 High, 8 Medium, 2 Low.
• 87 total glossary terms governing James translation (19 inherited exactly from the Romans baseline + 71 new James-specific entries), of which 46 are Critical or High risk (20 Critical, 26 High) and therefore subject to the strictest glossary-enforcement tier.
• Chapter 2 (the core passage) and Chapter 5 are the highest-risk zones, together containing the majority of the letter’s Critical-tier doctrine: the faith/works vindication sense, the forbidden הוצדק/הצטדק verb distinction, the Genesis 15:6 citation match, the synagogue/church term boundary, the Lord of Hosts/Tetragrammaton decision, the two-comings framework for the Lord’s return, and the mandatory avoidance of the כפר/atonement root at “cover a multitude of sins.”
• One irreducible interpretive ambiguity — James 4:5’s disputed “spirit” referent (Holy Spirit vs. human spirit) — cannot be resolved by Hebrew orthography and requires a standing theologian-authored translator note at every occurrence, not a translation decision.
• A genuinely novel forbidden-substitution risk was discovered and must extend the baseline’s list: the reflexive verb הצטדק (“justified”), which colloquially means “made excuses for himself” in Modern Hebrew — a false-cognate trap the Romans baseline’s noun-form caution (הצטדקות) did not by itself cover for James’s verb usage.

Risks

• Critical: Silent doctrinal smoothing of James 2:24 (“justified by works, not by faith alone”) against Romans 3:28 by a translator or reviewer unaware both claims must stand at full strength, answering different questions.
• Critical: A single slip from הוצדק to הצטדק, or from מעשים to מעשי התורה, each of which inverts or imports a doctrine James’s own text does not teach.
• Critical: Merging James 2:2’s synagōgē into the Romans baseline’s קהילה, erasing a historically significant datum about early Jewish-Christian congregational life and risking a supersessionist-adjacent flattening the baseline elsewhere works hard to avoid.
• Critical: A default, “idiomatically natural” translator instinct toward a כפר-root rendering at James 5:20, creating a direct collision with the doctrine of Christ’s unique atonement.
• High: Under-teaching James’s unusually positive Torah framing (1:25; 2:8,12) by reflexively applying the more defensive posture appropriate to Paul’s adversarial Torah passages, thereby muting a genuine bridge to Jewish readers that the text itself supplies.

Opportunities

• The Akedah (2:21), lashon hara (3:1-12), Leviticus 19:15/18 (2:1-13), the erekh apayim divine attribute (5:7-8’s patience), and teshuvah/Vidui (5:16,19-20) are all ready-made, culturally load-bearing Hebrew categories that make James land with more immediate force for a Hebrew-speaking reader than for almost any other target-language audience in this pipeline — Phase 2 teaching material should be tuned to surface these connections explicitly rather than merely avoiding collisions.
• The מ־ש־ח (anoint) / מָשִׁיחַ (Mashiach) shared root at 5:14 offers a genuine, teachable wordplay parallel to the Yeshua/yeshu’ah connection already documented in the Romans baseline.
• The deliberate ידיד (friend) root shared between “friend of God” (2:23) and “friendship with the world” (4:4) is a literary device fully preservable in Hebrew and should be flagged for consistent cross-chapter rendering in batch/parallel Phase 2 processing.

Recommended actions

1. Route every segment in James 2:14–26 to mandatory human theologian review without exception; no automated or native-speaker-only approval path.
2. Add הצטדק (justified, reflexive) and any כ־פ־ר-rooted “cover sins” rendering to the enforced forbidden-substitution list in Phase 2 tooling, alongside the inherited Romans baseline list (ישו, bare צדקה, קידוש, עדה, bare השגחה, גבורה).
3. Require the standing James 2:14-26 harmonization note (vindication-before-others vs. forensic-declaration-before-God) to be attached programmatically, not left to individual translator discretion, at every occurrence.
4. Confirm the Habrit Hachadasha YouVersion version ID against the live platform before generating any Phase 2 hyperlinks (per 05_translation_landscape.md), and lock the הוצדק/בית הכנסת/יהוה צבאות decisions as non-negotiable house style before batch translation begins.
5. Brief all assigned theologian reviewers specifically on the James 4:5 spirit-referent ambiguity and the James 5:6 “righteous one” Isaiah 53 resonance question before Phase 2 Step 17 review scheduling, since both require a documented interpretive judgment call rather than a lookup-table answer.

---

This summary synthesizes 04_comparative_theology.md, 05_translation_landscape.md, 06_linguistic_gap_analysis.md, 07_semantic_analysis.md, 08_core_glossary.md, 11_doctrine_analysis.md, and the assets/ registries. All figures are synchronized with assets/doctrine_risk_registry.json and assets/translation_memory.json as of this document’s date.