Church Part 13: What Did Ancient People Mean by “God”?

Before we ask what the Bible teaches about God, we may need to ask what its writers meant by the word.

The Question We Didn’t Know We Were Asking

Let’s begin with a very simple question.

When you hear the word God, what appears in your mind?

Not what you think should appear.

What actually appears?

Maybe you picture the Creator of heaven and earth.

Maybe you think of the Trinity.

Maybe you imagine a supreme being, eternal and all-powerful, outside time and space.

Maybe, if we are being honest, some part of your imagination still reaches for the old Sunday school picture: an elderly man in the sky with a white beard, looking faintly disappointed in everyone.

That is not a silly picture.

Most of us inherited some version of it.

I certainly did.

We grow up hearing the word God as though it is obvious. As though everyone, everywhere, has always meant the same thing by it. We read Genesis, Exodus, Psalms, Isaiah, John, Paul, and Revelation with one English word sitting neatly in our minds.

God.

Simple enough.

Except maybe it is not simple.

Maybe the problem begins before theology.

Maybe the problem begins with language.

So let’s slow down.

When Abraham heard words for deity, did he hear what we hear?

When Moses spoke of the God of Israel, was he using the same mental categories that a modern Christian, Jew, atheist, philosopher, or Sunday school teacher uses?

When Isaiah wrote about Yahweh, was he answering the same question we are asking when we say, “Do you believe in God?”

I am not asking that to be clever.

I am asking because ancient texts are old houses.

If we walk into them carrying modern furniture, we may think we understand the room simply because we recognise the walls.

But the chairs may not be where we expect.

The table may have had a different purpose.

The lamp may not have been a lamp at all.

This is where reading ancient texts becomes both difficult and beautiful. Words survive, but worlds change.

A word can travel across centuries and still look familiar while carrying a different set of assumptions inside it. That happens all the time.

Imagine reading an ancient text that says, “The king ruled the land.”

Fine.

We know what a king is.

Or do we?

A Bronze Age king, a medieval king, a constitutional monarch, and a fairy-tale king do not occupy the same mental room. The word may overlap, but the world behind it changes.

Or take the word president.

To one person it means an elected head of state.

To another it means the president of a company.

To another it means the person presiding over a meeting.

Same word.

Different furniture.

So what happens when we do this with the word God?

That is the question I want to investigate.

Not settle.

Investigate.

This is not a theology post.

Not yet.

It is not an attempt to prove a doctrine. It is not an argument about what you should believe. It is not apologetics dressed in a linen shirt and pretending to be archaeology.

Allegedly.

This is something quieter.

We are going to ask how ancient people used divine language.

What words did they use?

What did those words mean in context?

Did one word always mean one thing?

Did English preserve the distinctions?

Or did English sometimes smooth over rough places that the Hebrew text leaves visible?

Before we answer, we need to make one careful distinction.

Observation is not interpretation.

And interpretation is not conclusion.

That sounds obvious, but it is where many arguments go wandering off into the woods without a torch.

An observation says, “This word appears in more than one kind of passage.”

An interpretation says, “Perhaps the word has a broader range than our English translation suggests.”

A conclusion says, “If that is true, then we may need to reread certain passages more carefully.”

Those are not the same move.

We need to keep them separate.

Otherwise we start doing something ancient readers would find very strange: we make the text answer questions before we have listened to the words it actually uses.

That does not mean modern theology is useless.

Not at all.

It simply means we should not begin there.

If we want to understand an ancient text, we have to let the ancient text speak with its own accent first.

Later theology may be wise.

Later philosophy may be careful.

Later doctrine may be profound.

But none of that removes the need to ask what the original writers were doing with their own language, in their own world, among their own assumptions.

And that world was not ours.

The biblical writers did not live in a secular universe where “religion” was one private category among many. They did not imagine reality as a flat material stage with occasional supernatural interruptions.

They lived in a world thick with meaning.

Visible and unseen were not sealed off from one another.

Kings represented powers.

Nations had divine associations.

Mountains mattered.

Temples mattered.

Names mattered.

Allegiance mattered.

And words for divine beings did not always behave the way our English word God behaves.

Notice that carefully.

I did not say what that proves.

I said it gives us something to investigate.

There is a difference.

And perhaps that difference is the whole point of this series.

Because if we rush, we will read too quickly.

If we read too quickly, we will assume too much.

And if we assume too much, we may end up defending or rejecting ideas the ancient authors were not actually trying to say.

That is not a problem only for religious readers.

It is a problem for anyone reading old texts.

Believers can import later doctrine too early.

Skeptics can import modern categories too confidently.

Scholars can import technical frameworks too neatly.

Preachers can import sermons before the sentence has finished speaking.

All of us are capable of this.

Every single one of us walks into the ancient world carrying baggage.

The question is not whether we brought baggage.

We did.

The question is whether we are willing to set it down long enough to look around.

So for this part of the series, we are going to practice a slower method.

First, we will gather the vocabulary.

Then we will look at the world those words lived in.

Then we will follow one especially important word through several passages and see what it does.

Only after that will we begin building a possible model.

Not a final answer.

A model.

A way of reading that explains more of the evidence with fewer forced moves.

That is all.

For now, I want us to resist the urge to solve the whole question in the first room.

Ancient texts do not reward impatience.

They are more like forests than instruction manuals.

You have to walk slowly.

You have to notice tracks.

You have to admit when you do not yet know whether that sound in the branches is a bird, a squirrel, or something with opinions.

So before we ask, “What does the Bible teach about God?” maybe we need to ask a more basic question.

What words did the biblical writers actually use?

And what did those words mean before English gathered them under one familiar roof?

The Vocabulary

Now we have to do something that feels almost too simple.

We have to look at the words.

Not the doctrines yet.

Not the later debates.

Not the stained-glass vocabulary that gathered around these words after centuries of sermons, councils, hymns, arguments, translations, and very sincere people with very strong opinions.

Just the words.

Because English gives us a problem.

It often hands us one word:

God.

But the biblical writers were not working with one flat English term. They were using Hebrew, Aramaic, and later Greek words, each with its own history, range, and behaviour.

That matters.

A word is not a label slapped onto reality.

A word is a little basket.

It carries assumptions.

It carries memory.

It carries the world of the people who used it.

So before we ask what ancient people believed about God, we need to ask what vocabulary they actually had available.

Let’s start with a small handful.

First, there is El.

In Hebrew and related Northwest Semitic languages, El can mean “god,” “deity,” or “mighty one,” depending on context.

Notice that phrase.

Depending on context.

That little phrase is going to keep saving us from nonsense.

El can appear as a general divine term. It can also appear in names, titles, and poetic language. It is short, old, and sturdy, like a word that has been carried across a lot of desert.

Then there is Elohim.

This is the word many readers meet immediately in Genesis 1.

“In the beginning God created the heavens and the earth.”

In Hebrew, the word translated “God” there is Elohim.

And here we need to slow down.

Elohim looks plural in form.

That is an observation.

When it refers to the God of Israel, it often takes singular verbs.

That is also an observation.

Sometimes it refers to Israel’s God.

Sometimes it refers to other gods.

Sometimes it appears in passages where English translators have to make difficult decisions about whether the meaning is “God,” “gods,” “divine beings,” “spirits,” or even “judges.”

