feat(content): difficult-passage "Has 'LORD' Suppressed Yahweh's True Name?"

[CraigBuckmaster]

Strategic context

A second wave of viral "Ethiopian Bible" content adds a Sacred Name / Hebrew Roots hook: the claim that mainstream translations have suppressed the divine name by rendering YHWH as "LORD," and that "the Ethiopian Bible preserves Yahweh's true name." This is the bridge that lets the conspiracy-Christian content cross-pollinate with the Sacred Name Movement audience.

The claim is doubly false:

• Rendering YHWH as kyrios / "Lord" is not a modern editorial suppression — it is a Second Temple Jewish convention going back to the Septuagint (3rd century BC) and to the Jewish reading practice that substituted Adonai aloud
• Ethiopic Ge'ez does not use a transliteration of YHWH — it uses Egzi'abḥer ("Lord of the Universe"), which is itself a translation, not a preservation

We have a Hebrew lexicon (lexicon-hebrew.json) that almost certainly covers YHWH/Adonai linguistically, but nothing in apologetic shape addressing the suppression-claim directly. This card adds one tightly-scoped difficult-passage entry.

Parent epic: #1536
Related cards: #1817 (Watchers Tradition journey), #1818 (scholar registry — soft dependency)

Soft dependency

• feat(scholars): add Heiser, Bauckham, Walton, Kline, Arnold to scholar registry #1818 adds Walton to the scholar registry — useful but not strictly required if response uses other scholars. Card can ship before feat(scholars): add Heiser, Bauckham, Walton, Kline, Arnold to scholar registry #1818 lands if needed by substituting block or wegner (verify wegner is present, omit if not); with feat(scholars): add Heiser, Bauckham, Walton, Kline, Arnold to scholar registry #1818 landed, walton is preferred for response 1.

Deliverable

One difficult-passage entry in content/meta/difficult-passages.json.

Schema: Match the nephilim-sons-of-god precedent exactly — id, title, category, severity, passage, question, responses[] with tradition, tradition_family, scholar_id, summary, key_verses[], strengths, weaknesses.

Entry spec

id: divine-name-translation
title: Has "LORD" Suppressed Yahweh's True Name?
category: theological-linguistic
severity: moderate
passage: Exodus 3:13-15; Exodus 6:2-3; Leviticus 24:16; Deuteronomy 6:4
question: Some popular accounts claim that mainstream Bible translations have
  deliberately suppressed the divine name YHWH by rendering it as "LORD" — and
  that the Ethiopian Bible preserves "Yahweh's true name" while other
  translations hide it. Is this historically and linguistically accurate?

Responses (minimum three)

Response 1 — The "LORD" convention is ancient Jewish reading practice, not modern suppression

