Executive Summary: James — Javanese Translation Requirements

Why it matters

The book of James is going into production as a Javanese Bible-study curriculum built on top of an already-shipped Romans Language Package. James is short, concrete, and pastorally beloved — but it concentrates an unusually dense cluster of doctrinally load-bearing vocabulary that collides with three distinct Javanese religious frameworks at once: mainstream Islamic-Javanese vocabulary (dunya/akhirat, nafs, wali, sabar), the region’s syncretic kejawen mystical layer (kasampurnan, ngèlmu, kasekten, dhemit/lelembut), and the pipeline’s own prior Romans commitments (kaslametan, kaanggep bener dening Gusti Allah). Getting this wrong risks either a translation that appears to contradict Romans’ own doctrine of justification by faith alone, or one that quietly imports ascetic-mystical, ritual-potency, or grave-veneration meanings into James’s plain ethical instruction. Getting it right requires more standing translator notes, per-occurrence vigilance, and theologian review than Romans did, packed into a shorter book.

Key findings

• The single highest-stakes decision in the whole package: James 2:21/2:24/2:25 reuse the Romans-fixed forensic-justification phrase for a different sense (vindication of genuine faith by works), and without a mandatory standing translator note at every occurrence, James 2:24 will read as a direct contradiction of Romans 3:28.
• A five-times-recurring Critical collision: τέλειος (“perfect/mature/complete,” James 1:4, 1:17, 1:25, 2:22, 3:2) sits directly on top of the baseline’s already-forbidden kasampurnan (Javanese ascetic-mystical attained perfection). This is not a one-off flag like in Romans — it recurs across nearly every chapter and needs independent verification each time.
• A same-chapter sense-split with reversed risk direction: James 5 uses σῴζω for both eternal salvation (5:20, where the established kaslametan + slametan-ritual note is correct) and physical healing (5:15, where using that same root would be the wrong choice and reinforce, not correct, the ritual association the baseline works to avoid).
• A single-word collision with a live devotional practice: “friend of God” (2:23) most naturally maps to Javanese wali, the term for the venerated Wali Songo saints whose graves are pilgrimage sites today — this is not a historical or abstract risk, it is a currently practiced tradition.
• Full-book scan confirms 15 distinct doctrines across all 5 chapters, none silently skipped, with 12 of 15 requiring mandatory human theologian review — a notably higher proportion than Romans’ comparable ratio, driven by James’s density of concrete, culturally-loaded vocabulary in a short span of text.

Risks

• Critical, theologian-review-required doctrines: 4 of 15 (Faith and Works; Worldliness versus Friendship with God; Prayer and Healing; Sanctification and Spiritual Maturity).
• High risk doctrines: 8 of 15, also requiring theologian review — bringing the total requiring theologian oversight to 12 of 15 doctrines (80%).
• Medium risk: 2 doctrines (native speaker review); Low risk: 1 doctrine (automated review only).
• At the term level (per the James-specific bible_term_registry.json), 14 terms are Critical risk and 24 are High risk — 38 terms combined requiring mandatory human theologian review, before counting the additional Critical/High terms inherited unchanged from the Romans baseline (God, Jesus, Lord, Holy Spirit, Grace, Righteousness, Salvation, Sin, Glory, Law, Election, Providence, Sanctification, Imputed Righteousness — 14 further terms already flagged Critical/High in Romans and reused exactly here).
• Compounding risk pattern unique to James: several of its highest-risk terms are not isolated occurrences (as most Romans flags were) but recurring word families (τέλειος x5) or same-book sense-splits (σῴζω x2 directions, δικαιοσύνη ethical-vs-forensic, πνεῦμα anthropological-vs-Holy-Spirit) — meaning a single correct rendering early in the book does not guarantee correctness later, and per-occurrence checking cannot be shortcut by pattern-matching a prior segment.

Opportunities

• The Romans baseline vocabulary carries over cleanly for 23+ shared terms (God, Jesus, Lord, Holy Spirit, Father, Faith, Grace, Righteousness, Salvation, Law, Sin, Glory, Kingdom of God, Church, Election, Prophet, Apostle, Providence, Peace, Sanctification, Imputed Righteousness, Intercession) — no new vocabulary decisions needed there, only James-specific usage notes.
• James’s concrete, agrarian, and household imagery (tongue as fire, bridle, rudder, mirror, spring, fig tree) is largely low-risk and translates naturally, giving reviewers room to concentrate scrutiny on the identified Critical/High cluster rather than spreading thin across the whole letter.
• The letter’s short length (108 verses across 5 chapters) makes exhaustive, verse-by-verse theologian review operationally feasible in a way that would be harder for a longer book — full-book coverage has already been completed in Phase 1 (Steps 4–8) with no chapter or verse range silently omitted.
• Standing translator notes, once written, are highly reusable: the justification note, the τέλειος note, and the σῴζω sense-selection note each apply verbatim across multiple occurrences, reducing marginal review cost after the first correct instance is documented.

Recommended actions

1. Lock the mandatory translator notes now (justification vindication-vs-declaration; τέλειος maturity-vs-perfection; σῴζω healing-vs-salvation) into Phase 2 tooling as non-skippable segment attachments, not optional annotations, given how easily a single lapse reopens a doctrinal collision already flagged as Critical.
2. Route all of James 2:14-26 as a single reviewed unit to human theologian review rather than segment-by-segment, since the passage’s internal coherence (Abraham v.21-23, Rahab v.25, the body/spirit analogy v.26) depends on consistent handling of δικαιόω, φίλος θεοῦ, and πνεῦμα across the whole unit.
3. Run a dedicated cross-occurrence consistency pass on the τέλειος family and the σῴζω split after initial batch translation and before final Doctrinal Fidelity Review (Step 17), since these risks specifically manifest as inconsistency between occurrences rather than error within a single occurrence.
4. Brief native speaker reviewers explicitly on the krama/ngoko register risk in James 2:1-9 (favoritism), since Javanese’s own status-encoded register system could inadvertently reproduce the very partiality the text condemns if narrative dialogue is not handled with care.
5. Carry the James translation_memory.json and bible_term_registry.json forward as permanent additions to the shared language package, not James-only artifacts, since several entries (τέλειος fencing, δαιμόνια fencing, σῴζω-healing fencing) will recur in any future NT epistle curriculum for this language.