Executive Summary: 1 Thessalonians Language Package (Maithili)

Why it matters

1 Thessalonians brings a bereaved young church’s questions about death, Christ’s return, and final judgment into a Maithili-speaking context whose devotional imagination is already densely populated with competing answers: cyclical time, periodic avatar-descent, reincarnation, and karma-governed liberation. The core passage (4:13-18) is Paul’s pastoral answer to grief — but every key phrase in that answer sits directly on top of vocabulary this culture already uses for a different theological system. Getting this book right matters more for pastoral care than Romans did, because it is read at gravesides, not just in classrooms.

Key findings

• Full-book doctrinal density confirmed across all 5 chapters — no chapter is doctrine-free; Chapter 1 alone anchors five separate registry doctrines in ten verses.
• 68 total glossary terms now tracked in this curriculum’s translation_memory.json: 25 inherited unchanged from the Romans baseline, 43 newly introduced by 1 Thessalonians.
• 36 of 68 terms (53%) are Critical or High risk (14 Critical, 22 High), requiring theologian-level enforcement in Phase 2 — a higher proportion than Romans, driven by this book’s concentrated eschatological vocabulary.
• 27 named doctrines tracked; 19 require mandatory human theologian review (7 Critical + 12 High), 6 require native speaker review, 2 are automated-only — matching doctrine_risk_registry.json exactly.
• Two entirely new collision fronts beyond the Romans baseline: (1) eschatology/cosmology — parousia, rapture, and Day of the Lord collide with Mithila’s yuga-cycle and Kalki-avatar expectations; (2) anthropology — the spirit/soul/body triad (5:23) reuses आत्मा, the very word already reserved for the divine, personal Holy Spirit, inside the same letter.

Risks

• Highest-severity risk in the whole curriculum: 5:23’s आत्मा, प्राण, शरीर triad reuses the word for the divine पवित्र आत्मा (1:5-6; 4:8; 5:19) within one short letter, in a linguistic environment where Advaita Vedanta’s Ātman-equals-Brahman claim is a live, sophisticated position, not a naive mix-up.
• पुनरागमन (Return of Christ) risks being heard as one more turn of Mithila’s own periodic avatar-descent story — a live risk made sharper by Mithila being the Ramayana’s own geographic setting, not distant background.
• प्रभुक दिन (Day of the Lord) risks assimilation to the popular “end of Kali Yuga” / coming Kalki avatar expectation if not explicitly fenced.
• आशा (hope) and शोक (grief) in the core passage risk collapsing into, respectively, wishful sentiment or a blanket anti-grief command if not kept grammatically anchored to their qualifying clauses — a mistranslation that would invert the pastoral point of 4:13.
• मूर्ति (idols, 1:9) carries the highest cultural-sensitivity load of any single verse in the book, given active regional image-worship traditions.

Opportunities

• The faith-hope-love triad (1:3; 5:8) offers a natural, repeatable teaching structure for reinforcing all three baseline/new terms together without diluting any one of them.
• The Romans baseline’s existing passive-construction pattern (बजाओल जाएब) gives a ready-made, internally consistent grammatical template for coining उठाओल जाएब (rapture) — a genuinely new term that nonetheless feels native rather than borrowed.
• 1 Thessalonians’ pastoral warmth (4:18, “encourage one another with these words”) is an opportunity to model Maithili Christian comfort-register vocabulary for the first time in this Language Package tradition, since no settled precedent currently exists.

Recommended actions

1. Route 5:23 and 4:16-17 to human theologian review as indivisible units — do not segment in Phase 2 in a way that separates interacting Critical-tier doctrines.
2. Enforce the five mandatory first-occurrence translator notes (1:9; first parousia occurrence; 4:13; 5:1-2; 5:23) as structural requirements, not discretionary style choices.
3. Hold ज्योतिक सन्तान (5:5) as provisional pending native-speaker confirmation against उज्जवलताक सन्तान before Phase 2 finalization.
4. Confirm पवित्रता at High risk tier (resolving the flagged uncertainty carried over from Step 8) and keep it grammatically distinct from पवित्रीकरण throughout Phase 2 output.
5. Carry forward all 25 inherited Romans terms unchanged, byte-for-byte, into Phase 2 tooling — any mismatch against the Romans baseline should be treated as a blocking error.

*Feeds Phase 2 Step 17 review routing together with `assets/doctrine_risk_registry.json` and `assets/bible_term_registry.json`.*