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

Executive Summary

Executive Summary: The Gospel of John (English → Hebrew)

Why it matters: John is the most theologically dense book in the New Testament for a Hebrew-speaking destination audience — every chapter runs directly through Tanakh-shared vocabulary (light, water, bread, shepherd, vine, “I am,” the Word) that is simultaneously the translation’s greatest asset and its sharpest risk. A Hebrew reader does not encounter this vocabulary as foreign; they encounter it as their own scriptural inheritance being reapplied to claims (the Word who is God, “I and my Father are one,” “my Lord and my God”) that sit directly against the Shema — the single most centrally recited affirmation of Jewish identity. Getting this translation right is not a matter of finding equivalent words; it is a matter of teaching a Hebrew-literate reader to hold their own tradition’s vocabulary open to a claim it was not previously asked to carry.

Key findings:

  • 82 glossary terms now govern Phase 2 translation of John: 27 inherited byte-for-byte from the Romans baseline package, plus 55 new John-specific terms introduced across all 21 chapters (see assets/translation_memory.json).
  • Of these 82 terms, 37 are Critical risk and 25 are High risk — 62 terms (76% of the entire glossary) require mandatory human theologian review before any segment containing them may be approved. Only 2 terms are Low risk.
  • The doctrine risk registry logs 28 doctrines across the full book (9 curriculum-assigned doctrines plus 19 cross-cutting doctrines this book’s vocabulary makes unavoidable, e.g., “The Jews,” Israel/Vine typology, Temple fulfillment). 15 are Critical and 7 are High — 22 of 28 doctrines (79%) require human theologian review; the remaining 6 require native speaker review; zero doctrines are automated-review-only, a materially higher oversight burden than the Romans baseline package carried.
  • The core passage (John 3:1-21) alone triggers 9 of the 28 registry doctrines simultaneously — the highest doctrinal density of any single passage surveyed in either language package to date.

Risks:

  • The untranslatable core-passage pun: Greek ἄνωθεν’s double sense (“from above”/“again,” John 3:3-4) has no single Hebrew equivalent; without a mandatory standing translator’s note, Nicodemus’s entire narrative misunderstanding — the engine of the core passage’s dialogue — silently disappears from the Hebrew reader’s experience.
  • “The Jews” (היהודים): the single highest-sensitivity recurring term in the book (12+ chapters), compounded by John 8:44’s documented history of weaponization against Jewish people generally. This term is release-blocking: no segment containing it may ship without individual per-occurrence referent assessment, and 8:44 specifically may not ship without a mandatory contextual note.
  • Paraclete/פרקליט collision: Modern Hebrew’s most natural cognate for “Counselor” has narrowed almost entirely to “attorney” (State Attorney’s Office usage), and the recommended primary alternative (הַמְנַחֵם) collides with a traditional Rabbinic name for the Messiah — a double naming risk unique to this doctrine.
  • Sectarian rendering contamination: the existing Hebrew-language translation landscape includes documented demoted-Christology patterns (New World Translation-derived אֱלוֹהַ substitutions, Sacred-Name יהוה insertions, fringe “restored Hebrew Gospel” retranslations) that a Hebrew-speaking learner is likely to encounter independently; Phase 2 validation must actively screen for and reject any back-translation matching these patterns.
  • Vine, Lamb, and Temple typology: three separate doctrines (Israel-as-vine, Passover/Lamb, Temple fulfillment) each carry genuine supersessionism risk if taught as replacement rather than fulfillment — a risk category with real historical weight (the Church’s own history of antisemitic misreading) rather than a merely theoretical translation subtlety.

Opportunities:

  • אני הוא (John’s “I am” statements) recovers Isaiah’s own theophanic self-declaration idiom (41:4; 43:10, 13, 25; 46:4; 48:12) with unusual precision — a stronger positive resource than most target languages possess for this doctrine, provided all seven predicated forms plus the absolute form are rendered with total consistency.
  • עולם’s double duty (world / root of “eternal life”) produces a genuine Hebrew-specific wordplay at John 3:16 (“God so loved the olam… gives chayei olam”) that is absent from the Greek — a teaching asset, not merely a risk, if actively surfaced.
  • רוח’s wind/Spirit pun (John 3:8) survives translation into Hebrew perfectly, unlike the ἄνωθεν pun — a rare case where Hebrew preserves a Greek wordplay intact.
  • חסד ואמת (grace and truth, John 1:14, 17) recovers Exodus 34:6’s own covenant-character idiom exactly, letting the Incarnation doctrine be taught as fulfillment of Sinai revelation rather than a foreign import.
  • הישועה מן היהודים (John 4:22, “salvation is of the Jews”) gives the curriculum a direct, first-person dominical affirmation of Israel’s redemptive priority — reinforcing rather than complicating the baseline’s “to the Jew first” framing.

Recommended actions:

  1. Lock assets/translation_memory.json (82 terms) and assets/bible_term_registry.json as the binding Phase 2 glossary before any batch translation begins; treat every “Inherited from Romans package” entry as immutable.
  2. Route all 62 Critical/High glossary terms and 22 Critical/High doctrines through mandatory human theologian review per the escalation rules in analysis/12_ai_translation_requirements.md; do not permit automated-only approval anywhere in this book.
  3. Attach the five mandatory standing translator’s notes (ἄνωθεν double-sense; Paraclete advocate/comforter/Menachem disambiguation; “the Jews” referent assessment; John 8:44 contextual framing; the עולם/חיי עולם wordplay) at every qualifying occurrence, not merely at first occurrence per chapter.
  4. Confirm the working YouVersion Hebrew version ID (1275) against the live catalog and lock the JHN book-code hyperlink pattern before batch reference-link generation.
  5. Screen every back-translated segment against the documented sectarian-pattern list (§4 of 05_translation_landscape.md) as a hard validation gate, in addition to the standard forbidden-substitution checks.

This summary synthesizes analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, analysis/11_doctrine_analysis.md, analysis/04_comparative_theology.md, analysis/06_linguistic_gap_analysis.md, and analysis/05_translation_landscape.md. All statistics are drawn directly from those documents and from assets/translation_memory.json as delivered in this Phase 1 pass.

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