Again, we are not interpreting yet.

We are only noticing the behaviour of the word.

And already, Elohim is not behaving like a simple one-to-one equivalent of the modern English word God.

Interesting.

Then there is Yahweh.

This is different.

Yahweh is not a category word in the same way.

It is the personal name associated with Israel’s God.

In Hebrew, it is written with four consonants often represented as YHWH. The Tetragrammaton in Hebrew letters י (yod/Y) ה (he/H) ו (vav/W) ה (he/H)

You may have heard this called the Tetragrammaton, which is a grand word meaning “four letters.” Scholars do enjoy putting a cloak on a simple thing and sending it to university.

But the point matters.

When English Bibles print LORD in small capital letters, they are usually signalling that the Hebrew underneath is YHWH.

Not the title “lord.”

The name.

That means “the LORD God” is often not simply two generic religious words sitting side by side.

It may be representing something closer to:

Yahweh Elohim.

The name and the divine term together.

That is worth noticing.

Not because it solves everything.

It does not.

But because names and titles do different work.

If I say “the doctor,” I am using a title.

If I say “Katya” I am naming a particular person.

If I say “Bunny,” now we are either close friends or you have wandered into a very strange footnote.

Names locate.

Titles describe roles.

Categories group things together.

Those are not identical functions.

So far we have at least three kinds of language:

El, a short divine term.

Elohim, a broader and more complicated divine word.

Yahweh, a personal name.

Already the English word God is carrying a lot of cargo.

Then we meet Adon.

Adon means “lord,” “master,” or “owner.”

It is relational language.

It tells us something about authority, honour, or social position. It can be used in ordinary human settings. It can also be used in divine settings.

That matters because “Lord” in English can sound automatically religious to us.

But in the ancient world, lordship was a relationship.

A servant had a lord.

A household had a master.

A ruler could be called lord.

A deity could be called lord.

The word itself does not always tell us everything.

Context has to do the work.

Then comes Baal.

This one carries a lot of emotion for biblical readers, because “Baal” often appears as the name or title of a rival deity in Israel’s story.

But before we load the word with later reaction, let’s notice its basic meaning.

Baal can mean “lord,” “master,” “owner,” or even “husband.”

It can function as a common noun.

It can also function as a divine name or title.

So again, context matters.

This is not an argument that Baal worship was secretly fine.

No.

That would be leaping about like an overcaffeinated goat.

The observation is simpler: ancient divine vocabulary often grew from ordinary social words about authority, ownership, power, and relationship.

That is useful.

It tells us that ancient people did not always separate “religious language” from “political language” or “household language” as neatly as we do.

Lordship, kingship, land, inheritance, covenant, household, service, and worship all lived closer together in their imagination.

Now step forward into Greek.

By the time we reach the Greek-speaking world of the New Testament, two more words become especially important.

Theos And Kyrios.

Theos is the ordinary Greek word for “god” or “deity.”

When Greek translators rendered Hebrew Scriptures into Greek, Theos often carried words like El and Elohim into Greek.

So when English readers see “God” in the New Testament, we are usually seeing English standing on Greek, which may itself be standing in a long conversation with Hebrew.

That is not bad.

It is just layered.

Like archaeology.

Or lasagne.

Possibly both, if the excavation has gone terribly wrong.

Then there is Kyrios.

Kyrios means “lord,” “master,” or “owner.”

It overlaps with the kind of meaning we saw in Adon.

But it also carries another important burden.

In many Greek translations of the Hebrew Bible, Kyrios is used where the Hebrew text has YHWH.

So by the time we reach the New Testament, the word Lord is not simple either.

Sometimes it means master.

Sometimes it is a title of respect.

Sometimes it carries the weight of Israel’s divine name through the Greek translation tradition.

This is why we have to move slowly.

English makes things look tidy.

Hebrew and Greek keep leaving tools on the table.

Let’s put the observations in order.

El can function as a divine term.

Elohim has a wide range and does not always refer to only one kind of being.

Yahweh functions as a personal name.

Adon and Kyrios are lordship words.

Baal can be a common word for lord or owner, and also a divine title or name.

Theos is the ordinary Greek term for deity.

Those are observations.

Now here is a possible interpretation.

Maybe the English words God and Lord are doing more work than most readers realise.

Maybe when we read them too quickly, we lose distinctions the ancient writers may have expected their audience to hear.

Maybe some confusion begins because we are asking one English word to carry several ancient words at once.

That does not prove a doctrine.

It does not disprove one either.

It simply tells us to be careful.

If a text says Yahweh, that may not function exactly like a text saying Elohim.

If a text says Adon, that may not function exactly like a text saying El.

If a Greek text says Kyrios, we may need to ask whether we are hearing ordinary lordship language, divine-name tradition, or both.

And if English gives us “God,” we may need to ask which ancient word is standing underneath it.

This is where the investigation becomes interesting.

Because the next question is not merely, “What do these words mean in a dictionary?”

Dictionaries help.

But words do not live in dictionaries.

Words live in worlds.

So now we have to ask:

What kind of world used this vocabulary?

What did ancient people imagine reality looked like?

And what mental furniture was already in the room before the biblical writers ever picked up a pen?

The Ancient World

Now we have our first problem.

Words do not float.

They live somewhere.

They belong to a people, a landscape, a set of habits, fears, stories, assumptions, rituals, and ordinary ways of arranging reality.

So if we want to understand words like El, Elohim, Yahweh, Adon, Baal, Theos, and Kyrios, we cannot simply ask what they mean in a dictionary.

That helps.

But it is not enough.

We have to ask what kind of world used them.

Because the ancient world did not imagine reality the way most modern people do.

Most of us inherited a very tidy map.

There is the physical world.

Trees.

Rivers.

Bread.

Taxes.

Children asking questions at the precise moment you have finally sat down.

Then, somewhere else, there is the spiritual world.

Heaven.

Angels.

God.

Maybe demons, depending on your tradition and how much coffee your pastor had before preaching through Ephesians.

We often imagine these as separate layers.

The visible world here.

The invisible world elsewhere.

Occasionally one interrupts the other.

A miracle.

A vision.

A voice.

A burning bush.

But otherwise, we tend to keep them apart.

The ancient Near Eastern world did not arrange the room quite that way.

Let’s slow down and look at the furniture.

For many ancient people, the visible and unseen worlds were not sealed off from one another. They overlapped. They touched. They explained one another.

The sky was not merely weather.

The sea was not merely water.

A mountain was not merely geology wearing a hat.

A temple was not merely a religious building.

A king was not merely a political administrator with better jewellery.

The world was thick with agency.

That does not mean everyone believed exactly the same thing.

They did not.

Egypt was not Babylon.

Babylon was not Ugarit.

Ugarit was not Israel.

Israel was not Greece.

We should be careful here.

Ancient people were not one large blurry crowd wearing sandals and agreeing about the supernatural.

Different cultures had different stories, different gods, different rituals, different temples, different political structures, and different ways of naming divine power.

But there are family resemblances.

That is the observation.

Across much of the ancient Near East, people assumed reality included more than human beings, animals, land, weather, and kings.

There were divine beings.

There were heavenly courts.

There were councils.

There were messengers.

There were territorial loyalties.

There were powers associated with nations.

