Adonai — Blog - The Blame is on the Sheep

The Great Lexical Blackout — How "God" Erased Ten Identities

Belem Anderson Costa — Sun, 29 Mar 2026 00:00:00 +0000

Public source text: WLC + Nestle 1904. Translation: Belem-2025 Bible translation.

The Crime Scene

Open any conventional Bible translation. Search for the word “God.” It appears thousands of times — uniform, generic, invariable. Now open the codices. The oldest Hebrew and Greek manuscripts we possess. The word “God” does not exist in them. Not even once.

What exists are ten distinct designations, with distinct etymologies, distinct referents, distinct grammatical contexts and — in many cases — distinct entities. Conventional translation collapsed all of them into one generic word. And nobody noticed. Or rather: nobody was supposed to notice. That is the point.

This is not a translation problem. It is a forensic blackout.

When a forensic report replaces the names of ten different suspects with the phrase “the man,” the case does not advance — it collapses. When an investigator cannot distinguish between the agents at the crime scene, he does not investigate; he assumes. And whoever assumes does not discover — they repeat.

The Belem-2025 Bible translation conducted a complete sweep of 31,287 verses of the canon. The result is this:

Designation	Language	Occurrences	Conventional Translation
Elohim (אלהים)	Hebrew	613	“God”
Theos (Θεός)	Greek	443	“God”
Iesous (Ἰησοῦς)	Greek	908	“Jesus”
Christos (Χριστός)	Greek	158	“Christ”
Adonai (אדני)	Hebrew	563	“Lord” / “God”
Kyrios (Κύριος)	Greek	343	“Lord” / “God”
El (אל)	Hebrew	246	“God”
Eloah (אלוה)	Hebrew	16	“God”
Yeshua (ישוע)	Aramaic	9	“Jesus” / “Joshua”
yhwh (יהוה)	Hebrew	6,800+	“Lord” / “LORD” / “God”

In the Belem-2025 Bible translation, the count of “God,” “Lord,” “Jesus” and “Christ” as substitute translations is: zero. Clean. Each designation preserved in its original language, with its original spelling, pointing to the referent that the text — not tradition — determines.

Anatomy of the Blackout: Designation by Designation

1. Elohim (אלהים) — 613 Occurrences

Elohim is morphologically plural. The suffix -im is a masculine plural marker in Hebrew. There is no linguistic debate about this. The debate begins when ecclesiastical tradition needs to explain why a plural term takes a singular verb in Bereshit 1:1 — “bara Elohim” (Elohim created) — and decides that this is a “majestic plural.” A grammatical invention with no parallel in classical Hebrew syntax, created to solve a theological problem, not a textual one.

But the blackout goes beyond grammar. Elohim does not refer to a single entity in the codices. The same designation is applied to:

The Creator (Bereshit 1:1)
The “elohim acherim” — other elohim, literally “other divinities” (Shemot 20:3)
Human judges in the juridical context of Shemot 21–22
The entity invoked by the medium of En-Dor (1 Shemuel 28:13)
The divinities of foreign nations (Shophetim 11:24)

When you translate all these occurrences as “God” — capitalized, as if it were a proper name — you erase the distinction between five categories of referents. The modern reader has no way to know, from the translation alone, whether “God” in that verse is the Creator, a human judge, or the deity of Moab. The text knew. The translation decided the reader did not need to know.

The forensic statistical analysis (binomial test, Wilson confidence intervals, chi-square with Cramér’s V) confirms: the hypothesis that Elohim refers to a single entity is rejected by the corpus itself. Elohim functions as a generic title — “powerful being,” “divinity” — not as a proper name. Proper names in Hebrew do not take a definite article. Elohim does: ha-Elohim (הָאֱלֹהִים). That is morphological proof, not opinion.

2. Theos (Θεός) — 443 Occurrences

Theos is the functional equivalent of Elohim in Koine Greek. It is a title, not a name. And just like Elohim, Theos is applied to referents that are not the Creator:

