01 Executive Summary — James — English → Manipuri Language Package

Why it matters

James is a short, densely load-bearing epistle whose central argument — that genuine, saving faith necessarily produces works (James 2:14-26) — sits directly on top of the single most theologically sensitive term-reuse risk this project has yet documented: the identical Manipuri phrase অচুম্বা ওইহনবা (“justified”) that the Romans baseline fixed for initial forensic declaration by faith alone must, in James, carry a demonstrative/vindicating sense instead. Get this wrong and the curriculum either (a) teaches Scripture contradicting itself on justification, or (b) hands readers from Manipur’s actively practiced Gaudiya Vaishnava bhakti tradition — where standing with the divine is built through সেবা, devotional merit-service — exactly the works-based misreading this entire Language Package has otherwise been built to prevent. James also introduces three further live-tradition collision points with no Romans precedent: Abraham as “friend of God” (colliding with sakhya bhāva, an actively practiced bhakti-devotional friendship-mode toward Krishna), anointing the sick with oil (colliding with both the Sanamahi maiba’s ritual healing practice and Vaishnava abhisheka), and the Lord’s return (colliding with the Vaishnava expectation of Kalki, Vishnu’s awaited final avatar).

Key findings

• 25 doctrines identified across all 5 chapters (full-book coverage, no chapter silently skipped): 9 Critical, 13 High, 3 Medium, 0 Low. 22 of 25 require mandatory human theologian review; 3 require native speaker review; none are automated-only.
• ~83 James-specific terms catalogued in the term registry, of which 19 are Critical risk and 30 are High risk (49 of 83 — roughly 59% — require theologian-level scrutiny), on top of 22 inherited Romans-baseline terms carried forward unchanged.
• James’s vocabulary gap profile differs from Romans: rather than requiring wholly new theological categories, most risk is concentrated in (a) cross-book harmonization (justification’s two senses) and (b) crowded-neighborhood fencing of new terms against Manipur’s two live, currently practiced traditions — Sanamahism and Gaudiya Vaishnavism — rather than missing vocabulary per se.
• Two lexical items remain unconfirmed and blocking: লে (“tongue,” James 3, blocks the entire “Taming the Tongue” doctrine cluster until verified against a current printed Manipuri Bible) and থাওয়াই অনি (“double-minded,” James 1:8/4:8, risks being heard as Sanamahi spirit-possession without a native-speaker-confirmed non-literal alternative).
• One exegetical ambiguity remains unresolved at the committee level: James 4:5’s disputed πνεῦμα (human spirit vs. Holy Spirit) must not be resolved by default rendering; it requires theological-committee decision before Phase 2 lock-in.

Risks

• Highest risk — cross-canon self-contradiction: without the mandatory Genesis 15:6/Genesis 22 harmonization note at every James 2:21-25 occurrence of অচুম্বা ওইহনবা, learners moving between Romans and James materials may conclude Scripture disagrees with itself on how a person is justified.
• Second-highest risk — sakhya-bhakti absorption: “friend of God” (2:23) and its deliberate antithesis “friendship with the world” (4:4) sit directly inside Manipuri Vaishnavism’s live, taught devotional-relationship framework; mishandling either half of this literary pairing collapses a unique biblical covenant category into an existing bhakti devotional mode.
• Third-highest risk — ritual-practice conflation: anointing the sick with oil (5:14-15) structurally resembles both the Sanamahi maiba’s healing ritual and Vaishnava abhisheka; no lexical choice alone resolves this — only mandatory, consistently-worded theological framing at every occurrence prevents the practice itself from being misread as ritually efficacious rather than as faith-dependent on God’s sovereign will.
• Fourth risk — eschatological structural collision: “the Lord’s coming” (5:7-8) shares a narrative shape (an awaited future divine arrival ending corruption) with the Vaishnava Kalki expectation; this is a structural, not merely lexical, collision requiring the same rigor the baseline applies to অবতার.
• Standing lexical-confidence risk: লে (tongue) is unconfirmed and blocks Chapter 3’s entire doctrine cluster; deploying Phase 2 translation of James 3 before confirmation risks propagating an unverified core term throughout an entire doctrine.

Opportunities

• James 2:23’s citation of Genesis 15:6 is the strongest documented cross-book doctrinal bridge in this project to date: it uses the exact same baseline term (পীথোকপা অচুম্বা চৎনবিরাক) Romans 4:3 builds its entire justification argument on, giving the curriculum a clean, textually-grounded way to teach faith-and-works as one harmonious doctrine rather than two competing claims.
• James’s concrete, proverb-like imagery (fire, mirror, bridled horse, farmer awaiting harvest) is generally easier to render naturally at the target Class 8-10 reading level than Romans’ extended theological argumentation, and translates well into Meitei oral-tradition-adjacent registers without doctrinal loss.
• The Favoritism-and-the-Poor doctrine (1:9-11, 2:1-13), grounded explicitly in the image of God (3:9), offers a theologically clean, non-politically-coded way to teach impartial love that does not require — and this curriculum explicitly avoids — mapping onto Manipur’s contemporary inter-community tensions.
• Because James reuses so much baseline Romans vocabulary (থাজবা, পাপ, য়াথাং, তেংবাং মপুগী থৌরাং, কলিসিয়া), most of the Language Package’s heaviest lexical-engineering work is already done; this curriculum’s remaining work is concentrated in teaching-layer harmonization and fencing rather than new coinage.

Recommended actions

1. Before any Phase 2 work: confirm লে (tongue) against a current printed Manipuri Bible edition; commission native-speaker consultation on a non-literal alternative to থাওয়াই অনি (double-minded); convene the translation committee to resolve James 4:5’s disputed πνεῦμα reading.
2. Bake the harmonization note into templates, not memory: build the mandatory Genesis 15:6/Genesis 22 justification-harmonization note into the Phase 2 segment template itself for every James 2:14-26 segment, so it cannot be silently dropped by a batch worker.
3. Require paired review for the friendship antithesis: flag James 2:23 and 4:4 for joint theologian review whenever either is translated, so the literary pairing is verified as a unit rather than two independent segments.
4. Treat anointing-with-oil (5:14-15) as a standing Critical-review item, not a one-time note: every occurrence across every derived lesson requires the full maiba/abhisheka contrastive framing, verified at each reuse, not only at first translation.
5. Extend, do not replace, the Romans AI instruction set: deploy 12_ai_translation_requirements.md (James extension, v3.0) alongside — never instead of — the Romans baseline (v2.18), since James depends on the baseline’s forbidden-substitution list and dual-tradition framework remaining fully in force.
6. Flag James for a second-pass Phase 1 review focused specifically on Kalki/parousia and sakhya-bhakti/friend-of-God framing with a theologian who has specific fluency in contemporary Manipuri Gaudiya Vaishnava devotional teaching, given that these two collision points have no precedent or fencing template in the Romans baseline.

Full detail supporting every claim above is documented in analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, analysis/06_linguistic_gap_analysis.md, analysis/11_doctrine_analysis.md, assets/translation_memory.json, assets/bible_term_registry.json, and assets/doctrine_risk_registry.json.