The Translation Rules of the Desvelational Forensic School

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

Someone tampered with the crime scene

Imagine you arrive at a crime scene. The body is on the floor. The evidence is scattered. Blood marks on the walls. Footprints in the corridor. Every detail — every stain, every position, every angle — tells a story.

Now imagine that before you arrived, someone entered the room. They cleaned the blood “because it was unpleasant.” They moved the body “to make it more presentable.” They rearranged the objects “so that they made more sense.” And they left a note: “Done. Now the scene is easier to understand.”

Would you trust that scene? Could you reconstruct what happened?

That is the situation of anyone who reads a conventional Bible translation. Someone got there before you. They cleaned what was uncomfortable. They softened what was rough. They rearranged what seemed out of order. And they delivered a beautiful, fluid, comfortable text — and adulterated one.

You never asked them to do that. Never authorized it. Never knew. But it was done. In every verse. In every book. Over centuries.

The Belem-2025 Bible translation is the first translation in the Portuguese language that refuses to clean the scene. It goes to the original codex — the untouched crime scene — and photographs. Without retouching. Without filters. Without editing.

And to guarantee that no one touches the scene, it operates by rules. Not preferences, not guidelines, not “good editorial sense.” Rules. Absolute. Verifiable. Auditable.

This article reveals each one of them. And when you finish reading, you will understand why your Bible does not show what is really in the codices.

The theft nobody noticed

Open any Bible in English. Search for the word “God.” You will find it thousands of times. In the Old Testament. In the New Testament. In Genesis. In the Unveiling (apokálypsis). It is everywhere.

Now a simple question: in which original codex — Hebrew, Aramaic, or Greek — does that word appear?

In none.

The word “God” is derived from Latin roots. It does not exist in the Hebrew manuscripts. It does not exist in the Greek manuscripts. What exists is something else entirely. In the Hebrew codices, there are five distinct designations: yhwh, Elohim, Eloah, El and Adonai. In the Greek codices, there is Θεός. Five Hebrew words and one Greek word — six completely different terms, with different meanings, in different contexts — were all flattened into the same rendering.

Imagine a forensic report where six different chemical substances — arsenic, cyanide, strychnine, thallium, ricin and aconitine — were all identified as “poison.” Without distinction. Without specification. Just “poison.” The report would be useless. The investigation would be impossible. And that is exactly what conventional translations do with divine designations.

The Belem-2025 Bible translation does not accept that flattening. It preserves each designation in its original form.

The 8 words nobody has the right to touch

Eight words — five Hebrew, three Greek — are untouchable in the translation. They are not translated. They are not substituted. They are not domesticated. They appear in direct transliteration, exactly as in the codices.

And each one has a reason.

yhwh (יהוה). The tetragrammaton. The most important name in the entire Hebrew corpus — written approximately 6,500 times in the manuscripts. Six thousand five hundred times. And what did conventional translations do with it? They replaced it with “Lord.” Or “LORD.” A word that is not a name — it is a generic title. Imagine someone taking your father’s name and replacing it with “citizen” in every family document. Birth certificate: “citizen.” Will: “citizen.” Personal letters: “citizen.” You would lose the ability to know who he is. That is exactly what happened. The name yhwh disappeared from millions of Bibles — and with it, the reader’s ability to distinguish when the text speaks of the name and when it speaks of the title. In the Belem-2025 Bible translation, yhwh remains yhwh. Always lowercase — without confusion with abbreviations. How many times have you read “Lord” in the Bible without knowing there was a proper name there?

Elohim (אֱלֹהִים). Here lives one of the best-kept secrets of the Hebrew text. Elohim is a plural form. But translators treat it as singular when the context is “monotheist” and as plural when the context is “pagan.” They write “God” or “gods” — and with a single capitalization decision, they resolve an ambiguity that the Hebrew text deliberately maintained. The Belem-2025 Bible translation does not resolve it. It keeps Elohim — and the ambiguity of the plural it carries.