There were divine names, divine titles, divine roles, and divine hierarchies.

Again, that is not a conclusion about what the Bible teaches.

It is a description of the world in which the Bible was written.

And description matters.

If someone writes a letter from a battlefield, it helps to know there is a war.

If someone writes a poem from exile, it helps to know they are not on holiday.

If someone writes Scripture from within the ancient Near East, it helps to know what kinds of categories ancient Near Eastern people already had in their heads.

Otherwise we may mistake the argument because we misunderstood the room.

Here is one way to imagine it.

Every culture has mental furniture.

Chairs.

Tables.

Windows.

Storage boxes.

A very suspicious cupboard nobody opens because grandmother said not to.

These are the categories people use without thinking.

Modern people have mental furniture too.

We have categories like religion, politics, science, economics, psychology, private belief, public fact, myth, history, nature, supernatural.

Those categories feel obvious to us.

They are not obvious everywhere.

They are inherited arrangements.

Ancient Israel had different furniture.

So did its neighbours.

They thought in terms of covenant, land, kinship, inheritance, household, temple, kingship, priesthood, purity, blessing, curse, wisdom, nations, heavenly beings, divine council, and allegiance.

Some of those categories overlap with ours.

Some do not.

Some look familiar until you try to sit on them and discover they are not chairs.

This is why context matters.

When modern readers see the word god, we often jump immediately to a philosophical category.

Supreme being.

Ultimate reality.

Creator of everything.

Omnipotent.

Omniscient.

Eternal.

Outside time.

Those are serious ideas.

They are not foolish ideas.

But before we assume those are the first ideas an ancient reader brought to the word, we need to ask a smaller question.

What did the word do in their world?

Did it always describe ultimate reality?

Did it sometimes describe a member of the unseen realm?

Did it sometimes describe a spiritual power?

Did it sometimes describe a being worthy of fear, honour, worship, or allegiance?

Did it sometimes overlap with authority language?

Did it sometimes appear in ways that make modern English readers uncomfortable because our categories are narrower?

Maybe.

Or perhaps not in every case.

We are not ready to answer yet.

But we are ready to notice the question.

And that is progress.

One of the most useful discoveries for this conversation comes from ancient Ugarit, a city on the coast of what is now Syria.

Ugarit matters because its texts give us a close cousin to the world of biblical Hebrew.

Not identical.

Cousin.

Same family reunion, different potato salad. (I swear it wasn't me John 😂 I totally don't have you saved in my phone as that)

The Ugaritic texts show a Northwest Semitic world with divine names, divine councils, high gods, storm gods, messengers, kingship language, and a richly populated unseen realm.

That does not mean the Bible simply copied Ugarit.

Careful.

That is too easy.

It means the Bible was written in a cultural neighbourhood where certain kinds of divine vocabulary and imagery were already part of the shared air.

Writers do not have to explain the air their first readers are breathing.

They assume it.

That is why modern readers often miss things.

We are reading someone else’s mail after the furniture has been moved, the lamps rewired, the curtains replaced, and the old family jokes forgotten.

So when the Hebrew Bible speaks of a divine council, ancient readers may not have stopped and said, “How strange. What an unusual category.”

They may have understood the image immediately.

When it speaks of nations, inheritance, heavenly beings, kingship, messengers, and divine authority, those ideas were not floating in a vacuum.

They belonged to a world where earthly rule and heavenly rule mirrored one another more closely than many modern readers expect.

Again, let’s separate the pieces.

Observation:

The ancient Near Eastern world commonly imagined reality as populated by unseen beings and structured by divine authority.

Interpretation:

The biblical writers may be using some of the same broad categories, even when they reshape them around Israel’s own confession of Yahweh.

Conclusion:

We should be cautious before assuming our modern word God carries exactly the same range of meaning as ancient divine vocabulary.

That is not a radical conclusion.

It is a patient one.

And patience is often where the text begins to breathe.

Notice also what we are not saying.

We are not saying Israel believed exactly what its neighbours believed.

We are not saying all divine beings were viewed as equal.

We are not saying ancient Israelite religion was simple polytheism with a different flag.

We are not saying later Jewish or Christian theology is automatically wrong because it developed more precise language.

None of that has been proven.

We are not even trying to prove it here.

We are doing something more basic.

We are learning to hear the text before we organise it.

There is a difference between saying, “The Bible assumes an unseen realm populated by various beings,” and saying, “Therefore I know exactly how to classify every one of those beings.”

The first is an observation.

The second is a system.

Systems can be useful.

But if we build them too early, they become cages.

The ancient authors seem very comfortable speaking about heavenly beings, messengers, councils, spirits, gods, lords, and powers without stopping every three verses to give us a chart.

Which is inconsiderate of them, frankly.

A small laminated handout would have been appreciated.

But ancient writers rarely pause to explain what everyone in their own world already understood.

That leaves us with the work.

We have to reconstruct enough of the mental world to follow the language.

Not perfectly.

Not arrogantly.

But carefully.

This matters because when we reach words like Elohim, the ancient furniture becomes unavoidable.

If modern readers assume there are only two possible categories — God with a capital G, or fake gods with a lowercase g — some passages will feel awkward.

Very awkward.

They will not behave.

Psalm 82 will start causing trouble in the corner.

1 Samuel 28 will raise its hand.

Exodus will make translators choose.

Deuteronomy will begin whispering about nations, inheritance, and heavenly beings.

And suddenly we will realise that the Bible may be using divine language with more texture than our English categories prepared us for.

That does not mean the Bible is confused.

It may mean we are reading too flatly.

So now we are ready to follow one word in particular.

Not because it answers everything.

But because it keeps appearing in places where our assumptions have to slow down.

The word is Elohim.

And if we follow it carefully, without trying to force it into one English box too soon, we may begin to see why ancient divine vocabulary is stranger, richer, and more interesting than we were taught to notice.

Following Elohim

Now we follow the word.

Carefully.

No running ahead.

No grabbing one verse by the collar and forcing it to confess to a system it has not yet agreed to join.

Just observation.

The word is elohim.

And the first thing to notice is that English readers usually meet it in the most familiar place possible.

Genesis 1.

“In the beginning God created the heavens and the earth.”

That sentence feels simple to many of us because we already know how we are supposed to hear it.

God created.

One God.

Creator.

Beginning.

Heavens.

Earth.

Grand opening.

Excellent lighting.

But underneath the English word God is the Hebrew word elohim.

Here is our first observation.

Elohim is plural in form.

Here is our second observation.

In Genesis 1, it takes singular verbal action.

“He created,” not “they created.”

So whatever we do with that, we need to account for both pieces.

If we only say, “It is plural,” we have not read carefully enough.

If we only say, “It means the one God,” we have also not read carefully enough.

The word has a plural shape, but in this sentence it behaves with singular grammar.

Observation first.

Interpretation later.

Now move a little further.

Exodus 20.

This is the famous commandment passage.

“I am the LORD your God.”

Then:

“You shall have no other gods before me.”

Most readers hear that in English and understand the basic meaning well enough.

Yahweh claims Israel’s loyalty.

Israel is not to worship other gods.

But let’s look more closely at the vocabulary.

“The LORD” is representing the divine name, YHWH.

“Your God” is your elohim.

“Other gods” is also drawing from that same divine vocabulary.

