Translation — Blog - The Blame is on the Sheep

Sea of Reeds, Not Red Sea — The Most Perpetuated Translation Error in History

Belem Anderson Costa — Sat, 14 Feb 2026 00:00:00 +0000

Public source text: WLC (Westminster Leningrad Codex) + Nestle 1904. Translation: Bíblia Belem AnC 2025 — literal, rigid, straight from the public códices.

Opening the Dossier: YAM SUPH

You have heard about the “Red Sea” your entire life. Moses parts the Red Sea. The Israelites cross the Red Sea. Pharaoh’s armies are swallowed by the Red Sea. It is one of the most iconic scenes in human history — imprinted on the minds of billions of people through millennia of repetition.

But the Hebrew text never said “red.”

The Hebrew text says יַם־סוּף (Yam Suph). Literally: Sea of Reeds.

This is the forensic report on one of the most perpetuated translation errors in history — an error that began 2,300 years ago in Alexandria and that 99% of modern translations continue to copy without question.

Initial Report: The Word סוּף (Suph)

Before investigating what happened to the name, we need to isolate the primary evidence. What does the word סוּף (suph) mean?

Hebrew Term	Transliteration	Strong’s	Lexical Meaning	OT Occurrences
סוּף	suph	H5488	Reed, rush, aquatic plant	28x
יָם	yam	H3220	Sea, large body of water	~390x
יַם־סוּף	Yam Suph	Compound	Sea of Reeds	23x

The semantic field is unequivocal. Suph is a plant. An aquatic plant. A reed. A rush. The same type of vegetation that grows on the banks of rivers and marshes.

There is no respectable Hebrew lexicon that assigns to סוּף the meaning of “red.” None. Zero.

The forensic question is: if the word means “reed,” why do you read “red” in your Bible?

Material Evidence: Exodus 2:3,5

The most compelling evidence against the “Red Sea” translation is in the book of Exodus itself — two chapters before the crossing.

In Exodus 2:3, Moses’ mother places the baby in a basket and hides him:

וַתָּ֤שֶׂם בַּסּוּף֙ עַל־שְׂפַ֣ת הַיְאֹ֔ר

vatasem bassuph al-sefat hayeor

“And she placed [him] among the reeds (suph) on the bank of the Nile”

In Exodus 2:5, Pharaoh’s daughter finds the basket:

וַתִּרְאֶ֥ה אֶת־הַתֵּבָ֖ה בְּת֣וֹךְ הַסּ֑וּף

vatire et-hattevah betoch hassuph

“And she saw the basket in the midst of the reeds (suph)”

The same word. סוּף. Exactly the same. And here, all translations correctly render it as “reeds” or “rushes.” Nobody translates Exodus 2:3 as “and she placed [him] among the reds on the bank of the Nile.” That would be absurd.

Easter Egg #1: The same word — סוּף (suph) — translated as “reeds” in Exodus 2:3,5 is the same one that forms the name יַם־סוּף (Yam Suph) in Exodus 13:18. If suph means “reeds” in chapter 2, why would it mean “red” in chapter 13? The change of meaning has no lexical basis whatsoever. It is an inheritance of tradition.

The Chain of Contamination

How did a “Sea of Reeds” become “Red Sea”? The answer lies in a chain of editorial decisions that propagated over 23 centuries:

1. ORIGINAL HEBREW TEXT (13th-6th c. BCE)
יַם־סוּף (Yam Suph) = Sea of Reeds
↓
2. SEPTUAGINT (LXX) — Alexandria, 3rd-2nd c. BCE
ἐρυθρὰ θάλασσα (Erythra Thalassa) = Red Sea
↓ ❌ ERROR INTRODUCED HERE
3. LATIN VULGATE — Jerome, 4th c. CE
Mare Rubrum = Red Sea
↓ ERROR PERPETUATED (source rejected by the Desvelational School)
4. MODERN TRANSLATIONS (KJV, NIV, ESV, NASB)
"Red Sea" — copied from the LXX/Vulgate
↓
5. FINAL READER (2026)
Reads "Red Sea" without knowing the Hebrew says "Sea of Reeds"

Each link in this chain distances the reader from the original meaning. And most critically: translations that claim to be “faithful to the original” did not return to the Hebrew on this point. They copied the Septuagint’s editorial decision.

