Executive Summary: 1 John — English → Persian Language Package

Why it matters

1 John is being added to a Persian-language Bible curriculum pipeline that already carries the Romans baseline as its language authority. This letter’s compact, repetitive, binary-contrast style (light/darkness, love/hate, truth/lie, life/death) puts a small number of terms under unusually concentrated theological pressure — above all the two “God is ___” predicate-identity statements (“God is light,” “God is love”) that anchor the core passage (1 John 4:7-21) and the whole book. Getting these terms wrong does not produce vague imprecision; it risks actively re-narrating the letter’s central claims into Twelver Shia Imamate/Mahdi eschatology, Sufi pantheistic mysticism, or Illuminationist emanation metaphysics — the same three collision zones the Romans baseline already documented, now hitting a much smaller, more repetitive vocabulary set with proportionally higher per-word stakes.

Key findings

• 27 doctrines analyzed across all five chapters (full-book coverage confirmed; no chapter reviewed as doctrinally silent) — 11 Critical and 12 High risk (23 total requiring mandatory human theologian review), 4 Medium (native speaker review), 0 Low.
• 64 terms now in the enforced 1 John translation memory — 13 inherited unchanged from the Romans baseline (god, jesus, son_of_god, holy_spirit, father, sin, faith, fellowship, glory, intercession, law, salvation, righteousness) plus 51 new terms proprietary to this letter. Of the 64: 25 Critical, 18 High (43 total requiring theologian review), 19 Medium, 2 Low.
• Three genuinely missing-vocabulary gaps identified (not just crowded ones) with no existing Persian religious equivalent at all: new birth/regeneration (از خدا مولود شدن), the regenerating “seed of God” (بذر الهی), and present-tense assurance of salvation as a knowable fact before death (5:13) — all three collide with Islamic fitrah (innate purity) and mizan (future deeds-weighing) defaults that have no adult-regeneration or present-assurance category at all.
• Four terms required a deliberate departure from the more common but riskier Persian word, following the exact methodology the Romans baseline used for law/ناموس: testimony (گواهی, not شهادت), Christ’s return (بازگشت, not ظهور), antichrist (ضدمسیح, not دجال), and — highest safety priority — lawlessness, which must NEVER use the fused compound بی‌ناموسی, a severe and wholly unrelated colloquial honor-insult in everyday Persian.

Risks

• Highest-severity risk: the predicate-identity statements “God is light” (1:5) and “God is love” (4:8,16) can slide, via ordinary Persian syntax or via Sufi/Illuminationist devotional resonance already present in the culture, from personal moral-character claims into an impersonal cosmic Light/Love-principle — the same emanationist failure mode baseline flagged for فیض (grace), now doubled.
• Second-highest: the incarnation-confession test at 4:2 (“come in the flesh,” جسم) is the letter’s single confessional linchpin; any softening reopens the Quranic crucifixion-denial collision at its most concentrated point in the book.
• Devotionally acute: خون (blood) and کفّاره (propitiation) sit directly against Iran’s most emotionally developed religious practice — Karbala/Ashura martyrdom-intercession piety — and شفیع (advocate, 2:1) does the same against active Imam-intercession devotion.
• Zero-tolerance safety risk: a single fused-compound slip on “lawlessness” (بی‌ناموسی instead of the mandated two-word عصیان [از ناموس خدا]) produces not theological confusion but an offensive, unrelated social insult — this is a translation-QA failure mode not previously documented in the Romans baseline and requires its own automated guard.

Opportunities

• Two genuinely low-risk bridge concepts exist and should be used pedagogically, not just tolerated: روح گمراهی/روح راستی (spirit of error/truth, 4:6) parallels the Quranic hidayah/dalalah polarity productively, and بت‌ها/idols (5:21) shares real common ground with Quranic shirk-condemnation.
• The letter’s short length and high repetition mean that once the 15 ranked highest-risk ambiguities (documented in the linguistic gap analysis) are correctly fenced in translation memory, enforcement compounds favorably across the whole book rather than requiring fresh adjudication verse-by-verse.

Recommended actions

1. Load assets/translation_memory.json (1 John) layered on top of the Romans baseline before any Phase 2 segment processing begins; treat the 43 Critical/High terms as absolute, non-negotiable renderings.
2. Route all 23 Critical/High doctrines to mandatory human theologian review per assets/doctrine_risk_registry.json; do not allow native-speaker-only sign-off to substitute for theologian review on any of these.
3. Add an automated hard-fail QA check specifically for the fused compound بی‌ناموسی before any 1 John 3:4 segment is accepted — this single check protects against the pipeline’s most severe non-doctrinal failure mode.
4. Prioritize theologian attention on the core passage (4:7-21) first, since it concentrates the book’s top-ranked risks (predicate-identity statements, advocate/propitiation, κόσμος disambiguation), then proceed chapter-by-chapter through 1, 2, 3, and 5 using the same enforcement discipline.