Eloah (אֱלוֹהַּ). An archaic singular form that appears predominantly in the book of Job. A distinct designation. But for conventional translations? “God.” The same word as Elohim. The same word as El. The distinction — which the author of Job considered important enough to use — has disappeared.

El (אֵל). The most primitive, most compact, most ancient form. Three Hebrew designations — El, Eloah, Elohim — three deliberate choices by the original authors. Three nuances that became one: “God.” As if the colors red, crimson, and scarlet were all called “red” in a textile fiber report. The evidence is destroyed by the simplification.

Adonai (אֲדֹנָי). “My lord” — a title, not a name. But there is an extra layer of manipulation here. The Masoretes — scribes who vocalized the Hebrew text between the sixth and tenth centuries — replaced the oral reading of yhwh with Adonai. The reader sees yhwh but reads Adonai. It is like crossing out the name on a badge and sticking another one on top. The Belem-2025 Bible translation preserves both — the name yhwh and the title Adonai — so that the reader can see the difference the Masoretes tried to merge.

Θεός (Theos). Greek has a grammatical distinction that English ignores: ὁ Θεός (with the definite article — “the Theos,” specific reference) and Θεός (without the article — “divinity,” generic reference). The translation “God” with a capital letter turns every occurrence into a specific reference — erasing the grammatical data that Greek preserved. Can you grasp the size of the information lost with that simplification?

Iesous (Ἰησοῦς). A proper name. The rule is surgical: names are not translated — they are transliterated. The form “Jesus” is not Greek. It is the result of a path that passes through Greek, crosses Latin, and arrives in English. The Belem-2025 Bible translation goes from Greek to the target language without stopping in Latin.

Χριστός (Christos). It is not a surname. It was never a surname. It is a title — “anointed one,” from the verb χρίω (chrio, “to anoint”). Saying “Jesus Christ” is like saying “John President” — fusing name and title as if they were a single thing. The translation preserves Χριστός as a title, separate and traceable.

And the most radical consequence of these eight rules? The word “God” does not appear a single time in the Belem-2025 Bible translation. Not once. Because it does not appear a single time in the codices.

The names that were erased

It is not only divine designations. The ecclesiastical tradition translated proper names — and in doing so committed a philological crime that goes unnoticed.

Mosheh became Moses. Shelomoh became Solomon. Yerushalayim became Jerusalem. Beit-Lechem became Bethlehem. Paulos became Paul. Every name carries etymology, history, cultural identity. Mosheh — “drawn from the waters.” Beit-Lechem — “House of Bread.” Yerushalayim — “Foundation of Peace.” When you translate, you erase. When you transliterate, you preserve.

The Belem-2025 Bible translation transliterates. It does not domesticate. The reader encounters Mosheh — and is reminded that they are reading a foreign text, from another culture, from another millennium. The strangeness is intentional. Domestication creates the dangerous illusion of familiarity — as if the text had been written in English, by contemporary people, for contemporary readers. It was not. And the translation must not pretend it was.

The marks the translator leaves — visible

Every translation requires interventions. Points where the translator must add something the original does not have, because the target language requires it. The difference between an honest and a dishonest translation is simple: the honest one marks each intervention. The dishonest one hides it.

The Belem-2025 Bible translation marks. Three brackets. Three situations.

[OBJ] — Hebrew omitted the direct object. The target language needs it to function. The translator inserts it — and marks it. The reader sees the mark and knows: this is not in the codex. It was added so that the sentence functions in my language. The decision was the translator’s. And it is visible.

[grammatical_ellipsis] — Hebrew and Greek are languages that can condense in one sentence what Portuguese or English would need three to say. When the translator expands a condensed structure, they mark it. The reader knows where the original was “stretched” to fit the target language.