The belly, in Philippians 3:19 — “ōn ho theos hē koilia” (whose Theos is the belly)
The adversary, in 2 Corinthians 4:4 — “ho theos tou aiōnos toutou” (the Theos of this age)
Human beings, in Ioanes 10:34, quoting Tehilim 82:6 — “I said: you are elohim”

Conventional translation renders all these occurrences as “God” — capitalized when convenient, lowercase when embarrassing. But the Greek text has no such distinction. The uncial Greek of the oldest codices is written entirely in capital letters. The choice of where to capitalize is the translator’s, not the text’s. It is an editorial decision, not textual evidence.

When a translation says “god of this age” (lowercase) and “God the Father” (uppercase), it has already interpreted. It has already decided who is who. It has already eliminated the ambiguity the text preserved. The investigator who reads only the translation never even realizes that the same Greek word is at stake in both cases.

3. El (אל) — 246 Occurrences

El is the oldest singular form. It appears in constructs such as El-Elyon (אל עליון, “El Most High”), El-Shaddai (אל שדי), El-Olam (אל עולם). Each construct designates a different function or attribute. Conventional translation collapses them all: “God Most High,” “God Almighty,” “Eternal God.” Three distinct constructs, three distinct functions, one single result: “God + adjective.”

But El is not Elohim. El is singular. Elohim is plural. They are different forms of the same semantic field, but they are not interchangeable synonyms — just as “man” and “men” are not, or “people” and “peoples.” The translation that equates both eliminates a distinction that the Hebrew text maintains across 39 complete books. Have you ever asked yourself why the author used El instead of Elohim in that specific verse? Conventional translation ensured you would never have reason to ask.

4. Eloah (אלוה) — 16 Occurrences

Eloah is the intermediate singular form, predominantly poetic. It appears almost exclusively in Iyov (Job). It is the form Iyov uses when speaking directly with — or about — the divinity in the context of suffering and questioning. Tradition translates it as “God,” indistinguishable from Elohim, El, Theos or any other designation. But the author of Iyov chose Eloah, not Elohim. The lexical choice is data. Ignoring the data is forensic negligence.

Why does this matter to you? Because if Iyov uses a different designation when confronting the divinity in the midst of pain, that data could completely change the reading of the most enigmatic book of the canon. But translation leveled everything. “God” in Iyov. “God” in Bereshit. “God” everywhere. As if the word were the same. It is not.

5. Adonai (אדני) — 563 Occurrences

Adonai means “my sovereign” or “my sovereigns” (the form is also technically plural with a first-person pronominal suffix). It is a title of authority, not a name. In the codices, Adonai is used both for the Creator and for human lords, kings, husbands, and military commanders.

But Adonai carries another forensic problem: the Masoretic tradition introduced it as an oral substitute for yhwh. Where the consonantal text reads יהוה, the Masoretes vocalized it with the vowels of Adonai (ֲ-ֹ-ָ), signaling to the reader to pronounce “Adonai” instead of the name. Conventional translation took this mechanism further: where the text says yhwh, the translation says “Lord” (which is a translation of Adonai, which is a substitute for yhwh). The name was removed twice — first from pronunciation, then from the page.

6. Kyrios (Κύριος) — 343 Occurrences

Kyrios is “sovereign,” “lord,” “master.” In the New Testament, it is applied to Iesous, to the Creator, to slave masters, to vineyard owners, to husbands. The translation says “Lord” for all of them — and the reader cannot tell whether they are reading about the Messiah, the Creator, or the owner of a plot of land.

But the greater damage comes from the Septuagint (LXX). When Alexandrian translators rendered the Tanakh into Greek in the third century B.C., they systematically replaced יהוה with Κύριος. That act of translation created a cascade: the New Testament authors, quoting the LXX, used Kyrios where the Hebrew text said yhwh. The result is that in hundreds of OT quotations in the NT, the modern reader reads “Lord” without knowing that the original Hebrew text said yhwh — a proper name, not a title. The chain of substitution has three links: yhwh → Kyrios (LXX) → “Lord” (modern translation). Three links, zero transparency.

7. yhwh (יהוה) — The Erased Name