So in the same commandment world, elohim language can refer to Yahweh, Israel’s God, and also to the forbidden objects of rival worship.

That is interesting.

Again, that does not settle what those “other gods” are.

Are they real spiritual beings?

Are they idols?

Are they nations’ deities?

Are they human-made images treated as divine?

Are several layers being held together?

Different passages may emphasize different aspects.

We do not need to answer all of that yet.

For now, the observation is enough:

Elohim language is not restricted to one English category.

It can refer to Yahweh.

It can also refer to “other gods” in contexts of prohibited worship.

That should make us slow down.

Now we come to Psalm 82.

Psalm 82 is one of those passages that sits quietly in the house until someone finally notices it, and then suddenly everyone is rearranging the furniture.

The opening line is startling:

“God has taken his place in the divine council; in the midst of the gods he holds judgment.”

In many English translations, we can see the tension immediately.

God.

Divine council.

Gods.

Judgment.

The Hebrew uses elohim language in a way that makes English translators choose how to signal the difference.

One elohim stands in authority.

Other elohim are being addressed or judged.

Now pause.

This is where we must be disciplined.

Observation:

The psalm uses divine vocabulary in a council scene.

Observation:

English translations often render one occurrence as “God” and another as “gods.”

Observation:

The scene involves hierarchy, speech, accusation, and judgment.

Interpretation:

Perhaps the word elohim is not functioning here as a personal name, but as a broader term for beings belonging to the divine or unseen realm.

Conclusion?

Not yet.

Not all the way.

We can say the passage is difficult to explain if elohim can only ever mean “the one true God” in the full modern sense.

But we should not pretend Psalm 82 answers every question we have about ancient Israelite theology.

It does not.

It gives us evidence.

Evidence is not the same thing as a finished map.

Still, it is a large piece of evidence.

It tells us that the biblical writers could use divine language in ways that include more than one figure in a heavenly courtroom or council scene.

That is not nothing.

Let’s keep walking.

1 Samuel 28 gives us another strange case.

This is the story of Saul and the medium at Endor.

Saul is desperate.

Samuel is dead.

The kingdom is slipping from his hands.

The silence of God has become unbearable.

So Saul does what frightened people often do.

He reaches for a forbidden door because the proper door will not open.

When the woman sees something rising, she says she sees an elohim coming up from the earth.

English translations vary here.

Some say “a god.”

Some say “a divine being.”

Some say “a spirit.”

That variation matters.

It shows us that translators recognize the difficulty.

They are not all looking at a simple word with one obvious English equivalent.

The scene is strange.

The vocabulary is strange.

Saul believes he is encountering Samuel.

The woman describes what she sees with elohim language.

What does that mean?

Let’s not rush.

Observation:

The word elohim appears in a necromancy scene involving a figure perceived as the dead Samuel.

Observation:

English translators do not all render it the same way.

Interpretation:

This may suggest that elohim can sometimes refer to a being from the unseen realm without meaning “God” in the way modern English readers usually mean it.

Conclusion:

If that interpretation is right, then elohim has a broader range than many readers assume.

Notice the “if.”

It is doing honest work.

Now let’s look at another group of passages: foreign gods.

The Hebrew Bible often speaks of the gods of Egypt, Canaan, Moab, Ammon, Philistia, Babylon, and other peoples.

Sometimes these gods are mocked.

Sometimes their idols are condemned as human-made objects.

Sometimes Israel is warned not to follow them.

Sometimes the language sounds like rivalry.

Sometimes it sounds like emptiness.

Sometimes it sounds like rebellion.

Sometimes it sounds like adultery, because covenant loyalty is being described like marital faithfulness.

That variety matters.

The Bible does not speak about foreign gods in only one register.

At times, idols are nothing but wood and stone.

At other times, worship of other gods is treated as traffic with real spiritual danger.

Those two observations do not have to cancel each other out.

A carved image can be powerless as an object and still be connected to a forbidden spiritual allegiance.

Maybe.

That is one possible way to hold the evidence.

But the main point for now is simpler.

The word elohim can appear in contexts involving Yahweh, rival gods, heavenly beings, and strange unseen figures.

That does not mean all those beings are equal.

That does not mean they are all worship-worthy.

That does not mean ancient Israel believed the same thing as every surrounding nation.

Please do not let the goat back into the kitchen.

We are only observing range.

The word has range.

Now there is another wrinkle.

Some passages may use elohim in legal contexts where English translations differ between “God” and “judges.”

For example, in parts of Exodus, disputes are brought before elohim.

Some English Bibles render this as “before God.”

Others render it as “before the judges.”

That is not because translators are being sneaky.

It is because the context is difficult.

Ancient legal authority could be understood as standing under divine authority. Human judges could act as representatives of divine judgment. The word may carry that tension in ways English has to resolve more sharply than Hebrew does.

Again, careful.

We should not simply announce, “Elohim means judges.”

Sometimes that may be the best translation in context.

But the fact that translators disagree is itself evidence that the word is doing complicated work.

And complicated does not mean confused.

It means we need better tools.

Let’s gather what we have seen.

In Genesis 1, elohim refers to the creator and takes singular verbal action.

In Exodus 20, elohim language appears for Yahweh as Israel’s God and also in the warning against other gods.

In Psalm 82, elohim language appears in a divine council or heavenly judgment scene.

In 1 Samuel 28, elohim language appears in a strange encounter with a being from the unseen realm.

In some legal texts, elohim may be rendered in ways that connect divine authority and human judgment.

That is the pattern.

Not the conclusion.

The pattern.

Now, what interpretations might explain that pattern?

One possibility is that elohim is sometimes being used as a category word.

Not a personal name.

Not always a title.

A category.

Perhaps it refers broadly to beings who belong to the unseen or divine realm.

Yahweh is elohim, but not all elohim are Yahweh.

That is a model some scholars have argued for in different ways.

It has explanatory power.

But let’s not make it carry more than it can carry.

It does not automatically answer how ancient Israelites understood monotheism.

It does not automatically tell us what every biblical writer in every century believed.

It does not automatically settle the relationship between idols, demons, angels, heavenly beings, foreign gods, and human judges.

It simply gives us a way to read the evidence without forcing elohim to mean exactly the same thing in every sentence.

And that may be the important step.

Because one of the easiest mistakes in reading ancient texts is assuming that a word must have one meaning everywhere.

Modern words do not behave that way.

Why should ancient words?

If I say “court,” I might mean a legal institution.

I might mean a royal court.

I might mean a basketball court.

I might mean courting someone, which is either romantic or alarming depending on the person and the century.

The word does not become meaningless because it has range.

Its meaning is discovered by usage.

By context.

By grammar.

By surrounding words.

By the world it inhabits.

So perhaps we should treat elohim the same way.

Not carelessly.

Not suspiciously.

Carefully.

When it refers to Yahweh, we read it in that context.

When it refers to other gods, we read it in that context.

When it appears in a council scene, we ask what kind of scene this is.

When it appears in a strange encounter with the dead, we admit the passage is strange instead of sanding off the edges.

When translators disagree, we pay attention.

Disagreement is not always a problem.

Sometimes it is a signpost saying, “There is something interesting here.”

And there is something interesting here.

The English word God often feels singular, settled, and obvious.