[interpretation_needed] — This is the rarest. And the most courageous. There are passages where the original text is genuinely ambiguous. Two possible readings. Three. Four. And all equally valid from the textual data. What does the conventional translator do? They choose one and hide the others. What does the Belem-2025 Bible translation do? It does not choose. It marks: [interpretation_needed]. And it returns the decision to the reader.

Think about what that means. Every translation you have ever read has made hundreds of interpretive decisions without warning you. The Belem-2025 Bible translation warns you. Every bracket is a warning. Every warning is a confession: “Here I intervened. Check.”

The same word — always

This principle will change the way you read the text.

In conventional translations, the same Greek word can be rendered differently depending on context. θηρίον (thērion) appears as “beast” in Revelation and as “animal” elsewhere. ἄγγελος (angelos) appears as “angel” when the context seems celestial and as “messenger” when it seems human. ἐκκλησία (ekklēsia) appears as “church” in Acts and as “assembly” in secular contexts.

What is the translator doing? Interpreting before translating. They look at the context, decide what the word “should” mean there, and deliver to the reader a translation that already carries the translator’s judgment. The reader never knows that the same Greek word was used in both contexts — because the translator used different words.

The Belem-2025 Bible translation follows an iron rule: same original word = same translation. Always.

θηρίον is “beast” — in all 46 occurrences. Not “beast” here and “animal” there. “Beast.” Always. If you are used to reading “beast of the Apocalypse,” prepare yourself: in the Belem-2025 Bible translation, it is desvelacao-nao-apocalipse/">“beast of the Unveiling” — and the difference is not cosmetic.

ἄγγελος is “messenger” — whether in heaven or on earth. Not “angel” in one verse and “messenger” in another. Greek uses the same word. The translation uses the same word.

ἐκκλησία is “assembly” — in Acts, in the letters, everywhere. Not “church” when it suits and “assembly” when it does not.

The effect is transformative. When the reader encounters the same word in two apparently disconnected contexts, they perceive a pattern that the conventional translator concealed. They begin to see the connections the original author planted — and that two thousand years of interpretive translation buried.

The order that nobody respects

The words in the codices are in a specific order. That order is not accidental. In Greek, the position of a word in the sentence indicates emphasis. What comes first receives more weight.

When Greek writes κέρατα δέκα καὶ κεφαλὰς ἑπτά — “horns ten and heads seven” — the emphasis is on the nouns. Horns first. Heads after. The numbers come in the background. The author wants you to see the horns and the heads before counting how many there are.

What does the conventional translation do? It inverts: “ten horns and seven heads.” Fluent. Beautiful. And wrong. The emphasis changed. The numbers moved to the front. The nouns moved to the back. The reader receives a rearranged sentence — and never knows that the rearrangement concealed a reading cue.

The Belem-2025 Bible translation preserves: “horns ten and heads seven.” Does it sound strange in English? Yes. Because it was not written in English. It was written in Greek. And the translation preserves the structure of the Greek — with its strangeness, with its emphases, with its clues.

The discomfort is a tool. When the text sounds strange, the reader stops. When they stop, they think. When they think, they investigate. When they investigate, they discover. Fluency puts to sleep. Strangeness wakes up.

Six doors to the same text

Most translations deliver a single product. One layer. One version. Take it or leave it. But what if you could choose how much assistance you want when reading the text?

The Belem-2025 Bible translation offers six layers — like a microscope with six magnification levels. The reader chooses how much assistance they want. And can change their mind at any moment.

N0 is for those who want the raw data — the researcher, the philologist, the forensic text investigator. N5 is for those who need support — but want to maintain control. In both cases, the reader knows which layer they are in. They know what was added. They know what is original and what is assistance.

In conventional translations, you receive something between N3 and N5 — without knowing. Without choosing. Without being able to go back to N0 and verify.

The numbers that did not exist

Open any Bible. See the numbered verses. 1, 2, 3, 4, 5. Each sentence with its number. It seems natural, right? As if it had always been that way.

It had not.