Easter Egg #2: The Septuagint was produced in Alexandria, Egypt — territory where Greek dominated and Hebrew was in decline. The translators likely identified the Yam Suph with the body of water the Greeks already called ἐρυθρὰ θάλασσα (the present-day Red Sea/Gulf of Suez). They confused geographic identification with linguistic translation. It is like translating “Río Grande” into English as “Big River” — you lose the proper name and introduce a description that does not exist in the original.

Textual Comparison: Exodus 13:18

The first mention of Yam Suph in the Exodus context. Let us see how each source treats the same text:

The key passages with יַם־סוּף in the Hebrew text (WLC) —

וַיַּסֵּ֨ב אֱלֹהִ֧ים אֶת־הָעָ֛ם דֶּ֥רֶךְ הַמִּדְבָּ֖ר יַם־סֽוּף

“And Elohim made the people go around by the way of the wilderness of the Sea of Reeds (יַם־סוּף).” — Exodus 13:18

מַרְכְּבֹ֥ת פַּרְעֹ֛ה וְחֵיל֖וֹ יָרָ֣ה בַיָּ֑ם וּמִבְחַ֥ר שָֽׁלִשָׁ֖יו טֻבְּע֥וּ בְיַם־סֽוּף

“Pharaoh’s chariots and his army He cast into the sea, and the elite of his captains sank in the Sea of Reeds (בְיַם־סוּף).” — Exodus 15:4

לְגֹזֵ֤ר יַם־ס֣וּף לִגְזָרִ֑ים כִּ֖י לְעוֹלָ֣ם חַסְדּֽוֹ

“To Him who divided the Sea of Reeds into divisions (לְגֹזֵר יַם־סוּף לִגְזָרִים), for His loyalty [endures] forever.” — Psalm 136:13

Source	Text	Result
WLC (Hebrew)	וַיַּסֵּ֨ב אֱלֹהִ֧ים אֶת־הָעָ֛ם דֶּ֥רֶךְ הַמִּדְבָּ֖ר יַם־סוּף	“Yam Suph” (Sea of Reeds)
LXX (Greek)	εἰς τὴν ἐρυθρὰν θάλασσαν	“Red Sea”
Vulgate (Latin)	juxta Mare Rubrum	“Red Sea”
KJV	“the way of the wilderness of the Red sea”	Copies the LXX
NIV	“toward the Red Sea”	Copies the LXX
Bíblia Belem AnC 2025	“way of the wilderness Yam Suph”	Preserves the Hebrew

Four translations — and only one preserves what the Hebrew text actually says.

Other critical examples:

Passage	Hebrew	Conventional Translations	Belem AnC
Exodus 15:4 (Song of Moses)	יָ֥רָה בְיַם־ס֑וּף	“cast into the Red Sea”	“cast into the Yam Suph”
Exodus 15:22	מִיַּם־ס֑וּף	“from the Red Sea”	“from the Yam Suph”
Psalm 136:13	לְגֹזֵ֤ר יַם־ס֣וּף לִגְזָרִ֑ים	“divided the Red Sea into parts”	“divided Yam Suph into parts”

All Occurrences of יַם־סוּף in the Old Testament

The compound Yam Suph appears 23 times in the Hebrew códices. All of them — without exception — were translated as “Red Sea” in conventional versions:

Book	Occurrences	References
Exodus	5x	10:19, 13:18, 15:4, 15:22, 23:31
Numbers	4x	14:25, 21:4, 33:10, 33:11
Deuteronomy	2x	1:40, 2:1
Joshua	3x	2:10, 4:23, 24:6
Judges	1x	11:16
1 Kings	1x	9:26
Nehemiah	1x	9:9
Psalms	5x	106:7, 106:9, 106:22, 136:13, 136:15
Jeremiah	1x	49:21
TOTAL	23x	—

Twenty-three occurrences. Twenty-three times the reader of conventional translations read “Red Sea.” Twenty-three times the Hebrew text said something else.

Why “Red”? — Hypotheses Under Investigation

If the Hebrew text does not say “red,” why did the Septuagint translate it that way? Four hypotheses have been raised:

