Executive Summary — Gospel of John Language Package (Pashto)

Why it matters

The Gospel of John introduces an entirely new theological vocabulary layer on top of the Romans baseline — Logos, life, light, darkness, world, truth, the seven “I Am” statements, the Counselor — and does so in a book whose central claims (Christ’s deity, pre-existence, and unity with the Father) sit at the point of maximum collision with Sunni tawhid theology, the shared religious framework of virtually every Pashto-speaking reader. John also contains this pipeline’s single sharpest textual collision anywhere in Scripture: the Qur’an’s explicit denial that Jesus was crucified (4:157) runs directly against nine full chapters (10-11, 18-20) of John’s own historical, eyewitness-structured argument for exactly that event. Getting this Language Package right is a precondition for every downstream Phase 2 translation decision in this curriculum.

Key findings

• 30 doctrines are tracked in doctrine_risk_registry.json (John v1): 10 Critical, 13 High, 6 Medium, 1 Low — 23 of 30 (77%) require human theologian review, higher than the Romans baseline’s proportion, driven by John’s concentration of direct deity/sonship/unity claims (5:18; 8:58; 10:30; 20:28; 20:31).
• 84 terms are seeded in assets/translation_memory.json (John): 28 inherited exactly from the Romans baseline, 56 newly introduced by John’s distinct vocabulary. 55 of 84 terms (65%) are Critical or High risk (26 Critical, 29 High).
• The “I Am” formula (زه یم) must be rendered identically at every one of its roughly 20 occurrences (absolute and predicated) — the single most repeated, most doctrinally load-bearing pattern in the book, and the one most at risk of silent flattening into ordinary speech precisely because its Pashto rendering is grammatically unremarkable.
• Two genuine translation gaps were surfaced with no clean Pashto lexical solution: the Greek πνεῦμα wind/Spirit pun (John 3:8, inside the core passage itself) and the ἀγαπάω/φιλέω distinction in Peter’s restoration (21:15-17). Both require mandatory footnoting rather than a lexical fix.
• One glossary gap was identified and closed during this analysis: no standing term existed for the general “God so loved the world” (ἀγαπάω, 3:16) until flagged in 06_linguistic_gap_analysis.md; مینه is now seeded as a High-risk term in assets/translation_memory.json with an explicit fencing note against Pashtunwali’s reciprocity-creating melmastia default.

Risks

• The Paraclete/Ahmad apologetic tradition (ch.14-16) is not a generic collision but a specific, organized argument already circulating in regional Islamic apologetics claiming John’s Counselor predicts Muhammad; a single careless rendering foregrounding “the praised one” rather than “the helper” could appear to concede the argument. Flagged Critical, theologian review at every occurrence.
• “Lifted up” (ὑψόω, 3:14; 8:28; 12:32-34) sits directly on top of the Qur’an’s own “raising up” (rafa’) language for Jesus, which asserts the opposite meaning (rescue from the cross, not death on it); any rafa’-family root in Pashto would reinforce, not confront, the crucifixion-denial.
• “Only begotten” (μονογενής) and the Word/Logos (κλam) both sit on the Qur’an’s direct denial targets (112:3; kalam theology’s revealed-speech-as-attribute framework); both require sustained, repeated teaching, not a one-time glossary fix.
• Mission and sending (20:21) carries the same severe, potentially life-threatening legal and social risk for converts from Islam already flagged Critical in the Romans baseline — this risk is undiminished, and arguably sharpened, by John’s explicit “as the Father sent me, I send you” commissioning language.
• Pashto’s youngest-in-pipeline Bible translation tradition (first complete Bible in any dialect only in 2019-2020) means several of this package’s term decisions (کلام, مرستندوی, یوازینی) have no tested local precedent to fall back on if theologian review surfaces a problem in the field.

Opportunities

• Living water (4:10-14; 7:37-39) and peace/سوله (14:27) carry strong, ready-made positive resonance given the region’s lived experience of water scarcity and decades of conflict/peace-negotiation vocabulary — genuine assets requiring calibration, not invention.
• Lamb of God (1:29,36) and the Good Shepherd (10:11,14) both connect to positively-regarded regional practices (Eid al-Adha/Qurbani sacrifice; pastoral/herding life) that can be built on once the “final, not repeatable” distinction is taught explicitly.
• Nanawatai (ritual submission accepted in place of retaliation) remains available, as in the Romans baseline, as a genuine cultural bridge for substitutionary atonement, and John supplies a fresh, narratively ironic entry point via Caiaphas’s unwitting prophecy (11:50).
• Orphan-care imagery (14:18) and the childbirth grief-to-joy analogy (16:20-22) carry strong positive social and religious resonance across the Islamicate world and Pashtun culture specifically, offering low-risk, high-warmth pastoral material.

Recommended actions

1. Load both the Romans baseline and John-specific translation_memory.json files before any Phase 2 segment translation begins; treat the 55 Critical/High terms as non-negotiable.
2. Route all 23 Critical/High doctrines to human theologian review per doctrine_risk_registry.json (John), with standing (not just first-occurrence) review for the I AM formula, the Counselor/Paraclete, and “lifted up.”
3. Insert the four mandatory standing footnotes identified in 12_ai_translation_requirements.md (John 3:8 wind/Spirit pun; first I AM occurrence; first Counselor occurrence; John 1:14 periphrastic incarnation gloss) into every document that touches these verses, rather than leaving them to translator discretion.
4. Prioritize theologian review capacity for chapters 3, 5, 8, 10, 14-17, and 18-20, which the doctrine analysis identifies as the book’s densest concentrations of Critical-tier material.
5. Carry the newly identified مینه (general love) term into every subsequent Phase 2 document from this point forward; it was missing from the Language Package until this analysis and must not be silently reintroduced as an unglossed, unfenced term.

---

See analysis/11_doctrine_analysis.md for the full doctrine matrix and chapter-by-chapter coverage table; assets/doctrine_risk_registry.json for the machine-readable doctrine risk source of truth; assets/translation_memory.json for the enforced term database; and analysis/12_ai_translation_requirements.md for the complete Phase 2 AI instruction set.