Executive Summary: 1 John Pashto Language Package

Why it matters

1 John is being translated for one of the most linguistically young and pastorally exposed audiences in this pipeline: a small, often secret, persecuted Pashto-speaking house-church readership in Afghanistan and Pakistan, almost entirely converts from Islam, working from a Bible translation tradition barely five years old in its most complete dialect form. The core passage, 1 John 4:7-21 (“God is Love”), sits directly on top of the two hardest theological fault lines this audience faces — an honor-shame culture asked to receive an unconditional, one-directional divine gift, and a strict-tawhid religious environment asked to receive an ontological claim about God’s essence with no clean structural precedent in its own theology. Getting this letter right, or wrong, shapes how new believers understand whether they are safe, loved, and secure in a faith that already costs them their family and tribal standing.

Key findings

• 64 theological terms are now tracked across the baseline-inherited and newly-introduced vocabulary for this book — 24 Critical-risk and 20 High-risk (44 total) requiring mandatory human theologian review at every occurrence, per assets/translation_memory.json and assets/bible_term_registry.json.
• 23 doctrines span the full five chapters of 1 John — 11 Critical and 8 High (19 total, 83% of all doctrines) route to mandatory theologian review; only 3 doctrines require native-speaker-only review and 1 is automated-only, per assets/doctrine_risk_registry.json.
• The core passage (4:7-21) alone activates 9 of the 23 catalogued doctrines simultaneously — the highest doctrinal density of any comparable stretch in the letter — making it the correct theological anchor for this curriculum, not merely one section among many.
• Two ontological identity claims — “God is light” (1:5) and “God is love” (4:8, 16) — have no clean grammatical precedent in either English or Pashto and risk being heard as one divine attribute among 99 names (al-Wadud) rather than God’s essence; both require a deliberate copula-emphasis rendering, not a direct literal translation.
• The letter introduces genuinely new collision risks the Romans baseline never had to solve: antichrist/al-Dajjal calibration, anointing/Messiah root confusion, khatm-e-nubuwwat political sensitivity around “false prophet,” and Sufi fana/wahdat-al-wujud risk for “abide” — none of which existed in the Romans package.

Risks

• Propitiation (2:2; 4:10): the standard Islamic term كفاره is a live, tempting substitute that inverts the text’s own logic (God as initiator, not appeased party); explicitly rejected in favor of a periphrastic rendering paired with a calibrated nanawatai bridge.
• False prophet / testing the spirits (4:1): carries a dual danger — folk-Islamic jinn-testing conflation on one side, and accidental entanglement with Pakistan’s legally fraught khatm-e-nubuwwat/Ahmadiyya controversy on the other, an unrelated dispute that must never be implied.
• Brother (ورور): the letter’s love-for-the-brethren test collides directly with Pashtun tribal blood-brotherhood structures (qawm/khel, tarburwali, badal); mistranslation or under-explanation here carries real, sometimes acute social and safety cost for converts, not just doctrinal imprecision.
• Deity/Sonship claims (4:9, 15; 5:20): “the true God” applied directly to Jesus Christ is the paradigm shirk case from a tawhid standpoint; any softening toward honorific sonship would be the single most theologically damaging failure available in this book.
• World (κόσμος, نړۍ): the same Pashto word carries opposite doctrinal valence (God’s saving love for the world, 4:9, vs. the world believers must not love, 2:15) with no lexical marker to distinguish them — a silent, easy-to-miss error surface.

Opportunities

• Nanawatai and sola (peace) remain, as in the Romans baseline, genuine positive cultural bridges — now extended specifically to propitiation (2:2; 4:10) and confidently deployed wherever atonement is taught, provided the initiative-direction correction is always attached.
• Wakil (advocate, 2:1) is a strong, concrete new bridge unique to this letter: the jirga/legal-representative role gives Christ’s advocacy before the Father an immediately intelligible cultural image, calibrated against a human wakil’s merely contingent success.
• Qabil/Habil (Cain/Abel, 3:12) and the shared devil/shaitan figure (3:8-10) are low-risk, high-value points of contact requiring no adaptation, carrying the letter’s moral argument cleanly across traditions.
• Sunni expectation of Isa’s return offers real, calibrated common ground for 1 John 2:28’s parousia teaching, provided Christ’s unique glorified-Judge role (not a subordinate-to-Mahdi role) is made explicit.

Recommended actions

1. Load assets/translation_memory.json and assets/bible_term_registry.json (1 John) alongside the Romans baseline files before any Phase 2 segment processing; never treat the 1 John extension as replacing the baseline.
2. Route every segment touching 1 John 4:7-21 to mandatory theologian review by default, given its 9-doctrine density, per the escalation rule in analysis/12_ai_translation_requirements.md.
3. Enforce the forbidden-substitution list (كفاره, حقیقت as primary, unanchored پاکول, unqualified مسح/ضد مسیح) at validation for every batch, with automated pre-checks where feasible ahead of human review.
4. Require the copula-emphasis rendering and accompanying teacher note for both “God is light” and “God is love” at every occurrence, not only their first appearance, given their structural unfamiliarity.
5. Brief all human theologian reviewers explicitly on the khatm-e-nubuwwat/Ahmadiyya sensitivity before they review any “false prophet” or “testing the spirits” segment, since this is a legal-political risk distinct from, and easy to conflate with, the letter’s actual doctrinal content.
6. Carry all 65 term-level and 23 doctrine-level decisions forward unchanged into Phase 2; any proposed deviation must first be escalated as a versioned change to assets/translation_memory.json or assets/doctrine_risk_registry.json, never introduced silently at the segment level.

---

This summary synthesizes analysis/07_semantic_analysis.md, analysis/08_core_glossary.md, analysis/06_linguistic_gap_analysis.md, analysis/11_doctrine_analysis.md, assets/translation_memory.json, assets/bible_term_registry.json, and assets/doctrine_risk_registry.json. All counts are drawn directly from those artifacts and must be re-verified against them if any is revised.