Theory	Argument	Forensic Assessment
Geographic association	The LXX translators identified Yam Suph with the gulf of the Red Sea (Erythra Thalassa to the Greeks)	Probable — but confuses location with meaning. Identifying where it is located is not the same as translating what it means
Algae color	Red algae (Trichodesmium erythraeum) periodically color the water	Modern speculation — lexically unfounded. Suph does not designate algae
Solar reflection	Reddish light at sunrise/sunset over the water	Poetic — but does not justify a translation decision
Homonym suph = “end”	There is a homonym סוּף (H5490) meaning “end, cease” — “Sea of the End”	Possible confusion, but the context of Exodus 2:3,5 eliminates the doubt: suph = plant

Easter Egg #3: The most forensic hypothesis is the first: the LXX made a correct geographic identification (the crossing site was probably near the gulf) but incorrectly translated the name. The proper name “Yam Suph” described the characteristic of the place (full of reeds), not the color of the water. When you translate the name, you lose the description. When you preserve the name, you keep the clue.

Textual Consequences: What Is Lost

The “Red Sea” translation is not merely imprecise. It destroys intertextual connections that the Hebrew text deliberately constructed.

1. The pattern of salvation through the suph

In Exodus 2:3-5, baby Moses is saved among the reeds (suph) of the Nile.

In Exodus 13-15, all of Israel is saved by crossing the Yam Suph (Sea of Reeds).

The repetition of the term suph creates a narrative arc: what saved one (reeds of the Nile) prefigures what saved all (the Sea of Reeds). The same word connects both salvations.

When you translate one as “reeds” and the other as “red,” that connection becomes invisible.

Easter Egg #4: The Hebrew text creates a suph pattern — salvation through/among aquatic plants. Moses was placed in the reeds (suph) and saved. Israel crossed the Yam Suph and was saved. The lexical repetition is deliberate. Translating as “Red Sea” erases the author’s signature.

2. False geographic certainty

“Red Sea” sounds specific. The reader immediately thinks of the large body of water between Africa and Arabia. That closes the investigation prematurely.

“Yam Suph” — Sea of Reeds — opens the investigation. Where were there reeds? Marshes? Shallow lakes? The Nile Delta? The Bitter Lakes region? The name describes vegetation, not color. And vegetation is a different geographic clue — it points to shallow, marshy waters with reed beds.

3. Dependence on tradition rather than text

The reader who reads “Red Sea” never questions. The name seems definitive. “Sea of Reeds” demands investigation. And that is precisely what rigid literality does: it returns to the reader the work of investigating, rather than delivering an answer pre-chewed by tradition.

The Position of the Bíblia Belem AnC 2025

The Bíblia Belem AnC 2025 preserves יַם־סוּף as Yam Suph in all 23 occurrences. It does not translate it as “Red Sea.” It does not translate it as “Sea of Reeds.” It preserves the Hebrew name — because proper names are not translated.

Principle	Application
Rigid literality (R5)	Suph = reed — never “red”
Rejection of the LXX as authority	The Septuagint is a reference source, not a source of truth
Total rejection of Latin	Vulgate discarded — does not enter the chain of evidence
Preservation of names	Yam Suph is a proper name — transliterated, not translated

Report Conclusion

Item Investigated	Finding
Hebrew term	יַם־סוּף (Yam Suph) = Sea of Reeds/Rushes
Meaning of suph (H5488)	Reed, rush, aquatic plant — proven in Ex 2:3,5
Origin of the error	Septuagint (LXX), 3rd-2nd c. BCE — ἐρυθρὰ θάλασσα
Mechanism	Confusion between geographic identification and lexical translation
Perpetuation	Vulgate → Protestant translations → modern translations
Occurrences affected	23 in the Old Testament — all erroneously translated
Consequence	Intertextual connection suph (Ex 2) → Yam Suph (Ex 13-15) destroyed
Status	ERROR PERPETUATED FOR 2,300 YEARS

There is no lexical basis for translating סוּף (suph) as “red.” The word means reed, rush — and Exodus 2:3,5 proves it within the very context of the same book.

The “Red Sea” translation is an inheritance from the Septuagint — an editorial decision made in Alexandria 23 centuries ago. And 99% of modern translations copy that decision without returning to the Hebrew text.

The Bíblia Belem AnC 2025 preserves Yam Suph. Because the Hebrew text said Yam Suph. And proper names are not translated. They are investigated.

“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: Bíblia Belem AnC 2025 – 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 Bíblia Belem AnC 2025 — 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
Bíblia Belem AnC 2025	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 Bíblia Belem AnC 2025 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). ↩︎