The Hebrew word elohim behaves with more texture.

That does not mean our English Bibles are bad.

It means translation is doing more interpretive work than many of us were taught to notice.

Which brings us to the next part of the investigation.

If Hebrew has one kind of flexibility, and English has to make choices, what happens when those choices become invisible?

What happens when the original text has no capital letters, but our English Bible has “God,” “god,” “LORD,” and “Lord”?

What happens when typography starts carrying theology?

Let’s keep following the evidence.

Translation

Now we need to talk about English.

Gently.

No throwing chairs at translators.

They have suffered enough.

Translation is difficult work. Anyone who has tried to move meaning from one language into another knows this. Words do not line up like obedient little soldiers.

They wander.

They overlap.

They carry smells from old rooms.

They remember things the new language has forgotten.

So when we talk about English Bibles, we need to be fair.

Translation is not deception.

Translation is decision-making.

And every decision reveals something.

It also hides something.

That is not a failure.

It is the nature of the work.

Let’s begin with something so obvious most of us never think about it.

Hebrew manuscripts do not work like modern English print.

They do not give us capital letters and lowercase letters the way English does.

So when you open an English Bible and see:

God

god

LORD

Lord

those distinctions are not sitting in the Hebrew text in exactly that form.

They are translation choices.

Interpretive signals.

Helpful signals, often.

But signals nonetheless.

That matters because English typography can make a passage feel cleaner than it is.

If English says “God,” we tend to know what to do.

If English says “god,” we also tend to know what to do.

Capital G means the real one.

Lowercase g means the other sort.

Problem solved.

Tea had.

Everyone home by six.

Except the Hebrew text may not be making the distinction that way.

It may be using the same word and allowing context to do the sorting.

That does not mean the distinction is wrong.

It means the distinction is interpreted.

There is a difference.

Take Psalm 82 again.

In English, many translations say something like:

“God has taken his place in the divine council; in the midst of the gods he holds judgment.”

That English sentence helps us read the hierarchy.

“God” with a capital G.

“gods” with a lowercase g.

But the Hebrew is doing something more compact and more uncomfortable for English readers.

It uses divine vocabulary in both places.

The translator then has to decide how to help the English reader hear the difference.

Again, that is not dishonest.

It may be exactly the right English choice.

But once we notice it, we realise we are not simply reading the ancient words untouched.

We are reading the ancient words through a set of English decisions.

That should make us humble.

Not suspicious.

Humble.

The same thing happens with “LORD.”

Many English Bibles use LORD in small capital letters to represent the divine name YHWH.

This is not the same as the ordinary word “Lord.”

That small typographic difference is doing a lot of work.

“LORD” usually points to the name.

“Lord” usually points to a title.

But if you are reading aloud, the difference can vanish.

Your ears hear “Lord” either way.

The page may distinguish them.

The voice often does not.

And if no one has ever explained the small capitals, a reader may never realise that English is quietly signalling two different things.

One is a name.

One is a title.

That is not a small distinction.

If I say, “the pilot,” I am telling you a role.

If I say, “Kat,” I am naming a person.

If I say, “the tiny menace in wool socks who owns too many maps,” I am apparently being described by friends and will be reviewing my social circle shortly.

Names, titles, and descriptions do different work.

The Bible uses all three.

English sometimes makes them look more similar than they are.

So when Genesis 2 says “the LORD God,” the English is often representing something like YHWH Elohim.

The name and the divine term together.

That is different from Genesis 1, where the text simply uses Elohim.

What does that difference mean?

Careful.

We are not solving that here.

We are noticing it.

Observation:

Genesis 1 uses Elohim.

Observation:

Genesis 2 introduces YHWH Elohim in many English translations as “the LORD God.”

Interpretation:

The text may be doing something meaningful by joining the personal name with the divine term.

Conclusion:

We should not flatten both phrases into the same vague idea of “God” without asking why the wording changed.

That is the method.

Slow.

Annoyingly slow, perhaps.

But useful.

Now consider Exodus 20.

“I am the LORD your God.”

In English, that sounds familiar enough that we may pass right over it.

But underneath the English, the sentence is doing something precise.

It identifies Yahweh by name.

Then it identifies Yahweh as Israel’s Elohim.

Then the command forbids Israel from having “other gods.”

So the passage is not merely making an abstract statement about deity.

It is naming a relationship.

Yahweh.

Your Elohim.

No other elohim before me.

That sounds different when we hear the vocabulary more clearly.

Not necessarily different in doctrine.

Different in texture.

Different in emphasis.

Different in the way an old wooden table feels different once you stop seeing it as “furniture” and notice the knife marks, the repairs, the hands that built it.

Translation can preserve meaning beautifully.

But it cannot preserve every texture at once.

That is why we compare.

That is why we slow down.

That is why we ask what word stands underneath the English.

Now let’s return to the legal passages for a moment.

In parts of Exodus, people bring disputes before elohim.

Some English translations say “before God.”

Others say “before the judges.”

That difference can feel alarming if we expect translation to be mechanical.

But translation is not mechanical.

It is contextual.

The translator has to ask:

Is the text saying the matter comes before God directly?

Is it saying it comes before human judges who represent divine justice?

Is the word carrying a sense of sacred legal authority that English cannot easily express in one phrase?

Those are real questions.

And they show us something important.

Sometimes English translation does not merely transfer ambiguity.

It resolves it.

The Hebrew may leave a little mist in the valley.

English often has to decide whether to call it fog, cloud, smoke, or weather being dramatic again.

That decision may be reasonable.

But once the decision is printed, the English reader may no longer see that there was mist at all.

This is why comparing translations can be useful.

Not because one is always faithful and the others are wicked little gremlins.

Usually not.

Different translations often make different choices because the original text allows more than one possible reading.

Sometimes one choice is stronger.

Sometimes the evidence is genuinely debated.

Sometimes the difference comes from translation philosophy.

Is the translator trying to stay close to the form of the original language?

Or trying to communicate the meaning naturally in English?

Both goals matter.

They simply produce different results.

A very literal translation may preserve the awkwardness of the original but confuse modern readers.

A smoother translation may communicate the basic point but hide the awkwardness.

And sometimes the awkwardness is where the interesting things live.

Psalm 82 is awkward.

1 Samuel 28 is awkward.

The “before God” or “before the judges” passages are awkward.

The difference between Elohim and YHWH Elohim is easy to miss.

The difference between “LORD” and “Lord” is easy to miss.

The difference between “God” and “gods” may be an English distinction placed over a Hebrew word with broader usage.

None of this means English Bibles are useless.

Please do not throw your Bible into the sea.

The sea has enough problems.

It means English Bibles are translations.

And translations are bridges.

A bridge is good.

A bridge gets you across the river.

But a bridge is not the river.

If we want to understand the landscape, sometimes we have to step off the bridge and look at the banks.

That is what we are doing here.

We are not accusing translators of hiding things.

We are noticing that translation always involves interpretation.

We are noticing that English capital letters can create distinctions Hebrew did not mark typographically.

We are noticing that “LORD” often represents a personal name.

We are noticing that “God” may represent Elohim, a word with a wider range than English readers usually assume.

We are noticing that sometimes different English translations disagree because the underlying word or context is genuinely difficult.

Those are observations.

The interpretation is beginning to emerge:

