Log in

or use your email

Search the Library

Keyword search across Doctrine Analysis, Core Glossary, Comparative Theology, and Regional Analysis. Mention a language name for the best results — e.g. "remnant burmese" or "what glossary terms conflict for burmese."

Type at least 2 characters to search.

Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Download Translation Skill

John — javanese

TRI knowledge bundle for John (javanese).

Executive Summary

Executive Summary: Gospel of John — Javanese Language Package

Phase 1 Complete

Why it matters: The Gospel of John will be the second curriculum translated into Javanese under this pipeline, building directly on the Romans baseline. John’s Christology-dense vocabulary — the Word, the Seven “I Am” statements, the Father-Son unity — sits closer to Java’s single most dangerous doctrinal collision point (the kejawen mystical teaching manunggaling kawula gusti) than almost anything in Romans, and its core passage, John 3:1-21, hinges on wordplay (ἄνωθεν, πνεῦμα) that has no natural one-word Javanese equivalent at all.

  • John introduces significantly denser deity-claim vocabulary per chapter than Romans, concentrated in a Muslim-majority context where competing Christological claims (Isa as a non-divine prophet) and syncretic kejawen claims (self-Divine mystical fusion) are both live, everyday realities, not merely historical curiosities.
  • The core passage is not a scope boundary but a five-Critical-doctrine anchor (New Birth, Eternal Life, God’s Love for the World, Christ’s Substitutionary Death typology, Judgment/Unbelief), plus one Medium doctrine (Kingdom of God) — every segment of John 3:1-21 requires human theologian review.

Key findings:

  • Full-book coverage confirmed. All 21 chapters of John have been analyzed; chapters contributing no new doctrine-matrix entries (2, parts of 18, parts of 21) are explicitly documented as reviewed, not silently skipped.
  • 29 doctrines identified across the full book (13 Critical, 12 High, 3 Medium, 1 Low), extending but never contradicting the baseline Romans doctrine framework — 25 of these 29 doctrines require mandatory human theologian review.
  • 130 terms are now enforced in translation memory for this curriculum: 28 terms inherited exactly from the Romans baseline (9 Critical, 9 High, 4 Medium, 4 Low, 2 unlisted-Medium/Low mix) plus 88 new John-specific terms (22 Critical, 21 High, 27 Medium, 18 Low) registered for the first time — 61 terms across the combined inherited-plus-new set are Critical or High risk and require mandatory human theologian review at every occurrence.
  • The single highest-risk item in the entire language package is now identified as John 10:30 (“I and the Father are one”) against manunggaling kawula gusti — a collision more direct and more culturally live than any single term flagged in the Romans baseline, because this kejawen teaching is taught and practiced across Javanese spiritual circles today, not confined to history.
  • Two untranslatable wordplays sit inside the core passage itself: the ἄνωθεν double meaning (“again”/“from above,” 3:3-7) that drives Nicodemus’s own confusion, and the πνεῦμα wind/Spirit pun (3:8) — both require mandatory translator footnotes rather than a clean lexical solution.

Risks:

  • Theological: Unqualified use of Sabda (Word/Logos) risks assimilation to the Islamic Kalimatullah Christology, which affirms Jesus as “a Word from God” while explicitly denying deity — the opposite of John 1:1’s claim.
  • Syncretism: Manunggal-root vocabulary anywhere near a Father-Son unity statement (10:30, 14:9-11, 17:11,21-23) risks the single most dangerous collapse in the whole package, into an attainable mystical state rather than a unique, eternal, ontological relationship within the Godhead.
  • Root-collision recurrence: The kaslametan/slametan collision already flagged in Romans recurs more frequently in John (3:17; 4:42 “Savior of the world”; 5:34; 10:9; 12:47) than in Romans itself, multiplying the number of occurrences requiring the mandatory distinguishing note.
  • Political resonance: Mardika/merdeka (freedom, ch.8) carries live Indonesian national-independence resonance that could distort the sin-bondage teaching if left unqualified — notably, the text’s own original hearers made exactly this misreading (8:33).
  • Consistency risk: The Seven “I Am” Statements and the absolute ἐγώ εἰμι form share identical Javanese surface grammar (“Kula punika…”) with ordinary self-introduction; without the mandated standing translator notes, the divine-Name resonance of 8:58 is invisible to readers.

Opportunities:

  • Javanese already possesses a mature, continuous Christian Bible tradition (Gusti Allah, Gusti Yesus, Roh Suci, kaslametan) that John’s vocabulary can build on directly, minimizing the need for new coinages outside the doctrinally load-bearing terms catalogued here.
  • Sabda’s royal/authoritative-utterance resonance (“sabda pandita ratu”), once properly fenced with explicit predication, is a genuine asset for conveying the Word’s binding divine authority — a rare case where a crowded semantic neighborhood, correctly handled, strengthens rather than weakens the doctrine.
  • John’s own text supplies built-in teaching moments for its hardest doctrines: Nicodemus’s literal misunderstanding of “born again” (3:4) and the disciples’ own political misreading of “freedom” (8:33) are opportunities to teach the correct doctrine using the passage’s own narrative logic, not an imported analogy.
  • The core passage’s concentration of five Critical doctrines in twenty-one verses means Phase 2 reviewer effort can be front-loaded efficiently: mastering John 3:1-21’s fencing rules equips reviewers for a large share of the doctrinal risk found across the rest of the book.

Recommended actions:

  1. Load assets/translation_memory.json, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, and analysis/12_ai_translation_requirements.md (John) alongside the full Romans baseline package before any Phase 2 segment translation begins — never one without the other, since John relies on baseline-governed shared vocabulary throughout.
  2. Prioritize human theologian review capacity for John 3:1-21 first, given its five-Critical-doctrine density, before broader Phase 2 processing of the remaining chapters begins.
  3. Enforce the mandatory translator-footnote requirements at John 3:8 (wind/Spirit pun) and at every absolute ἐγώ εἰμι occurrence without exception; these are not optional style choices but the only available mitigation for genuinely untranslatable Greek wordplay.
  4. Apply the “sami setunggal” / never-manunggal-root fencing rule to every occurrence of Father-Son unity language with zero tolerance for stylistic variation, given this doctrine’s status as the package’s single highest cultural-collision risk.
  5. Extend the kaslametan distinguishing-note requirement to all five John salvation-root occurrences (3:17; 4:42; 5:34; 10:9; 12:47), not only to segments that would trigger the rule under the Romans baseline alone.

This summary reflects Phase 1 Steps 1-11 for the Gospel of John Javanese Language Package. See analysis/11_doctrine_analysis.md for the full doctrine matrix, analysis/08_core_glossary.md and analysis/06_linguistic_gap_analysis.md for term-level detail, and analysis/12_ai_translation_requirements.md for the complete Phase 2 AI instruction set.

View full executive summary page →

Culture Impact Analysis

Doctrines

Glossary

Library content is free and openly licensed under CC BY-NC-SA 4.0 — share and adapt it for non-commercial use, with attribution to tri-bible.ai.

Give feedback

How would you rate this page?

0 / 500 words