• tradition: Historical Translation Convention
• tradition_family: evangelical
• scholar_id: walton (added by feat(scholars): add Heiser, Bauckham, Walton, Kline, Arnold to scholar registry #1818) — fall back to block if feat(scholars): add Heiser, Bauckham, Walton, Kline, Arnold to scholar registry #1818 has not landed
• summary (200–350 words): The substitution of Adonai ("Lord") for YHWH in reading aloud is attested in Second Temple Judaism well before the Christian era. The Septuagint (3rd–2nd century BC) renders YHWH as kyrios ("Lord") throughout — this is the form Jesus and the apostles read and quoted. The Dead Sea Scrolls preserve a range of conventions: some manuscripts use paleo-Hebrew script for the divine name within otherwise Aramaic-square text (a graphic mark of reverence), some substitute Adonai, some use four dots (the tetrapuncta). By the 2nd century AD, Adonai substitution in reading was universal in synagogue practice. The Masoretes (7th–10th century AD) preserved the consonants YHWH but pointed them with the vowels of Adonai — a graphic reading-aid, not suppression. English "LORD" in small caps is a direct translation of this reading tradition, transparent to anyone who reads a preface. Calling this "suppression" requires ignoring 2,300 years of Jewish reading practice.
• key_verses: Exodus 3:13-15; Leviticus 24:16; Deuteronomy 6:4; Mark 12:29 (quoting Deut 6:4 as kyrios)
• strengths: Long, documented historical record; falsifies the "suppression" framing on textual evidence rather than appeal to authority.
• weaknesses: A reader committed to the Sacred Name framing may dismiss Septuagint and Masoretic evidence as already-compromised — the response cannot persuade a reader who rejects the textual record.

Response 2 — The Ethiopian Ge'ez Bible does not "preserve" Yahweh

• tradition: Comparative Translation
• tradition_family: catholic-orthodox (verify enum value in existing entries; substitute the closest valid family if needed)
• scholar_id: vanderkam
• summary (200–350 words): VanderKam's work on the Ethiopian biblical tradition documents that classical Ge'ez biblical manuscripts render the divine name as Egzi'abḥer ("Lord of the Universe") and as Egzi' ("Lord") — both translations, both functionally equivalent to Greek kyrios and English "Lord." Ge'ez does have phonological capacity to transliterate YHWH but the manuscript tradition does not do so. The Ethiopian Tewahedo canon's distinctive contributions are textual (the preservation of 1 Enoch and Jubilees in Ge'ez) and liturgical, not a preservation of the Tetragrammaton against suppressed Western translations. The claim that "the Ethiopian Bible preserves Yahweh's true name while other translations hide it" reverses the actual evidence: every major translation tradition — Ethiopian included — renders the Tetragrammaton with a "Lord"-equivalent word in running text.
• key_verses: Exodus 3:13-15; Psalm 110:1
• strengths: Directly falsifies the specific empirical claim with manuscript evidence.
• weaknesses: Requires the reader to accept manuscript-tradition arguments; not all Sacred Name framings rest on the Ethiopian claim specifically.

Response 3 — What the Sacred Name Movement gets right, and where it overreaches

• tradition: Charitable Engagement
• tradition_family: evangelical
• scholar_id: block
• summary (200–350 words): The Sacred Name Movement gets one thing right: the divine name is theologically significant, and most modern readers are unaware that "LORD" in their English Bible (small caps) marks the Tetragrammaton. Recovering that awareness is genuinely useful — it lets readers see the difference between God's covenant name (YHWH, "LORD") and the generic-title rendering (Adonai, "Lord"). Where the movement overreaches is in claiming (a) that pronouncing a specific reconstructed form (whether "Yahweh," "Yehovah," "Yahuwah," or another) is required for valid worship — the vocalisation is genuinely uncertain and Jewish reading practice has substituted Adonai aloud for at least 2,300 years; and (b) that translations using "LORD" are agents of deliberate suppression — they are inheritors of an unbroken Jewish-then-Christian reading tradition. The charitable reading recognises the legitimate concern (the divine name matters; English convention obscures it) while declining the overreach (only one pronunciation valid; "LORD" is suppression).
• key_verses: Exodus 3:14; Exodus 20:7; Philippians 2:9-11
• strengths: Concedes the kernel of legitimate concern without surrendering on the historical and textual claims; usable pastorally with a reader who has encountered Sacred Name material.
• weaknesses: Will be seen as compromise by committed Sacred Name advocates and as too generous by readers who want a flat rejection.

Tone constraints

• Apologetic, not polemical
• Never name specific Sacred Name organisations, Hebrew Roots ministries, or vendors
• Engage the claim, not the movement
• The kernel-of-truth concession in response 3 is the pastoral hinge — do not drop it

---

Acceptance criteria

• difficult-passages.json parses cleanly; entry id: divine-name-translation is unique
• All scholar_id references resolve in scholars.json (preferred: walton if feat(scholars): add Heiser, Bauckham, Walton, Kline, Arnold to scholar registry #1818 landed, else block)
• tradition_family enum values match existing entries — verify catholic-orthodox or eastern-orthodox against current schema before using
• schema_validator.py passes
• build_sqlite.py runs clean
• validate_sqlite.py passes
• Quality scorer ≥ 90 (quality_scorer.py)
• No references to specific Sacred Name organisations, ministries, or vendors
• If lexicon-hebrew.json has a YHWH/Adonai entry, this card cross-references it; if not, that is a separate enrichment and out of scope here

Out of scope

• New entries in lexicon-hebrew.json (linguistic content separate)
• Engagement with specific Hebrew Roots / Sacred Name authors or organisations by name
• The related-but-distinct question of "Yeshua vs Jesus" (own card if needed — see the apologetic-journeys backlog seeded under [Epic] How We Got The Bible — Canon, Extra-Biblical Literature & Second Temple Context #1536)
• New chapter content