Verse numbering was invented in 1551. By Robert Estienne — a French publisher, not a prophet, not an apostle, not an inspired scribe. He created the numbering during a journey on horseback between Paris and Lyon, to facilitate cross-references in his printed edition. A practical solution from a sixteenth-century editor. And that system — invented for typographical convenience — crystallized as if it were part of the sacred text.

The Belem-2025 Bible translation removed them. All 31,156 verse markers. Each one.

The effect is disturbing — and revealing. Without verses, the reader is forced to read paragraphs. Complete arguments. Blocks of thought. Not isolated fragments that can be ripped out of context and used as ammunition for any doctrine. Without verses, the text becomes text again — not a database of quotable citations.

Chapters were preserved — they are an older division, less invasive, and closer to the original narrative structure. But verses? Artificial. Late. Invasive. Removed.

Latin is contraband

There is a principle that governs all the other rules: the translation goes from the original codex to the target language. Without intermediaries. Without stopovers. Without Latin.

This seems obvious. It is not.

Most Bible translations in any modern language carry Latin DNA. Not because they were translated from Latin directly — but because the terms they use passed through Latin at some point in history. “Apocalypse” is a Latinization of the Greek (apokalypsis). “Christ” passed through Latin (Christus) before arriving in English. Biblical terminology was shaped by Jerome’s Vulgate — a fourth-century translation that decided how Greek and Hebrew words would be rendered into Latin, and from Latin into all European languages.

The Belem-2025 Bible translation cuts that chain. The path is direct: Hebrew/Aramaic/Greek → target language. Period.

“Apocalypse” (Latinization) → Unveiling/Revelation (apokálypsis) — from the Greek ἀποκάλυψις — literally “removal of the veil.” “Christ” (Latinization) → Χριστός (original Greek, “anointed”).

Every Latin word that naturalized itself in Bible translations is contraband. It entered through the Vulgate, crossed centuries, and today is treated as if it were legitimate. It is not. The Belem-2025 Bible translation confiscates the contraband and returns the original.

The three frauds you never saw

Every conventional translation applies three editorial processes. Each one seems harmless in isolation. Together, over 31,287 verses, they produce a text that is more editorial fiction than historical document.

Softening. Hebrew has rough, strange, uncomfortable constructions. The conventional translator cleans. Smooths. Makes palatable. The result is a beautiful text that conceals the roughness the original author considered important. The Belem-2025 Bible translation preserves the roughness. If Hebrew is uncomfortable, the translation will be uncomfortable. Because discomfort is data — not a flaw to be corrected.

Harmonization. Two accounts of the same scene with diverging details. Genealogies that do not add up. Parallel narratives with discrepancies. The conventional translator aligns. Harmonizes. Makes everything appear consistent. The Belem-2025 Bible translation does not harmonize. If the codices diverge, the translation diverges. If there is inconsistency, the inconsistency is there — visible, verifiable, untouched. The reader decides what to do with it.

Implicit interpretation. The Greek πνεῦμα (pneuma) can mean “spirit,” “breath,” or “wind.” The uncial manuscripts — the oldest — are written entirely in uppercase, without the distinction “Spirit” (divine) versus “spirit” (human) that modern translations introduce. When the translator writes “Spirit” with a capital in one verse and “spirit” with a lowercase in another, they made an interpretive decision the original manuscript did not make. They decided where pneuma is divine and where it is human — and hid the decision inside a capital letter. The Belem-2025 Bible translation does not make distinctions the original does not make. Want to understand the real impact of this? Read how the translation handles pneuma across the entire corpus.

The machine that does not think

One final rule. Perhaps the most important of all.

The exeg.ai platform — the artificial intelligence that operates over the corpus of the Belem-2025 Bible translation — follows the same principle as the translation: zero interpretation.

If the user asks about a passage, the AI searches the data. It finds terms. It maps occurrences. It presents lexical connections. But it does not say what the data means. It does not connect passages as “prophecy and fulfillment.” It does not construct theological narratives. It does not suggest spiritual meanings.

