Executive Summary — Zechariah Language Package (English → Hindi)

Why it matters

Zechariah gives Hindi-speaking believers the clearest Old Testament portrait of the coming Messianic King (9:9-10, the core passage) and the most theologically loaded single verse in the prophetic corpus for the deity of Christ (12:10, “look on me… on him whom they have pierced”). It also sits closer to Hindu religious vocabulary than almost any other biblical book in this pipeline’s queue: a humble-yet-victorious king, a personal God’s exclusive “oneness,” an inherently sacred city, and a divine “jealousy” for his people all have near — and dangerously misleading — analogues in Indian devotional and philosophical tradition. Getting this Language Package right protects five named doctrines (Coming Messianic King, Restoration of Jerusalem and the Temple, Visions of God’s Sovereign Plan, the Piercing of the One They Have Pierced, God’s Zeal for Zion) from collapsing into avatar theology, cyclical eschatology, or Advaitic monism.

Key findings

• Full-book coverage confirmed. All 14 chapters carry load-bearing doctrinal content; none was silently skipped (see 11_doctrine_analysis.md Part 2).
• 97 tracked terms in assets/translation_memory.json: 31 inherited exactly from the Romans/Galatians baseline, 66 newly minted for this book.
• 68 of 97 terms (27 Critical + 41 High) require mandatory human theologian review on every occurrence — a Critical/High share (70%) markedly higher than the Romans/Galatians baseline, driven by Zechariah’s Hebrew divine-name cluster and Christological cruxes.
• 26 doctrines tracked in doctrine_risk_registry.json: 8 Critical, 16 High, 2 Medium, 0 Low (count reconciled in 11_doctrine_analysis.md). 24 of 26 doctrines route to human theologian review; only 2 (the flying scroll curse, Satan’s accusation) route to native speaker review, and none are automated-only — a first for this Language Package family.
• A brand-new three-way divine-name fence (यहोवा / परमेश्वर / प्रभु) is required because Hebrew distinguishes YHWH, Elohim, and Adonai — a distinction Romans’ Greek source text never forced the baseline to make.
• Two structural (not lexical) translation gaps were identified with no precedent in the baseline: the grammatical person-shift in 12:10 (“look on ME… HIM whom they have pierced”), which fluent Hindi composition instinct will try to “fix” and thereby destroy; and the MT-passive/LXX-active tension in 9:9’s “having salvation.”

Risks

• Highest-priority risk (book-wide): Zechariah 14:9’s “the LORD will be one, and his name one” can be absorbed into Advaita Vedanta’s impersonal Brahman-monism (“all is ultimately one”), inverting the verse’s claim of exclusive personal monotheism. No existing Hindi Christian formula fully insulates against this; only a mandatory, never-omitted translator note does.
• Core-passage risk: धर्मी (righteous, 9:9) sits one morpheme from the forbidden धर्म; a lapse at the curriculum’s most-memorized verse has outsized pedagogical consequences.
• Avatar-descent assimilation risk: the humble king riding a donkey (9:9) has a ready-made cultural template in Krishna/avatar-descent narratives; अंकुर (the Branch) and राजगद्दी पर याजक (priest-king union) have no Indian religious analogue at all and must be taught, not merely translated.
• Sacred-geography and sacred-water assimilation risk: “I will dwell in your midst” (2:10-11) and “living waters” (14:8) risk merging with India’s tirtha-yatra and sacred-river (Ganga) theology unless pastorally fenced every time.
• Divine-jealousy vocabulary gap: no existing Hindi doctrinal term positively names God’s own covenant-jealousy; जलन is the least-bad option and fails without its mandatory reframing note.
• Cross-testament lock failure risk: four passages (9:9, 11:12-13, 12:10, 13:7) require verbatim or near-verbatim alignment with four different Hindi New Testament verses; any drift silently erases the fulfillment argument for Hindi readers.

Opportunities

• Idolatry/divination material (10:1-2; 13:2) confronts live, mainstream Hindi-speaking practice (astrology, household deities) more directly and pastorally usefully than almost any other book in this pipeline — a genuine discipleship entry point if delivered with the sensitivity already specified.
• God’s impartiality and universal peace-to-the-nations (9:10; 8:20-23) offer strong anti-hierarchy, anti-exclusion teaching material resonant with the pipeline’s existing caste-confrontation doctrines from Galatians.
• The Feast of Booths’ universal pilgrimage requirement (14:16-19) and the “many nations shall join themselves to the LORD” promise (2:11) give the Gentile-inclusion doctrine unusually vivid, concrete imagery for teaching.
• Fasting critique (7:5-10) carries its own built-in theological corrective to merit-based ritual — a rare case where the biblical text itself, not just the translator’s note, does the syncretism-guarding work.

Recommended actions

1. Lock the three-way divine-name fence (यहोवा/परमेश्वर/प्रभु) into Phase 2 tooling as a hard validation gate before any other check runs.
2. Require the four mandatory-every-occurrence translator notes (14:9 oneness; 1:14/8:2 zeal for Zion; 12:10 person-shift; 13:7 “my companion”) as non-skippable fields in the segment cache, not optional annotations.
3. Run the cross-testament lock verification (9:9, 11:12-13, 12:10, 13:7 against their NT targets) as an automated pre-sign-off check, since four independent documents’ renderings must agree.
4. Route all 8 Critical and 16 High doctrines to human theologian review with no exceptions, per doctrine_risk_registry.json; reserve native speaker review only for the 2 Medium doctrines (flying scroll curse, Satan’s accusation).
5. Brief theologian reviewers in advance on the two structural gaps (12:10 person-shift; 9:9 MT/LXX salvation tension) so reviewers do not “correct” deliberate ambiguity or grammatical tension out of the translated text.

---

This summary synthesizes 04_comparative_theology.md, 05_translation_landscape.md, 06_linguistic_gap_analysis.md, 07_semantic_analysis.md, 08_core_glossary.md, 11_doctrine_analysis.md, and the Zechariah assets/translation_memory.json, assets/bible_term_registry.json, and assets/doctrine_risk_registry.json. It must be read alongside, and never in place of, those source documents.