Bíblia Belem AnC 2025 — The Method Behind the Translation

Belem Anderson Costa — Sun, 01 Feb 2026 00:00:00 +0000

Public source text: WLC (Westminster Leningrad Codex) + Nestle 1904. Translation: Bíblia Belem AnC 2025 — literal, rigid, straight from the public códices.

The Translation That Was Missing

There are dozens of Bible translations in Portuguese. Almeida Corrigida. NVI. NVT. NTLH. Almeida Atualizada. Each one made editorial choices — softened here, harmonized there, interpreted elsewhere. All of them deliver to the reader a processed text.

The Bíblia Belem AnC 2025 is different. It delivers the text raw. Morpheme by morpheme. Without softening. Without harmonization. Without implicit interpretation. The reader receives exactly what the códices say — in rough, uncomfortable, and radically faithful Portuguese.

It is the first rigid literal translation in the Portuguese language. The first of its kind.

The Accepted Códices

The translation works exclusively with public domain códices in the original languages. No Latin. No secondary translations. Only the oldest verifiable sources.

Old Testament

Codex	Abbreviation	Description
Westminster Leningrad Codex	WLC	Standard academic Masoretic text — Hebrew + Aramaic

The WLC is based on the Codex Leningradensis (c. 1008 AD), the oldest complete Masoretic manuscript in existence. It is the basis for virtually all academic editions of the Hebrew OT (BHS, BHQ).

New Testament

Codex	Abbreviation	Usage
Nestle 1904	NA1904	Critical text — primary source
Westcott-Hort 1881	WH	Critical text — comparison source
Textus Receptus 1550	TR	Ecclesiastical text — comparison source

The primary source for the NT is Nestle 1904 — a critical edition by Eberhard Nestle based on the collation of Tischendorf, Westcott-Hort, and Weymouth. It is public domain and academically rigorous.

WH 1881 and TR 1550 are used for comparison and recording of textual variants. When there is divergence between texts, the Bíblia Belem AnC records the variant.

REJECTED Source

Source	Status	Reason
Latin Vulgate	REJECTED	Derived translation, not a primary source. Contaminated by ecclesiastical editorial decisions
Any modern translation	REJECTED as source	Translations are derivations — the Belem AnC works only with primary sources
Non-public domain manuscripts	NOT USED	Verifiability requires public access

The Translation Method

Step 1: Source Text Identification

The translator identifies the Greek or Hebrew text in the public domain codex. There are no intermediaries.

Step 2: Morphological Analysis

Each word is morphologically analyzed:

Root/lexeme — dictionary form
Tense/mood/voice (Greek verbs) or binyan (Hebrew verbs)
Case/number/gender (nouns, adjectives, pronouns)
Prefixes and suffixes (especially relevant in Hebrew)

Step 3: Morpheme-by-Morpheme Translation

Each morphological unit receives a Portuguese correspondence. Word order from the original is preserved when possible. When Portuguese grammar requires minimal reordering, it is done — but indicated.

Step 4: Preservation of Designations

Divine designations are kept in their original script with transliteration:

Θεός (Theos), Κύριος (Kyrios), Χριστός (Christos)
יהוה (yhwh), אלהים (Elohim), אדני (Adonai)

Step 5: Zero Interpretation

The translator does not add interpretive notes in the body of the text. Does not soften strange constructions. Does not harmonize apparent contradictions. If the original text is ambiguous, the translation preserves the ambiguity.

What the Reader Finds

The experience of reading the Bíblia Belem AnC is deliberately different from any other translation:

What the reader expects	What the reader finds
Fluid and pleasant text	Rough and literal text
“God,” “Lord,” “Christ”	Θεός, Κύριος, Χριστός
Reorganized sentences	Original order preserved
Embedded interpretation	Zero interpretation
Explanatory footnotes	No interpretive notes

This is intentional. The discomfort is a pedagogical tool. When the reader stumbles on a strange construction, they are forced to investigate. When they encounter a Greek designation, they are forced to research. The text does not deliver answers — it delivers questions.

And questions are the engine of all investigation.

The Canon: 66 Books

The Bíblia Belem AnC works with the Protestant canon of 66 books — 39 from the Old Testament and 27 from the New Testament. The deuterocanonical/apocryphal books are not included.

Testament	Books	Original Language
Old Testament	39	Hebrew + Aramaic (parts of Daniel and Ezra)
New Testament	27	Koine Greek
Total	66	3 languages