yhwh is the only proper name on this list. All other designations are titles, epithets, or common nouns used as designations. yhwh is a name. And it is the name that tradition most aggressively erased.

In the Hebrew codices, yhwh appears more than 6,800 times in the Old Testament. It is the most frequent name in all of Hebrew Scripture — more frequent than Mosheh, Avraham, David, or Israel. No conventional Portuguese translation preserves this name. It is replaced by “Lord,” “LORD” (in small caps), “Jehovah,” or simply “God” — depending on the translator’s denominational tradition, not the text.

The Belem-2025 Bible translation preserves yhwh — always lowercase, as per the standardized spelling — because a proper name is not translated. We do not translate “Mosheh” as “Drawn from the Waters.” We do not translate “Avraham” as “Father of Multitudes.” But tradition found it acceptable to translate — or worse, remove — the name of the central entity of the Old Testament.

8. Iesous (Ἰησοῦς) — 908 Occurrences

Iesous is the Greek transliteration of the Hebrew Yehoshua (יהושע), which in turn contracted to Yeshua (ישוע). The name means “yhwh saves” or “yhwh is salvation” — the name of yhwh is inside the name of Iesous. The translation to “Jesus” via the Latin “Iesus” erased the etymological connection with yhwh. The reader who reads “Jesus” has no way of knowing, from the translation, that the Messiah’s name is a declaration about yhwh. The etymological data was removed in the journey Hebrew → Greek → Latin → English.

Do you see what happened? The most sacred name of the OT — yhwh — is embedded in the most recognized name of the NT — Iesous. But the translation cut the thread. “Jesus” does not recall yhwh. “Iesous” does. That is the difference between reading a name and reading a theological declaration compressed into six Greek letters.

And there is another blackout: Iesous is not exclusive to the Messiah in the codices. In Acts 7:45 and Hebrews 4:8, Iesous refers to Yehoshua bin-Nun, the successor of Mosheh. Conventional translation solves the problem by translating as “Joshua” in these verses and “Jesus” in the rest — creating the illusion that they are different names. In the codices, the spelling is identical: Ἰησοῦς. The decision to distinguish is the translator’s, not the text’s.

9. Christos (Χριστός) — 158 Occurrences

Christos is the Greek translation of the Hebrew Mashiach (משיח) — “anointed.” It is not a name; it is a function. In the Old Testament, mashiach is applied to kings (Shaul, David), priests, and even to Koresh (Cyrus), king of Persia (Yeshayahu 45:1). Conventional translation rendered mashiach as “anointed” in the OT but transliterated it as “Christ” in the NT — creating the impression that “Christ” is the surname of Iesous, when it is a functional title that the OT applies to multiple figures.

Stop and think: when you read “Jesus Christ,” what does your mind register? A first name and a last name. But “Christos” is a title — like “president,” like “commander.” Translation transformed a function into an identity. And in doing so, it erased from your field of vision all the other mashiachim of the canon. Have you ever read that Cyrus is called mashiach? Most readers never knew. Translation ensured that.

10. Yeshua (ישוע) — 9 Occurrences in the OT

Yeshua appears in the Old Testament as a proper name belonging to individuals — most notably the high priest in Ezra and Nechemyah (Yeshua ben-Yotsadak). Conventional translation renders it as “Joshua” or “Jeshua,” never as “Jesus,” even though the linguistic chain is direct: Yeshua → Iesous → Jesus. Tradition protects the uniqueness of the name “Jesus” in the NT by preventing the reader from noticing that other bearers of that same name exist in the OT.

The Report: Consequences of the Blackout

The lexical collapse is not an accident. It is engineering. Each substitution produces a specific effect:

Operation	Effect
Elohim → “God”	Erases the plurality of referents and the plural morphology
Theos → “God”	Hides that the same word designates belly, adversary and Creator
El → “God”	Eliminates the singular/plural distinction and functional constructs
Eloah → “God”	Erases the deliberate lexical choice of the author of Iyov
Adonai → “Lord”/“God”	Confuses a title of authority with a proper name
Kyrios → “Lord”	Perpetuates the Alexandrian substitution of yhwh
yhwh → “Lord”/“LORD”	Removes the most frequent proper name of the OT
Iesous → “Jesus”	Erases the etymological connection with yhwh and the homonymy with Yehoshua
Christos → “Christ”	Transforms a functional title into a surname
Yeshua → “Joshua”	Prevents identification with Iesous of the NT