The AI is a high-powered microscope pointed at the text. It amplifies. It illuminates. It measures. But the report — the meaning, the interpretation, the conclusion — belongs to the investigator. To the reader. To whoever is looking.

If two texts share a rare term, the AI shows: “These two texts share the term X.” It does not say: “This OT text prophesies that NT text.” That connection — if it exists at all — belongs to the reader. The AI presents data. The interpretation belongs to whoever reads.

The engine behind the rules

None of these rules is applied manually, verse by verse, by a human translator with coffee and goodwill. They are encoded in three computational glossaries — the backbone of the system.

keep_original.json — The 8 untouchable words. Each entry documents the original spelling in Hebrew or Greek, the transliteration, the reason for preservation, and all morphological variants. When the system encounters yhwh, it consults no translator. There is no decision to make. The rule is: keep. And it keeps.

hebrew.json — Approximately 12,000 Hebrew terms, each mapped to its literal translation. Strong’s numbers included for full traceability. The researcher can go from the translation back to the Hebrew root in one click.

greek.json — Approximately 2,000 terms of Koine Greek, mapped with the same precision.

The system is deterministic. The same word in the same morphological context produces the same translation — today, tomorrow, ten years from now. There is no “editorial style.” There is no “current preference.” There is no human variation. Consistency is computational, not subjective.

Every word of the 441,646-token corpus is processed against these glossaries. If it is in keep_original → untouchable. If it is in the glossary → mapped literal translation. If it is in neither → flagged for manual analysis, documented, and incorporated into the glossary after review.

The system grows. But it never contradicts itself.

Why this matters

Perhaps you are thinking: “These are details. Linguistic minutiae. Academic questions that do not affect reading.”

They are not.

When 6,500 occurrences of a proper name — yhwh — are replaced by a generic title — “Lord” — the reader loses the ability to track the presence of that name in the text. They lose the ability to perceive when the text speaks of the name and when it speaks of the title. They lose data. And lost data is destroyed evidence.

When three distinct designations — El, Eloah, Elohim — become a single word, the reader loses the ability to perceive that the original authors made deliberate distinctions. That they used Eloah in Job for a reason. That they used El in specific contexts for another reason. Three colors become one. The picture is impoverished.

When the translator decides that ἄγγελος is “angel” in one context and “messenger” in another, they decide for you whether the messenger is human or celestial. You never saw the decision. Were never consulted. Never knew that the same Greek word was in both contexts. You lost the clue.

Every rule of the Belem-2025 Bible translation exists to return to the reader something that was taken from them. Every rule is a restitution. Every rule says: “This is yours. It always was. And nobody had the right to take it.”

The conventional translation is a filter between you and the text. The Belem-2025 Bible translation is a window.

Filters choose what you see. Windows show everything.

These rules guarantee that the window stays clean.

Want to receive the next investigations directly in your inbox? Subscribe to the newsletter — no spam, no doctrine, just data from the codices:

Subscribe to the Newsletter

Want to go deeper? The Little Book A Culpa é das Ovelhas applies these translation rules to the forensic investigation of the Unveiling (apokálypsis) — and what emerges from the codices will change the way you read every page:

Discover The Little Book

Want to verify for yourself? The Belem-2025 Bible translation is available — open it, read it, compare it with the translation you know:

Read the Belem-2025 Bible translation

Public source text: WLC (Westminster Leningrad Codex) + Nestle 1904. Translation: Belem-2025 Bible translation — literal, rigid, direct from the public codices.

These rules in action

Want to see the desvelational rules applied to a complete investigation? “The Little Book — A Culpa é das Ovelhas. Edition 666, the beasts exposed” is the first work to apply the method in its entirety: rigid literal translation, public codices, rejection of Latin and tradition, and forensic identification of the Beasts of Revelation 13.

369 pages. 12 chapters + 5 appendices. Zero ecclesiastical tradition.

Read free online →

“You read. And the interpretation is yours.”