English often makes ancient divine vocabulary feel simpler, flatter, and more settled than it appears in Hebrew.

The conclusion is still modest:

If we want to read carefully, we need to ask what the English word is translating before we build too much on the English word alone.

That may sound small.

It is not.

Small hinges move heavy doors.

Once we see this, familiar passages begin to change shape.

Not because the Bible changed.

Because we started hearing more of what was already there.

So now we have the vocabulary.

We have the ancient world.

We have followed elohim through several difficult rooms.

We have noticed how translation can both help and hide.

Now we can begin, very carefully, to build a model.

Not a doctrine.

Not a final answer.

A model.

A way of holding the evidence without crushing it.

Building a Model

Now we are finally allowed to begin connecting the pieces.

Carefully.

Very carefully.

This is the moment where many of us want to sprint.

We have seen enough to feel the shape of something, and the mind naturally wants to finish the picture. It wants the clean sentence. The satisfying conclusion. The little bow tied neatly around the ancient world while everyone claps politely and nobody asks about Psalm 82.

But ancient texts are not vending machines.

You cannot insert three Hebrew words and receive one tidy doctrine with exact change.

So let’s not build a doctrine yet.

Let’s build a model.

A model is humbler.

A model says, “Here is a way of arranging the evidence that seems to explain what we have seen so far.”

It does not say, “All questions are now finished. Please exit through the gift shop.”

A good model has to do a few things.

It has to explain Genesis 1, where elohim refers to the creator and takes singular action.

It has to explain Exodus 20, where Yahweh identifies himself as Israel’s elohim, while warning Israel against other elohim.

It has to explain Psalm 82, where divine language appears inside a council and judgment scene.

It has to explain 1 Samuel 28, where elohim language appears in a strange encounter with a being from the unseen realm.

It has to explain why some legal passages can be translated “before God” or “before the judges.”

It has to explain why English translations sometimes make distinctions that Hebrew does not mark with capital letters.

And it has to do all of that without forcing every passage to mean exactly the same thing.

That is the trick.

Because words have range.

They are not little tin soldiers.

They do not stand in one place forever.

So here is a possible model.

Maybe elohim is not first functioning like a personal name.

Maybe it is functioning more like a category.

Not always.

Not mechanically.

But often enough that the pattern deserves attention.

In that model, elohim can refer to a being associated with the divine or unseen realm.

Yahweh is elohim.

But not all elohim are Yahweh.

Let that sentence sit for a moment.

It sounds strange in English because our English word God usually behaves differently.

In modern religious speech, “God” often means the supreme being, the creator, the one ultimate reality.

So if we say, “Yahweh is God, but not all gods are Yahweh,” it can sound as though we are making a theological claim before we have earned it.

But in Hebrew vocabulary, the sentence may be doing something more modest.

It may be distinguishing category from identity.

Think of the word human.

Abraham Lincoln was human.

But not all humans are Abraham Lincoln.

That sentence does not make Lincoln ordinary in every respect.

It simply places him inside a category while still allowing him to be a particular person.

Or think of the word king.

David was a king.

Pharaoh was a king.

Nebuchadnezzar was a king.

But saying all three belong to the category “king” does not mean they had the same authority, the same kingdom, the same character, or the same relationship to Israel.

Category is not equality.

That is important.

Very important.

If elohim can function as a category term, that does not mean every elohim is equal to Yahweh.

It does not mean every elohim is worthy of worship.

It does not mean every elohim is creator.

It does not mean every elohim is eternal, sovereign, covenant-making, or morally good.

Those are separate questions.

And this is where we must keep our hands steady.

Observation:

The word elohim appears in multiple contexts.

Interpretation:

It may have a broader range than the English word God.

Possible model:

Elohim may sometimes function as a category for beings belonging to the unseen or divine realm, while Yahweh functions as the personal name of Israel’s God.

Conclusion:

If that model is right, then some passages may be less confused than they first appear in English.

They may simply be using ancient categories we forgot to bring with us.

Now notice what this model does.

It lets Genesis 1 remain fully singular in action.

Elohim creates.

The grammar points to one actor.

We do not need to pretend the plural shape of the word is meaningless, but neither do we need to make Genesis 1 say “gods created.”

The word has a plural form, but the sentence uses singular action.

Both facts stay on the table.

Good.

It also helps us read Exodus 20 with more texture.

“I am Yahweh your elohim.”

That is not merely an abstract claim.

It is covenantal.

It names the one who brought Israel out of Egypt.

It identifies Yahweh as Israel’s God.

Then it demands exclusive allegiance.

“You shall have no other gods before me.”

So perhaps the first commandment is not trying to answer every later metaphysical question in one sentence.

Maybe it is doing something more direct.

It is saying:

This is the one who rescued you.

This is the one to whom you belong.

No rival allegiance.

No divided worship.

No other powers placed before his face.

That does not make the commandment smaller.

It may make it sharper.

Then there is Psalm 82.

If elohim can name more than one kind of being in the unseen realm, then Psalm 82 does not need to be treated as an embarrassment hiding under the rug.

It can be read as a divine council or heavenly judgment scene where Yahweh, or Israel’s God, stands in authority over other divine beings.

Again, that is a model.

Not every scholar phrases it the same way.

Some interpreters understand the “gods” in Psalm 82 as human rulers or judges.

Others understand them as heavenly beings.

Some readings may even see overlap between earthly injustice and heavenly accountability.

We should acknowledge that.

Scholarship is not one person in a cardigan handing down tablets from a library mountain.

There are debates.

There are reasons for those debates.

But whatever interpretation we choose, Psalm 82 asks us to think more carefully than our simple English categories usually allow.

That alone is useful.

Then 1 Samuel 28.

If elohim can refer to a being from the unseen realm, the woman’s strange description becomes less random.

She sees an elohim coming up.

English has to decide whether to say “god,” “divine being,” or “spirit.”

None of those words is perfect.

Each one carries different baggage.

But the model helps us understand why translators struggle.

The Hebrew word is wider than our neat English options.

Now, what about the legal passages?

This is where we should remain especially cautious.

If a dispute is brought before elohim, it may mean before God.

It may mean before judges.

It may reflect a world where human judgment and divine authority are more closely connected than our categories expect.

That does not mean we can flatten every case into one answer.

But it does mean the ancient world did not always separate courtroom, temple, kingship, and divine authority the way modern readers might.

The model helps us see why translation gets difficult.

It does not remove the difficulty.

That is all right.

A model does not need to eliminate mystery.

It needs to keep us from inventing unnecessary confusion.

Here is the simplest version so far:

Yahweh behaves like a personal name.

Elohim behaves more broadly.

English often translates both into familiar religious language.

Ancient Israel’s world assumed more than one kind of unseen being.

The biblical writers seem deeply concerned not merely with existence, but with allegiance.

Who is Israel’s God?

Who rescued them?

Who commands loyalty?

Who judges the nations?

Who stands above every rival power?

These may have been more immediate questions than the later philosophical question, “What is the abstract definition of deity?”

That does not make philosophy bad.

It simply means we should not force philosophy to speak first.

Let the ancient text speak in its own order.

Name.

Rescue.

Covenant.

Allegiance.

Worship.

Loyalty.

Judgment.

Then, later, metaphysics.

Perhaps.