Ten erasure operations. Ten translation decisions that, combined, produce a text where the reader cannot ask the most basic question of any investigation: who is who?

A report that calls ten suspects “the man” is not a report — it is obstruction. A translation that calls ten designations “God” is not a translation — it is uniformization. And uniformization is the opposite of literalism. Whoever uniformizes is not translating; they are deciding for the reader what the reader should decide for themselves.

The Broken Chain of Custody

In forensic science, chain of custody is the continuous record of who handled a piece of evidence, when, and how. If the chain is broken, the evidence is inadmissible. The chain of custody of the biblical text was broken at at least three points:

Link 1 — The Septuagint (3rd century B.C.): The Alexandrian translators replaced yhwh with Kyrios. The proper name became a generic title. The evidence was tampered with at the first transfer.

Link 2 — The Latin Vulgate (4th century A.D.): Jerome consolidated the substitution. Kyrios became “Dominus.” Elohim became “Deus.” Latin — the language this school rejects as a biblical source — cemented the lexical blackout that all vernacular translations would inherit.

Link 3 — Modern Translations (16th century onward): Luther, Tyndale, Almeida, King James — all inherited the chain of substitution without breaking it. “Lord” for yhwh, “God” for Elohim, Theos, El, Eloah. Tradition became so solid that questioning the translation seems like questioning the text — when it is exactly the opposite. Questioning the translation is defending the text.

What the Belem-2025 Bible Translation Does Differently

The Belem-2025 Bible translation does not translate divine designations. It preserves each one in its original transliterated spelling, with the referent determined by textual context — not by ecclesiastical tradition.

When the text says אלהים, Belem-2025 says “Elohim.” When it says Θεός, it says “Theos.” When it says יהוה, it says “yhwh.” The reader sees exactly what the text says. And then something occurs that no conventional translation allows: the reader notices that not every Elohim is the Creator. That not every Theos is sacred. That Kyrios is not yhwh. That “Jesus” is Iesous is Yeshua is Yehoshua — and that the name carries inside itself the name of yhwh.

The blackout is reversed. The ten suspects recover their names. And the reader — finally — can investigate.

You Cannot Un-Read It

Now that you have seen the ten names, there is no going back. Every time you open a conventional translation and read “God,” you will know that there was once Elohim, or Theos, or El, or Eloah there — and that the translation decided for you that the distinction did not matter. Every “Lord” will carry the shadow of erased yhwh. Every “Jesus” will echo Iesous, which echoes Yehoshua, which echoes yhwh. The blackout continues on shelves. But in your reading, no longer.

And this article covered only one of the erasures — the lexical one. There are others. The morphological erasure (plurals turned into singulars). The intertextual erasure (connections between OT and NT that translation cut). The numerical erasure — such as the enigma of 666, whose value in gematria points to Nezer HaKodesh, the priestly crown, not to Nero Caesar. Each layer removed is a layer of investigation blocked.

If what you read here provoked you, there are three things you can do now:

Read the codices for yourself — the Biblical Reader of the Belem-2025 Bible translation preserves all ten designations. Open it and compare with the translation you use. The contrast speaks for itself.
Investigate more deeply — The Little Book — A Culpa é das Ovelhas decodes other erasures that tradition consolidated, including the functional chain of the mark and the enigma 666. Ten chapters of forensic analysis of the biblical text.
Use technology in service of the text — the Gematria Calculator lets you calculate the numerical values of Hebrew and Greek designations yourself. Check the numbers. Trust no one — verify.
Receive the next investigations — subscribe to the newsletter and receive each forensic piece directly in your email.

Belem Anderson Costa Police Inspector — RJ Desvelational Forensic School “Belem an.C-2039” Belem-2025 Bible translation — 100% tokens translated

