Executive Summary — Song of Solomon (English → Arabic)

Why it matters

Song of Solomon is the highest doctrinal-risk-density book this Arabic Language Package has processed to date. A single verse — the core passage’s climax at 8:6 — concentrates four separate Critical/High doctrines in one sentence: the book’s only explicit divine name (“flame of the LORD”, tied to the baseline’s Critical الرب term), its central exclusivity image (“seal,” خاتم, which shares a root with Islam’s defining prophetic-finality title), its comparison to Sheol (الهاوية, the Qur’an’s own proper name for Hellfire), and covenant jealousy. Beyond 8:6, the book’s frank celebration of marital desire runs directly against شهوة’s base-appetite connotation in everyday and religious Arabic, and Song of Solomon 5:16 contains a documented, circulating polemical claim (a spurious “hidden prophecy” of Muhammad’s name) that requires active, mandatory correction rather than silent translation. Getting this book wrong does not just blur a doctrine — it risks actively importing a competing theological claim into the translated text itself.

Key findings

• 23 doctrines analyzed across the full book (all 8 chapters reviewed, none silently skipped): 6 Critical, 9 High, 7 Medium, 2 Low per doctrine_risk_registry.json — 15 doctrines require mandatory human theologian review, 7 require native speaker review, 2 automated review suffices.
• 54 total terms now tracked in translation_memory.json: 7 inherited exactly from the Romans baseline (الرب, النعمة, الإيمان, العهد, الكنيسة, مقدس, إسرائيل) and 47 new to this curriculum.
• Of the 47 new terms, 3 are Critical risk (flame_of_the_lord, desire, machamaddim) and 10 are High risk (seal, fountain_sealed, garden_enclosed, sheol, no_blemish, bride_sister, mutual_belonging_formula, solomon, she_is_the_only_one, beloved_masc) — combined with the 4 inherited Critical/High terms that recur here (lord, grace, faith, israel), 16 total Critical/High terms require theologian-level enforcement in Phase 2.
• Four convergence points carry the highest combined severity: (1) the ח-ת-ם/خ-ت-م root (“seal”) colliding with Khātam al-Nabiyyīn; (2) שַׁלְהֶבֶתְיָה’s divine-name element colliding with الرب’s shirk-adjacency; (3) the documented 5:16 apologetic collision (מַחֲמַדִּים / Muhammad-name-prophecy claim); (4) גַּן/جنة (“garden”) colliding with Qur’anic Paradise vocabulary.
• The book’s own internal logic (monogamous ideal, “she is the only one,” 6:8-9) sits in real tension with Solomon’s historical polygamy and with polygyny’s continued legal status in several Arab jurisdictions — this requires explicit teaching resolution, not silence.

Risks

• Silent softening risk: the single greatest failure mode across this entire curriculum is de-theologizing — dropping الرب from 8:6’s flame image, dropping أختي’s literal kinship term, or reaching for a euphemism at any of the fenced terms — because each softening independently erases a doctrine this curriculum is built to teach, not merely a stylistic choice.
• Unaddressed collision risk: unlike most Romans terms, several Song of Solomon terms (شهوة, جنة, الهاوية, خاتم, root-literal 5:16 renderings) are not risky because the correct Arabic word is unclear, but because the correct word is also already claimed by mainstream Islamic vocabulary for an incompatible concept. Silence, not word choice, is the primary risk here — every one of these requires an explicit, mandatory footnote.
• Genre/canonicity risk: without deliberate framing, readers across traditions may either dismiss the book’s frankness as embarrassing (leading to euphemized translation) or dismiss the book’s allegorical weight as imposed and non-scriptural (leading to a flattened, purely secular reading). Both undercut assigned doctrines.
• Political-sensitivity risk: “Jerusalem” (6:4) and “Israel” (background) carry present-day political weight that could pull an OT literary comparison into contemporary conflict commentary if not explicitly fenced.

Opportunities

• Existing cultural bridges are unusually rich for this book. The classical Arabic ghazal genre already uses gazelle-imagery for a beloved; Sufi ‘ishq/shawq vocabulary already treats intense longing for the divine as a legitimate devotional register; Eastern Christian Arabic liturgical tradition (Byzantine, Syriac) has centuries of precedent reading this book allegorically and can be cited as an authoritative in-tradition resource rather than a foreign imposition.
• Eastern Christian canon law’s monogamy requirement is a genuine, pre-existing point of agreement with the poem’s own monogamous ideal, usable as a bridge when addressing the polygamy tension rather than treating it as purely adversarial.
• The baseline’s grace doctrine (النعمة) already gives this curriculum a ready-made, doctrinally-consistent bridge for 8:7’s “love cannot be bought” and 8:10’s favor/חֵן language — no new doctrinal apparatus is required, only the explicit cross-reference.

Recommended actions

1. Route every occurrence of Song of Solomon 8:6, 5:16, 7:10, and the 4:9-12/5:1/8:8 bride-sister passages to mandatory human theologian review before Phase 2 approval — no exceptions, regardless of translator confidence.
2. Enforce the nine mandatory footnotes specified in 12_ai_translation_requirements.md as non-optional; build automated validation checks that fail a segment if any required footnote is absent, not merely a style warning.
3. Brief all native-speaker reviewers explicitly on the شهوة/رغبة distinction and the جنة/بستان fencing rule before their first pass, since both are easy, natural-sounding mistakes for a fluent but unbriefed translator to make.
4. Prepare the 6:8-9 polygamy-tension teaching note and the 5:16 apologetic footnote as pre-approved, reusable boilerplate text (not drafted fresh per document) to guarantee consistency and completeness across every curriculum document that touches these verses.
5. Confirm the نشيد الأناشيد / SNG citation and YouVersion linking conventions (§Cross-Reference Preservation Rules) are loaded into Phase 2/3 tooling before batch processing begins.

---

See 11_doctrine_analysis.md for the full doctrine matrix and chapter-by-chapter walkthrough; see assets/doctrine_risk_registry.json and assets/translation_memory.json for the enforcement databases underlying every count above.