Executive Summary

Obadiah | English → French Language Package

Curriculum: Obadiah Core passage: Obadiah 1:15–21 Generated: 2026-07-03

---

Why it matters: Obadiah is the shortest book in the Old Testament (21 verses, one chapter) but packs an unusually dense concentration of Critical- and High-risk theological vocabulary — including the covenant name of God, the fixed “Day of the LORD” formula, and the book’s climactic kingship declaration — directly on top of French religious-cultural fault lines (Catholic liturgical calendar, Republican civic vocabulary, Eucharistic imagery, and contemporary Middle East politics). This Language Package extends, and never contradicts, the Romans baseline so that French-speaking learners moving between Romans and Obadiah encounter a single, doctrinally coherent glossary rather than two competing vocabularies for the same underlying realities.

---

Key findings

• 46 total enforced terms now govern Obadiah translation: 12 inherited exactly from the Romans baseline (with Obadiah-specific register-fence guidance added) and 34 new Obadiah-specific terms covering the whole book, from the opening “vision” (1:1) through the climactic “la royauté” (1:21).
• The single largest translation risk in the whole book is a register collision, not a vocabulary gap: French already has adequate words for nearly every Obadiah concept, but those words are heavily “crowded” by competing senses — most acutely, “le jour du Seigneur” already means Sunday in ordinary Catholic French, directly threatening the book’s pivotal “le jour de l’Éternel” (Day of the LORD) formula in verse 15.
• Two Critical-tier lexical fences protect the book’s theological architecture: (1) “l’Éternel” must never be replaced by “Seigneur,” which is reserved for the NT Lordship confession; (2) “la royauté” (1:21) must never be replaced by the baseline’s fixed NT phrase “Royaume de Dieu,” a different original-language term in a different testament register.
• The core passage (1:15–21), though only 7 of the book’s 21 verses, concentrates 2 of the book’s 3 Critical doctrines and 4 of its 6 High doctrines — Phase 2 should expect this short span to require the heaviest theologian-review load of the entire curriculum.

---

Risks

• Doctrine-level: Of 11 tracked doctrines, 3 are Critical and 6 are High — a combined 9 of 11 doctrines (82%) require mandatory human theologian review; only 2 require native-speaker review and zero are automated-only. This is a substantially higher Critical/High concentration than the Romans baseline (which had 2 Critical and 10 High out of 40 doctrines).
• Term-level: Of the 34 new Obadiah-specific terms, 4 are Critical and 9 are High — 13 of 34 new terms (38%) require theologian-level enforcement, on top of one inherited Critical-tier fence (“lord”) and one inherited High-tier reuse-guidance term (“gentiles”/“nations”).
• Live cultural collisions requiring explicit anchoring, not just glossing: “violence” (chamas) with the contemporary organization “Hamas”; “le mont Sion” and the land-restoration list with contemporary Israeli-Palestinian politics; “Sepharad” with the modern French-Jewish “monde séfarade” identity term; “frère” with the Republican motto “fraternité”; “royauté” with France’s own monarchical history.
• Structural/rhetorical risk: The book’s argument depends on exact, repeated French phrasing across non-adjacent verses (the fourfold “le jour de ton frère” refrain, vv.11–14, building to “le jour de l’Éternel,” v.15; the “rescapés”/v.17 vs. “pas de survivant”/v.18 contrast). Any inconsistent rendering silently destroys the passage’s logic without triggering an obvious mistranslation flag.

---

Opportunities

• Obadiah’s brevity makes it an efficient, high-density teaching unit for reinforcing the Romans baseline’s own register discipline (Seigneur vs. l’Éternel; Royaume de Dieu vs. royauté), turning a small book into an outsized training asset for translator consistency across the whole curriculum.
• Several cross-tradition bridge concepts are unusually strong for this book (Islamic Yawm al-Din for the Day of the LORD; Jewish liturgical Malchut for God’s kingship; French WWII “Libération” memory for “libérateurs”) and can be used pastorally to build understanding across France’s religiously diverse readership, provided teaching notes redirect each bridge concept back to Obadiah’s specific covenantal claim rather than leaving a loose analogy unresolved.
• The book’s climactic verse (1:21) offers a clean, low-risk opportunity to teach typological (not lexical) continuity between the OT’s “la royauté” and the NT’s “Royaume de Dieu,” modeling for learners how this Language Package handles testament-register distinctions generally.

---

Recommended actions

1. Load both assets/translation_memory.json (Obadiah) and the Romans baseline translation_memory.json for every Phase 2 Obadiah session — no segment should be processed with only one file loaded.
2. Route all core-passage (1:15–21) segments to human theologian review by default, given the concentration of Critical/High doctrine documented above; do not rely on per-segment auto-flagging alone given how easily register collisions (e.g., “Seigneur” for “l’Éternel”) slip past automated checks that only test for presence/absence of a term, not register correctness.
3. Enforce the 11 forbidden-substitution fences verbatim (see 12_ai_translation_requirements.md Obadiah addendum), with particular priority on the “le jour du Seigneur” vs. “le jour de l’Éternel” collision, the single highest-probability everyday-French error in the book.
4. Attach mandatory historical-anchor and geographic-orientation footnotes wherever flagged (violence/chamas; the 1:19–20 restoration list; Zion/Sion) rather than attempting to resolve these risks through word choice alone — some risks in this book are literacy/context risks, not lexical ones, and require supplementary material rather than translation adjustment.
5. Brief Catholic-background reviewers explicitly on the “l’Éternel” vs. post-2008 liturgical “le Seigneur” divergence before review begins, since this is the single most likely “correction” a well-meaning reviewer would otherwise silently introduce.