Auditable data: The occurrence counts were extracted from the complete corpus of the Belem-2025 Bible translation (31,287 verses, 441,646 tokens). Source codices: WLC/OSHB (Hebrew OT), SBLGNT + Nestle 1904 (Greek NT). Licenses: Public Domain + CC BY 4.0.

Verification tool: elohim_forensic_analysis.py — forensic statistical analysis with binomial test, Wilson confidence intervals, chi-square, and Cramér’s V.

“You read. And the interpretation is yours.”

Nominal Erasure — Adonai and Lilit as Case Studies

Belem Anderson Costa — Wed, 04 Feb 2026 00:00:00 +0000

Public source text: WLC (Westminster Leningrad Codex) + Nestle 1904. Translation: Belem-2025 Bible translation – literal, rigid, straight from the public códices.

What is nominal erasure?

When you read “Lord” in a Portuguese Bible, which original designation is behind it? It could be Yahweh (יהוה — yhwh; trad. “Jehovah”¹) (יהוה), it could be Adonai (אדני), it could be Adoni (אדני with hiriq). Three ontologically distinct designations compressed into a single word: “Lord.”

When you read “screech owl” in Isaiah 34:14 in the KJV, or “night creatures” in the NIV, or “night ghost” in other versions — what is behind it is a proper feminine name: לִּילִ֔ית — Lilit. Erased. Replaced. Invisible.

This is nominal erasure: the replacement of a proper name or specific designation with a generic term in translation, resulting in loss of referential information. The reader not only receives a different translation — they lose the ability to identify WHO or WHAT the original text names.

The numbers: 441,649 tokens scanned

To investigate this phenomenon, we performed an exhaustive computational scan of the Cloudflare D1 database of the Belem-2025 Bible translation — all 441,649 tokens from the 66 canonical books.

Metric	Value
Total tokens scanned	441,649
Total verses	~31,100
Total books	66
OT source	WLC (Westminster Leningrad Codex)
NT source	Westcott-Hort 1881
Query date	February 4, 2026

Result: two case studies that reveal the same mechanism operating at radically different scales.

Case Study 1: Adonai — 855 tokens leveled to “Lord”

The Hebrew designation Adonai (אדני) occurs in 855 tokens, distributed across 771 verses and 32 books of the Old Testament. There are at least 6 distinct morphological variants.

The 10 books with the most occurrences

Book	Verses
Ezekiel	215
Psalms	73
Isaiah	53
Gênesis	42
Jeremiah	38
Exodus	31
Judges	27
2 Samuel	26
1 Kings	25
Deuteronomy	22

Ezekiel concentrates 27.9% of all occurrences — almost exclusively in the construction Adonai Yahweh (yhwh) (אדני יהוה). This compound form appears ~217 times in the OT, and the forensic question emerges: why does Ezekiel insist on Adonai Yahweh (yhwh) while Isaiah and Jeremiah predominantly use Yahweh (yhwh) alone?

The vowel taxonomy: an editorial decision

The lexicon of Brown, Driver & Briggs (1906) distinguishes two consonantally identical forms:

Form	Final vowel	Classification
אֲדֹנָי (Adonay)	qamats ָ	“Divine” (sacral usage)
אֲדֹנִי (Adoni)	hiriq ִ	“Human” (king, husband, lord)

The critical datum: both share the same consonantal skeleton א-ד-נ-י. The difference lies EXCLUSIVELY in the Masoretic vowels — added in the 7th-10th century AD. The text that the prophets wrote contains only אדני, without vowels. The divine/human classification was ADDED by the Masoretic editors.

The trifusion: three designations, one word

The tripartite confusion becomes visible in Psalm 110:1 (WLC), where Yahweh (yhwh) and Adoni coexist —

נְאֻ֤ם יְהוָ֨ה לַֽאדֹנִ֗י שֵׁ֥ב לִֽימִינִ֑י עַד־אָשִׁ֥ית אֹ֝יְבֶ֗יךָ הֲדֹ֣ם לְרַגְלֶֽיךָ

“Declaration of Yahweh (yhwh) (יְהוָה) to my lord (אדֹנִי): Sit at my right hand, until I make your enemies a footstool for your feet.” — Psalm 110:1

