Deuteronomy — Hmong Language Package: Executive Summary

The bottom line: The Hmong Deuteronomy Language Package is now fully specified — glossary, term registry, doctrine registry, comparative theology, linguistic gap analysis, translation memory, and Phase 2 AI instructions are complete and internally consistent with the governing Romans baseline. Every one of Deuteronomy’s 34 chapters has been reviewed; all 8 assigned doctrines and 25 individual terms carry Critical or High doctrine risk and require mandatory human theologian review before any content reaches learners.

---

Why it matters

Deuteronomy is Moses’ covenant-renewal sermon to Israel on the edge of the Promised Land — the theological hinge of the Torah, and the source of the Shema, the template for covenant blessing/curse theology, and the prophecy Christ himself fulfills (Deut 18). For a Hmong-speaking audience whose traditional religion is an actively practiced system of ancestor veneration, spirit-appeasement, ritual cursing, and — uniquely among this pipeline’s collision risks — a named ethno-messianic folk tradition (“Yaj Saub”) that the book’s own vocabulary for “prophet” directly invokes, this is the single highest-collision-risk book yet processed in this Language Package family. Getting it wrong risks either assimilating YHWH into the existing spirit-pantheon, reinforcing fortune/curse ritualism instead of grace-grounded obedience, or recasting Christ as a folk ethnic deliverer rather than the covenant-mediating Prophet Deuteronomy 18 actually promises.

---

Key findings

• Full-book coverage complete: All 34 chapters reviewed; 51 glossary terms catalogued (08_core_glossary.md); 9 explicitly logged as contributing no new load-bearing vocabulary (chs. 2, 3, 14, 19, 22, 23, 25, 31, 33 — partial or full) rather than silently skipped.
• 8 of 8 doctrines are Critical or High risk, none Medium/Low — identical to the Romans baseline’s own finding, confirming this pipeline’s Hmong packages consistently surface maximal doctrinal exposure: 5 Critical (Shema/Exclusive Love, Covenant Renewal, Blessings and Curses, Obedience not Merit, Warnings against Idolatry) + 3 High (Remembering Redemption, Coming Prophet, Choosing Life over Death).
• 25 terms require mandatory theologian review (9 Critical + 16 High, per 08_core_glossary.md summary statistics), on top of every Critical/High term already inherited unchanged from the Romans baseline (grace, election, law, idol, power, salvation, etc.).
• One term, koob hmoov (covenant blessing), sits in direct tension with a permanent Romans-baseline prohibition — it is the correct word here (material blessing) but the permanently forbidden word for grace elsewhere in the same package; this split-use must be actively documented for any generator trained only on the Romans baseline.
• A new master term, Yawmsaub (YHWH), was required — the Romans baseline contains no OT Tetragrammaton quotations, so this is a wholly new, Critical-tier naming decision distinct from the inherited generic tus Tswv.
• The single highest-stakes lexical decision in the package is tib leeg (xwb) — the Shema’s “God is one,” which must carry a mandatory exclusivity clause or risk being heard as naming merely the chief spirit among many in Hmong cosmology.

---

Risks

Risk	Severity	Why
Shema exclusivity (tib leeg) heard as “chief god among many”	Critical	Populated Hmong spirit-pantheon (ancestor, household, nature, clan spirits) has no native monotheism analogue.
Covenant blessing/curse (koob hmoov/foom) heard as fortune-and-ritual-appeasement system	Critical	Directly, currently practiced Hmong categories with counter-ritual remedies; risk of reinforcing exactly the merit theology the curriculum’s own doctrine (Obedience not Merit) exists to reject.
Idolatry warnings (dab mlom, thaj chaw teev dab, khoom xyeem) heard as descriptive of, or validating, live family practice	Critical	Unlike Romans’ retrospective Gentile-idolatry framing, Deuteronomy issues first-person prohibitions whose referents are currently practiced by Hmong households/clans.
”Coming Prophet” (tus yaj saub) assimilated into Hmong ethno-messianic folk expectation	High	Unique in this pipeline: collision is with a named cultural-political movement/figure, not a generic religious category.
Cherem/the ban generalized into a violence template	Critical (ethical)	Independent of animism-collision; requires bounded historical-redemptive framing every time.
koob hmoov split-use confuses Phase 2 generators trained only on Romans baseline	Critical (process risk)	Same word is simultaneously forbidden (for grace) and correct (for covenant blessing) within one Language Package.

---

Opportunities

• Strong positive cultural bridges exist and should be leveraged, not just fenced: Hmong clan-inheritance custom (heir/land), debt-redemption custom (redemption, debt-release), elder-honor custom (parental honor), and clan-obligation ethics toward the vulnerable (sojourner, widow, orphan) all map onto Deuteronomy’s ethics with minimal risk and high resonance.
• The redemption-memory doctrine (“Remembering God’s Redemption”) can draw on Hmong ancestor-remembrance ritual sensibility as a genuine bridge point, provided it is explicitly redirected from ritual obligation-to-the-dead toward gratitude-driven ethics toward a living Redeemer.
• The Prophet-like-Moses doctrine’s cultural loading, while risky, is also the strongest available rhetorical bridge in the book — “Yaj Saub” already carries emotional weight and expectation; a well-built comparative teaching module can turn the collision into the curriculum’s most memorable teaching moment rather than merely neutralizing it.

---

Recommended actions

1. Route all content touching Doctrines 1, 2, 3, 5, and 8 (Critical) and 4, 6, 7 (High) through mandatory human theologian review before publication — no automated-review bypass, per assets/doctrine_risk_registry.json.
2. Build the tus yaj saub comparative teaching module as a standing, reusable curriculum asset before generating any Deuteronomy 18 content — this is a structural requirement, not a per-occurrence footnote.
3. Enforce the koob hmoov split-use documentation in every Phase 2 prompt/style-guide context spanning Romans and Deuteronomy material, so automated systems do not either wrongly forbid it in Deuteronomy or wrongly permit it near grace language.
4. Prioritize theologian review capacity for Deuteronomy 6-10, 27-28, and 30 — the cross-doctrine risk concentration zones identified in analysis/11_doctrine_analysis.md Part C.
5. Leave levitical_portion and manna unresolved pending translator input; do not allow any Phase 2 automated process to assign them a permanent rendering.
6. Verify the proposed book-title rendering “Kevcai Rov Qhia” and the YouVersion version ID (1663) against the actual published HWB text before hard-coding either into production citation strings, per analysis/12_ai_translation_requirements.md §7.