Executive Summary — 2 John | English → Hebrew Language Package

Curriculum: 2 John (single chapter, 13 verses, full-book coverage) Core passage: 2 John 1:4–11 Baseline authority: Romans Language Package for Hebrew (extended, not contradicted, by this curriculum)

---

Why It Matters

2 John is thirteen verses long, yet it packs the same density of Critical-tier doctrinal collision risk as entire chapters of Romans — because a Hebrew-speaking audience meets, in rapid succession, the Incarnation (v.7), Christ’s co-equal Sonship (vv.3, 9), and a direct instruction to withhold hospitality (vv.10–11) that runs against one of Judaism’s most cherished values, הַכְנָסַת אוֹרְחִים. This is the first curriculum in the Hebrew Language Package family to introduce a genuinely new Critical-risk cultural collision point beyond anything documented in the Romans baseline. Getting this short letter right is disproportionately high-stakes: a mistranslation here does not dilute across sixteen chapters — it lands immediately and cannot hide behind volume.

Key Findings

• 34 new theological terms introduced across the letter’s four core doctrines (Walking in Truth and Love; Warning against Deceivers Denying the Incarnation; Hospitality and Doctrinal Discernment; Perseverance in the Teaching of Christ), plus 11 baseline Romans terms reused exactly and extended into new contexts — 45 enforced entries total in assets/translation_memory.json.
• 9 Critical-risk and 14 High-risk terms (23 total) require mandatory human theologian review at every occurrence, per assets/bible_term_registry.json — nearly double the proportional density of Critical/High terms found across the much longer Romans baseline.
• 8 of 11 doctrines (4 Critical + 4 High) identified in assets/doctrine_risk_registry.json require human theologian review; 2 require native speaker review; only 1 (Christian Joy and Fellowship, vv.12–13) is automated-review-only.
• Two genuinely novel constructed Hebrew renderings with no settled precedent were required: צוֹרֵר הַמָּשִׁיחַ (“antichrist”) and לֶקַח הַמָּשִׁיחַ (“teaching of Christ”) — neither inherits established tradition and both must be flagged as deliberate translation choices, not received vocabulary.
• The existing Hebrew-language translation landscape contains documented doctrinally contaminated sources (non-Trinitarian/Unitarian editions, Jehovah’s Witnesses material, Hebrew Roots/One Law fringe translations, anti-missionary polemical commentary) that directly conflict with this letter’s own Christological warnings — an ironic and material sourcing risk unique to this curriculum.

Risks

• Hospitality collision (Critical, vv.10–11): An under-scoped Hebrew rendering of “do not receive him… do not greet him” could land as a wholesale repudiation of הַכְנָסַת אוֹרְחִים, provoking rejection of a legitimate, narrowly-targeted doctrinal instruction. No single word choice is “wrong” in isolation — the risk is a doctrine-culture collision requiring mandatory scope-narrowing teaching material.
• Sonship/Deity sharpening (Critical, vv.3, 9): v.9’s “has/does not have God” idiom makes relationship with the Father explicitly conditional on the Son — the single highest-risk ambiguity in the letter, sharpening the baseline’s already-Critical Shema-collision risk into an unambiguous either/or claim.
• Mechanical homograph risk (High, v.9 ×2, v.10): Unpointed לקח (teaching) is visually identical to the verb “he took”; without mandatory niqqud or construct disambiguation at every occurrence, this produces parsing errors independent of doctrinal content.
• Torah-collision drift (High, vv.4–6): Documented pattern in circulating Hebrew Roots/One Law materials to reframe “his commandments” toward general Torah-observance; this is the most common doctrinal drift point found in the existing translation landscape survey.
• Antichrist register mismatch (Critical, v.7): Transliteration risks Israeli horror-genre/pop-culture associations that trivialize a serious eschatological category; the constructed alternative requires active teaching since it carries no inherited recognition.

Opportunities

• מתהלכים / הֲלָכָה resonance: “Walking in truth” naturally connects to an honored existing Jewish category of behavioral seriousness — a genuine asset when properly calibrated away from technical legal-observance narrowing.
• שלום withheld as a greeting (vv.10–11): Because שלום is Hebrew’s own reflexive daily greeting, deliberately withholding it is unusually vivid and weighty for a Hebrew-speaking reader — more forceful here than in most target languages.
• פֶּה אֶל פֶּה (v.12): A direct, positive echo of Numbers 12:8’s description of God speaking with Moses — pure asset, zero collision, ready to be leveraged in teaching material.
• הַזָּקֵן (the Elder, v.1): Resonates positively with the deeply rooted communal-elder tradition (Exodus 18; Numbers 11; the Sanhedrin) — an asset for establishing the author’s pastoral authority.
• “New yet old” commandment (v.5): Resonates naturally with Jeremiah 31:31’s own renewed-covenant language, offering a built-in bridge for teaching continuity-through-fulfillment rather than abrogation.

Recommended Actions

1. Merge assets/translation_memory.json (2 John, version 1) into the active Phase 2 enforcement database before any segment translation begins; do not process 2 John segments against the Romans-only translation memory.
2. Route all 8 Critical/High doctrines and all 23 Critical/High terms through mandatory human theologian review per analysis/12_ai_translation_requirements.md’s escalation rules — with special priority on v.7 (incarnation-denial), v.9 (Sonship/Deity relational-possession clause), and vv.10–11 (hospitality) as the three highest-stakes clusters.
3. Enforce mandatory niqqud or construct-phrase disambiguation on every occurrence of לֶקַח הַמָּשִׁיחַ before accepting any segment as complete — treat an unpointed, undisambiguated occurrence as a validation failure, not merely a flag.
4. Exclude, categorically, any phrasing traceable to the five documented contaminated-source categories in analysis/05_translation_landscape.md §4, regardless of surface fluency.
5. Ensure all accompanying teaching material for vv.10–11 explicitly states the narrow doctrinal scope of the hospitality restriction, kept separate from the verse translation itself, so the restriction is never misread as a general anti-hospitality or anti-evangelism principle.
6. Carry forward, unchanged, the YouVersion version-confirmation and hyperlink-construction pattern established in analysis/05_translation_landscape.md §6 into all subsequent Phase 2 outputs for this curriculum.

---

This summary synthesizes analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, analysis/11_doctrine_analysis.md, analysis/04_comparative_theology.md, analysis/06_linguistic_gap_analysis.md, analysis/05_translation_landscape.md, assets/bible_term_registry.json, and assets/doctrine_risk_registry.json. All counts above are synchronized with those source files as of this document’s date.