Maybe.

Let’s keep following the evidence.

There is another reason this model matters.

It helps us avoid two opposite mistakes.

The first mistake is flattening everything into later theology too quickly.

In that mistake, every occurrence of elohim gets quietly absorbed into our modern idea of capital-G God, and the strange passages are explained away before they can speak.

The second mistake is flattening everything into simple polytheism too quickly.

In that mistake, every mention of “gods” becomes proof that Israel’s faith was just like everyone else’s, and the distinctive claims about Yahweh are ignored.

Both moves are too fast.

Both may miss the texture of the text.

The biblical writers seem to be doing something more interesting.

They do not always deny the existence of other powers in the language modern readers might expect.

But they consistently call Israel to exclusive loyalty to Yahweh.

They present Yahweh as creator.

As deliverer.

As covenant Lord.

As judge.

As incomparable.

As the one before whom every rival power is ultimately answerable.

That is not the same as saying, “There are no other beings in the unseen realm.”

It is closer to saying, “None of them is Yahweh.”

And that difference may matter enormously.

Again, I am not asking you to accept that as a finished doctrine.

I am asking you to notice how the model works.

It explains why elohim can be used in multiple ways.

It explains why Yahweh’s name matters.

It explains why English translation sometimes feels too tidy.

It explains why ancient commands about worship often sound less like abstract philosophy and more like covenant loyalty.

And it explains why some passages become clearer when we stop forcing ancient words into modern boxes too early.

That is the test of a model.

Does it explain more evidence with fewer forced moves?

Does it let the difficult passages remain visible?

Does it help us read more carefully?

Does it make us more honest with the text?

If yes, then it may be worth carrying forward.

Not worshiping.

Carrying.

Models are tools.

Use them while they help.

Revise them when the evidence demands it.

Do not marry a model unless you are prepared for a very strange household.

So here is where we are.

We began with a question: What did ancient people mean when they used words we translate as “God”?

We found that there was not one word.

We found a vocabulary.

We found a world where visible and unseen realities overlapped.

We followed elohim through several passages and watched it behave with range.

We noticed that English translation often has to make interpretive decisions.

And now we have a possible model:

Elohim may often name a category of divine or unseen beings, while Yahweh names Israel’s particular God, the one who claims exclusive covenant loyalty.

That model does not answer everything.

Good.

If a model answers everything too quickly, check the cupboards.

Something has probably been shoved inside.

But it does change how familiar passages sound.

Especially the passages we thought we already understood.

The Shema.

The First Commandment.

“I am Yahweh your God.”

These lines do not become less powerful when we hear them through ancient ears.

They may become more powerful.

Less abstract.

More immediate.

Less like a definition floating in the sky.

More like a covenant claim spoken across a trembling people who have just come out of empire.

So now we return to those familiar words.

Not to finish the investigation.

To hear them again.

Chunk 7/7 — Why This Changes Everything

Why This Changes Everything

Now we return to the familiar passages.

This is where the whole investigation starts to matter.

Not because we have solved everything.

We have not.

Not because we have discovered a secret code hidden under the English Bible like some theological treasure map drawn by an overexcited raccoon.

No.

It matters because familiar words begin to sound different when we hear them inside their older world.

Let’s begin with the First Commandment.

“I am the LORD your God.”

We have heard that sentence so many times that it can become almost invisible.

But now slow down.

“The LORD” is not merely a religious title floating in the air.

It is representing the divine name.

YHWH.

Yahweh.

And “your God” is connected to elohim.

So the sentence is not only saying, “A deity exists.”

It is more personal than that.

More covenantal.

More dangerous, if we are honest.

It says:

I am Yahweh.

Your elohim.

The one who brought you out.

The one who rescued you from the house of slavery.

The command begins with identity before instruction.

Not, “Here is an abstract definition of divinity.”

Not, “Let us begin with metaphysics.”

But, “I am Yahweh.”

Name first.

Rescue second.

Then allegiance.

That order matters.

At least, I suspect it does.

Because the very next movement is:

“You shall have no other gods before me.”

Most of us hear that as a command against worshiping false gods.

That is not an unreasonable reading.

But now the sentence has more texture.

If elohim can function more broadly than our English word God, then the command is not merely drawing a line between “real God” and “fake gods” in the simplest modern sense.

It is demanding exclusive loyalty.

No rival powers.

No competing divine allegiances.

No other claimants placed before Yahweh’s face.

That does not weaken the command.

It sharpens it.

It becomes less like a vocabulary quiz and more like a marriage vow.

Not merely, “Do you acknowledge that I exist?”

But, “To whom do you belong?”

That question is much harder to dodge.

Ancient people did not usually treat worship as private opinion.

Worship was allegiance.

It was loyalty.

It was service.

It was trust.

It was the organising centre of a life, a household, a people, a nation.

So when Yahweh says, “No other gods before me,” perhaps the question is not only, “How many divine beings are there?”

Maybe the more immediate question is:

Who has your loyalty?

Who rescued you?

Who names you?

Who commands you?

Who gets to define reality for this people?

That is not a small shift.

It moves the commandment from the lecture hall into the bloodstream.

Now consider the Shema.

“Hear, O Israel: The LORD our God, the LORD is one.”

Again, familiar words.

Beautiful words.

Words prayed, sung, recited, carried, whispered, taught to children, held close through exile and grief and ordinary mornings.

But listen again with the vocabulary in view.

“The LORD” is Yahweh.

“Our God” is our elohim.

So we might hear something like:

Hear, Israel.

Yahweh is our elohim.

Yahweh alone.

Or Yahweh is one.

Scholars discuss the best way to render that final phrase, and we should not pretend there is no debate.

But whatever exact English wording we choose, the sentence is doing something deeply covenantal.

It is gathering Israel’s attention around Yahweh.

Not an unnamed divine force.

Not a general category.

Yahweh.

The named God of Israel.

The one to be loved with heart, soul, and strength.

Notice what follows the Shema.

Love.

Teach.

Remember.

Bind these words.

Speak of them in the house.

Walk with them on the road.

Put them on the doorposts.

This is not abstract speculation.

It is a way of life.

The text moves from confession to embodied loyalty.

From who Yahweh is to how Israel lives.

That may tell us something about the ancient question.

Maybe the biblical writers were not first asking, “Can we define God in philosophical terms precise enough to satisfy a later debate?”

Maybe they were asking, “Who is the one true covenant Lord of Israel, and what does loyalty to him require?”

That does not make later theology irrelevant.

It simply reminds us that later theology should listen before it speaks.

Now we can revisit the phrase that has been sitting underneath this whole investigation:

“Yahweh your God.”

Or more closely:

Yahweh your elohim.

If elohim is a broader category, and Yahweh is the personal name, then the phrase does something beautifully precise.

It identifies which elohim Israel belongs to.

Not Baal.

Not the gods of Egypt.

Not the gods of the nations.

Not the powers associated with empire, fertility, storm, death, wealth, or military strength.

Yahweh.

The one who heard the cries of slaves.

The one who judged Pharaoh.

The one who brought Israel through the sea.

The one who gave covenant instruction at Sinai.

The one whose name is bound to rescue before it is bound to rule.

That changes the emotional temperature of the sentence.

“I am Yahweh your God” is not a cold assertion.

It is a claim of relationship.