The Author of the Translation

Belem Anderson Costa is not a theologian. He is a police officer, developer, and studied Letters — without completing the degree.

Competence	Application in Translation
Critical textual analysis	Rigorous examination of códices
Morphology	Decomposition of words into morphemes
Syntax	Analysis of Greek and Hebrew sentence structure
Semantics	Mapping of fields of meaning
Pragmatics	Communicational context of passages

The degree in Letters — not seminary — is deliberate. The translator does not carry the weight of a denominational tradition. He was not trained to read the text from a specific perspective. He acquired competencies to analyze the text as text.

Easter Egg #7: The surname “Belem” (Βηθλέεμ — Bethleem) is a transliteration of the Hebrew בֵּית לֶחֶם (Beth Lechem — “House of Bread”). The author carries in his name the same city where the biblical text records the birth of Ἰησοῦς. The suffix “An.C” in the translation refers to “Antes de Cristo” (“Before Christ”) — but inverted: the translation goes from Christ (from the códices) to the present. “Belem AnC” is, therefore, a signature: from the House of Bread, from before Christ, until now.

The Public API

The Bíblia Belem AnC does not exist only as static text. It is available via a public REST API:

URL: https://biblia.aculpaedasovelhas.org

Endpoint	Function
`/api/v1/books`	List of all 66 books
`/api/v1/verses/:book/:chapter`	Verses of a chapter
`/api/v1/verses/:book/:chapter/:verse`	Specific verse
`/api/v1/verses/search?q=term`	Text search
`/api/v1/tokens/:verseId/interlinear`	Interlinear text (Greek/Hebrew + Portuguese)
`/api/v1/tokens/:verseId/morphology`	Token-by-token morphological analysis

The API allows any developer, researcher, or student to programmatically access the Belem AnC text. Integrate with your own systems. Build tools. Verify each translation.

The API is built with TypeScript (Hono framework) and hosted on Cloudflare Workers with a D1 database. The code is open source.

Open Source: CC BY 4.0

The Bíblia Belem AnC 2025 is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). This means:

Anyone can copy and redistribute in any format
Anyone can adapt, remix, and build upon the material
For any purpose, including commercial
As long as proper attribution is given

The reason is simple: if the translation is faithful to the original text, it must be tested by the greatest possible number of people. Access restrictions protect the translator — not the truth. Open source exposes the translator to scrutiny — and that is good.

If there is an error, it will be found. If there is bias, it will be identified. If there is imprecision, it will be corrected. Because public scrutiny is the greatest purifier of Truth.

Integration with exeg.ai

The Bíblia Belem AnC is the textual corpus of the exeg.ai platform. When the user asks a question to the AI, it consults directly the Belem AnC text — not another translation.

The platform offers:

Semantic search — finds similar passages by meaning (FAISS)
Interlinear analysis — Greek/Hebrew text + literal translation side by side
Easter Egg Engine — detection of lexical patterns between passages
Intertextual mapping — traceable OT/NT connections

All based on the rigid literal translation. The AI does not soften, does not harmonize, does not interpret. Just like the translation.

The Invitation

The Bíblia Belem AnC 2025 is not for everyone. It is for those who accept the discomfort of literalness. For those who prefer a rough but faithful text to a fluid but interpreted one. For those who want to investigate rather than consume.

Each reader becomes an investigator. Each verse becomes a piece of evidence. Each reading becomes a forensic act.

The text is open. The códices are public. The translation is verifiable. The method is documented.

All that is missing is the investigator.

“You read. And the interpretation is yours.”

Rigid Literality — Translating Without Interpreting

Belem Anderson Costa — Sun, 01 Feb 2026 00:00:00 +0000

Public source text: WLC (Westminster Leningrad Codex) + Nestle 1904. Translation: Bíblia Belem AnC 2025 — literal, rigid, straight from public códices.

The translator’s dilemma

Every translation faces a choice: fidelity to the original text or fluency in the target language. The more faithful to the original, the less fluent. The more fluent, the more interpretive.

Most biblical translations in Portuguese chose fluency. The Bíblia Belem AnC 2025 chose fidelity. Total. Non-negotiable.

This produces a text that sounds strange in Portuguese. Sentences that do not flow naturally. Constructions that demand effort from the reader. And this is intentional. Because the goal is not linguistic comfort — it is access to the original text.

