Executive Summary — English → Dutch | Gospel of John Translation Requirements

Why it matters

The Gospel of John curriculum extends the completed Romans (dutch) Language Package into new, higher-stakes doctrinal territory. John concentrates the New Testament’s strongest deity-of-Christ claims (the Logos, the absolute “Ik ben,” “Mijn Heere en mijn God”), its defining new-birth text (John 3, this curriculum’s core passage), and its most historically dangerous single translation decision in the whole Bible — the rendering of “hoi Ioudaioi” (“the Jews”) — into a Dutch context carrying acute WWII-deportation-era sensitivity and a strong contemporary Reformed Christian-Zionist readership. Getting this package wrong risks either doctrinal flattening (a diluted deity-of-Christ claim, echoing the Jehovah’s Witnesses’ Dutch Nieuwe-Wereldvertaling) or historical harm (a collective-guilt reading of Jewish identity). Getting it right requires Phase 2 tooling with materially more per-verse escalation logic than Romans needed.

Key findings

• 81 enforced terms now govern this curriculum: 24 inherited verbatim from the Romans baseline, 56 new John-specific terms, plus 1 recommended addition (“wedergeboorte,” pending native speaker sign-off).
• 40 of those 81 terms (49%) are Critical or High risk (14 Critical, 26 High), nearly double the proportion in the Romans baseline — driven by John’s density of absolute deity claims, the seven “I Am” statements, and the “the Jews” translation decision.
• 21 doctrines are tracked in the doctrine risk registry; 17 require mandatory human theologian review (11 Critical + 6 High), and the remaining 4 require native speaker review. Zero doctrines in this curriculum are automated-review-only — a meaningfully higher review burden than Romans, which had 6 automated-only doctrines.
• The core passage, John 3:1-21, is pre-flagged for 100% human theologian review by default, concentrating 8 of the registry’s 21 doctrines (5 of its 11 Critical doctrines) in twenty-one verses — most notably the untranslatable anōthen (again/from-above) wordplay and the water-and-Spirit sacramental fault line at 3:5, which this curriculum deliberately does not resolve in the base translation text.
• Three forbidden substitutions are newly added for this curriculum, beyond the baseline’s existing list: “Voorspraak” for the Holy Spirit’s Counselor role (Catholic saints’-advocacy collision), “Pasen” for pre-resurrection Passover references (anachronistic Easter-feast import), and any implied-predicate softening of the absolute “Ik ben” (divine self-designation).

Risks

• “Hoi Ioudaioi” (the Jews): the single highest-stakes term in the curriculum. A uniform “de Joden” across all ~70 occurrences risks reactivating collective-guilt readings with the heaviest local historical weight of any decision in this project. Mitigation requires per-verse, not per-term, escalation — a workflow pattern this curriculum introduces that did not exist in the Romans baseline.
• Sacramental fault lines (John 3:5; 6:53-56): Reformed and Catholic readings diverge sharply on baptismal regeneration and Eucharistic presence. Silent resolution in either direction would misrepresent one of the Netherlands’ two dominant Christian traditions.
• Cult/sect contamination: the Jehovah’s Witnesses’ Dutch Nieuwe-Wereldvertaling is in active circulation and specifically attacks this curriculum’s central doctrine (Deity and Pre-existence of Christ) at John 1:1, 1:18, and 8:58. Any drift toward its renderings must be auto-flagged.
• Secularization drift: “eeuwig leven,” “geloven,” and “wereld” are all high-frequency terms vulnerable to flattening into generic, duration-only, or relativistic readings in one of Europe’s most secularized populations.

Opportunities

• Dutch’s existing four-way split for paraklētos (Trooster/Pleitbezorger/Helper/Voorspraak) is fully documented and fenced — a stronger position than most language pairs in this class of project, once “Voorspraak” is locked out.
• John’s own self-glossing habits (Rabbi, Rabbouni, Messias, Golgotha) reduce transliteration risk relative to Romans, since the source text itself supplies in-line explanations translators can simply retain.
• The HSV/NBV21 dual-reference-translation strategy, already validated for Romans, transfers cleanly to John with only one adjustment (HSV preferred over NBV21 specifically at 8:58 for tense fidelity).

Recommended actions

1. Adopt assets/translation_memory.json (John, v1) and the extended analysis/12_ai_translation_requirements.md into Phase 2 tooling before any segment translation begins; confirm both this file and the Romans baseline TM load together.
2. Stand up the per-verse “the Jews” escalation ledger as a persistent, cross-worker-synchronized Phase 2 workflow artifact, not a one-time term decision — this is a net-new process requirement versus Romans.
3. Route John 3:1-21 (core passage) to 100% human theologian review regardless of automated quality score, given its concentration of Critical-tier material.
4. Confirm native speaker sign-off on “wedergeboorte” before promoting it from recommended to enforced status in the translation memory.
5. Verify YouVersion version_id values for HSV and NBV21 against a live API lookup before generating any production hyperlinks (currently unverified placeholders: HSV 1394, NBV21 3839).