It is history compressed into a name.

It is rescue becoming allegiance.

It is memory becoming command.

Now, does that answer every question about monotheism?

No.

Does it settle every scholarly debate about divine council language, ancient Israelite religion, or the development of Jewish and Christian theology?

Also no.

And that is all right.

We were not trying to settle everything.

We were trying to learn how to read more carefully.

So what have we actually observed?

We observed that English often uses “God” where Hebrew may use El or Elohim.

We observed that Yahweh functions as a personal name.

We observed that words like Adon, Baal, and Kyrios involve lordship, mastery, ownership, or authority language.

We observed that the ancient world imagined visible and unseen reality differently than most modern readers do.

We observed that elohim appears in more than one kind of context.

We observed that translation often has to make interpretive choices.

Then we considered a possible interpretation.

Perhaps elohim can function as a broader category than the English word God.

Perhaps Yahweh’s uniqueness is not established by denying every other unseen being exists, but by declaring that none of them is Yahweh.

None of them is creator in the way Yahweh is creator.

None of them is Israel’s rescuer.

None of them is covenant Lord.

None of them deserves Israel’s worship.

None of them stands above him.

That is a different kind of claim than many modern readers expect.

It is not smaller.

It may be larger.

Because it does not merely say, “There is one God” as an abstract proposition.

It says, “Yahweh is incomparable among every power anyone fears, serves, names, invokes, worships, or obeys.”

That is not a tame sentence.

That sentence has teeth.

It walks into Egypt.

It walks into Babylon.

It walks into Canaan.

It walks into empire.

It walks into every room where power claims the right to own human beings.

And it says:

No.

Not that one.

Yahweh.

Now perhaps we can see why vocabulary matters.

If we flatten the words too early, we may flatten the story.

If we assume “God” always meant exactly what we mean by “God,” we may miss the drama of Yahweh being named among rival claims of power.

If we assume ancient people were simply primitive philosophers with worse stationery, we will misunderstand them.

They were asking questions from inside a world alive with powers, loyalties, fears, temples, kings, nations, and names.

The biblical claim about Yahweh enters that world.

It does not float above it in clean modern abstraction.

It confronts it.

It rearranges it.

It judges it.

It calls a people out of it.

And then it teaches them how to live.

That is why this changes everything.

Not because it gives us a clever new doctrine.

But because it teaches us to read slowly enough for the ancient text to become strange again.

And strange is often where learning begins.

We should not be afraid of that strangeness.

The Bible was not written in our accent.

It does not owe us modern categories before we have done the work of listening.

If anything, the strangeness is a gift.

It forces us to stop using familiar words as shortcuts.

It asks us to notice.

It asks us to separate observation from interpretation.

It asks us to hold conclusions with enough humility that the next passage can still surprise us.

That may be one of the most important skills in reading any ancient text.

Not just Scripture.

Any old text.

Ask what the words meant in their world before demanding they answer questions from ours.

So where does this leave us?

At a doorway.

Not the end of the hallway.

We have gathered the vocabulary.

We have noticed the furniture.

We have followed elohim through several difficult rooms.

We have watched English translation make necessary choices.

And we have tested a possible model.

Now the next question rises naturally.

If Yahweh is Israel’s named elohim, and if the ancient world imagined nations, powers, councils, and rival allegiances, then what exactly is happening when the Bible speaks of the nations and their gods?

What does it mean for Yahweh to be Israel’s God and also judge of all the earth?

What happens when covenant loyalty meets cosmic geography?

That is where we go next.

But for now, perhaps this is enough.

Before we ask what we believe about God, we should ask what the ancient writers meant when they used the words.

Not because belief does not matter.

Because careful reading does.

And sometimes the first act of faithfulness to an ancient text is simply this:

Let it be ancient before asking it to be familiar.

---

The God Heist: Why the Word “God” May Not Be the Word We Thought It Was

If this were only a vocabulary problem, we might stop here.

It is not.

Because once we notice that Elohim does not behave exactly like our English word God, something strange happens.

Other passages begin tapping on the window.

Psalm 82 comes back.

Deuteronomy 32 starts looking suspicious.

The First Commandment feels less like a philosophical slogan and more like a loyalty claim.

And suddenly the question is no longer simply:

“Did ancient Israelites believe in one God?”

Maybe that is not the first question.

Maybe the better question is:

What did they mean by god in the first place?

Because if the word elohim can refer to Yahweh, other gods, divine beings, strange unseen figures, and possibly even sacred legal authority in certain contexts, then our English categories may be doing something very sneaky.

Not malicious.

Just sneaky.

Like a cat moving a spoon off the counter while maintaining eye contact.

English may have quietly gathered several ancient ideas under one familiar roof and told us:

“There. Nice and tidy.”

But ancient texts are rarely tidy.

They are layered.

They remember older worlds.

They carry arguments we have not yet learned to hear.

And sometimes the smallest word opens the largest door.

So next, we have to follow the trail further.

If Yahweh is Israel’s Elohim, and if the nations are also spoken of in relation to other gods, powers, and heavenly beings, then what exactly is happening in the biblical imagination?

Are we looking at theology?

Geography?

Covenant?

Cosmic politics?

All of the above?

That is where the God Heist begins.

Not because someone stole God.

But because somewhere between Hebrew, Greek, Latin, English, doctrine, tradition, and modern assumptions, we may have misplaced the ancient question.

Before we chase the answer, we will do what we have done from the beginning.

We will slow down.

We will read the words.

We will compare the translations.

We will let the ancient world speak before theology starts arranging the furniture.

Because if this investigation has taught me anything, it is this:

The smallest words sometimes carry the oldest worlds.

And that is exactly where we are headed next.

Dig Deeper

If you want to investigate this yourself, here are seven good places to begin. Do not use them to collect opinions like shiny rocks. Use them to collect evidence. Then ask what the evidence can actually carry.

1. STEP Bible
   Use this to look up Hebrew and Greek words, compare translations, and follow words through different passages.
   https://www.stepbible.org/

2. Sefaria Hebrew Bible
   Helpful for reading the Hebrew Bible alongside Jewish texts and translation traditions.
   https://www.sefaria.org/texts/Tanakh

3. Bible Odyssey — God
   A useful scholarly starting point for how biblical language about “God” works across Hebrew and Greek texts.
   https://www.bibleodyssey.org/dictionary/god/

4. Bible Odyssey — Yahweh
   Good background on the divine name, YHWH, and why English Bibles often render it as LORD.
   https://www.bibleodyssey.org/dictionary/yahweh/

5. Bible Odyssey — Divine Council
   A helpful doorway into the council language that becomes important in passages like Psalm 82.
   https://www.bibleodyssey.org/articles/divine-council/

6. My Jewish Learning — The Names of God
   A readable introduction to Jewish traditions around divine names, including why the divine name is treated with such care.
   https://www.myjewishlearning.com/article/the-names-of-god/

7. BibleGateway Translation Comparison
   Useful for comparing how different English Bibles render passages like Genesis 1, Exodus 20, Psalm 82, 1 Samuel 28, and Deuteronomy 32.
   https://www.biblegateway.com/

Remember...

The goal is not to find the translation that agrees with us fastest.

The goal is to become better readers.

And better readers learn to notice the hinge before pushing on the door.