What rigid literality is

Rigid literality means translating morpheme by morpheme, not meaning by meaning. Each minimal unit of meaning in the Greek or Hebrew text receives a direct correspondence in Portuguese.

Approach	What it does	Result
Dynamic equivalence	Translates the general meaning of the sentence	Fluid, interpretive text
Formal equivalence	Translates word by word	Reasonably literal text
Rigid literality	Translates morpheme by morpheme	Raw text, without editorial treatment

Rigid literality is the most extreme degree of fidelity to the original. The translator does not soften. Does not harmonize. Does not “improve” the text for the modern reader. He delivers the text as it is — raw, rough, unpolished.

Concrete examples

The differences are visible and measurable:

θηρίον (therion)

Translation	Choice	Problem
Almeida Corrigida	“besta” (beast)	Adds pejorative charge that the Greek does not possess
NVI	“besta” (beast)	Same problem
Bíblia Belem AnC	“fera” (wild animal)	Literal translation of θηρίον — wild animal, without value judgment

The Greek θηρίον simply means “wild animal, beast.” The Portuguese translation “besta” carries a semantic charge of stupidity, moral brutality, repugnance — none of these connotations exist in the Greek. The translator who chooses “besta” has already interpreted before translating.

ἄγγελος (angelos)

Translation	Choice	Problem
Most translations	“anjo” (angel)	Implies winged celestial being — concept not present in Greek
Bíblia Belem AnC	“mensageiro” (messenger)	Literal translation — someone who carries a message

The word ἄγγελος means “messenger.” It can be human, it can be celestial — the Greek does not specify. When the translator writes “angel,” he has already decided that the messenger is a celestial being. That decision is interpretation, not translation.

ἐκκλησία (ekklesia)

Translation	Choice	Problem
Most translations	“igreja” (church)	Implies organized religious institution
Bíblia Belem AnC	“assembleia” (assembly)	Literal translation — group summoned for gathering

In classical and koine Greek, ἐκκλησία is simply an assembly of summoned citizens. There is no temple. There is no hierarchy. There is no denomination. The translation “church” projects 2000 years of institutionalization onto a text that describes gatherings of people.

σταυρός (stauros)

Translation	Choice	Problem
Most translations	“cruz” (cross)	Assumes specific shape without textual basis
Bíblia Belem AnC	“estaca” or “madeiro” (stake/timber)	Literal translation — σταυρός = vertical post

The Greek σταυρός designates a vertical post, a stake. The cross shape (with horizontal crossbar) is a later artistic tradition. The Greek text does not specify the shape. The literal translation preserves this ambiguity that the original possesses.

The principle of non-softening

Conventional translations apply three editorial processes that the Bíblia Belem AnC rejects:

1. Softening

Making the text more pleasant for the reader. Example: transforming rough Hebrew constructions into fluid sentences in Portuguese.

Rejected. If the Hebrew is rough, the Portuguese of the translation will be rough.

2. Harmonization

Making apparently contradictory passages seem consistent. Example: adjusting divergent genealogies.

Rejected. If the códices diverge, the translation reflects the divergence. The reader decides what to do with it.

3. Implicit interpretation

Choosing a translation that already implies an interpretation. Example: translating πνεῦμα (pneuma) as “Spirit” with a capital letter in certain contexts and “spirit” with a lowercase letter in others — a decision that the Greek does not make (Greek does not have upper/lowercase in the same way).

Rejected. The translation does not make interpretive decisions for the reader.

The sovereignty of the reader

This is the central principle: the reader has absolute sovereignty over interpretation.

The translation delivers the raw text. Any processing — softening, harmonization, interpretation — is done by the reader, not the translator.

This inverts the power dynamic. In conventional translations, the translator makes hundreds of micro-interpretive decisions that the reader never sees. The reader receives an already-processed product and believes they are reading “what the text says.” In reality, they are reading what the translator decided the text says.

Easter Egg #5: The expression λίθον λευκὸν (lithon leukon — “white stone”) in DES 2:17 receives in the literal translation exactly those two words: “white stone.” Conventional translations sometimes add explanatory notes about Roman voting customs. The literal translation does not add them. The reader finds “white stone” and researches on their own. The explanation does not come embedded — because explanation is interpretation.

The text as an untouched crime scene