Traditional Portuguese translations do this:

Original designation	Translation	Lost information
יהוה (yhwh)	LORD	Proper divine name
אֲדֹנָי (Adonay)	Lord	Distinct sacral designation
אֲדֹנִי (Adoni)	lord	Human referent

Three ontologically distinct designations → one single Portuguese word. Differentiated only by typographic conventions that the common reader does not decode.

Easter Egg #1: Psalm 110:1 — “Declaration of Yahweh (yhwh) to my adoni: sit at my right hand.” The Masoretic form has Adoni (with hiriq — “human” classification), not Adonay (“divine” classification). However, the NT quotes this verse applying it to Christos (Mt 22:44, Acts 2:34, Heb 1:13) — treating it as a divine reference. The contradiction: the Masoretes classified the referent as human; NT authors as divine. By translating everything as “Lord,” translations conceal this tension.

Case Study 2: Lilit — the absolute hapax legomenon

A complete scan of 441,649 tokens returned exactly 1 match: Isaiah 34:14, position 12 of 15 tokens.

1 occurrence in ~31,100 verses. Maximum rarity. Absolute hapax legomenon.

The verse: Isaiah 34:14

Masoretic Text:

וּפָגְשׁ֤וּ צִיִּים֙ אֶת־ אִיִּ֔ים וְשָׂעִ֖יר עַל־ רֵעֵ֣הוּ יִקְרָ֑א אַךְ־ שָׁם֙ הִרְגִּ֣יעָה לִּילִ֔ית וּמָצְאָ֥ה לָ֖הּ מָנֽוֹחַ

Rigid literal translation (Belem AnC):

“And tsiim met with iyyim; and a sa’ir upon his companion called; indeed, there Lilit rested and found for herself repose.”

Quadruple evidence of feminine gender

The morphology leaves no room for doubt:

Evidence	Form	Meaning
Ending -ית	לִּילִ֔ית	Hebrew feminine suffix
Verb הִרְגִּ֣יעָה	hirgi’ah	3rd fem. sing. “rested”
Verb וּמָצְאָ֥ה	u-mats’ah	3rd fem. sing. “found”
Pronoun לָ֖הּ	lah	“for herself” — feminine

Lilit is a feminine being. The verbal, pronominal, and nominal agreement is unequivocal.

The erasure: no Portuguese translation preserved the name until 2025

Translation	How it rendered	Type of erasure
KJV (1611)	screech owl	Animal
Almeida Corrigida Fiel	animais noturnos	Animal (PLURAL!)
NIV	night creatures	Generic (PLURAL!)
ARA	night ghost	Generic concept
Latin Vulgate	lamia	Greco-Roman demon
LXX (Septuagint)	ονοκενταυρος	Mythical creature
Belem-2025 Bible translation	Lilit	Transliteration (preserved)

Easter Egg #2: ACF and NIV translate in the PLURAL (“night animals,” “night creatures”) — erasing the morphological singularity. The Hebrew has a singular form. A singular feminine entity becomes a neutral plural concept. The LXX, already in the 3rd-2nd century BC, did not recognize the name: by translating as ονοκενταυρος (onocentaur), the Alexandrian translators reveal that Lilit’s meaning was already obscure — or deliberately avoided — two centuries before Christ.

The sa’ir network: quantified context

Lilit does not appear alone in Isaiah 34:14. In the same sentence is the sa’ir (שָׂעִ֖יר). We mapped the entire network:

Metric	Value
Total sa’ir tokens	100
Unique verses	97
Books with occurrence	11 / 39 (OT)
Semantic domains	6

The 6 domains

Domain	Tokens	%	Examples
RITUAL	47	47%	Lev 16, Num 7, 28-29 (offerings)
GEOGRAPHY	39	39%	Gen 36, Dt 2, Ezk 35 (land of Seir)
ENTITIES	4	4%	Lev 17:7, 2Chr 11:15, Is 13:21, Is 34:14
PROPHECY	1	1%	Dan 8:21 (prophetic beast)
DECEPTION	1	1%	Gen 37:31 (Joseph’s skin)
HOMOGRAPH	1	1%	Dt 32:2 (rains, different root)

