Executive Summary: Gospel of John (English–Malay)

Curriculum: John 1–21 | Core passage: John 3:1–21 | Language pair: English–Malay Extends: Romans Language Package (baseline, reused exactly)

Why it matters

Malay is, on paper, one of the best-positioned languages in this pipeline for Bible translation — it has the longest continuous Bible translation history in the batch (since 1629) and long-settled, deliberately non-syncretistic vocabulary for its highest-risk terms (Allah, Yesus, Kristus, Anak Allah). But John’s Gospel pushes harder against that settled vocabulary than Romans did: it is saturated with deity claims staged as correctly understood by hostile hearers (5:18, 10:33, 19:7), climaxing in a single verse (20:28) that converges Malaysia’s two most legally contested theological terms in personal address to Jesus. This curriculum also introduces a distinctive, high-stakes risk absent from Romans entirely: a standard Malaysian Islamic apologetic argument that identifies John’s promised “Counselor” with Muhammad (the periklytos/Ahmad argument, tied to Qur’an 61:6). Getting this curriculum’s translation requirements right is not a routine glossary extension — it is the pipeline’s highest-density collision surface between Christian doctrine and both tawhid and Malaysia’s own legal history around religious vocabulary.

Key findings

• 30 doctrines analyzed, full-book coverage confirmed across all 21 chapters of John; 16 rated Critical, 10 High, 4 Medium, 0 Low. 26 of 30 doctrines (87%) require mandatory human theologian review, up from Romans’ already-high 27-of-37-equivalent bar — reflecting John’s unusually dense concentration of direct deity and Christology claims.
• 66 terms tracked in translation memory: 29 Critical-risk, 24 High-risk, 8 Medium-risk, 5 Low-risk. 53 of 66 terms (80%) are Critical or High risk and require mandatory human theologian review at every occurrence — a materially higher proportion than the Romans baseline.
• A genuinely new, pervasive collision not present in Romans: the Malay word Kebenaran must now carry two unrelated Critical-tier doctrinal payloads — righteousness (inherited from Romans) and truth (new to John, appearing 10+ times, including at the Gospel’s most quoted verses, 14:6 and 8:32). Every occurrence must be tagged with its Greek original in the Phase 2 segment cache.
• A genuinely new apologetic collision not present in Romans: John 14–16’s “Paraclete/Counselor” intersects with a standard, well-documented Malay-language Islamic apologetic argument claiming this passage foretells Muhammad. This requires direct, non-avoidant teaching-note rebuttal, not just correct translation.
• The single highest-stakes verse in the entire two-curriculum pipeline is John 20:28 (“Ya Tuhanku dan Allahku!”), converging Tuhan and Allah — the two terms with the deepest documented Malaysian legal history (2013 Court of Appeal; 2021 Kuching High Court) — in unqualified, Jesus-affirmed personal address.

Risks

• Silent softening under fluency pressure: several John-specific renderings are structurally fragile — a natural-sounding, more idiomatic Malay alternative exists and is wrong (e.g., “sehati/sepakat” for John 10:30’s “we are one”; “sudah berakhir” for John 19:30’s “it is finished”; dropping the “tunggal” qualifier from Anak Allah; dropping the “(dari atas)” parenthetical from “born again”). Batch translation at scale is the likeliest place these errors enter undetected.
• Apologetic weaponization: the Paraclete passages (John 14:16, 14:26, 15:26, 16:7) are live ammunition in real-world Malay-language interfaith exchange; an imprecise or transliterated rendering (e.g., a loanword resembling “Paraklitos”) could inadvertently strengthen, rather than rebut, the periklytos/Ahmad argument.
• Legal exposure on mission content: John’s sending/evangelism passages (4:34-38, 13:16, 13:20, 17:18, 20:21-22) sit inside Malaysia’s state Islamic administration enactments restricting proselytization of Muslims; this is a pastoral AND legal-safety risk, not solely a translation-accuracy one.
• Present-tense doctrines read as future-deferred: John’s repeated present-tense assurance and judgment claims (3:18, 3:36, 5:24, 10:28-29) run directly against mainstream Islamic eschatology’s Judgment-Day-deferred framework; softening Malay verb aspect here would quietly convert a distinctive Johannine claim into a generic, unremarkable one.

Opportunities

• John’s own text does fencing work for us in places Romans could not: John 18:36 (“My kingdom is not of this world”) directly resolves the Kerajaan Allah/government ambiguity; John 19:34-35’s blood-and-water eyewitness detail directly answers Qur’an 4:157’s denial of Jesus’s death; John 5:18 and 10:33 present the deity claim as the hostile hearers’ own correct understanding, which is rhetorically stronger than an assertion made only by friendly narrators.
• Genuine cultural bridges exist and should be used deliberately: the anak angkat (adoption) concept remains low-friction per the Romans baseline; Malaysia’s Hari Raya Aidiladha sacrificial tradition (Qur’an 37:107) offers real entry into Lamb-of-God substitutionary logic, provided the once-for-all distinction is taught explicitly; Malay royal-lineage tradition (salasilah diraja) supports the Son of Man/Davidic background.
• This document’s requirements are additive, not disruptive: every Romans-baseline rendering is reused exactly; production teams already trained on the Romans Language Package require only incremental onboarding to the John-specific rules.

Recommended actions

1. Load assets/translation_memory.json and assets/doctrine_risk_registry.json (both Romans and John editions) before any Phase 2 segment translation; treat the two as one combined enforcement database, never one in isolation.
2. Implement the four John-specific hard validation rules as automated pre-submission gates, not reviewer-discretion checks: (a) Kebenaran must carry a greek_original tag; (b) “tunggal” must be present in all monogenēs contexts; (c) “(dari atas)” must be present in all born-again contexts; (d) “sehati/sepakat” and “sudah berakhir” are hard-blocked strings in their respective contexts.
3. Route all Paraclete-passage segments (John 14:16, 14:26, 15:26, 16:7) and all Kebenaran-tagged segments to mandatory human theologian review with no sampling exception, given their combined Critical-tier and apologetic-sensitivity status.
4. Brief all Phase 2/3 production staff on the periklytos/Ahmad argument and the Allah legal history explicitly, per analysis/04_comparative_theology.md, so teams can explain — not just apply — these choices if questioned.
5. Prioritize theologian review queue sequencing by chapter density: John 3 (core passage), 8, 10, 14, 16, and 20 carry the highest concentration of Critical-risk terms and should be reviewed first.

---

Companion documents: assets/translation_memory.json, analysis/12_ai_translation_requirements.md, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, analysis/11_doctrine_analysis.md, analysis/08_core_glossary.md, analysis/07_semantic_analysis.md, analysis/06_linguistic_gap_analysis.md, analysis/05_translation_landscape.md, analysis/04_comparative_theology.md.