In criminal forensics, the crime scene must be preserved intact. Each piece of evidence must remain where it was found. No one reorganizes the scene so it “makes more sense” for the photographer.

Rigid literal translation operates by the same principle. The original text is the crime scene. The translation is the photograph of the scene. If the photograph is “improved” — objects reorganized, stains cleaned, artificial lighting — it loses probative value.

Conventional translation	Rigid literal translation
Reorganizes the scene for the reader	Photographs the scene as it is
Cleans the textual “stains”	Preserves every stain
Adds interpretive lighting	Shows with natural light
Produces a beautiful image	Produces a faithful image

A beautiful translation can be a lying translation. An ugly translation can be the true translation.

The exeg.ai platform and literality

The artificial intelligence platform exeg.ai follows the same principle as the translation: it does not apply normalization automatically.

When the user asks a question about a passage, the AI searches the data of the Bíblia Belem AnC and returns the literal text. It does not soften. Does not harmonize. Does not interpret. It offers tools — semantic search, lexical analysis, intertextual mapping — and the user decides what to do with the results.

The AI is a microscope. It is not a pathologist. The report belongs to the investigator.

Practical comparison: DES 13:1

Let us see how different translations handle the same verse:

Greek (Nestle 1904):

Καὶ εἶδον ἐκ τῆς θαλάσσης θηρίον ἀναβαῖνον, ἔχον κέρατα δέκα καὶ κεφαλὰς ἑπτά

Almeida Corrigida:

“And I saw rising from the sea a beast that had ten horns and seven heads”

NVI:

“I saw a beast that came out of the sea. It had ten horns and seven heads”

Bíblia Belem AnC 2025:

“And I saw out of the sea wild-animal ascending, having horns ten and heads seven”

The Belem AnC translation preserves:

θηρίον = “fera” / “wild-animal” (not “beast”)
The Greek word order: “horns ten and heads seven” (not inverted for fluency)
The preposition: “out of the sea” (ἐκ τῆς θαλάσσης — the exit is emphasized)

Is the text less fluid? Yes. Is it more faithful to the original? Also yes. And that is the choice rigid literality makes — in every verse, in every word, without exception.

The first of its kind in Portuguese

The Bíblia Belem AnC 2025 is the first rigid literal translation in the Portuguese language. Literal translations exist in English (such as Young’s Literal Translation of 1862), but in Portuguese this approach had not been attempted with this degree of rigor.

The project is open source, licensed under CC BY 4.0, and the API is publicly available at Bíblia.aculpaedasovelhas.org. Anyone can verify the translation choices. Anyone can contest. Anyone can propose corrections.

Because rigid literality is not a dogma — it is a method. And methods are refined by public scrutiny.

“You read. And the interpretation is yours.”

Bíblia Belem, An.C 2025

Belem Anderson Costa — Sat, 04 Jan 2025 00:00:00 +0000

The New Rigid Literal Translation That Returns to the Reader the Right to Judge the Sacred Text

Official name: Bíblia Belem An.C 2025

Nature: Proprietary translation, with registered rights, carried out directly from the original códices (Hebrew, Aramaic, and Greek) into Portuguese, in a faithful, literal, and rigid format.

1) The Central Problem: Was the Bible “Translated” or “Interpreted”?

Over centuries, Bible translations were produced with a declared objective: to make the text “comprehensible.” But, for Belem Anderson Costa, this objective carried a devastating cost: the replacement of the text by the translator’s choices.

The author argues that traditional translation processes frequently apply:

Grammatical and syntactic normalizations
Meaning harmonizations
Cohesion and fluency adjustments
Stylistic “corrections”
Embedded theological decisions

And this set of “improvements” would have caused an effect that is not merely linguistic, but spiritual and civilizational: the progressive dilution of the literal truth of the Sacred Text.

The result, according to the author, was the formation of a religious world where the reader does not read the original, but reads the reading that the translator made of the original.

2) The Proposal: Rigid, Faithful, and Direct Literalness

The Bíblia Belem An.C 2025 is born as a response to this thesis. Belem defines the principle of the project in one sentence:

“From the language of the sacred text directly to the language of the reader.”

The translation is built on the basis of:

Extreme literalness
Formal fidelity
Structural rigidity
Absence of “improvements”
Rejection of harmonizations
Resistance to tradition as a reading filter

The author describes this rigidity as literalness at the TEA level, assuming that pure literal reading is the only truly faithful and morally safe reading.

