James → Kashmiri Language Package: Executive Summary

Why it matters

James is the single most collision-prone book in this pipeline’s Kashmiri Language Package so far — not because of exotic theology, but because its plain, proverbial ethical register (“faith without works is dead,” “God is one,” “friend of God,” “draw near to God,” “elders shall pray”) tracks almost word-for-word onto everyday Kashmiri Islamic devotional speech and Rishi Sufi mystical vocabulary. The core passage, James 2:14-26, sits directly on top of the most sensitive fault line in the whole Romans-anchored package: works (عمل/اعمال) is the very term mainstream Islamic soteriology uses for deeds weighed against divine mercy. Get this wrong, and James appears to teach exactly the works-merit salvation the baseline Romans package was built to refute — reversing this curriculum’s central theological safeguard rather than reinforcing it.

Key findings

• 26 distinct doctrines identified across all five chapters (full-book coverage confirmed, no chapter silently skipped): 10 Critical, 10 High, 4 Medium, 2 Low.
• 67 distinct terms tracked in the extended glossary and translation memory: 13 Critical, 21 High, 27 Medium, 6 Low — of which 19 are inherited exactly from the baseline Romans package (ایمان, فضل, راستبازی, راستباز ٹھہرایہ گیہ, دِتمُت راستبازی, شریعت, گناہ, امن, جلال, خُداوند, خُدا, یِسوع, مسیح, کلیسیا, خُدایُک بادشاہت, نجات, پیغمبر, پاک روح, باپت) and 48+ are new coinages required by James’s distinctive vocabulary.
• 20 of 26 doctrines (77%) require mandatory human theologian review; 4 require native speaker review; only 2 are automated-only.
• The core passage (James 2:14-26) alone concentrates 6 of the book’s 10 Critical doctrines: Faith and Works; Justification’s evidential-vs-forensic sense; the “one God”/demons insufficiency argument; Abraham’s offering of Isaac; Friend of God; and the human-spirit-vs-Holy-Spirit disambiguation.
• Six terms are flagged as the highest-priority new Critical coinages given direct collision potential with core Islamic/Sufi vocabulary: عمل (works, vs. a’mal deeds-weighing), کامل (perfect, vs. Insan-i-Kamil), خُدایُک دوست (friend of God, vs. wali sainthood), خُداوندُک اننہٕ (the Lord’s coming, vs. the Islamic return of ‘Isa), ایمانہٕ ہٕنٛز دُعا (prayer of faith, vs. shrine-based dua/barakat healing culture), and اکہٕ خُدا (one God, vs. Tawhid/Shahada).

Risks

• Faith-and-works collapse into merit theology: without the mandatory harmonization clause at every occurrence in 2:14-26, a Kashmiri reader (Muslim-background especially) could read James as confirming deeds-weighing soteriology, directly undermining the Romans baseline’s grace/justification doctrine.
• False-friend affirmation in 2:19: “God is one” is near-verbatim Shahada language; without immediate framing, this verse risks being heard as an ecumenical endorsement of Tawhid as sufficient for salvation — the opposite of James’s own point.
• Silent contradiction with Romans on justification: James 2:21/24 use the same Kashmiri compound as Romans’ forensic justification, but in an evidential/vindicating sense; without a standing harmonizing note, learners moving between curricula will perceive a doctrinal conflict where none exists.
• Sufi-shrine substitution risk across at least six terms (خُدایُک دوست, کامل, حکمت, صبر, بزرگ, دُعا/anointing) where existing, vivid, doctrinally-loaded Kashmiri vocabulary could silently supply a Rishi Sufi mystical-attainment or shrine-intercession frame underneath biblical language that sounds experientially similar.
• Unglossed Isaac/Ishmael divergence (James 2:21) risks appearing to a Muslim-background reader as a factual error rather than a known, addressable interfaith divergence, if the historical note is dropped.
• Trika non-dualist collision at James 3:9 (“likeness of God”), which directly contradicts Kashmir Shaivism’s pratyabhijna (self-identity-with-Shiva) doctrine and requires audience-specific handling distinct from the Islamic-context risks above.

Opportunities

• James’s genuine points of contact — orphan/widow care (1:27, echoing Quranic ethics), oath-taking caution (5:12, echoing Islamic yamin discourse), and general divine-testing themes (1:2-3, echoing Quranic testing-of-believers language) — offer authentic, low-risk bridges that this curriculum should name explicitly as shared ethical ground rather than only flag for divergence.
• The book’s proverbial, concrete register (farmer awaiting harvest, mirror, bridle, spring of water) is well suited to natural Kashmiri agrarian idiom, offering strong opportunities for accessible, resonant translation once doctrinal fencing is in place.
• Because this Language Package extends rather than re-derives the Romans baseline, 19 already-vetted, high-confidence terms carry over directly, reducing net new translation-risk surface area compared to building a Kashmiri package from zero.

Recommended actions

1. Route all segments within James 2:14-26 as a single non-splittable unit through mandatory human theologian review in Phase 2 Step 16/17, per the escalation rules in analysis/12_ai_translation_requirements.md.
2. Enforce the “standing fence” requirement (not a one-time footnote) for کامل, حکمت, صبر, خُدایُک دوست, خُدایہٕ نزدیک گژھُن, دُعا-compounds, بزرگ, and گمراہ at every individual occurrence across all five chapters.
3. Confirm all James-specific new coinages — especially عمل/اعمال, اِضحاق, اکہٕ خُدا, and کامل — with a Kashmiri-speaking theologian familiar with both mainstream Sunni theology and Kashmir Shaivism before wide Phase 2 deployment, matching the baseline’s own precedent for imputed_righteousness.
4. Load the James translation memory and doctrine risk registry ALONGSIDE (never in place of) the baseline Romans package for every Phase 2 session; verify version numbers are logged in the segment cache header.
5. Prioritize the six highest-priority Critical coinages (see Key Findings) for earliest theologian sign-off, since they gate the largest share of downstream lesson content.

*Prepared under the same Language Package governance model as the baseline Romans curriculum; see `assets/translation_memory.json`, `assets/bible_term_registry.json`, `assets/doctrine_risk_registry.json`, and `analysis/12_ai_translation_requirements.md` (James extensions) for full supporting detail.*