The ENTITIES domain, although representing only 4% of tokens, concentrates all the critical forensic verses. And the most disturbing datum:

Easter Egg #3: All 4 verses in the ENTITIES domain present translation errors in the database — an error rate of 100%. Offset errors (pt_literal contains the next Hebrew word instead of the translation) and lexical errors (שָׁם/sham = “there” confused with שֵׁם/shem = “name”). Automated translation fails systematically in precisely the most critical contexts.

The intertextual pattern: ruins inhabited by entities

The pattern “empire falls → entities inhabit ruins” appears three times in the corpus, forming an OT-OT-NT chain:

Text	Empire	Entities	Who judges
Is 13:21	Babylon	Se’irim dance	Yahweh (yhwh)
Is 34:14	Edom (Seir)	Sa’ir + Lilit rests	Yahweh (yhwh)
DES 18:2	“Great Babylon”	daimonion + pneuma akatharton	Theos

Lilit appears exclusively in the Edomite setting, not in the Babylonian. The se’irim appear in both. This territorial exclusivity is forensic data: why is Lilit specific to Edom/Seir?

Easter Egg #4: DES 18:2 replicates exactly the structure of Isaiah 13 and 34: a destroyed city/empire becomes the habitation of spiritual entities. The same formula, separated by ~700 years of composition. Sa’ir is translated as “goat” or “hairy one.” Lilit as “owl.” Daimonion as “demon.” When you translate everything generically, the intertextual connection breaks.

The counter-argument — and its failure

The traditional argument for erasure is accessibility: translating “Lilit” as “owl” makes the text more understandable. The same for “Adonai” → “Lord.”

This argument fails for two reasons:

1. Presupposition of meaning. Translating “Lilit” as “owl” implies that the translators KNOW that Lilit = owl. But the LXX translates as “onocentaur,” the Vulgate as “lamia,” the ACF as “night animals” (plural). The disagreement demonstrates that nobody knows what Lilit is — and replacing the unknown with a generic term is not translation, it is concealment.

2. Asymmetry of treatment. Proper names like “Jerusalem,” “Moses,” and “Elijah” are systematically transliterated. Nobody translates “Jerusalem” as “the holy city” or “Moses” as “the one drawn from the waters.” The principle should be the same for Lilit and Adonai.

Conclusion: the erasure is not accidental — it is a pattern

The data from the computational scan sustain:

Adonai (855 tokens, 32 books): designation with complex vowel taxonomy, uniformized to “Lord” in all traditional translations, merged with Yahweh (yhwh) and deprived of its referential identity.
Lilit (1 token, 1 verse): proper feminine name with quadruple morphological evidence of gender, erased throughout the entire history of Bible translation in Portuguese until 2025.
Nominal erasure is not the exception — it is the pattern. It has operated since the LXX (3rd-2nd century BC) and persists in all contemporary translations.
The sa’ir network (100 tokens, 6 domains): verses in the ENTITIES domain — the most forensically significant — present a 100% error rate, suggesting systemic failure in the translation pipeline.
Rigid literalness returns to the reader the information that the original text contains. The Belem-2025 Bible translation is the first translation in the Portuguese language to adopt systematic transliteration for Adonai and Lilit.

The underlying philosophy:

“You read. And the interpretation is yours.”

Artificial form: vowels from Adonai (אֲדֹנָי → a, o, a) placed over consonants YHWH — Masoretic qere perpetuum. Medieval Latin readers merged both, producing “YeHoVaH” — a hybrid that never existed as a Hebrew word. The most accepted academic reconstruction is Yahweh /jah.ˈweh/, based on Greek transcriptions (Ιαβε — Clement of Alexandria, ~200 AD; Ιαουε — Theodoret of Cyrus, ~450 AD), abbreviated biblical forms (Yah — הַלְלוּ יָהּ), theophoric names (Yahu/Yeho — Eliyahu, Yehoshua) and Samaritan oral tradition (Yabe/Yawe). ↩︎