The consequence is not to produce an “easy” text. The consequence is to produce an honest text.

3) The Reader Returns to the Place of Judge of the Text

For Belem, traditional translation displaced the center of biblical reading:

The Shift

Before: the reader judges the text
After: the translator judges the text and delivers his judgment to the reader

The Bíblia Belem An.C 2025 seeks to reverse this. The idea is simple and radical: the reader needs to receive the text raw enough so that they themselves may judge.

This includes:

Syntactic strangeness
Unusual constructions in Portuguese
Uneliminated repetitions
Ambiguity maintained when it exists in the original
Rigid and consistent lexical choices

The reader is invited to exercise:

Their philological intelligence
Their personal theology
Their sense of textual coherence
Their spiritual discernment

And not to absorb “invisible conclusions” from translators and traditions.

4) The Normalization Tool: Support Is Commanded by the Reader

Belem states that the problem is not “using support.” The problem is when support replaces the text and decides for the reader.

For this reason, the project includes a key element: an intelligent normalization tool commanded by the reader.

The translation remains rigid and literal
Normalization does not come embedded in the text
The reader activates normalization when they wish
The reader chooses the level of support
The reader decides how much they want to “adapt” for comprehension

The core of the thesis is this:

The translation must not contain the interpretation. The interpretation must be born from the reader before the text.

5) The Great Deception and Apostasy as a Textual Phenomenon

The author sustains a total theological and historical thesis: apostasy and the great deception also happened (and primarily) through the progressive adulteration of the text via translation and tradition.

According to Belem:

There has not been, in the world, a fully true Church of Jesus Christ
Because the text was altered by successive layers of translation + tradition
And this prevented humanity from solving the enigmas and hidden codes of the Sacred Text
Making the reader’s judgment dependent on external authorities

Apostasy, in this formulation, is not merely “doctrinal deviation.” It is a global structure of deception, fueled by:

Softened language
Domesticated meaning
Religious fear
Myth and mysticism
Contours of terror
A culture of dependence on the “official interpreter”

6) The Unveiling of Jesus Christ: Book 66 as the Key to the World

Belem affirms that Jesus revealed to the apostle John the truth about the Great Deception. And that this text is not correctly understood by the name “Apocalypse.”

He affirms that the true name is: The Unveiling of Jesus Christ

And that the system of deception would have operated once again:

Renaming the book to “Apocalypse”
Wrapping it in terror and mysticism
Transforming the most important book in the history of Jesus Christ into the least read
Isolating it as “a subject for specialists,” “end of the world,” “fear,” “fanaticism”

On this axis, the thesis is complete:

The Bible contains everything. Nothing was left out.
Book 66 is the key.
But book 66 requires a key.
And that key was reserved “for the correct time.”

7) The Declared Mission: The Little Book and the Sword That Proceeds from the Mouth

The Bíblia Belem An.C 2025 project is presented as part of a life mission. Belem affirms that, with “O Livrinho - A Culpa é das Ovelhas,” he is announcing to the world that:

The great deception has already happened
Apostasy has already consolidated
The beasts and the false prophet have been exposed
The prophecies of Daniel and the end times have their identity and structure revealed
And the antichrist is not an unsolvable mystery

The rhetorical core that the author sustains is:

Jesus Christ has already delivered the truth. And the truth is in the Unveiling of Jesus Christ.

The Bible, then, is not merely a spiritual text. It is a complete system of reality, history, and prophecy.

8) Why This Translation Exists Now

The Bíblia Belem An.C 2025 is positioned as a translation for a specific time. A time where:

Humanity has tools to read the original with technical support
The reader can command normalization layers without losing the raw text
Dependence on religious authorities can be broken
Interpretation can return to the hands of the reader
And the text can be read as it was written, without cultural “shields”

In the author’s view, this is not luxury. It is obligation.

9) Conclusion: Literalness as Liberation

The Bíblia Belem An.C 2025 is not just a translation. It is a thesis.

A thesis that declares:

The truth exists only in the literal text
The translator cannot be the judge
The reader needs to recover the right to judge
And humanity was deceived by a linguistic system disguised as “improvement”

The final proposal is not to soften. It is to expose.

It is not to facilitate. It is to return the source.

It is not to domesticate. It is to reveal.

Amen, amen: the time of the end, the time of the new beginning.