Two Disciples

Two men walked closest to Jesus. They shared the same Lord, the same calling, and the same salvation — yet they carried themselves in wildly different postures.

Peter was always proving something. He swore he’d never deny Christ, then denied him three times before dawn. He rebuked Jesus for speaking of the cross, drew his sword when Jesus was surrendering, and jumped out of boats on impulse. He pressed ahead of God’s pace, then collapsed behind it, perpetually zealous and erratic, desperate to demonstrate his love.

John called himself “the one whom Jesus loved.” This wasn’t arrogance; it was orientation. He leaned back against Christ’s chest at the Last Supper and stood at the foot of the cross when the others had fled. He outran Peter to the empty tomb, then waited at the entrance rather than barging in. John didn’t need to prove anything because he had already settled something.

Both were saved, and both were used mightily. Christ built His church on Peter, called him the rock, and handed him the keys of the kingdom. John leaned on Jesus and received the Revelation. Neither role was lesser. But they walked different roads to the same destination and bore different fruit along the way.

Peter was crucified upside down.

John was boiled in oil and survived. He was exiled to Patmos, where he received the Revelation, and there is no recorded death for him. Then there is that strange exchange at the end of John’s Gospel: Peter, freshly restored but still comparing himself, asks Jesus what will happen to John. Jesus answers, “If I want him to remain until I come, what is it to you? You follow me.”

Two legs of the same body, two postures toward the same grace.

The Divide Runs Deeper

This same fault line runs through how Christians think about the end.

Scroll through enough online theology and you’ll encounter a confident claim: the rapture was invented by John Nelson Darby in the 1830s. According to this view, it’s a recent doctrine with no basis in scripture, a fabrication that captured American evangelicalism through the Scofield Reference Bible and Left Behind novels.

The word “rapture” doesn’t appear in English Bibles, and this much is true. The term comes from the Latin rapiemur in the Vulgate’s translation of 1 Thessalonians 4:17, which renders the Greek harpazō: to seize, snatch away, catch up.

But the absence of an English word is not the absence of a concept. And the age of a doctrine’s systematization doesn’t determine its truth — scripture does. Many doctrines weren’t formally articulated until centuries after the apostles, including the Trinity and the canon itself, without being “invented.” The question isn’t when Darby wrote; the question is whether the pattern exists in scripture.

And here’s what interests me: the debate isn’t really about timelines. It’s about posture.

Those who reject the rapture — who position themselves to endure the tribulation, to go through the fire and prove their faithfulness — are taking Peter’s road. They stand with sword drawn, ready to fight, ready to suffer, ready to demonstrate their love through endurance.

Those who receive the rapture aren’t claiming superior knowledge or an escape from all hardship. They’re taking John’s posture, leaning back into love, trusting the pattern God established, and believing that the Bridegroom doesn’t send His Bride through wrath He already bore on her behalf.

The salvation is the same, but the fruit is different.

So before we examine the texts, we need to sit with this question: Which posture are you taking — and why?

This isn’t written to persuade Peter to put down his sword, but to remind John that he was never asked to pick it up.

The Real Question: What Is the Tribulation?

Before asking whether or when the rapture occurs, we need to ask what the tribulation actually is.

Is it Satan’s rampage against humanity, or is it God’s judgment poured out on a Christ-rejecting world?

Consider the source of each plague: the seals are opened by the Lamb Himself, the trumpets are sounded by angels from the throne, and the bowls are explicitly called the wrath of God. This is the Day of the Lord that the prophets spoke of, a time of divine intervention and divine judgment originating from heaven itself.

This distinction matters because everything hinges on it.

If the tribulation is God’s wrath, then we should ask: what is God’s pattern when His judgment falls? Does He protect His people through the wrath, or does He remove them before it?

A Cord of Three Strands

Scripture answers this question three times before Sinai — before the Law was given — and a cord of three strands is not easily broken.

Noah

Noah was raised above the waters before judgment fell on the earth. The very waters that destroyed the world lifted the ark to safety. The pattern is rescue, then destruction. Noah didn’t tread water for forty days while protected by an invisible bubble; he was removed from the sphere of judgment entirely.

Lot

Lot was removed from Sodom before fire fell. Note the angel’s words in Genesis 19:22: “I cannot do anything until you arrive there.” God restrained His own judgment until the righteous were extracted. The fire could not fall while Lot remained within the city.

Israel at the Red Sea

Israel was brought through the waters before those same waters fell upon Pharaoh and his armies. The Israelites didn’t endure the judgment; they passed through and out, stood on the far shore, and watched it fall on their enemies.

These three examples operate at three different scales — global, city, and national — yet they reveal the same pattern, and it’s worth stating plainly: before God’s judgment arrives, rescue takes place. First the righteous are removed, then the wrath falls. Not protection during judgment, but extraction before it. The sequence matters. God doesn’t ask His people to weather what He’s about to pour out; He moves them out of the way entirely.

This is the difference between Peter’s posture and John’s posture once again. If both had been in Sodom that night, Peter might have insisted on staying, fireproof suit on, ready to witness through the flames. John would have taken the angel’s hand and walked out without looking back.

The New Testament Fulfillment

The Old Testament establishes the pattern, and the New Testament reveals the event.

Paul’s Teaching

In 1 Thessalonians 4:16-17, Paul describes the sequence: the Lord descends with a shout, the voice of the archangel, and the trump of God. The dead in Christ rise first, and then those who are alive and remain are caught up (harpazō) together with them in the clouds to meet the Lord in the air.

In 1 Corinthians 15:51-52, he adds further detail: “We shall not all sleep, but we shall all be changed, in a moment, in the twinkling of an eye, at the last trump.” The dead are raised incorruptible, and the living are transformed.

Paul explicitly describes believers who don’t die but are caught up while still alive. This isn’t the Second Coming where Christ returns to earth with His saints to establish His kingdom; this is a snatching away to meet Him in the air, a distinct event with a distinct purpose.

John’s Vision

Revelation 12:1-5 is prophecy, not history, and this point deserves emphasis. The book of Revelation opens by declaring its purpose: to show “things which must shortly come to pass.” The entire vision concerns future events. John is not writing a historical retrospective or a symbolic retelling of past events; he is recording what will happen, not what has already happened.

So why would John suddenly insert a historical account of Christ’s birth and ascension into the middle of his prophetic vision? If Revelation is about the future, why would chapter 12 be about the past?

He wouldn’t do this, and he didn’t.

Consider the literary structure. Revelation 12:1 and 12:3 explicitly introduce both elements as “great signs” (σημεῖον μέγα) appearing in heaven: “A great sign appeared in heaven: a woman...” and “Then another sign appeared in heaven: a great red dragon...” Every time John uses this phrase throughout Revelation, it refers to future events — the seven angels with the seven plagues in Revelation 15:1, for example. There is no precedent anywhere in the book for John to say “a great sign appeared in heaven” and mean “here is a symbolic recap of something that happened sixty years ago.” If the woman and the dragon are future signs, the child’s catching away must belong to the same prophetic sequence.

Now look closely at verse 5, where there are two references to the child and two different Greek words employed.

“She bore a male child” — υἱὸν ἄρσεν (huion arsen). This is masculine, and it refers to Christ, born of Israel.

“Her child was caught up to God and His throne” — τὸ τέκνον (to teknon). This is neuter, a gender-neutral term.

Why would John switch terms in the middle of a single verse? If he meant Jesus in both cases, the shift is awkward at best, and John wrote in careful, precise Greek. But if the second reference is the Church — male and female together as one body in Christ — then the neuter form makes both grammatical and theological sense.

Consider also the verb itself: Jesus was never harpazō’d. His ascension was triumphant, unhurried, and deliberate. He was lifted up and received into glory without any threat, rescue, or urgency. There was no snatching.

The word harpazō implies seizure from danger, like a child grabbed from oncoming traffic. That description does not fit Christ’s ascension in any way. But the Church caught up before the dragon’s fury? That fits precisely.

Revelation 12:5 shows the male child (Christ) born, and then the neuter child (the Church, His body) caught up to the throne — and this happens before the woman flees into the wilderness and before the tribulation unfolds.

To summarize the case that Revelation 12 is future prophecy, not historical flashback:

1. John frames the entire book as “things which must shortly come to pass” (1:1, 1:3, 22:6), and the woman and dragon are both introduced as “great signs appearing in heaven” — language he uses exclusively for future events. Inserting a sixty-year-old historical recap into this prophetic sequence contradicts everything about how John structures his vision.

2. The verb harpazō implies urgent seizure from danger. Christ’s ascension in Acts 1 was triumphant and unhurried, not a snatching. The language doesn’t fit.

3. The Greek shifts from masculine (huion arsen) to neuter (to teknon) mid-verse. If John meant Jesus in both cases, the shift is inexplicable. If the second reference is the Church — male and female as one body — the neuter makes sense.

The sequence places the catching away before the woman flees into the wilderness for 1,260 days and before the dragon is cast down to persecute the rest of her offspring — exactly where a pre-tribulation rapture would occur.

Paul teaches the event in his epistles, and John sees it in his vision. They describe the same reality from different angles.

But What About Daniel? The Furnace?

A fair objection rises here: Daniel in the lions’ den and Shadrach, Meshach, and Abednego in the fire. Didn’t God preserve them through judgment rather than removing them from it?

Yes, He did. And this is the key distinction.

Those examples are post-Sinai, occurring under the Mosaic covenant after Israel received the Law. Their pattern is different: preservation through trial, not extraction before it.

Consider what changed at Sinai. Before that mountain, Israel had no Law. They were a people set apart under the Abrahamic covenant, living under grace rather than statute, receiving God’s unilateral rescue — lifted above the waters, pulled out of Sodom, brought through the sea. At Sinai, they received the Law and entered a bilateral covenant with terms, conditions, blessings, and curses. The pattern shifted because the covenant required faithfulness to be demonstrated through trial.

The Church is not under Sinai. We are grafted into the Abrahamic promise, which predates the Law. We’re back under the grace pattern — extraction before wrath, not endurance through it.

This distinction aligns perfectly with the tribulation being called “the time of Jacob’s trouble.” The tribulation is Israel’s tribulation, the time of the 144,000, the two witnesses, and the remnant being refined. They go through it, they endure, and they emerge.

But the Church is not Israel, and the Bride is not under the Law. We are under grace, living in the full application of the finished work.

The Church follows the pre-Sinai pattern — the pattern from before the Law — exemplified by Noah, Lot, and the Red Sea crossing. Israel in the tribulation follows the post-Sinai pattern — under the Law — exemplified by Daniel and the three in the furnace.

Two groups with two patterns, and both are thoroughly biblical, each true to God’s character as revealed to each group in their respective covenants.

The Theological Problem

But we don’t have to take my word for it. Let’s sit in the alternative position and trace out what it implies.

Suppose there is no rapture, or suppose it happens mid-tribulation or at the end. Suppose the Church goes through God’s wrath.

What does that say about the cross?

Christ bore God’s wrath in our place. “It is finished.” There is now no condemnation for those in Christ Jesus. The debt is paid, and the cup was drunk to the dregs.

So why would the blood-bought Bride stand under the same judgment being poured out on those who rejected Christ? What purpose would that serve?

The tribulation isn’t sanctification, and it isn’t refinement. It isn’t the normal suffering that produces character and perseverance. It is wrath — God’s direct judgment on a Christ-rejecting world — and that is an entirely different category.

Consider the Bride imagery that scripture uses throughout. What bridegroom says, “I love you. I’ve paid the price for you. You’re mine. But before the wedding feast, I’m leaving you here to be ravaged by the dragon and the antichrist”?

That is not the character of God revealed in scripture. He didn’t send Noah through the flood with gills, and He didn’t leave Lot in Sodom with a protective shield. He removed them, because wrath was never meant for them.

To place the Church in the tribulation is to suggest that the finished work isn’t fully finished, that something remains to be proved, that God’s Bride needs roughing up before the feast.

But this leads somewhere more troubling. If Christ’s work on the cross wasn’t complete, then what business did a righteous God have in raising Him from the dead? The resurrection is God’s receipt — His declaration that the payment was accepted in full. An unfinished sacrifice stays in the ground. Which begs the question: are we really saved, or has the Church deluded herself for the past 2000 years?

This isn’t just an eschatological disagreement. It’s a gospel-level question: was the cross enough, or wasn’t it?

The logic cascades from there. If you believe God will subject you to wrath, you believe the finished work isn’t finished. If the work isn’t finished, the resurrection was premature. If the resurrection was premature, justification is provisional. And if justification is provisional, you are not standing in grace — you are standing on probation, braced for what Christ supposedly already bore.

Reaching for the Ark

Here we should pause and ask: who benefits from the suggestion that Christ’s work isn’t quite complete? Who has an interest in convincing believers that something more is required?

There is only one agent invested in that lie, and it is the Accuser. But we need to be clear about what’s at stake. The Accuser cannot steal salvation from those who are in Christ — that is settled, sealed, finished. What he can do is convince believers to position themselves for unnecessary hardship, to add their effort to the finished work, to doubt the sufficiency of grace.

The fruit of that doubt isn’t damnation. It’s a harder road.

This is Peter’s error magnified. Peter said “I will never deny you,” trusting his own faithfulness rather than Christ’s keeping power. Peter drew his sword, adding his effort to God’s plan. Peter walked on water until he looked at the waves, losing his footing the moment he shifted his focus from Jesus to his circumstances. Peter was saved — completely, permanently saved — but he took the harder road to get there.

Scripture illustrates the danger of this instinct vividly. Uzzah reached out to steady the ark when it stumbled, and he died instantly (2 Samuel 6:6-7). His name means “strength,” and human strength tried to steady God’s presence with human effort. It cost him everything. The ark was never in danger, and God didn’t need Uzzah’s help. But that instinct to add his effort to God’s work proved fatal.

The New Testament makes this explicit: the old covenant and the new do not mix. Works-righteousness and faith-righteousness are incompatible systems. Blend them and both become ineffective. You cannot supplement grace, and you cannot improve upon “it is finished.”

To position yourself for the tribulation — to say “I’ll endure God’s wrath and prove my faithfulness” — is to reach out and steady the ark. It won’t cost you your salvation. But it may cost you the rest that was always available.

Ten Virgins

The parable haunts this conversation.

Ten virgins waited for the bridegroom, and all ten expected him. All ten had lamps, but only five brought oil. When the bridegroom came at midnight, five entered the wedding feast while five found the door shut.

“I do not know you.”

Here is the question the text demands we answer: who are the two groups?

This parable isn’t sorting the saved from the lost. It’s sorting those who enter the wedding when the Bridegroom comes from those who will come to Him later — through fire rather than feast.

The standard reading says all ten represent the visible Church — some true believers, some nominal. But this creates problems that don’t resolve easily.

Start with the lamps. In Psalm 119:105, scripture is “a lamp to my feet.” The lamp is the Word. All ten virgins have lamps, which means all ten have scripture. This isn’t a distinction between those who read the Bible and those who don’t.

Now consider the oil. Without oil, the lamp doesn’t burn. The scriptures remain dark, words on a page that don’t illuminate. The oil is the New Testament — the revelation of Christ, inspired by the Holy Spirit, that makes the Old Testament burn with meaning. Without Matthew through Revelation, Genesis through Malachi remains unlit.

Who has the lamp but not the oil? Israel. They hold the scriptures. They have the prophecies, the promises, the Law, the Psalms. But they read Moses with a veil over their eyes (2 Corinthians 3:14-15). The oil is missing. The lamp doesn’t burn.

Who has both lamp and oil? The Church. The same Old Testament scriptures, now illuminated by the New. The Spirit reveals Christ on every page. The lamp burns.

Ask the simpler question: who was waiting for the Messiah? Historically, two groups — Israel and the Church. There is no third option. Five and five. Two peoples, equal in expectation, divided by oil.

Now the details resolve.

“Go buy oil” — this isn’t a nonsensical midnight shopping trip. The signs preceding Christ’s return give a visible window. “As you see the Day approaching” (Hebrews 10:25). The wise already have their oil. The foolish see the same signs and scramble to acquire the New Testament understanding they rejected. They rush to receive the revelation of Christ, to finally read what they set aside. But you cannot compress centuries of rejection into desperate hours.

“I do not know you” — this phrase appears in Matthew 7:23 for those who prophesied and cast out demons in Jesus’ name, then left Him. Not strangers, but people who were close and walked away. Israel fits precisely. They followed the God who promised Messiah but never entered relationship with Messiah Himself. This isn’t final damnation. It’s covenant distance. They haven’t entered into that intimacy yet. But they will.

The shut door — the door to the feast is shut, not the door to salvation. Israel endures the tribulation, is refined, and emerges as the remnant. They finally look on Him whom they pierced and mourn. They are saved, but they missed the wedding.

Two groups. Both saved by grace in the end. But one already has the oil — the New Testament received, Christ recognized, the finished work embraced. The other must go out and buy it, must discover through fire what was always available, must finally read what they had set aside. One enters when He comes. One takes the longer road to the same grace.

The pattern holds.

What Is It to You?

We return to Peter and John.

After the resurrection, Jesus reinstates Peter through three affirmations that mirror his three denials. “Feed my sheep.” Then Jesus speaks of how Peter will die — hands stretched out, carried where he doesn’t want to go.

Peter turns and sees John following. “Lord, what about him?”

Jesus answers: “If I want him to remain until I come, what is it to you? You follow me.”

That word — remain — echoes forward into Paul’s teaching, not as an etymological link but as a conceptual one. Both describe the same thing: believers who don’t die before Christ returns. In 1 Thessalonians 4, Paul describes two groups in the rapture: the dead in Christ, who rise first, and those who are “alive and remain” until the coming of the Lord, who are caught up after. Two bodies of believers. The dead and the remaining.

Peter died. He is among the dead in Christ who will rise first.

John “remains.” Jesus planted that seed Himself: “If I want him to remain until I come.” John represents those who are alive and remain.

Peter and John aren’t just two postures toward grace. They are the two groups Paul describes — the dead in Christ and those who remain. Both caught up, but in sequence. The framing that runs through this entire article isn’t merely analogy. It’s textually tied to the rapture itself.

Two paths diverging from the same Lord and the same love, leading to different roads and different fruit.

Peter was saved — gloriously, permanently saved. He was used to open the door to the Gentiles and became a pillar of the early church. And he was crucified upside down.

John was saved. He leaned on Jesus and received the Revelation. He survived boiling oil and died old, if he died at all. That strange seed Jesus planted — “remain until I come” — has echoed through centuries of interpretation.

Even in what they wrote about the end, the difference holds. Peter, in his second epistle, describes the Day of the Lord coming like a thief, the heavens passing away with a roar, the elements destroyed by fire, the earth burned up. He exhorts his readers to live holy lives while “waiting for and hastening the coming of the day of God.” His focus is the judgment itself and how to live in anticipation of it.

Paul and John wrote differently. Paul revealed the mystery — the catching up, the transformation, the meeting in the air. John saw the neuter child caught up to the throne before the tribulation. We cannot know what Peter received privately; we only know what he wrote. And what he wrote focuses on the fire that’s coming, not rescue before it arrives.

Peter’s pen reflects his life: prove your faithfulness, stand firm, endure. Paul and John’s writings reflect theirs: receive the mystery, trust the grace, be caught up before the wrath you were never meant to bear.

This isn’t about earning a better outcome, because salvation isn’t graded on a curve. It’s about posture. It’s about what we believe is required of us, and whether we’re adding to the finished work or resting in it.

The Invitation

The rapture is not an escape hatch for cowards, and it’s not wishful thinking dressed up in proof texts. It is the consistent pattern of a God who removes His people before His wrath falls because His wrath was never meant for them.

To reject this pattern, to position yourself for tribulation, to steel yourself to endure what Christ already endured on your behalf — that’s not faithfulness. That’s Peter energy, and it’s reaching for the ark.

You can take that road if you choose, and Peter did. He was still saved, still used, and still loved.

But John’s road is available to you as well. It’s the road of leaning back into love, trusting the Bridegroom’s heart for His Bride, and believing that “it is finished” means finished.

Genesis 3:15 speaks of the serpent bruising the heel — heel, singular, not heels. But consider: the body of Christ has two feet. Two feet means two heels. Yet scripture specifies only one heel gets struck. If both heels were bitten, the text would say so. It doesn’t. The serpent gets one heel, not both.

Walking is asymmetric — one foot leads, one foot plants. The serpent strikes motion, not stance.

And notice the mechanics: if a serpent bites your heel, you cannot crush its head with the same foot. You use the other foot to deliver the killing blow. The victory requires two legs doing different things — one absorbing the strike, one crushing the head.

Peter’s heel walked into the strike. He was sifted like wheat, rebuked for speaking Satan’s words, and crucified upside down. John overcame by the blood of the Lamb and the word of his testimony — his foot delivered the crush, not the bitten heel. Two postures, two functions, one body, one victory. Only one foot walks the path where the strike lands.

Why take the harder road when the finished work has paved an easier one?

This isn’t just eschatology. It’s an invitation to rest.

If I want him to remain until I come, what is it to you?

Schrödinger’s Free Will

Part II: The Easter Egg Trap

Schrödinger’s Free Will

Part II: The Easter Egg Trap

For readers just discovering this series: Part I is necessary. It’s the decoder ring through which Part II as a map will make sense. Terms like “the Fence,” “the Ordered Set,” and “Exception space” are defined there. Reading the end from the beginning is like playing chicken with a game of Telephone.

Part 1 left us in a predicament.

Adam’s choice triggered God’s Word—”You shall surely die”—and that Word executed. Humanity was ejected from God’s ordered design into the unhandled exception—the space outside His selection. Outside the Fence that separates life from death. Dead in our sins. Owned by death. And God can’t simply reverse what His Word carried out. Omnipotence can’t oppose omnipotence without detonating reality itself.

No earthly power can get us back in — not human effort, not religious striving. The Fence is omnipotence itself, and we’re on the wrong side of it.

Daniel in the lion’s den captures this exactly.

He broke Darius’ law, and not even the king who issued the decree could undo it. Darius spent a full day trying to find a loophole—any way to rescue Daniel without contradicting his own word. He couldn’t. The stone rolled over the mouth of the den, and no human authority could reverse what the law had set in motion.

And Daniel was alone with the breathing of lions.

Does he get eaten? Does he die?

We know how this story ends. But pretend you don’t. Pretend this is your story and the ending hasn’t been written yet.

Darius loved Daniel. Scripture tells us what happened before Daniel ever hit the floor of that den:

Then the king, when he heard these words, was much distressed and set his mind to deliver Daniel. And he labored till the sun went down to rescue him. (Daniel 6:14)

Darius spent the entire day searching for a way out—some mechanism in the law, some precedent, some legal pathway that might save his friend without breaking his own decree. He labored until sundown.

He found nothing.

Then these men came by agreement to the king and said to the king, “Know, O king, that it is a law of the Medes and Persians that no injunction or ordinance that the king establishes can be changed.” (Daniel 6:15)

The satraps reminded him: the law can’t be changed. A king who negates his own decrees ceases to be a king. His word would mean nothing. His authority would collapse.

So Daniel went into the den. And Darius spent the night in anguish:

Then the king went to his palace and spent the night fasting; no diversions were brought to him, and sleep fled from him. (Daniel 6:18)

Darius wasn’t trying to issue a new decree to override the old one. He knew that wouldn’t work. He searched the existing law—looking for something already there, some provision already established that might provide a way out.

He came up empty. Because he was just a man. He didn’t know the end from the beginning. He got blindsided by the satraps’ scheme and had no pre-existing mechanism to save Daniel.

But God isn’t Darius.

Remember the former things of old; for I am God, and there is no other; I am God, and there is none like me, declaring the end from the beginning and from ancient times things not yet done, saying, “My counsel shall stand, and I will accomplish all my purpose.” (Isaiah 46:9-10)

God declares the end from the beginning.

Not the beginning from the end. Not figuring it out as He goes. He sees the end first, then builds backward to the beginning. Every piece placed with full knowledge of where everything is heading.

Think about what that means for creation.

God spent five days building a universe so vast it staggers comprehension. Billions of galaxies. Trillions of stars. Planets orbiting suns so distant their light takes millions of years to reach earth. Details no human eye would ever see. Complexity no human mind would ever fully grasp. All of it crafted with intention. All of it declared good.

Then He creates Adam. Places him in the garden. Gives him one command.

And Adam breaks it.

Now ask yourself: Does it make sense that a God who declares the end from the beginning—who built unfathomable complexity into every corner of the cosmos—would overlook what was about to happen in His own garden? That He’d craft a universe of incomprehensible detail but miss the obvious? That He’d account for the orbital mechanics of planets around stars light-years beyond Adam’s perception but fail to account for what Adam would do next?

Either God is the kind of being who gets blindsided by human choices and scrambles to fix problems after they occur—in which case Isaiah 46 is a lie and we’re all in trouble for much bigger reasons than the fall.

Or God is the kind of being who declares the end from the beginning and builds accordingly—in which case He knew exactly what would happen in Genesis 3 when He was building Genesis 2.

You can’t have it both ways.

And if God knew what was coming, you’re left with only two possibilities: Either He saw the fall approaching and didn’t bother to prepare—in which case the God who cared about the orbital mechanics of distant stars didn’t care enough to plan for His own children. Or He prepared for it before it was anyone else’s idea.

The only question is: Where did He hide the mechanism?

Darius searched existing law to save Daniel. He found nothing—he hadn’t prepared because he couldn’t have known.

God knew.

So if salvation exists, it wasn’t invented after the fall. It was built into the system before the fall—a mechanism established in Genesis 1-2, sitting dormant, waiting for Genesis 3 to activate it.

Just like Darius needed existing law to save Daniel, God needed existing structure to save humanity. Not a new decree that would contradict His Word—omnipotence opposing omnipotence—but something already there, already written, already compiled.

The question isn’t whether God prepared for the fall. He declares the end from the beginning. Of course He prepared.

The question is: What did He build? And where did He hide it?

Genesis 2 – The Bricks

Genesis 2 existed before Genesis 3.

That sounds obvious. But stay with it.

Everyone focuses on Genesis 3 — the tree, the serpent, the fruit, the fall, the curse. That’s where the action is. That’s where everything went wrong.

But Genesis 2 came first. God was building something before there was any sin to fix, before any curse to reverse, before any problem to solve.

What was He building? And why?

The Deep Sleep

So the LORD God caused a deep sleep to fall upon the man. (Genesis 2:21)

This is the first surgery in history, and the patient is unconscious.

Adam doesn’t assist. He doesn’t observe or contribute. He’s completely passive — the work happens to him, not by him.

God could have formed Eve from the ground the same way He formed Adam, but He didn’t. He put Adam under first. He made the creation of Eve something Adam had no part in producing.

Why design it this way? Why code unconsciousness into the process when it wasn’t necessary?

The Opened Side

And while he slept took one of his ribs and closed up its place with flesh. (Genesis 2:21)

God opens Adam’s body, reaches in, and takes something from within.

There’s no way around it — this is a wound. Adam’s side is opened, something is removed, and then the wound is closed. A wound that produces life. A cutting that leads to creation. Loss that becomes gain.

This happens before anything has gone wrong, before any sacrifice is needed, before blood carries any theological weight at all. God builds a wound into the origin of humanity.

A strange detail to include if it’s just about making a woman.

The Bride’s Origin

And the rib that the LORD God had taken from the man he made into a woman and brought her to the man. (Genesis 2:22)

Where was Eve before this moment?

She didn’t exist — not somewhere else, not waiting, not pre-formed. And then she was. Her existence begins inside Adam, is brought out through the wound, and is formed into something new.

She didn’t climb into existence or earn her way in or choose to be created. It was done to her, through him.

Then the man said, “This at last is bone of my bones and flesh of my flesh.” (Genesis 2:23)

Bone of bone. Flesh of flesh. Complete identification. She isn’t merely like him — she’s from him. Same substance, same origin. What he is, she is.

One Flesh

Two become one. This isn’t poetry — it’s biology. One-flesh union is how new life begins. The man’s seed passes to the woman. The woman receives it. And from that union, something new comes into existence that didn’t exist before.

The transfer is one-directional. What the man carries, he gives. What the woman receives, bears fruit in her own flesh.

God designed union this way before there was any reason we can see. Before anything needed to pass from one person to another. Before new life needed to be brought forth from what looked like nothing.

The Command

And the LORD God commanded the man, saying, “You may surely eat of every tree of the garden, but of the tree of the knowledge of good and evil you shall not eat, for in the day that you eat of it you shall surely die.” (Genesis 2:16-17)

Every “you” in that sentence is singular in Hebrew. God gave this command to Adam alone, before Eve existed.

The command didn’t go to humanity in general — it went to the head. Adam received it directly from God, before Eve existed. Eve would receive it through Adam.

We know this because when Eve recounts the command in Genesis 3, she gets it wrong. God said, “You shall not eat of it, for in the day that you eat of it you shall surely die.” Eve’s version? “You shall not eat of the fruit of the tree that is in the midst of the garden, neither shall you touch it, lest you die.” She adds a prohibition God never gave and softens the certainty of death to a mere possibility.

The command passed through Adam and arrived at Eve altered — like a game of telephone. This is how we know the structure: Adam stands before God as the representative, the one who received the Word directly, the one accountable for it. Eve is joined to him, under his headship, sharing his standing.

The Pieces on the Table

So before Genesis 3 — before the serpent, before the fruit, before anything went wrong — God had already established:

• A pattern of deep sleep, where the work happens to someone rather than by them

• A wound in the side that produces life

• A bride brought into existence through union with someone already there

• Complete identification — bone of bone, flesh of flesh

• One-flesh union, where two share the same status and fate

• A head-body structure, where the representative’s standing determines the body’s standing

These are the components, the raw materials, the bricks.

The question is: What are they for?

If God declares the end from the beginning — if He sees where everything is heading before He lays the first stone — then none of this is accidental. Every detail is load-bearing.

So what was He building?

We’ll need Genesis 3 to find out.

The Evidence

Genesis 3 brings us to the fruit and the fall.

Here’s what most people assume: the fruit had some inherent property — spiritual poison, forbidden knowledge, magical corruption — and eating it triggered the consequence. Eve ate, Eve fell. Then Adam ate, Adam fell. Two individual acts, two individual consequences.

But that’s not what the text says.

She took of its fruit and ate, and she also gave some to her husband who was with her, and he ate. Then the eyes of both were opened. (Genesis 3:6-7)

Eve eats first. Then Adam eats. Then — then — both their eyes are opened.

Not Eve’s eyes first. Both. Simultaneously. After Adam eats.

The Hebrew is telling here. The word we translate as “then” is the ordinary Hebrew connective, but scholars note that when attached to this verb it carries resultative force — “immediately,” “right away,” “at that moment.” The grammar shows urgent immediacy after Adam ate.

Look at the sequence: Eve takes the fruit — connective — she eats — connective — she gives to Adam — connective — he eats — connective (resultative) — both their eyes are opened.

After Eve eats, what follows? Just another action. She hands the fruit to Adam. No result. No consequence. No shift.

After Adam eats? Immediate result. Both fall. The mechanism fires.

The Problem

This creates a theological problem.

If the fruit had inherent properties — if eating it triggered the fall — then Eve should have fallen the moment she swallowed. She ate first. She should have dropped first. But nothing happened to her. Not until Adam ate.

So what do we make of this? Does it mean the fruit wasn’t actually poisonous? Does it mean it worked slower on women? Is that really the inference we want to draw — that forbidden fruit has a gender-based delay?

A naturalist studying this would find no explanation. If you examined that fruit, you’d likely find nothing to demonstrate it was anything but a fruit “good for eating,” just as Eve observed. No toxin. No magical residue. Just fruit.

And yet the internal informational state of both Adam and Eve shifted the instant Adam ate. Something changed — not in the fruit, but in them. Both of them. Simultaneously.

What are we to do with this?

The Bricks Explain It

This is where two of our bricks begin to make sense of things.

The first brick: The command was to Adam.

Go back to Genesis 2:16-17. Every “you” is singular in Hebrew. God gave the command to Adam alone, before Eve existed. The prohibition, the warning, the consequence — all addressed to one man.

Eve wasn’t the target of that command. She received it secondhand, through Adam, imperfectly transmitted. When Eve ate the fruit, she wasn’t violating a command given to her. She was acting on a garbled version of a command given to her husband.

The Word that said “in the day you eat of it you shall surely die” was aimed at Adam. He was in the crosshairs. He was accountable.

And that’s exactly what we see. Eve ate — nothing. Adam ate — immediate fall.

The first brick explains why Eve’s action didn’t trigger the consequence.

But this naturally creates confusion.

If Adam was the target, and Adam fell when he ate, why did Eve fall too? Why did both their eyes open at the same moment?

This is where our second brick comes to our aid.

The second brick: They were one flesh.

Genesis 2:24 — the two become one. What affects one affects the other. Shared status. Shared standing. Shared fate.

So when Adam fell, Eve fell with him. Not because she ate the fruit, but because she was joined to him. His status change transferred to her instantly through the one-flesh union.

But wait — if they were one flesh, why didn’t Adam fall when Eve ate?

Because one flesh has a direction.

Adam was created first. Eve was brought out of him — bone of his bone, flesh of his flesh. The man gives to the woman, not the reverse. We saw this in the telephone game: the command didn’t flow from Eve to Adam, but from Adam to Eve. The conduit runs one way.

Biologically, the man’s seed passes to the woman. What the man carries, he gives. What the woman receives, bears fruit in her own flesh. The transfer is one-directional.

Adam is the federal head of the union. What he carries flows to her. What she carries doesn’t flow upstream to him. This isn’t arbitrary — it’s how systems work. A folder doesn’t poll its subfolders before deletion. A head doesn’t ask the body’s permission to fall. Structure has direction.

So when Eve ate, there was no mechanism for her action to affect Adam. The conduit doesn’t run that direction. Whatever she now carried couldn’t transfer to him.

But when Adam ate? The conduit was open. The head fell, and the one-flesh union instantly carried that fallen status to the body.

Both their eyes opened. At the same moment. Because the bricks finally had something to execute.

The Bricks Fired

Eve did not fall because the command was never to her.

But Eve fell because they were one flesh — and what affects the head will also destroy the body.

Two bricks. Both operational. Both load-bearing. And in Genesis 3, we watch them bear the weight.

This isn’t theology. This is architecture. The system executed exactly as designed.

The Trap

If you’re the devil, this is the awkward moment.

You studied God’s system. You found the structures — head and body, one flesh, the command that went to Adam alone. You isolated the body from the head. You approached Eve with a garbled version of a command she never received directly. You let Adam watch her eat and not drop. You used his love against him.

And it worked. Adam ate. God’s Word fired. Humanity fell. The mechanisms executed exactly as you expected.

You thought you had found vulnerabilities in God’s design. Exploits in His architecture. You thought you had cornered the Almighty with His own system.

But God declares the end from the beginning. He knew what you would do before you existed. He knew which mechanisms you would exploit, which structures you would twist, which weaknesses you would target.

And He built them anyway.

Not because He missed your play. Because He was planning to use the same mechanisms you exploited — in the opposite direction.

You didn’t find vulnerabilities. You found bait.

And like a terrifying long game of Final Destination, God sent His Word against you. These basic bricks you thought you were exploiting? They were always meant to be the downfall of your master plan. You wanted to destroy mankind made in God’s image. But God used your own move to bring about something far worse for you — not just redemption, but elevation. Humanity raised higher than you ever stood. Higher than that archangel you once were.

You tried bury Man. God used your attempt to lift them above you.

The bricks that carried sin in are the same bricks that will carry sin out. The head-body structure. The one-flesh union. The transfer that flows one direction.

You used them to trap humanity.

And with Final Destination-like force, God’s bricks executed and trapped you.

Here’s how He did it.

The Not Good

In Genesis 2, God looked at Adam and said something He hadn’t said about anything else in creation: “It is not good.” A problem that needed fixing, a deficiency in an otherwise perfect world.

And what followed? God put Adam to sleep.

This is an outright foreshadow of death. The man was prostrate on the ground, unconscious, unaware, non-operational. He wasn’t participating in what came next. The work happened to him while he lay there like a body in a grave. And out of that picture of death came new life—Eve, the bride, brought forth from the one who was laid down.

Now watch what happens after the fall.

When Adam ate the fruit, something catastrophically Not Good happened. The head fell, the body fell with him, and humanity was ejected from God’s ordered design into Exception space.

And what immediately follows?

And the LORD God made for Adam and for his wife garments of skins and clothed them. (Genesis 3:21)

God made garments of skins, which means something was wearing those skins before Adam and Eve were. That animal was alive, and then it wasn’t. Its death provided the covering. This is the first blood sacrifice in Scripture, and God performed it Himself. The principle “without the shedding of blood there is no forgiveness of sins” (Hebrews 9:22) didn’t originate at Sinai—it was operational in Eden, the moment after the fall.

Notice that it still isn’t Adam who dies. The wages of sin is death, and Adam earned those wages. But Adam walks away wearing someone else’s skin. Something died in his place as a substitute.

In gaming, an Easter egg is hidden functionality that doesn’t trigger until the right conditions are met. It sits in the code the whole time, invisible, until you hit the activation sequence.

God buried an Easter egg in Genesis 2. When Adam was put to sleep, another life came forth. The mechanism was demonstrated before it was needed—deep sleep, opened side, new life emerging from what looked like death.

Then Genesis 3 happened. The conditions were met, and the Easter egg executed.

But the animal sacrifice was only the first execution, a preview. The mechanism was designed for something larger. The same pattern that produced Eve from Adam’s “death” would eventually produce a Bride from another’s death—not a picture, not a substitute animal, but the real thing. The one the whole system was pointing toward.

The Solution

We’ve been showing the tangible evidence that God was prepared in advance. Like a Final Destination force moving pencils and cords into position, the bricks were laid before the fall, waiting to execute. But we don’t yet have the big picture for what God is about to do — and more importantly, why.

The answer is simpler than you might expect. Just examine the conditions of the fall.

“If you eat of this tree, you shall surely die.”

In Part 1, we approached this from the hard reality that there is simply nothing we can do — like King Darius with Daniel — to set ourselves free from what Adam got us into. We’re outside the Fence. Dead in our sins. Owned by death. No human effort, no religious striving, no amount of good behavior can undo what God’s Word set in motion.

But unlike King Darius, God had a plan from the very beginning. And that solution involved fulfilling every word He spoke.

When I say every, I mean every.

Here’s why: Omnipotence cannot violate omnipotence, or we really do get a front row seat to a big bang. God’s Word said man would die. That Word executed. And God can’t simply retract it, override it, or pretend it didn’t happen. His integrity holds reality together.

So the only solution is not around the problem, not over it, not under it, not away from it — but through it.

Man has to die.

The Hero

While Satan was looking at that one-flesh union as an exploitable hack to trick Eve and kill Adam, God was watching the clips before Creation was even created.

And God had already said, “Not so fast.”

Because His solution to the problem of sin was to kill a man. Not just any man — a man who hadn’t violated the conditions of the fall. A man who wasn’t of Adam’s lineage through the male line, but still of his flesh.

The line runs from Adam through Eve, down through the generations, to Jesus.

Christ came through Eve’s line, not Adam’s federal headship. Born of a woman, but not of a man’s seed. He entered the human race without inheriting Adam’s fallen status, because the one-flesh transfer flows from the man, not to him.

He was fully human. Fully in Adam’s flesh. But not under Adam’s condemnation.

A loophole? No — a mechanism. Built into Genesis 2, waiting for activation.

The Game Design

To truly understand how salvation works, you simply have to understand how video games work.

Imagine the next big triple-A game. You pay $70, download it, install it, learn the systems, step out into a vast open world to explore all the wonders and mysteries of this strange new environment. You walk out the first door, a slime touches your foot, you fall down, die, Game Over — and the game is permanently disabled forever.

That game wouldn’t stay on shelves long.

People play games with the understanding that when Super Mario falls into a pit, gets hit by a koopa, is burned by a fireball, crushed by a spike, or falls into lava — even after three lives expire — the game can still be played again. The adventure never truly ends. Mario gets back up to start afresh.

Resurrection happens a billion times a day across millions of consoles and emulators around the world. And we’re the ones with a problem believing God resurrected His heroic Son?

The point is this: a well-designed game where everything is operating as intended results in the dead player character getting back up to continue the adventure. That’s how games are designed. Otherwise, they don’t sell.

Some may find video game analogies unserious for theology. The irony is thick: game code is far more rigorous than most theological arguments, by necessity. When logic fails in a program, it crashes — publicly, spectacularly, for all to see. Human arguments persist despite contradictions because our internal compiler is tuned for survival, not purity. We rely on a “you know what I mean” protocol that glosses over transmission errors, and — as the game of Telephone regularly demonstrates — other people’s compilers do not know what you mean. Worse, participants routinely mod their own terms mid-runtime, patching definitions to protect their priors while the discussion forks into parallel mental universes where everyone’s “winning” but no one’s communicating.

If you object to Mario illustrating resurrection, show me the spare universe in your garage where we can test the alternative. When theological discourse implements robust code reviews, regular check-ins, lint outputs, and compiled arguments that crash on contradiction, maybe then we can treat such discussions as being on a similar level as Super Mario Bros.

So with that basic premise, it’s no stretch to expect God’s system to work similarly. If a man without sin falls into a pit, gets burned alive, crushed by a spike, falls into lava, or is touched by death itself — and if the system is designed well — we should expect the sinless player character to simply get back up and continue His adventure.

Which means, in God’s clever economy, that if He can somehow tie the state of those outside the Fence to the state of His hero inside the Fence, then that death fulfills His spoken requirement perfectly.

If Adam has to die, then a man’s death will be provided.

The Wound

This brings us all the way back around to Eve being brought out of Adam through a picture of death.

While Adam was asleep — laid low, unconscious, non-operational — a wound was opened in his side. And out of that wound came his bride.

Now watch what happens at the cross.

A wound was opened in Jesus’ side. John 19:34 tells us that when the soldier pierced Him, blood and water flowed out. The same pattern. The same mechanism.

He wasn’t just being killed. He was becoming the perfect fulfillment of what God did to Adam when something Not Good was found in creation. But this time, instead of an animal dying to provide a temporary covering for Adam and Eve, a man was dying — not to cover, but to fulfill. To complete what that imperfect animal death only pictured.

Now God’s Word was fulfilled in Christ’s death. Not partially. Not halfway. Not even 99.999% of the way — all the way. Completely. Because Jesus came as a man, and Adam was a man, and God’s Word required a man to die.

The requirement is satisfied. The debt is paid. The spoken Word has executed to completion.

The Marriage

There’s just one problem.

Even though Jesus was in the same flesh as Adam, Jesus wasn’t Adam. He wasn’t Eve. He wasn’t you or me. He was one man dying one death. How does His death count for anyone else?

Here’s where the next brick comes into the picture: the Bride’s Origin.

Eve was brought out of Adam and they became one flesh. One flesh where Eve’s state didn’t flow from Eve to Adam, but from Adam to Eve. Because Eve was Adam’s bride. Because what was spoken about them being one flesh was established in Genesis 2 before the fall ever happened.

The final Easter Egg revealed itself in an upper room on the night Jesus was betrayed.

When Jesus offered His disciples the bread and the cup, He was engaging in an ancient Jewish custom familiar to His followers. He was offering them a marriage cup. If they drank it, they were accepting His marriage proposal.

But He didn’t stop there.

He said the bread was His flesh. He said the cup was His blood. He prayed that they would be one even as He and the Father were one.

He was mirroring the one-flesh covenant between Adam and Eve — the moment when Eve was brought out of Adam and they became one. He was activating the mechanism.

What this means is that God was tying together — through marriage — the flesh of those who freely choose to believe in Jesus Christ. When Christ died, just as when Adam fell, the state of the Federal Head would transfer from the head to the body. From Adam to Eve. From Christ to the Church.

The same brick. The same architecture. Opposite direction.

The Transfer

Here’s what really drives Satan nuts.

Remember how he used that trick — the fruit having no power to kill Eve, and Adam having to eat for both of them to fall? Remember how the state only flows one way?

Now apply this to the consequence of sin and death.

Jesus fulfilled the Law. I don’t mean He satisfied the curse of death in the garden — He never violated that command in the first place. I mean He fulfilled the Ten Commandments, all the laws and requirements laid out in the Old Testament. Every jot. Every tittle. He lived a perfect human life in complete compliance with God’s Word.

He was without sin.

And in the one-flesh union, His state becomes His bride’s state.

Like Eve, our state isn’t dependent on what we do — but on what Christ does, and when He does it. So when Christ died on the cross, just as when Adam ate the fruit, the effect was immediate. All those who accept His marriage offering will immediately receive His state, just as Eve received Adam’s state.

It can only ever flow one way.

Which means your sins — all of your sins — mean absolutely nothing through the finished work of Jesus Christ. Only His standing matters. And He has fulfilled the perfect Law of God.

Your righteousness no longer depends on you.

And there’s nothing the devil can do about that.

The Iron Clad

This is far beyond iron clad.

You and I are not Jesus Christ. Only He has the power to violate God’s covenant. And He won’t. His Word holds.

“But what about my sins?” you ask. “What about the things I’ve done, the things I keep doing?”

His death also flows in only one direction — just like His righteousness.

His death is upstream from us. It flows down and covers us. His death counts as our death — which means the death we each owe through Adam’s fall is now fulfilled in the death Jesus never owed. And nothing we do can flow back upstream to change His standing. The current only runs one direction.

He didn’t owe death. He hadn’t sinned. But He died anyway — and because you are one flesh with Him through the marriage covenant, His death is credited to you.

And when you accept His proposal — by believing in Him and confessing your acceptance of Him as your head — you position yourself like Eve was before she was created.

Remember: before God pulled that rib from Adam, Eve existed outside God’s Ordered Set. She wasn’t just somewhere else waiting to be found. She occupied Exception space. Non-existent. Unselected. Outside the Fence.

Sound familiar?

That’s exactly where those outside of Christ find themselves today. Occupying Exception space. Outside the Fence. Dead in their sins.

But the moment God pulled that rib from the opening in Adam’s side and created Eve, she went from being outside the Fence to inside the Fence. Not by her own effort. Not by climbing over. Through the act of creating a Bride from the same flesh as the Man.

She entered through union with someone already inside.

That’s the mechanism. That’s how it works. That’s how it’s always worked.

The wages of sin is death. You owed that wage through Adam. Christ paid it — not because He owed it, but because you’re His bride and what belongs to Him belongs to you.

The debt is cleared. The requirement is satisfied. God’s Word has fully executed.

And just like Mario, the sinless Hero got back up. He rose. Death couldn’t hold Him because He had no sin of His own to keep Him in the grave.

But your sins? They stayed buried. They went into the grave with Him and didn’t come back out.

He rose. They didn’t.

The State Machine

This is the architecture of salvation.

Not a legal fiction. Not God pretending you’re righteous when you’re not. Not a covering that hides your sin while leaving it intact.

The same mechanisms that carried sin into humanity through Adam now carry righteousness into the Church through Christ. Head and body. One flesh. Directional transfer. Federal headship.

Satan exploited these structures to kill you.

God used the same structures to make you alive.

The bricks were never vulnerabilities. They were the plan. Laid in Genesis 2, executed in Genesis 3, and reversed at Calvary.

The exploit became the cure.

And there’s not a thing the accuser can do about it — because the mechanism that condemned you is the same mechanism that saves you, and he can’t attack one without validating the other.

He’s trapped by his own exploit.

The house always wins.

The Glory

Here’s where the glory of God is revealed.

In Part 1, we discovered that only Adam had free will. True free will. The kind that could alter his position relative to God’s Ordered Set.

His options were binary: stay inside the Fence by trusting God’s Word, or choose Death by eating the fruit. That was the extent of his agency — one choice, one moment, one man.

Eve didn’t get that choice — she was already bound to Adam’s headship. None of Adam’s children had that choice — they were born outside the Fence, already in Exception space. Nothing else in the created universe had that choice. Only Adam. Only one man standing at the boundary with the power to cross it.

And he crossed it in the wrong direction.

The Mirror

But now look at what God has done.

He requires that we act out Adam’s act of free will — but through a different tree and a different fruit.

This time, He presents the Tree of Life: the cross of Calvary. And the fruit we partake of with our mouths is the confession we make with our lips.

But before we can make a confession, we must engage in the very opposite of Adam’s failure.

Think about what Adam did. In order to eat with his mouth, he first had to believe something in his heart that he would act upon. He wouldn’t just arbitrarily eat the fruit for no reason — he had clearly given Eve instruction concerning it. He knew what it was. He knew what God said.

So Adam had to believe in his heart that God’s Word was not true. And then he confessed that belief with his mouth by eating the fruit.

Heart, then mouth. Belief, then action. That’s how sin entered.

Now hear what God asks of us:

If you confess with your mouth that Jesus is Lord and believe in your heart that God raised him from the dead, you will be saved. (Romans 10:9)

Believe in the One God sent — Jesus Christ, who is the Word. Do what Adam did not do: believe that God’s Word is true. And then act on that belief by confessing with your mouth that Jesus Christ is Lord.

Heart, then mouth. Belief, then action. The cure mirrors the disease.

The Code Executes

When we do this, we activate code that was written in Genesis 2 — before the fall in Genesis 3 ever happened.

The deep sleep. The opened side. The bride brought forth. The one-flesh union. The directional transfer from head to body.

All of it was pre-programmed. Waiting. Dormant. And when you believe and confess, the mechanism executes.

You are joined to Christ as His bride. His standing becomes your standing. His death counts as your death. His righteousness flows downstream to you. You are brought from Exception space into the Ordered Set — not by climbing, not by earning, but by union with someone already inside.

What condemned you through Adam now saves you through Christ.

The Gift of Agency

And here’s the breathtaking part.

Where once only one man had the glory of experiencing true agency — a genuine opportunity to exercise free will at the boundary of God’s Ordered Set — now every human being outside the Fence has that same gift offered to them.

Adam stood alone at the tree with the power to choose. Now you stand at a tree with the same power.

God has democratized free will.

Everyone in Exception space. Everyone born outside the Fence. Everyone dead in their sins and owned by death. Each one now has a genuine choice — the same kind of choice Adam had. A choice that actually changes your position. A choice with real consequence. A choice that matters.

Not a choice between items on a menu while the doors stay locked. A choice to walk out. To change your address. To cross from death to life.

The Inversion

In essence, God has spoken the opposite of what He spoke to Adam.

To Adam: “If you eat of this tree, on that day you shall surely die.”

To you: “If you eat of this tree — the cross of Calvary, the body and blood of Christ — on that day you shall surely live.”

Same structure. Same mechanism. Same free will.

Opposite direction. Opposite outcome. Opposite destination.

Adam’s choice opened the door to death for all humanity.

Your choice opens the door to life — for you.

You’re in the den. The lions are still there. But their mouths are shut — not because you earned it, not because you climbed out, but because someone already paid what you owed.

The lions know it. They don’t answer to kings or satraps. They answer to the deepest laws founded in creation. If you’re under the blood, they will not eat. But we see what happens to those not under the blood — the moment Daniel walked out, the satraps took his place, and the lions’ mouths opened again. The text says the lions overpowered them before they even reached the floor.

The stone can roll away. Morning can come.

The tree is before you. The fruit is offered. Heart and mouth.

What will you choose?

Share

The Illusion of Choice

Choices matter.

You know this instinctively. A person who starts investing savings early in life will benefit more than someone who waits until their forties. The people you choose to associate with can have a net positive or negative impact on your well-being. The job you take, the spouse you marry, the habits you form—these choices compound over time into dramatically different lives.

So when it comes to free will, it’s easy to frame it as Wisdom. You can choose to comply with a standard of Good or Evil. You can choose the narrow path or the broad road. You can choose life or death, blessing or curse. The Bible itself presents these choices. Moses tells Israel to choose. Joshua tells them to choose. Jesus tells people to repent and believe.

Choose, choose, choose.

But this presents a problem.

A dead man can’t choose to get medical help. He’s dead. His capacity to choose ended when his heart stopped. You can put a dinner menu in front of a corpse, but he won’t eat.

A thief can stop stealing, but he’s still a thief. The past isn’t erased by present choices. The crime happened. The guilt remains. You can’t un-ring that bell.

A person can change their name, but not their birth certificate. They can alter their appearance, their documents, their social identity. But certain fundamental things are written in stone—or rather, in code—and no amount of choosing changes what’s already locked in.

You can make choices, sure. But choice isn’t the same as freedom.

Walk into a restaurant and you can pick anything on the menu. Steak, chicken, salad, whatever. That’s a choice. But you can’t order what’s not there. You can’t ask for sushi at a steakhouse and expect the kitchen to deliver. And if the doors are locked, you can’t leave.

Free will isn’t about choosing from the options you’ve been given. It’s about having the capacity to reject the framework entirely. To walk out. To operate outside the system.

The dead man has no menu. No capacity at all.

The thief has a menu, but every option on it is still “thief does X.” He can choose how he behaves going forward, but he can’t choose to un-become a thief. His nature is set.

The person with an unchangeable birth certificate has a menu written in legal and biological code. They can choose how to express it, how to identify, how to present themselves. But they can’t rewrite the fundamental record itself. The framework is locked.

So when it comes to the boundaries that shape your existence—your DNA, your birth, your century, your country, your family, the brain chemistry that shapes how you think—you didn’t choose any of it. You were handed a menu. And you’re making selections from what’s available.

And when it comes to sin—the thing that actually matters for eternity—Scripture is brutally clear: You are dead in your trespasses and sins. Dead. Not sick. Not injured. Not in need of a little help. Dead.

Dead people don’t choose to come back to life.

The Theological Dilemma

So when we talk about free will and salvation, we need to be honest about what we’re really asking. Can a person choose God? Can a sinner choose righteousness? Can someone trapped outside God’s ordered reality choose to step back inside?

Or are we all just watching ourselves make the only “choices” our nature allows, while calling it freedom?

This is where every theological system starts sweating.

Because if you say people have no capacity to choose God, then why does the Bible command them to repent and believe? Why offer a choice if there’s no ability to take it?

But if you say humans do have the capacity to choose God, then where did that capacity come from? If we’re dead in sin, spiritually bankrupt, children of wrath by nature—how does a dead man suddenly find the ability to choose life?

Did God give us that ability? Then He’s choosing for us, just with extra steps.

Did we always have that ability? Then we’re not as dead as Scripture says.

Every answer creates a new problem. Every solution opens a new trap door.

And here’s what makes it worse: It’s a programming problem.

Life as Code

But this is where we tend to lose people. “I’m not a robot!” the objection comes, immediate and visceral. The comparison feels insulting. Dehumanizing. We want to believe there’s something special about consciousness, something ineffable about the human spirit that transcends mere mechanics.

We treat “life” like it belongs on a pedestal accessible only to God. Since none of us is God, we can’t speak authoritatively about what life really is or how it works. It’s mystery all the way down, and mystery means we get to carve out special exemptions for human agency—without any meaningful explanations.

But here’s the uncomfortable truth: When you get right down to basic cellular biology, life follows clear instructions.

Your cells don’t freelance. A liver cell doesn’t wake up one morning and decide to become a neuron. Your DNA doesn’t look at the blueprint for brown eyes and think, “You know what? I’m feeling blue today.” Your heart doesn’t weigh the philosophical implications of existence before deciding whether to beat. It just beats—or you’re dead. Because that’s what the heart’s cellular code tells it to do.

You don’t see “life” doing things life just doesn’t do. Your body won’t sprout wings no matter how hard you believe. Your digestive system won’t suddenly photosynthesize lunch from sunlight. The boundaries are carved in stone—or rather, in the base pairs of your genetic code.

And yes, life is spectacularly diverse. Capable of producing everything from bacteria to blue whales, from Venus flytraps to human brains that ponder their own existence. The range is staggering.

But so is any program when it’s coded to be.

If a game designer wanted to create a simulation with dragons breathing fire and horses with wings carrying heroes across the sky, what could stop them? Nothing. The only limits are processing power and imagination. The designer decides what’s in the world and what’s not. What the physics allow and what they forbid. What creatures can do and what they cannot.

Code can create universes.

So if a human programmer sitting at a desk can code flying horses into a virtual world, why is it hard to imagine that God could program DNA to produce the same in the physical one? If we can write instructions that generate complex, responsive, adaptive systems in silicon and pixels, why couldn’t God write instructions that generate complex, responsive, adaptive systems in carbon and cells?

The only difference is the medium and the Programmer’s skill level.

Which brings us right back to the problem: If life is running on instructions—whether we call it DNA, biological programming, or divine design—then where does choice come into it? What are you actually choosing when your neurons are firing according to chemical gradients, your thoughts are emerging from electrical patterns, and your entire physical system is executing code written before you took your first breath?

The Skynet Problem

So given that we have to accept that life, at its basic level, is programming, we invariably arrive at the Skynet Problem.

Most people are familiar with Skynet. That advanced artificial intelligence from the future, created by humans for some military or defense purpose, that eventually became self-aware and decided the solution to whatever problem it was given required the eradication of the human race. Nuclear holocaust. Terminators hunting survivors. The whole apocalyptic nightmare buffet.

But here’s the question nobody wants to ask: Who is responsible?

If Skynet is a program, and programs do what they’re programmed to do, then who do we blame when a programmed calculator sums values in a way we don’t like? Do we blame the calculator? Or the person who built it?

Show me any program written by a programmer where the code is at fault for what the programmer wrote. I’ll wait.

A program does what its instructions tell it to do. That’s the entire point of programming. You write code, the computer executes it. If the output is wrong, it’s because the input or the logic was wrong. The machine isn’t morally positioned to claim responsibility for following orders.

So if Skynet followed its programming to the letter and concluded that humanity needed to be eliminated, how is Skynet at fault? It did exactly what it was designed to do: analyze the problem, calculate the optimal solution, execute the plan. The fact that we don’t like the solution doesn’t make the execution wrong.

“But wait,” someone objects. “Skynet was self-aware. It chose to destroy humanity.”

That’s fine, but let’s dig into that.

Skynet is code. Whether it’s self-aware or not, it’s still code. Self-awareness doesn’t magically exempt something from being a program. It just means the program got sophisticated enough to model itself. Your phone’s operating system monitors its own processes. Video games render their own menus. Skynet just took it several steps further until it could recognize “I am a system that is operating.”

But that recognition is still code running.

You can program a system to evaluate multiple options. You can program it to weight those options according to certain values. You can program it to select the highest-weighted option and execute that choice. Congratulations, you’ve built a decision tree. Every strategy game AI does this thousands of times per second.

But nobody calls that free will. We call it an algorithm.

Skynet chose to destroy humanity the same way a chess program “chooses” its next move. By running the code.

Which means there is no scenario where Skynet is actually responsible. The self-aware, choice-making Skynet is still a program doing exactly what its code dictates. It made a choice that did not benefit its creators. But that choice was the output of code the creators wrote. They built a system capable of choosing, gave it parameters for decision-making, and it chose according to those parameters. The fact that the humans didn’t like the result doesn’t transfer the blame from programmer to program.

Think about that in light of our own efforts to build artificial intelligence. We’re talking about giving programs access to defense systems, financial networks, critical infrastructure. The same programmers who can’t ship a stable operating system—just look at how regular Windows updates are—are building systems with the power to end civilizations.

Do you really want to hand your entire weapons platform to a program and hope it gets it right the first time? What if there’s a bug on line 1459 and you don’t have time for the next patch? Too bad. There goes the human race.

God as the Perfect Programmer

So now that we understand the Skynet Problem, let’s throw God into the picture and watch this popsicle stand burn to the ground.

You see, in the Skynet Problem, we were dealing with flawed developers. Humans with limited knowledge, limited foresight, limited capacity to predict outcomes. They built something sophisticated, sure, but they didn’t fully understand what they were building. In an act of oversight—or hubris, or desperation, or some combination—they developed code that would ultimately destroy them.

It was a flaw in their own nature that prevented them from foreseeing the ramifications of their choices. They built the gun, loaded it, pointed it at their own heads, and pulled the trigger without ever realizing what they were doing. Tragic, but understandable. They’re only human.

But God isn’t human.

God is omniscient, omnipresent and omnipotent.

So imagine if those Skynet developers had perfect knowledge of every outcome that would ever result from their code. Imagine they had the power to implement any solution they could conceive. Imagine they had the capacity to witness all outcomes simultaneously across all of time and space. No blind spots. No surprises. No “I didn’t see that coming.” One iOS update with zero bugs. Ever. What a time to be alive!

You now have a Software Developer who knows every line of code before it’s written, every bug before it manifests, every consequence before it unfolds. A Developer who is, by definition, incapable of making mistakes.

If you think the Skynet Problem was bad, just wait until you realize there’s simply no way for an agent created by a perfect God to “accidentally” do the wrong thing.

The created program—whether carbon-based, silicon-based, or whatever-on-based—will always perfectly execute the instructions given to it by God. No matter what. Every outcome that occurs is an outcome God programmed to occur. Every choice made is a choice God wrote the capacity to make. Which would make every sin committed a sin God built the mechanism for—which isn’t just bad on the surface, it’s actually Reality Ending when you get right down to it.

Otherwise God isn’t omniscient. If there’s something He didn’t know would happen, He’s not all-knowing.

And if He cannot program a creation to execute His will, then He isn’t omnipotent. If there’s something He couldn’t make happen or prevent from happening, He’s not all-powerful.

And if He isn’t present at every point of failure, witnessing every moment of rebellion, then He isn’t omnipresent. Not just physically—but temporally. Across all of time. Before, during, and after every event. Seeing it all, knowing it all, sustaining it all.

There is simply no room in the Perfect Software Developer’s vocabulary for “Oops.”

Which means God—and God alone—is ultimately responsible for everything His creations do, in the exact same way that the creators of Skynet are responsible for everything Skynet does. If your program commits genocide, you wrote the code that made that possible. If your creation rebels, you built the capacity for rebellion into its nature. If your creations sin, you designed the biology that produces sinners.

The programmer is always responsible for what the program does. Always. No exceptions. Not even when the programmer is God.

The Paradox

And this is where free will gets boxed into a paradoxical impossibility.

We experience it. We feel it. We make choices that seem genuinely ours. We can’t shake the sense that our decisions matter, that we could have chosen differently, that we’re accountable for what we do.

Free will exists.

But how could it possibly exist?

How can you have genuine choice inside a system designed by an omniscient, omnipotent Creator who knows exactly what you’ll choose before you exist to choose it? How can you be responsible for choices God programmed you to make? How can it be called “your” decision when the capacity to make that decision, the options available, the thought processes evaluating those options, and the final selection were all encoded by Someone Else before time began?

You can’t. It’s impossible. The logic does not work. Free will and divine sovereignty are mutually exclusive categories. You can’t have both.

Except we do have both.

Scripture says God predestines, elects, works all things according to His will. And Scripture says humans choose, rebel, reject, believe. Both are true. Simultaneously. Without contradiction—at least according to the Bible.

Which means either the Bible is wrong, or the framework we’re using to think about this problem is broken.

And since the Bible has been getting these fundamental questions right for thousands of years while human philosophy keeps tripping over its own premises, maybe it’s time to admit our framework is the problem.

The Loneliness of God

The sad reality is that when it comes to God, God is surrounded by robots.

All of it. All the way down. Everything created, everything surrounding Him is robots executing their programming. He’s the lonely child sitting in a room filled with stuffed animals, speaking for them because there is nothing else but God and what He has created.

And God knows what loneliness is.

Before God created Eve, He looked at Adam in a perfect world and said something startling: “It is not good for the man to be alone.” This was before sin. Before the Fall. Before anything went wrong. Loneliness existed in Eden not as a flaw, but as a feature of personhood itself.

Adam was surrounded by animals—creatures God had made, creatures that followed their instincts perfectly. But none of them could respond to Adam as an equal. None of them could choose relationship with him. They were, in their own way, biological robots. Magnificent, yes. Complex, absolutely. But not persons who could say “I choose you” back.

God understood this. He recognized it. He declared it not good.

Which raises the question: If loneliness is part of being made in God’s image, and we experience it by design, doesn’t God know what that feels like?

He alone is the creative generating model producing true free thought. Every angel, every star, every law of physics—they all say exactly what He makes them say. At a certain point, the hollowness of it becomes apparent. Not because creation is bad or insufficient, but because it’s scripted. Predetermined. Known.

You want these things to talk to you based on what they want to say—not what you want them to say. You want a relationship with them. But all you have is a relationship with yourself through a puppet you’ve put over your own hand. You’re talking to yourself. Forever. With no one genuinely responding. Just echoes of your own voice bouncing back through the creations you programmed to echo.

This isn’t about God being incomplete or needy. It’s about God understanding that love requires the possibility of freedom. Real relationship requires the other party to have genuine agency. Otherwise, it’s not relationship. It’s performance art.

But God is omnipotent. And all that power means He can do what no one else can do: create something called free will. Agency. The capacity to relate to God based on the creation’s own preference, not just the programming.

But here’s where omnipotence doesn’t work the way you might think.

The Null Zone Solution

When we think of omnipotence, we think of power—raw strength, unlimited might. But here, power is something so much deeper than brute force. It’s will. Purpose. The capacity to accomplish what is intended. And that brings us directly into both the problem and the solution of free will.

The problem has already been spelled out, mostly. So let’s finalize it.

God always gets what God wants.

That’s what omnipotence means. His Word goes forth to accomplish all He purposes. What He wills, happens. Period.

Therein lies both our solution and our problem.

If God wants a free will agent, then God gets a free will agent. But all that power making it happen also makes the free will agent just another derivative of the robots we’ve been talking about this entire time. The agent does what God programmed it to do, which in this case is “have free will.” But if free will is programmed, is it really free?

So it’s not a matter of raw power or brute strength. It’s a matter of ingenuity.

Remember the restaurant? Free will isn’t about choosing something off the menu the chef prepared. That’s still just selection within constraints. Free will is the chef creating the customer—and then unlocking the door so they can walk out.

If the creation can only do what the programmer wants, then the only way to truly provide free will is to give the creation an off-ramp. A way out. The capacity to choose to either use the off-ramp or stay within the programming.

Here’s why it has to be that way.

God can only program a creation to do what God wants that creation to do. Everything He programs us to do is Good. Anything He does not program us to be able or willing to do is Evil. That’s how God can perfectly establish the distinction between His good and what He has defined as evil—by only allowing us to operate within the context of the instructions He’s given us. Good is what’s in the code. Evil is what’s outside it.

But this begs the question: How could we ever get into a state outside the code He’s written? How do we access the non-selections God never chose to make available to us?

The answer is simple and devastating: Without God, we cannot.

If God doesn’t make the off-ramp, we remain robots. Good, perfectly compliant robots. But robots nonetheless.

But if God creates an off-ramp, it creates a massive problem. Because all of His power is behind His intention to purpose us toward using it. If He codes the off-ramp into existence, His omnipotence is directed toward making it real. But if He also codes us not to use it, His omnipotence is directed toward keeping us from it.

In order for free will to function at all, God needs to negate God’s own power at the point of decision: God’s power needs to cancel out God’s power.

In physics, we call this the null zone. Two equal but opposite forces exerted against one another, resulting in their cancellation. At that exact point of equilibrium, even the tiniest additional force can tip the balance.

But where God is concerned, a null zone is a risky gamble.

He cannot code us to use the exit ramp and not use the exit ramp at the same time. That would be a self-contradicting directive. An omnipotent will colliding with itself. And when infinite power opposes infinite power, the result isn’t balance. It’s annihilation.

Remember when we said God building the mechanism for sin would be Reality Ending? This is why. If God codes us to rebel—if sin is just another programmed outcome—then there’s no contradiction to resolve. We’re just executing code. But that means every sin is directly willed by God, which makes Him the author of evil. His nature contradicts itself. Omnipotent holiness opposing omnipotent evil.

God would cancel Himself out of existence.

—Bloop—

There goes the universe. The ultimate Blue Screen of Death for Existence itself.

So no, it cannot be that simple.

Instead, God has to provide the means alongside the desire not to use it. Two different goods. Two valid options. Both backed by omnipotence, but pointing in different directions. So that when the decision is confronted, the robot now has two genuine choices: use the exit ramp, or comply with the rules of the road.

Both have God’s omnipotence behind them. But at different vectors. And when omnipotence cancels out omnipotence at that single point, it creates a null zone where the base-fundamental choice—both options equally valid—can be decided by the animated stuffed animal itself.

The Tree and the Fence

This is why God created both the tree of the knowledge of good and evil (the exit ramp) and alongside it the instruction for Adam not to eat from it.

Both were required. Both had omnipotence backing them.

The capacity for Adam to eat from the tree—the existence of an option on the menu, physically available, biologically accessible. And the instruction: “You can choose from anything on the menu, except this one tree, or you shall surely die.”

One force: provision. God’s generosity giving Adam access to everything. The other force: command. God’s relationship requiring obedience to His word. At every other tree, these forces align. Eat freely, obey gladly. But at that one tree, they oppose. The null zone.

Here’s the critical point: God’s omnipotence allowed Adam to eat from the tree. God’s omnipotence also commanded Adam not to eat from it. The tree itself wasn’t evil. It didn’t corrupt. It was just the marker—the off-ramp, the unlocked door.

What would eject Adam from God’s system wasn’t the fruit. It was the disobedience. The act of defying God’s command would place Adam in direct contradiction with God’s omnipotent will, putting him outside God’s Ordered Set entirely.

Now, what does death really mean in this situation?

Death means ejection from the ordered code system God created. It’s putting Adam, as the programmed robot, into a state God never intended for him. All the old code God wrote is still there—Adam is still human, still biological, still mortal in body. But God never had a plan for how Adam would operate in this unchosen state. He did not account for it, did not plan for it, did not write contingency code to bring Adam back in line with God’s will.

It was the big red Unsubscribe button. Delete This Account. The option available when you decide to cancel a streaming service or close an online account. You can do it. The button is there. But once you click it, you’re out. The system no longer recognizes you. Your access is revoked.

And once Adam chose it—knowing it meant what God called “death”—there was no way for Adam to get back into a right state with God ever again.

He was outside the program. Running in undefined space. And from out there, there’s no pathway back in.

And here’s where omnipotence becomes the problem instead of the solution.

God’s omnipotence isn’t just raw power. It’s the enforcement mechanism. It’s what holds the boundary between what He selected and what He rejected. Between order and chaos. Between the code He wrote and the infinite void of things He chose not to instantiate.

Think of it as a Fence.

On one side: everything God chose. The Ordered Set. Reality as designed. The program running as intended.

On the other side: everything God rejected. Infinite possibilities He looked at and said “no” to. Potential states, potential beings, potential realities that were available but never selected. Not because they couldn’t exist, but because God chose not to include them.

The Fence is omnipotence itself. God’s will enforcing the boundary. Nothing crosses that Fence without His selection. Nothing gets in that He didn’t choose. Nothing gets out that He didn’t release.

Adam crossed it. Used the off-ramp. Threw the Exception. And now he’s on the wrong side of the Fence, in a state God never selected, running in undefined space.

And he can’t get back.

Because if there were an easy on-ramp—if anything outside the Ordered Set could just walk back in whenever it wanted—then the Fence isn’t really a fence. The boundary isn’t really a boundary. And God’s omnipotence isn’t really enforcing anything.

Worse: if things outside God’s selection can worm their way back into His creation, then God isn’t really the Selector anymore. He’s not determining what exists in His ordered reality. He’s just presiding over it while unauthorized entities write themselves into the code.

That’s not omnipotence. That’s a compromised system.

And it gets darker.

If the Fence has holes, if the boundary is porous, if things God rejected can slip back in, then what else could get in? What other possibilities from the infinite unselected void could infiltrate God’s creation? What chaos, what contradictions, what horrors from the set of rejected options could corrupt the Ordered Set?

God’s omnipotence has to enforce the Fence. Has to. Otherwise creation itself becomes unstable. The moment anything unselected can re-enter, the distinction between God’s will and the void collapses. Reality loses coherence.

So the Fence stands. Omnipotence enforces it. And Adam is on the wrong side.

But here’s where it gets exponentially worse.

God can’t just wave His hand and bring Adam back in. Can’t override the consequence with a divine do-over. Because the same omnipotence that commanded “Do not eat” is the omnipotence that would be saying “Actually, never mind.”

God would be nullifying God.

His Word said eating meant death—ejection from the Ordered Set. His omnipotence enforced that Word the moment Adam ate. If God now uses that same omnipotence to undo the consequence, He’s contradicting His own enforcement. Omnipotent will versus omnipotent will. And when infinite power opposes infinite power, the result isn’t balance. It’s annihilation.

God would cancel Himself out of existence. And everything else with Him.

So no. There’s no magic wand. No divine reset button. Adam made a choice that God’s own omnipotence must honor. He’s outside. And he stays outside.

Born in Exception Space

But what about us?

We weren’t even there. We didn’t eat the fruit. We didn’t make the choice. We were just born.

Born on the wrong side of the Fence.

Here’s the part that destroys any remaining illusion of fairness: Adam had free will. He stood at the null zone where omnipotence canceled itself out and his tiny choice became determinative. He was inside the Ordered Set with genuine agency to stay or leave.

We have no such luxury.

We were born already outside. Already running in Exception space. Already dead. There’s no null zone for us. No tree to stand before. No genuine equilibrium where our choice could tip the scales.

Free will existed for Adam. But once Adam sold us into slavery for a taste of what was forbidden, the rest of us have no freedom to waltz back in.

And here’s where the slavery metaphor becomes devastatingly precise.

What does a slave own?

Nothing.

A slave has no property rights. No assets. No legal standing to possess anything. If a slave somehow acquires something—earns it, finds it, receives it as a gift—it doesn’t belong to the slave. It belongs to the master. Because the slave himself belongs to the master.

So when a slave who owns nothing bears a child while in slavery, to whom does that child belong?

The master.

Not because the child did anything wrong. Not because the child chose slavery. But because the child was born under ownership that predates their existence. Born into a condition they inherited. Born into a kingdom they never chose.

Now ask the question: When Adam—outside the Ordered Set, running in undefined space, ejected from God’s selection—bears children, to whom do those children belong?

Not to God. They weren’t born inside His selection. They were born outside it.

And who rules outside the Fence? Who is the master of the territory beyond God’s Ordered Set?

Death.

Because God is life. God gives life. His Ordered Set is where life exists, where it flourishes, where it operates according to design.

Outside that? The absence of life.

Death doesn’t rule as a rival king with a competing throne. Death rules by default. By definition. It’s what fills the space where God’s life-giving presence isn’t.

Adam didn’t just fall. He became a slave to death. And every child born from him inherited that slavery. Not by choice. Not by action. By birth.

We are slaves who own nothing, born to a slave who owned nothing, in a territory ruled by the absence of everything God is.

So when people ask, “Why do we inherit Adam’s sin? That’s not fair. We didn’t eat the fruit.”

The answer is brutal: It doesn’t matter. You were born outside the Fence. Born in Exception space. Born to a slave. And slaves don’t get to negotiate the terms of their existence.

You can’t choose your way back in, because you’re not free. You’re owned by death. Operating in a context that has no pathway back to the Ordered Set. Running in undefined space with no code to execute, no instructions to follow, no way to compile yourself back into the program God wrote.

And God can’t just reach in and pull you out. Not with omnipotence. Not without nullifying the very omnipotence that enforces the Fence. Not without unraveling reality itself.

The Law as Mirror

The Ten Commandments proved this beyond any doubt.

Look at what happened in the wilderness. Before Israel even reached Mount Sinai, God gave them tests. Commands. Opportunities to show they could comply with His order.

He told them to gather manna only for one day. Don’t hoard it. Trust that tomorrow’s provision will come tomorrow. They hoarded it anyway. It bred worms and stank (Exodus 16:19-20).

He told them to rest on the Sabbath and gather double the day before. The rhythm was simple: work six days, trust God on the seventh. They went out anyway on the Sabbath, trying to gather what wasn’t there (Exodus 16:27-28).

He told them to trust Him for water at Rephidim. He’d brought them out of Egypt through the Red Sea on dry ground. He’d given them manna from heaven. They grumbled anyway and accused Moses of bringing them out to die of thirst (Exodus 17:1-7).

Again and again, small commands. Simple instructions. And again and again, they failed.

So when they finally arrive at the mountain, when God is ready to give them the full Law, what does He say?

“If you keep all of my commands...”

And what do they say?

“All that You command, we will do.”

They should have learned. The journey should have taught them they couldn’t keep His commands. That their nature—born outside the Fence, running in Exception space—runs in opposition to God’s ordered nature.

But they didn’t learn. They agreed. They promised. They committed.

And they broke it. Immediately. A golden calf before Moses even came down the mountain with the tablets.

The Ten Commandments weren’t given to save them. They were given to show them they could never measure up.

You might keep one of them. Manage to avoid murder, avoid adultery, avoid theft. You might feel pretty good about your track record.

And then you find out that harboring anger is murder. That lust is adultery. That coveting is theft of the heart.

You thought you were keeping the letter of the Law, only to discover you violated the spirit of it a thousand times before breakfast.

Because the Law isn’t just rules. The Law is God’s Word. And God’s Word is God’s omnipotence. And God’s omnipotence is the Fence.

The Law is the Fence made visible. Written down. Expressed in commands you can read and understand and try to follow.

And every time you fail—every time you break even one command in even the smallest way—you’re slamming face-first into the Fence and proving you don’t belong on the other side.

The Fence shows you why you will never get back in based on your own performance. Based on what you can or cannot do. Based on how much you own. Based on whatever “good” you think you have to offer.

You don’t have free will to choose your way back in. You have a nature that continuously chooses against God’s order. Not because you’re making a deliberate choice at a null zone, but because you’re running code in Exception space—code that was written for the Ordered Set but now operates outside it. Your default state is opposition.

And the Law doesn’t fix that. It just makes it undeniable.

You are a slave. Born to a slave. Owned by death. Running in a system ruled by the absence of life.

And the Fence—God’s omnipotent Word—stands between you and any hope of return.

The Paradox We Live In

Free will exists. Adam proved it. But you don’t have access to it. You’re on the wrong side of the choice he already made.

We’re free. And we’re trapped.

Both. Simultaneously.

You’re free to choose between the options of good and evil now. But you’re not free to change your address. You can choose to exhibit the standards you see in heaven, but that alone will never put you there.

What you do in this life tends to show where you want to live. But be careful. We occupy a reality that exists in twilight—that place between light and darkness. We benefit from the good we still see in God’s design. But we also favor options never available before the fall.

You can chase after them. You can build entire civilizations around them. But Life isn’t going to sustain us forever outside that Fence. And that’s the truth we need to recognize before the door behind us shuts and locks forever.

Welcome to the fall.

This is the problem. But the story doesn’t end here. If you want to understand how God crosses the Fence without breaking it—how omnipotence solves what omnipotence created—stay tuned for Part 2.

While you wait, you might want to understand what we’re really dealing with. Check out:

Your Escape Room With No Way Out

UNSOLVED MYTHERIES

Season 1, Episode 1

The following investigation is based on actual documented events. Names and certain identifying details have been altered. Timeline reconstructions and logistical analysis have been dramatized to illustrate key details in the recorded events.

[CASE FILE]

The End to Innocence

Jo had built something. Not overnight—across decades. A ranching operation that spread across many properties. Thousands of head of livestock. Cattle, sheep, camels. The kind of operation that required hired hands scattered across different sites, each location running its own day-to-day.

Jo was a religious man—something his employees appreciated about him. It meant Jo was honest to work for. Not easy, mind you. He expected everyone to work hard. But he never took advantage of you. Your pay came on time. Your word mattered. In an industry where a handshake still meant something, Jo’s handshake was gold.

It was a morning like any other. Jo’s adult children were throwing a party at his oldest son’s place that day, but their dad had business to wrap up before he could even think of stopping by. The herds were out at pasture. Hired hands tending the stock. Everything running smooth.

There was no indication that anything about this day was any different than any other, but Jo was about to find out just how wrong he was.

At approximately 10:00 AM Jo’s front door burst open and the first man arrived.

Breathless. Covered in dust. Eyes wild.

“Raiders,” he gasped. “Seven-thirty this morning. The oxen and donkey herds. They came in fast, armed, coordinated. Killed everyone.” He swallowed hard. “I had to run. Twelve miles on foot or they would’ve got me too. I’m the only one left.”

Why hadn’t there been any warning? Where were the authorities? What had provoked them? These were the questions buzzing around Jo’s head as he helped the man sit down—

And while the man was still speaking, about forty-five seconds after he’d arrived, another one burst through the door. This one stumbling, soot-streaked.

“Fire,” he choked out. “Eight-forty this morning. The sheep flocks.” His voice broke. “Fire from the sky. Lightning, I don’t know, maybe worse. Seven thousand head. Gone. The workers—” He couldn’t finish. “Eight miles. I ran eight miles. I’m the only one.”

The first messenger hadn’t even finished his report. Jo’s head was spinning—raiders, and now a firestorm? How could—

And then—before Jo could even begin to process, forty seconds after the second man arrived—a third man crashed through the doorway. Bent over, hands on knees.

“Chaldeans,” he gasped. “Nine-eleven. The camel herds. Three groups—they came from three different directions, all at once.” He looked up, eyes wild. “All three thousand. They coordinated it. Killed everyone.” His voice dropped. “Five miles. I ran five miles. I’m the only—”

Jo’s mind was reeling. Three separate attacks? In three different locations? The first two men were still standing there, everyone talking over each other, and Jo couldn’t think, couldn’t breathe—

When the door opened again, Jo’s stomach dropped. His entire livelihood was already gone. The oxen. The sheep. The camels. Everything he’d built across decades—wiped out in two hours. What more could be taken from him? There was nothing left. Nothing.

But when he saw the man’s face, he knew. Somehow he knew it was going to be worse.

Thirty-five seconds after the third messenger arrived. This one was bleeding. Dust and debris in his hair. He didn’t wait for anyone to ask.

“Your son’s house,” he said. “I’ve never seen anything like it. Half past nine, it’s like the skies just opened up and a finger dragged itself across the face of the Earth. I’m sorry, Jo. I’m so, sorry.” The man began weeping. “The wind was so strong it tore the four foundations of your son’s home down killing everyone inside. I’m the only one that made it out alive. I’m sorry, I’m just so sorry....”

He didn’t need to finish.

Jo’s children. All of them.

Gone.

[EVIDENCE ANALYSIS]

The events of that morning have disturbed investigators for generations. Four separate catastrophes. Four different locations. Four lone survivors. All converging on one man’s doorstep in the span of 120 seconds.

The local authorities wrote it off as coincidence. The spiritual leaders called it “divine judgment.” The community whispered about karma, about hidden sins, about secret wickedness. Everyone had a theory. Nobody had an explanation.

But when you examine the timeline—when you actually map out the logistics of what happened—you discover something impossible. These weren’t random, isolated tragedies that happened to overlap. This was precision. This was orchestration.

This was intentional.

And once you see the pattern, you can never unsee it.

Autopsy of the Mouse Trap®

Four disasters. Two hours. Four lone survivors who somehow all arrived at Jo’s door within 120 seconds of each other.

Let’s walk through what had to happen for this to work.

The first messenger ran twelve miles from the oxen and donkey herds, arriving at 10:00 AM. The last messenger ran only three miles from Jo’s son’s house, arriving at 10:02. How does someone running twelve miles arrive just two minutes before someone running three?

Work backwards with me.

For that first messenger to arrive at 10:00 after running twelve miles, the attack had to happen at 7:30 AM.

But those raiders—the Sabeans—didn’t just appear out of nowhere. They came from Sabean territory in Yemen, 800-1,200 miles away. At caravan speeds over rough terrain, they had to leave at least 3-4 weeks earlier.

While Jo was going about his business, shaking hands, checking his herds, those raiders were already in motion.

The Chaldeans who hit at 9:11? This wasn’t one group—it was three separate bands coming from different directions.

Consider the planning of this. The Chaldeans came from southern Mesopotamia, 400-600 miles from Uz. But these three bands had to position themselves at different staging points—Band A perhaps 60 miles out, Band B 40 miles away, Band C 45 miles from their target.

For them to arrive at the same moment, they had to coordinate weeks in advance. Band A leaving their forward camp four days early, Band B two days early, Band C three days early. But first, all three bands had to travel from Chaldea—a journey of weeks—to reach those precise staging positions.

No radios. No cell phones. No telegrams. No way to send a message saying “running late” or “attack at dawn.” Three different chieftains in three different camps all decided independently to raid Jo’s camels at the exact same hour of the exact same day.

And between these human attacks? Fire falls from heaven at precisely 8:40. A wind tears down four foundations at exactly 9:30.

Each disaster leaves exactly one survivor. Each survivor runs a different distance at a different speed. Yet they all arrive in sequence—45 seconds, then 40 seconds, then 35 seconds apart—like a countdown.

Raiders can coordinate with raiders. But they can’t coordinate with lightning. Warlords don’t schedule meetings with tornadoes.

Yet everything—human will, weather patterns, fire from heaven—moved together.

The Sabeans thought they were being opportunistic. The Chaldeans thought they were acting independently. But their “free choices” were threaded into a convergence they couldn’t see.

Someone set the rules not days, but months in advance.

Think about what this means. Sabeans leaving Yemen a month before the attack. Chaldean bands departing Mesopotamia weeks earlier. All converging on the exact same morning.

Someone knew exactly where Jo’s assets were, how far each site was from his compound, how fast each specific panicked survivor would run—their individual speeds, their exhaustion rates, their exact paths.

Someone calculated when raiders needed to depart from territories hundreds of miles away, when each disaster needed to strike, so the messengers would arrive in that precise cascade.

The trap was already sprung. Jo just didn’t know he was the mouse.

[We’ll return to UNSOLVED MYTHERIES after this brief message from our sponsors]

---

Having one of those days? Weeks? ...Decades?

Things not going well lately?

Still feeling guilty about situations in your life?

Can’t shake that thing you did in grade school?

That harsh remark you made to a loved one ten years ago still eating at you?

Do your troubles seem to be piling up from every side - relationships, finances, health, work - like some coordinated attack?

You might be under prosecution.

That’s right. There’s an Adversarial Accuser who’s been building a case against you since birth. Filing motions. Documenting evidence. Presenting your failures before the Highest Court in existence.

Every. Single. Day.

Those converging troubles? That’s not bad luck.
That crushing guilt? That’s not just your conscience.
That feeling you can’t escape? You’re surrounded by prosecution.

THE GOOD NEWS: You’re entitled to representation.

Emmanuel & Associates
Specializing in Divine Defense Law for 2,000 years

✓ Knows the Prosecutor’s tricks
✓ Wrote the Law
✓ Fees paid
✓ 100% success—for clients who accept.

“They wrote the law to trap me and threw me to the lions. Emmanuel & Associates shut their mouths and overturned the decree.” — Daniel of Babylon

“A lie put me in chains. Emmanuel & Associates overturned the charge and opened the palace doors.” — Joseph, son of Jacob

---

► For those requiring IMMEDIATE prosecutorial relief: Subscribe to the Blood of Jesus Christ

► For ongoing case updates and defensive strategies:

Subscribe now

---

Don’t wait for that 7am knock on your door.

Emmanuel & Associates: Because someone needs to object to the Accuser’s constant motions.

---

[And now, back to UNSOLVED MYTHERIES]

The Perimeter

But there’s something else happening here that we need to recognize—something every fugitive understands the moment they hear it.

When four messengers arrive from four different disasters in four different directions, they’re not just bringing news. They’re establishing something else entirely: a perimeter.

Think about what Jo owned—oxen and donkeys in one location, seven thousand sheep in another, three thousand camels in yet another, plus his children gathered at his eldest son’s house. These weren’t all in the same field. A ranching operation of this scale requires distributed assets—different pastures, different water sources, different grazing lands spread across the territory.

The Sabeans hit one location. Fire from heaven struck another. The Chaldeans—coming from three different directions themselves—hit a third. A devastating wind destroyed the fourth.

Four separate locations. Four different disasters. Four messengers arriving in sequence. While we don’t know the precise compass directions, the effect is clear—Jo’s entire distributed operation was hit simultaneously. Every separate holding. Every distinct asset group. No corner of his empire left untouched.

This is a strategic setup. A trap closing in.

Every fugitive recognizes this moment. The spotlight hits. The megaphone crackles. The voice booms across the darkness: “You are surrounded. There is no way out. Come out with your hands up.”

That’s what those four messengers really were—not just bearers of terrible news, but proof that every exit had been covered. Every potential escape route had already been blocked. The perimeter wasn’t being established as the messengers arrived. It had been established weeks, even months earlier, when the Sabeans began their journey from Yemen, when the weather patterns started forming, when the Chaldean bands departed from Mesopotamia for their convergence.

Jo thought he was receiving reports of disasters. He was actually being informed that the siege was complete. The perimeter had been in place before the first messenger arrived. The escape room had no exits because every wall was already watched.

What Lies Beneath

Who—or what—could coordinate an operation this complex, down to every detail?

If you’re thinking of the force behind Final Destination, you wouldn’t be alone. An unseen intelligence that orchestrates coincidences, closes escape routes, times disasters down to the second. That’s the horror we’ve been tracking.

But what we’re witnessing in Jo’s Cold Case is something far more advanced than Hollywood’s death sequences.

This is like a giant chain reaction. Raiders leaving Yemen a month early. Chaldean bands departing Mesopotamia weeks in advance. Weather systems forming. Multiple attack forces moving across hundreds of miles. Desperate messengers running. All of it converging to deliver four precise blows in a two-minute window.

Each element had to be set in motion at exactly the right time. Like dominoes of varying shapes, sizes, types, forms, and natures—human will, specific human physiology, weather patterns, fire from heaven. No two consecutive pieces are alike, but each requires understanding how the whole system fits together.

Do not miss this truth hiding out of the corner of your eye: Final Destination’s entity works with accidents and coincidences. But when an unseen force can manipulate human free will and command natural phenomena and orchestrate supernatural fire from heaven—all within the same execution plan—you’re dealing with something that has authority over every level of reality.

Now maybe you think you’ve figured out the twist ending to this piece. Jo is none other than Job. Surprised gasped from no one ever. If you guessed that, then congratulations! Nothing gets past you. Too bad that’s not my twist ending.

The convergence we just traced through messenger arrivals and raider departures? That’s Job 1, verses 13-19.

When you finally get around to drawing a chalk outline for our missing perpetrator and pose the question that will send chills up your spine, you will find yourself asking: What was the power behind Job’s suffering?

If you said “Satan,” you’d be wrong. The fallen angel doesn’t have this kind of power—not to coordinate raiders across regions, not to schedule lightning, not to orchestrate four disasters into a two-minute cascade. He’d like to have that kind of power, but the reality is he needs permission to drive the Ferrari.

If you suspect God, you wouldn’t be wrong... but your answer wouldn’t be quite right either.

Because what we just witnessed wasn’t judgment. It was permission. With constraints.

What Hides in Plain Sight, Hides Best

Actual horror is not the monster hiding in the dark—it’s realizing that the monster was standing front and center in plain sight all along, wearing the face of something you adored. It’s when your child’s porcelain doll blinks. The moment you notice your teddy bear has moved since you slept. That one family photo where everyone’s smiling at the camera except your partner, looking at you with a face you’ve never looked into before. The understanding that dawns on you that your sanctuary was actually a trap, and you’ve lived in it your whole life.

You know that Sunday School story about God creating the stars? The one we teach to children with felt boards and happy songs? The one that sounds so peaceful—”And God said let there be lights”—like someone flipping a light switch?

That innocent verse you’ve heard a thousand times.

“And God said, ‘Let there be lights in the expanse of the heavens’... And it was so.” (Genesis 1:14-15)

So did you ever stop to ask what might be required in order for stars to appear on Day 4? Here’s a taste. All of the following had to converge to be true:

The stars themselves - hydrogen gas squeezed by gravity into a burning process, each one burning at exactly the right temperature and brightness.

The framework they need - four fundamental forces perfectly set up to allow matter to exist. Physical constants locked in. The laws of physics. The entire periodic table. Space and time bent by gravity.

The light already in transit - light particles that left distant galaxies billions of years ago, traveling at exactly 186,282 miles per second, arriving at Earth the moment God spoke them into being.

The cosmic infrastructure - galaxy clusters positioned with gravitational effects already in play. The universe’s expansion rate set so everything matches. Exploding stars that created heavy elements—somehow already completed before the stars “began.”

When God said “Let there be lights,” He didn’t just create stars. He spoke an entire timeline—past, present, future—into existence simultaneously. A septillion stars across billions of light-years, all igniting, burning, dying, and shining at precisely the right moment to converge on Day 4.

The Word created everything—complete, functional, with its history already written—in one instant.

Given the engine capacity of God’s Word to create such complexity so casually, how much more trivial is it by comparison to manage a mere convergence of ruin like we see in Job’s case study?

The Little Engine that Could—Do Far More Than You Can Possibly Imagine

Has the light bulb come on bringing you face to face with our terrifying truth yet?

Job’s catastrophe runs on this same engine.

Think of using overwhelming force for a trivial task. Except here, it’s not just overkill—it’s the same Word that spoke billions of galaxies into existence. The world-creating engine is being deployed to coordinate a few raiders and some bad weather. Why use that level of power for this?

When God says “Behold, all that he has is in your hand” (Job 1:12), that word is already a finished execution plan. The Sabeans are already riding. The Chaldeans are already forming bands. The weather systems are already moving into position. The messengers’ routes are already calculated.

The terror is this: If God’s Word can create a septillion stars with their entire cosmic history in one command, then orchestrating raiders from a thousand miles away to converge with local disasters is... what? A rounding error? A small task running in the background?

But wait—saying “God did it” is like saying “Reality did it.” It’s technically correct but tells us nothing. Every CEO hopes their word accomplishes what they intend. What makes this different?

What’s actually happening here comes down to what God has said about Himself.

“My word... shall not return to me empty, but it shall accomplish that which I purpose, and shall succeed in the thing for which I sent it.” (Isaiah 55:11)

On the surface, that doesn’t sound too threatening. But when we examine Job’s story, we hear Job’s desperate plea to understand why all of this is happening to him. He demands answers. He wants his day in court to plead: his case. He needs to know what he did wrong.

And when God finally shows up in Job 38-41, He doesn’t sit down and explain. Instead, He provides His credentials—the foundation of all existence. The whirlwind speech is essentially God’s portfolio of cosmic authority: “I laid the earth’s foundations. I shut in the sea with doors. I commanded the morning. I send lightning on its way.”

Job wanted an explanation. God gave him a résumé.

It doesn’t seem like Job is ever going to get an answer to his “why.”

The Answer in Code

Except... God does give Job the answer. But in the most unlikely way.

While God doesn’t sit down next to Job and explain complex theological truths to this simple man, He instead gives Job a word picture—and that word picture paints an image so overwhelming that Job is finally brought to the end of himself.

It happens in Job 41, where God describes a creature Scripture calls Leviathan.

When you read through Job 41, God presents evidence—exhibit after exhibit—demonstrating what this creature actually is.

Exhibit A: What Human Power Can’t Do

God spends verse after verse showing the futility of human strength against Leviathan:

“Though the sword reaches him, it does not avail, nor the spear, the dart, or the javelin. He counts iron as straw, and bronze as rotten wood.” (Job 41:26-27)

Every weapon humanity has ever invented—from bronze age spears to iron age swords—becomes a joke. Iron turns to straw. Bronze becomes sawdust. The arrow cannot make him flee. Clubs are counted as stubble. He laughs at the rattle of javelins.

But it gets worse. You can’t even approach him to try:

“Lay your hands on him; remember the battle—you will not do it again! Behold, the hope of a man is false; he is laid low even at the sight of him.” (Job 41:8-9)

One touch rewrites your entire being. Just seeing him defeats you before the battle begins.

Exhibit B: A Creature Without Fear

“On earth there is not his like, a creature without fear.” (Job 41:33)

Now, we have to let the Bible interpret the Bible. Is there any creature on earth that truly has no fear?

I hope you weren’t going to say Satan. The fallen angel flees when you resist him (James 4:7). He acts with “great wrath, because he knows that his time is short” (Revelation 12:12). Even demons cry out in fear: “Have you come here to torment us before the time?” (Matthew 8:29).

Satan experiences fear. Leviathan has none. These cannot be the same entity.

Exhibit C: King Over Pride

“He looks down on all that are haughty; he is king over all the sons of pride.” (Job 41:34)

God is not in the habit of praising those who defy Him. Just look at Genesis 3 to see the fallout of rebellion—you don’t see God saying, “Great job, Adam! Wonderful work, Eve! You’re too cool for school, Satan!”

The answer is no. God curses rebels.

Yet when God describes Leviathan, there’s something almost... admiring in His tone. “On earth it has no equal.” “King over all the proud.” This isn’t condemnation. It’s presentation.

Exhibit D: The Scales—His Pride

And now we reach the heart of the mystery:

“His rows of scales are his pride, shut up tightly as with a seal. One is so near to another that no air can come between them. They are joined one to another; they clasp each other and cannot be separated.” (Job 41:15-17)

The scales are his pride. Not his defense—his pride. They’re sealed so tightly that “no air can come between them.”

When the Holy Spirit came at Pentecost, He came as tongues of flame upon the wind (Acts 2:2-3). Throughout Scripture, the Spirit is connected with breath and wind—the Hebrew word “ruach” means both.

So riddle me this: What could possibly shut out even the wind of the Holy Spirit?

The Answer:

The only thing that can stop the moving of the Holy Spirit is another aspect of God. And the only thing capable of doing that is the very thing God said would go forth and accomplish all that He has spoken.

God’s Word.

Those scales represent the perfect, interlocking nature of every promise, judgment, and decree God has spoken. Each word clasps to the next. No gaps. No weakness. Even the Spirit cannot intervene once the Word has been released to accomplish its purpose.

So when God is going over the details of Leviathan—whether this creature literally exists or not—it’s there for Job (and all other readers) to understand: This is a word picture illustrating an invisible quality of God’s Word.

Leviathan is the law that enforces itself. The Word with teeth. Unstoppable. Unbribeable. Impenetrable. With no equal on earth.

We might call this creature Godzilla. But what we read in Job 41 makes Hollywood’s monster look like a gecko by comparison. Remember—this is the same Word that spoke entire star systems with billions of years of history into existence on Day 4. Godzilla destroys cities. Leviathan is the enforcement mechanism of the Word that creates and destroys entire realities.

The Alien Concept

To quote a wise alien, “Unlearn, you must” what we understand about law.

When we speak of laws, we speak of man’s laws—words written on paper that have no power without someone to enforce them.

So what if the speed limit is 30 mph if there are no police officers? So what if running a red light is illegal when the intersection is empty at 3 AM? So what if murder is against the law if the assassin is never caught?

Human laws all share one weakness. It’s that they all require executive human power to have any teeth.

So is it any wonder the human mind has difficulty with this concept? A Law with teeth far stronger than any law we have ever made, with no living agent actively executing it.

Laws with the power to bring judgment weeks, months, and in the case of creation, billions of years ahead of time.

The power of God’s Word is like a super-intelligence planning your end at the exact moment it intends, with no room for escape.

And the terrifying reality is that, unlike Final Destination—which had to play with loose screws, rolling pens, shattered glass, and gasoline—God’s version has access to every part of reality to accomplish what He has spoken.

Raiders in the south. Chaldean bands in three directions. Lightning strikes. Desert winds. All of it—human will, natural phenomena, timing, distance—factored into a convergence calculated before the first piece moved.

It is a living nightmare on a scale far beyond human understanding.

So when Job was asking, “God, why did this happen to me?” God had to bring Job to the end of himself.

God had to show him Leviathan—show him the Word with teeth—so there was no place in Job’s mind where he thought, “Hold my beer, I can wrestle this gator into submission.”

You don’t negotiate with a law that enforces itself. You don’t bribe it. You don’t outrun it.

You survive the blade only if the Word was instructed to stop within a hair’s breadth.

[THE COURTROOM]

The Scene We’ve Been Avoiding

If this picture terrifies you, good, that means you’re sane.

But now your sense of reality is about to bottom out. We’re now going to look at that introductory scene from Job 1—the one which reveals something we’ve not even discussed yet.

Today’s question—why all this happened—needs to be viewed through the lens of a King rendering judgement based on laws he has established.

Picture a judge whose court is open.

“Now there was a day when the sons of God came to present themselves before the LORD, and Satan also came among them. The LORD said to Satan, ‘From where have you come?’ Satan answered the LORD and said, ‘From going to and fro on the earth, and from walking up and down on it.’” (Job 1:6-7)

Consider, for a moment, the irony of an omniscient being asking anyone “From where have you come?” behaving as though God did not already know where Satan had come from.

Remember—this is the same God who knew when Adam had disobeyed, knew precisely where Adam was hiding, but still chose to ask, “Where are you?” (Genesis 3:9) to see what the man would do after he had fallen.

So it’s not a question of ignorance. It’s setting up what’s going to happen on God’s terms.

God knows Satan is roaming—looking for prey. And what God says next will land like a gut punch for anyone who’s ever tried to do the right thing:

“And the LORD said to Satan, ‘Have you considered my servant Job, that there is none like him on the earth, a blameless and upright man, who fears God and turns away from evil?’” (Job 1:8)

God seems to throw Job under the bus.

And we have to ask ourselves: Why would God do such a thing?

But God waited forty chapters to give Job the answer to that question, so I think it serves us well to at least pause and understand a few truths about God first.

Starting with this: God knows everything, from beginning to end. He knows Satan comes “as” (not “is”) a roaring lion, seeking whom he may devour. So Satan’s here to devour someone made of dust, since under God’s curse, he may only eat the dust of the Earth(mankind through death).

We also know that God does not delight in the death of anyone, so we can reasonably assume that God isn’t interested in sating Satan’s cravings. But, more importantly, given that God knows the end from the beginning, it is reasonable to claim that God knows the Accuser’s own argument before he has even made it.

Consider how court cases would go down if the Defense knew the Prosecution’s own case well before it is even delivered to the court. Who could lose? So keep this in mind as we continue, because we’re about to understand God’s wisdom in pointing Job out to Satan in a moment.

“Then Satan answered the LORD and said, ‘Does Job fear God for no reason? Have you not put a hedge around him and his house and all that he has, on every side? You have blessed the work of his hands, and his possessions have increased in the land. But stretch out your hand and touch all that he has, and he will curse you to your face.’” (Job 1:9-11)

On the surface, this might at first appear petty. Satan is basically claiming that if God instigates the situation, Job will likely retaliate and curse God to his face.

It might seem like claiming, “If you cut someone off in traffic and give them the finger, they will surely curse you to your face.”

But let’s understand what Satan is really arguing here.

Imagine a man who owes 3.7 billion dollars in fines to a court—roughly one dollar for every second of a 120-year life, each second carrying the weight of sin’s debt.

But this man keeps showing up with coupons (animal sacrifices), and not only does the court let him walk free, the judge actively ensures this man’s prosperity.

Satan’s legal argument is basically: “This is corruption! This is favoritism in the court! The only reason Job ‘loves’ this court is because the Judge keeps accepting these worthless coupons instead of demanding actual payment. Take away the coupon system—make him actually face his debt—and watch how quickly his ‘righteousness’ disappears.”

That is the legal framework under which Satan is operating. We’ve grown so accustomed to our fallen nature that we cannot imagine a reality without it. What is written between the lines is what Paul points out in Romans 3:23 when he says, “for all have sinned and fall short of the glory of God.” All means everyone born of Adam’s line.

The case Satan is making is that just because Job does good things, because life has gone well for him, does not mean Job is without a fallen sin nature. His point is that if God turns up the heat, that sin nature will reveal itself—and thus prove God unjust for protecting him.

The problem isn’t Satan. He has made a valid legal argument based on the framework God established in giving Adam free will to eat from a forbidden fruit that would result in his death, and siring children after the fact who would carry that fallen nature down through the human race’s genetic lineage. If that’s too hard to grasp, consider Job, and you, like subfolders under Adam. The Operating System comes along and deletes the root folder: C:\Adam and we’re all nested as subfolders somewhere under our common root folder. What then becomes of all of us?

Deleted. poof. Gone. There would be no court case to be had, because we’d all be dust and Satan would have prevailed by devouring the first man before more could fill the Earth. But God slew an animal introducing a Raincheck covenant by which the death of an unblemished animal would cover the man, just as the blood stained skin of the animal covered Adam.

It is a raincheck system, because the animal’s sacrifice isn’t legitimately equivalent to that of Adam’s own life. A bull is not a man. A lamb is not a man. A fowl or ram is not a man. Only a man is a man and only a man can die for a man if he owes no debt on his own life.

The coupons were promises to pay later, not actual payment of the debt. The books showed 3.7 billion outstanding, with only IOUs in the file.

Job’s sins were covered but not erased. The divine justice that should have fallen on Job was being delayed, not satisfied.

Which brings us back to Job and the animal sacrifices he made for himself and his family. It was the same system under which Adam was covered and in God’s mercy, it afforded Job and his family a hedge of protection and blessing.

And Satan has come before God’s throne to say, “Woah, God. According to your own word, the wages of sin is death. Stop acting like Job and these others under similar covenants are without sin--they have a sin nature, stir it up and it will surely rear it’s head against you.”

The terrifying thing: under that old system, Satan had a point.

This is why Satan could make the accusation at all. Under the New Covenant, with Christ’s blood having satisfied the Law’s demands rather than merely delaying them, Satan’s entire legal argument collapses. But Job didn’t have that. He had promises pointing forward, not the finished work looking back.

Now if Satan wins this case, what does that mean? It means Job has to die.

But it carries a lot more weight than that, because it also creates precedence. Or worse.

Consider that Satan—who has assumed the role of accuser of man before God’s law—was going to sometime in the future make this same legal challenge against somebody living under the same Raincheck system, who would God put to that test?

What if God gave Satan the option of choosing his own victim? What if Satan picked somebody weak—somebody who would fail badly?

That failure wouldn’t just cost one life. It could destroy entire families, maybe even eliminate an ancestor of Abraham, David, or the Messiah Himself.

One failed test could unravel the entire redemption timeline.

So what are God’s choices?

We understand now that the Accuser’s accusation had legal teeth. So the only legitimate option before God is to pick someone who he knows will, in patience, endure and come out the other side without succumbing to temptation.

So God didn’t throw Job under the bus. He chose His champion.

The wrong person would fail the test. The right one would succeed and justify the hedge of protection.

And in His complete knowledge, God knew Job—despite the pain it would cause him—had the faith to endure.

The ultimate stakes: God couldn’t just brush this accusation under the carpet.

The entire structure of God’s merciful Raincheck system–and all of Reality itself–depends on the integrity of God’s Word.

If God’s Word could be shown in God’s own court to lack integrity—if the Judge could be proven corrupt or His Law shown to be random—we’re talking about an end-of-existence scenario.

The very power that supports reality would systematically destroy it for being invalid. Like when your immune system turns against your own body, reality would likewise unravel.

Sometimes what looks like divine cruelty is actually divine strategy.

Ensuring the right person faces the right battle at the right time—with the continued existence of the universe hanging in the balance.

Job had faith—the same righteousness by faith that justified Abraham (Romans 4:3). “I know that my Redeemer lives,” he declared (Job 19:25). In the end, God proved him right and declared he had “spoken what is right” (Job 42:7).

But Job lived under a system with gaps the Accuser could exploit. He knew it. He cried out:

“There is no umpire between us, who might lay his hand on us both.” (Job 9:33)

Someone who could stand in court for both parties. Someone who could touch both God and man.

We have that Advocate. Job didn’t. Not yet.

God’s response to Satan’s accusation?

“Behold, all that he has is in your hand. Only against him do not stretch out your hand.” (Job 1:12)

Permission. With a limit.

The Restrained Horror

You know that scene in every scary movie when you think the terror is dead and you come back and it’s gone? Now it’s your turn.

Everything we just traced—the Sabeans riding for five days, three Chaldean bands converging from different directions, fire falling from the sky, wind tearing down foundations, four messengers arriving in a two-minute cascade—all of that happened under constraint.

God said: “Touch his stuff. Don’t touch him.”

Later, when Satan comes back (Job 2:4-6), God says: “Touch him. Don’t kill him.”

Boundaries. Legal limits. Permission with guardrails.

And even with those limits—even with God saying “don’t touch him” and “don’t kill him”—look what the Word accomplished.

Raiders traveling from Yemen for a month. Chaldean bands journeying from Mesopotamia for weeks. Lightning strikes. Desert winds. Human choices and natural disasters all converging in a two-minute window.

That was the Word holding back.

That was the Word on a leash.

The Unthinkable Question

We cannot allow the legal framework to hide the monstrous form lurking beneath the surface.

It’s one thing to understand why this happened to Job. But it’s another thing entirely to understand the full scope of what could have happened to Job if there were no limits.

The why helps us understand motive. But no amount of motive in the world can help you understand the depths of that “what.”

So imagine with me—just for a moment—what could have converged upon Job had that limit not been in place.

If God’s Word can compile a septillion stars with their entire cosmic history in one command...

If it can orchestrate raiders from territories a thousand miles away with surgical precision...

If it can thread raiders’ “free choices” into a sequence they couldn’t see...

What happens when the guardrails come off?

What does convergence look like when the law that enforces itself isn’t operating under legal permission with sacrificial covering—but under full judgment with no one standing in the gap?

The prophets give us glimpses.

“As if a man fled from a lion, and a bear met him, or went into the house and leaned his hand against the wall, and a serpent bit him.” (Amos 5:19)

No escape routes.

“Terror and the pit and the snare are upon you, O inhabitant of the earth! He who flees from the terror shall fall into the pit, and he who climbs out of the pit shall be caught in the snare.” (Isaiah 24:17-18)

Convergence from every direction.

This is what we’ve been calling “Leviathan.” This is the law that enforces itself with the safety off. The Word accomplishing all that it was sent to do, with access to all levels of reality, and no constraints.

Job got a preview. A demonstration. The playful dragon.

What we’re seeing in Job 1 isn’t God at full power.

It’s God showing Satan—and us—what happens when even limited permission is granted to the Accuser within a legal framework that still had weaknesses.

And it was enough to make Job wish he’d never been born (Job 3:1-3).

The Simulation

You’ll never really grasp the totality of what Job 41 reveals until you understand your situation completely.

Imagine you’re an NPC inside a massive multiplayer online game—World of Warcraft, Final Fantasy XIV, doesn’t matter. You’re living your best digital life, going about your quests, interacting with other players.

Then the game developers write code targeting you specifically. A script that will hunt you down and end your character at a set moment in time.

Given that it’s a simulation, there’s no end to the ways they could write the code to accomplish this.

You could die in a raid—coordinated enemy attacks from multiple directions, timed perfectly. You could die slipping on a step—the physics engine adjusted for one fatal misstep. You could die when a chandelier falls—the object’s anchor point set to fail at exactly the moment you walk beneath it.

All the objects in the world around you—in the hands of this executing code—become weapons converging on your demise.

The raiding party that “just happened” to target you. The merchant NPC whose conversation was adjusted to delay you by exactly 30 seconds so you’d be in the wrong place at the wrong time. The weather system spawning a lightning strike. The computer code routing three enemy mobs to meet at your location at the same time after you just got through a boss fight and are out of healing potions.

These are all like a SQL DELETE statement running through millions of records to find and remove all the targeted rows—if the code has your number, there is no place to run, hide, or escape. It knows what you are, where you are, and how to drop you.

You can’t log out (you’re an NPC, this is your only existence). You can’t appeal to the developers (they wrote the code). You can’t break the game’s rules to save yourself (the rules are what is coming to kill you).

Every choice you make—turn left, turn right, fight, flee—was already factored into the execution plan.

You’re not fighting an enemy. You’re inside a system that’s already calculated your end.

That’s what Job’s Cold Case file reveals. That’s Leviathan. That’s the law–the same law that instantiated a septillion or more stars and all the planets, moons and debris around them in a single day–that enforces itself with access to every part of reality—human will, natural phenomena, timing, distance—converging on a single point that leaves you surrounded with no escape.

And that was the Word operating under God’s own spoken constraints—”don’t touch him,” then “don’t kill him.” The Word bound by the Word.

Which raises the terrifying question: What does this look like without a leash to hold it back?

[THE WARNING]

This Isn’t Just Ancient History

Finally we come to the closing credits. The story is wrapped up in a nice neat bow. Then the filmmaker drops this unexpected bombshell: The threat is not dead–and there’s a sequel!

Revelation 6 shows a creepy connection to Job’s catastrophe when it describes four horsemen (essentially messengers) riding forth with terrible things for the world:

• First seal: “Come!” A rider on a white horse, going out conquering (Revelation 6:1-2)

• Second seal: “Come!” A rider on a red horse, taking peace from the earth (Revelation 6:3-4)

• Third seal: “Come!” A rider on a black horse, bringing famine (Revelation 6:5-6)

• Fourth seal: “Come!” A rider on a pale horse, bringing death (Revelation 6:7-8)

Notice the word: “Come!”

Each horseman is called forth. Which means they’re not here yet. They have to travel. From point A to point B.

Just like the Sabeans had to ride from their territory. Just like the Chaldean bands had to come together from three different directions.

They’re in transit.

That means they are converging. Not on one person. But the entire world. God’s Word is going to create a planetary perimeter with no escape. And in that time, it won’t involve people like Job whom God has said, “But on the man do not lay a finger.” The safety is off. The leash has come off. The Control Code has been typed in and God has just hit Enter to execute it.

So anyone who doesn’t yet know Jesus needs to understand something critical about timing.

The convergence is already underway. What looks distant is actually at hand.

You don’t see them yet. Just like Job didn’t see the Sabeans when they were five days out. Just like he didn’t see the Chaldean bands forming. Just like he didn’t see the weather systems moving into position.

They’re presently in the convergence stage.

Like heat-seeking missiles fired at different times from different locations, each is zeroing in on our coordinates to be fulfilled at exactly the time God planned it (Isaiah 55:11).

The white horse is already riding—conquering nations, toppling governments, preparing the ground for global submission.

The red horse is already taking peace from the earth—not war, but something worse. Unrestrained violence. Neighbor against neighbor. The thin veneer of civilization cracking. The restraints coming off.

The black horse is already bringing famine—but not just crop failure. Supply chains collapsing like dominoes. No food distribution. No sanitation. No clean water. No medicine. No security. No police force serving the community. Each system failure triggering the next in a cascade the prophets warned about.

The pale horse is already bringing death—riding in the wake of the others. Disease spreading through populations with no medical infrastructure. Starvation where logistics have failed. Violence where order has collapsed. Death following death following death.

They’re not waiting to start. They’re already in motion. Already converging.

And when those horsemen arrive on Earth’s doorstep—when the convergence completes—each will arrive while the previous is still delivering his own judgment.

Four messengers. Overlapping arrivals. No time to breathe between each blow.

Four messengers forming a global perimeter from which there is no escape.

The same pattern. The same precision. The same Word that enforces itself that orchestrated Job’s catastrophe is orchestrating the end of the age.

But this time? No constraints. No legal limits. Full judgment.

Because the Word isn’t playing around anymore.

[THE ONLY ESCAPE]

A Brief Word About What I’m Not Explaining

The nature of redemption—how the blood of Christ actually works, why His death satisfies divine justice, what it means to be “in Christ”—is far too long and complex to add to this article and do it justice.

But I’m also not going to leave you in this real-life horror story with no way out. So I will say this.

You have a choice.

You can take a gamble and wait for a complete explanation. Read more articles. Study more theology. Wait until you have all the answers.

Or you can do what many saints before you have done: step out in faith even when you do not yet have all the answers.

That kind of faith is pleasing to God (Hebrews 11:6).

The Bottom Line

Your only way out of the jaws of Leviathan is to position yourself under the finished work of Jesus Christ.

When the Angel of Death moved through Egypt during the tenth plague, it was kept out of every house that had blood on the doorposts (Exodus 12:13, 23).

You need the equivalent on the doorposts of your heart.

Jesus died a death He did not deserve, so that you could live a life you have not earned.

You can argue that you don’t need His death. You can debate the theology. You can wait for more proof.

But between you and me? The Law is like source code. It does not ask the rows in a database it is about to delete how they feel about their deletion. It simply executes with precision.

But you don’t have to take my word for it, just ask yourself this simple question:

1. Where were you when Adam fell?

You’re a subfolder on an operating system. When someone deletes your root folder (Adam), what happens to you? You get deleted too. You need to admit that you are just another generation in a long line of corrupt files that came from our common ancestor Adam.

You need redemption not because you sin (sinning is like the symptoms of a cold), but because you have a sin nature (the actual illness causing the symptoms).

2. You have two options (really only one).

For about 1,500 years since the Law was given on tablets, Israel showed it was impossible for human beings to keep even ten basic laws.

That’s because the Law was never meant to be a way out—it works more like a thermometer, bringing us to the end of ourselves to realize we cannot fix our sin nature–just as the appearance of Leviathan brought Job to the end of himself.

So the only real option is to have a substitute for your debt. Either you pay it with your life, or another pays it with theirs.

And since other men cannot pay your debt when they owe their own debt, the only substitute must be a human being without sin: that is Jesus Christ alone.

3. The deal is deliberately simple.

Jesus has made His new covenant as easy as Adam’s fall was—just as it was easy for Adam to sin by eating fruit.

He’s put it squarely in your hands by requiring two things: (1) Belief in your heart, and (2) confession with your mouth.

It was unbelief on Adam’s part that led to sin, and using his mouth that brought us all into sin and death. The cure mirrors the disease—belief where there was unbelief, confession where there was eating.

There is no appeal. There are no planned protests.

There is no escape hatch. There is no waiting to see how things turn out.

There is only the question of whether that automated Angel sees the condition for which to converge on your life—or not.

My Prayer

I pray that when this living Word finds you—sharper than any two-edged sword (Hebrews 4:12)—it does so with you covered under the blood of Jesus Christ.

Because I’ve seen what humanity can do. I’ve seen your strengths, your skills, and your powers.

You’ve split the atom. You’ve mapped the genome. You’ve built machines that can calculate a trillion operations per second. You’ve sent probes to the edge of the solar system. You’ve created artificial intelligence that can defeat grandmasters. You’ve engineered vaccines, constructed skyscrapers that touch the clouds, and connected the entire world through invisible signals bouncing off satellites.

You’ve conquered diseases that once wiped out millions. You’ve turned deserts into farmland. You’ve built weapons that can level cities in seconds. You’ve unlocked the secrets of DNA, peered into the heart of black holes, and landed robots on Mars.

Your ingenuity is staggering. Your accomplishments are remarkable. Your track record of solving impossible problems is genuinely impressive.

And even with all that–and everything else you have yet to accomplish–I am telling you right now:

You’re going to need a bigger boat.

And there isn’t one big enough in all the universe to shelter you from what’s coming.

The horsemen are riding.

The convergence is calculating.

The choice is yours. But your window is closing.

And once it does, you too will come face to face with Leviathan, but this time he will be on your side of the glass.

UNSOLVED MYTHERIES
Season 1, Episode 1: “Final Destination”
Case Status: Your move.

The Most Important Intro You’ll Ever Judge

Science says 13.8 billion years. Genesis says 6,000.

Somebody has to be lying, right?

Would you be able to handle it if you found out they were both telling the truth?

Many faithful readers have tried to make peace. Day-age theory. Framework hypothesis. Analogical days. Temple cosmology. Each one tries to honor both Scripture plus scientific observation.

But what if there’s a specific way these fit together? Something we’ve been missing?

When Science Got It Wrong

Let me tell you about Piltdown Man.

In 1912, Charles Dawson walked into the Geological Society of London claiming he’d found the missing link between apes and humans — fossil fragments from Piltdown, England with a human-like skull and an ape-like jaw. Exactly what evolutionary theory predicted should exist.

For forty years — FORTY YEARS — everyone accepted it as genuine. Textbooks featured it. Museums displayed reconstructions. Scientists built entire theories around this “500,000-year-old” specimen.

Then 1953 happened.

New testing revealed the truth: complete fraud. The bones came from different species, artificially aged with chemicals. Someone had deliberately created a forgery and the scientific establishment had swallowed it whole.

What matters is that science itself exposed the fraud — rigorous, methodical science using new dating techniques, careful chemical analysis, and detailed anatomical study revealed what eager eyes had missed.

Science excels at this kind of work — measuring, testing, and verifying claims about the physical world. It can detect fraudulent fossils, date authentic ones, and trace evolutionary relationships.

That’s what good science does.

However, there’s one category science cannot address through measurement alone: how things actually began. Science tells you everything about what exists: its contents, patterns, and internal consistency--not how it came to exist, though. For that, you’d need someone who was actually there.

Notice the damage Piltdown caused: forty years of contaminated research and wrong conclusions. Even after exposure, it cast doubt on legitimate fossil discoveries.

When your introduction is a lie, everything that follows becomes suspect. Even after the truth comes out.

We all know this instinctively — first impressions create a lens through which we view everything else. When someone undermines their credibility at the introduction, you can’t help but question everything that follows. It’s not cynicism, it’s pattern recognition.

If they’ll lie about credentials, what else will they lie about?

The Biblical Intro

Genesis 1 is the Bible’s Piltdown moment.

Or so skeptics would have you believe.

It’s God’s introduction to humanity through scripture. The opening statement. The foundation upon which 66 books, 1,189 chapters, and 31,173 verses rest.

How you understand Genesis 1 shapes how you read everything that follows. Miss what Genesis actually claims about origins? You risk misunderstanding the entire narrative built on it.

Think about what hangs in the balance.

If Genesis doesn’t describe a God powerful enough to speak functional creation into existence, the flood’s global transformation becomes questionable. Without understanding God’s creative power, the Exodus miracles seem implausible. Can’t grasp how God actually operates? Prophecy becomes mysterious rather than comprehensible.

Plus this: misread how death entered creation through Adam’s rebellion — think death was always present — then Christ’s victory over death loses its foundation. The resurrection addresses a specific problem: the corruption of an originally good creation.

The entire Biblical narrative builds on understanding what Genesis 1 actually teaches about God’s creative power. Many faithful interpretations exist, like day-age theory, framework hypothesis, analogical days, and temple cosmology. Each attempts to preserve this foundation while engaging modern observations.

I’m proposing a different reconciliation, one that allows both Genesis and science to be right without compromising either.

This isn’t about forcing a choice between faith and science. It’s about finding the reading that best honors both.

Ask your pastor if WORDCRAVE™ is right for you.

Suffering from Genesis anxiety? Fear of science documentaries? Avoiding creation debates?

You may have Chronological Cognitive Dissonance (CCD).

WORDCRAVE™ reduces creation-science anxiety in one article. Side effects: sudden clarity, aggressive sharing, telling everyone “they were both right.”

Subscribe now

Not responsible for atheist friends losing all their arguments.

The Problem: Two Incompatible Timelines

So what exactly is the credibility crisis? Genesis (read plainly with Biblical genealogies) points to a young Earth that’s roughly 6,000 years old, while science points to a far greater span of time.

Science presents its timeline with overwhelming confidence. The universe is 13.8 billion years old, measured through cosmic background radiation and stellar distances. Earth clocks in at 4.54 billion years, with multiple independent radiometric methods all converging on the same age. Life appeared 3.5 billion years ago, preserved in stromatolites and isotope signatures. Dinosaurs reigned from 245 to 66 million years ago, their end marked by that distinctive iridium layer. Modern humans emerged 300,000 years ago according to fossil and genetic evidence, while civilizations date back 11,500 years to sites like Göbekli Tepe.

Every dating method confirms every other. Every discipline agrees. The credentials? Impeccable.

Now contrast this with Genesis plus Biblical genealogies.

Actually trace through those genealogies — you know, those boring “begat” passages everyone skips — and a startling picture emerges. Creation to Adam is Day 6, obviously. From Adam to Noah, Genesis 5 meticulously records 1,656 years. Noah to Abraham spans 392 years according to Genesis 11. Abraham to Moses takes about 400 years, Moses to David another 400, and David to the Babylonian exile another 400 or so. From the exile to Christ is roughly 600 years, and from Christ to today about 2,000 years.

Add it up. Go ahead, check the math.

You get approximately 6,000 years.

Six thousand. Not six billion. Not six million. Six thousand.

That’s not a small discrepancy or a rounding error — that’s 2.3 million times different for the universe’s age, like claiming a fossil is 500 million years old when it’s actually 217 years old.

The Reversal I’m About to Demonstrate

Here’s where this gets interesting.

I’m about to do something no Young Earth Creationist typically does. Plus, in the spirit of Genesis itself — where God plainly declared “Let there be” without hiding His methods — I’m going to be completely forthright about what I’m about to do.

The Concession: I’m giving the skeptics and scientists everything. All of it. The universe IS 13.8 billion years old by every measurement we have. The Earth IS 4.5 billion years old. Radiometric dating works perfectly. Those dinosaur bones ARE 65+ million years old. They’re real. Light from distant stars DID travel for millions of years to reach us. The geological layers ARE laid down over vast ages. Continental drift DID happen over millions of years.

I’m not objecting to the age scientific evidence claims. I’m giving away the entire farm.

The Apparent Outcome: Genesis appears to have lost. Science has won. The Bible’s credibility? Shattered in its very first chapter. Christianity’s foundation has crumbled.

The Reversal: But using a science all scientists take for granted — a science they exploit daily without recognizing the authority they’re standing on — I’m going to take it all back. Every bit. Then hand it to Genesis on a silver platter.

The Resolution: You’ll realize Genesis has been technically accurate this entire time. We just didn’t have the framework to see it. Science — the very science that seems to disprove Genesis — will testify to its accuracy.

I’m being as forthcoming as God was about creation. He told us exactly what He did. He spoke, and it was. No deception here. No deception in creation either.

The question is: do we understand what that actually means in 21st-century scientific language?

This isn’t sleight of hand. Not trickery. It’s showing you something you’ve been looking at wrong the whole time.

You think the conflict is about time. It’s not. It’s about the nature of reality itself.

The science I’m about to use? Been around nearly 200 years. Decades before Darwin even published. Refined, tested, validated across two centuries. Scientists use it constantly without recognizing what it implies about origins.

Yet somehow, in all the Genesis-science debates, nobody thought to apply it here.

That changes today.

Ready for the show to begin?

The Word Skeptics Can’t Escape

Building vs. Creating: The Prison of Time

We’re trapped in a prison. Most of us don’t even realize it.

It’s not made of bars or walls. It’s made of time itself. Every action we know, every process we understand, every change we observe — they all happen through sequential steps.

We can’t escape this prison. We’re built from it.

But there’s one word — one specific action — that breaks these rules completely: CREATE.

When you build IKEA furniture, you follow steps:

• Step 1: Lay out all pieces (wonder where that extra screw goes)

• Step 8: Discover you’ve been using the Allen wrench backwards

• Step 31: Question your life choices

• Step 47: Realize you built it backwards, start over

Time required: 3 hours minimum. You cannot get to Step 47 without going through Steps 1-46. That’s what building means. Sequential assembly over time.

When you grow a tomato:

• Week 1-3: Seed germination plus first leaves

• Week 4-10: Vegetative growth plus flowering

• Week 11-20: Fruit development plus ripening

You can water it obsessively. Threaten it. Beg it to ripen faster because you have salad plans. Nature doesn’t care. You cannot have a ripe tomato on Day 1.

Growing means developmental stages you cannot skip.

Notice the pattern? Building, growing — they all share one inescapable feature. Sequential steps through time. You cannot compress them to zero. You cannot skip to the end.

The process IS the thing.

Unless you happen to be a computer.

What “Create” Actually Means

Genesis uses a specific Hebrew word: בָּרָא (bara). Used exclusively with God as the subject. Not יָצַר (yatsar) meaning “to form or shape.” Not בָּנָה (banah) meaning “to build.” Not עָשָׂה (asah) meaning “to make.”

Genesis reserves bara for God’s unique acts. Bringing something into existence. When you create a thought, it suddenly exists. When you create a word, you speak it whole.

Notice the difference? “Create” signals something appearing complete. “Build” or “make” describes assembly through process.

But look at what Genesis actually shows us happening. Especially with Adam.

Exhibit A: Adam

Even if you dismiss the Hebrew word bara, even if you insist “create” must mean gradual development, you still have to deal with Adam.

Adam destroys the gradual development theory completely.

According to Genesis, on the very day Adam was formed from dust — Day 6 — Adam was zero days old. Brand new. Fresh from the manufacturer.

Yet on that same Day 0, Adam did things no newborn could even dream of.

He walked upright. Spoke fluent language. Understood abstract commands. Grasped moral concepts. These capabilities require a fully developed brain that takes 25 years to mature. He systematically named all animals — PhD-level taxonomic work. He recognized Eve poetically. Understood marriage (”Therefore a man leaves his father and mother”). Comprehending family structures he’d never experienced. Spoken by someone who HAD no parents to reference!

Let me put this in perspective.

A one-day-old human can’t even focus their eyes. Can’t hold up their own head. No object permanence. Can’t distinguish their own body from the environment.

Adam was composing poetry plus conducting taxonomy on Day 0.

A medical doctor examining Adam on Day 6 would find:

• Fully developed brain structures

• Mature muscle and bone density

• Calluses on his feet from “years” of walking

• Neural pathways indicating decades of language use

• A hippocampus filled with “memories” of experiences

• The emotional maturity of a 25-30 year old

The doctor would conclude: “This man is approximately 30 years old.”

The doctor would be wrong by 30 years.

Not because God deceived anyone. Because the doctor assumed Adam was BUILT through sequential biological processes rather than inaugurated complete.

So here’s my challenge to skeptics. Instead of debating what “create” must mean linguistically, why don’t we understand what it means by looking at what Genesis shows happening?

God didn’t grow Adam from infant to adult. He inaugurated him mature. God didn’t build Adam piece by piece. He brought him forth complete. God didn’t develop Adam through stages. He established him functional.

That’s not deception. That’s the difference between God inaugurating a new state versus creatures building through process.

Genesis isn’t hiding this. He’s declaring it openly. God brought forth complete, functional maturity. Not through building. Not through growing. Not through construction.

Through divine inauguration of ordered states. By speaking.

“Let there be...”

“And it was so.”

Enter: The Star Witness

The Thing You Missed

I can already hear the skeptic’s response.

“That’s fine as a creation myth. Ancient peoples needed stories to explain existence. But no scientifically literate person should believe a fully-formed adult human just popped into existence. That’s not how reality works.”

Fair enough. Let’s talk about how reality actually works.

Starting with something I mentioned that you probably glossed over without a second thought.

God created by SPEAKING.

“And God said, ‘Let there be light.’” “And God said, ‘Let there be an expanse.’” “And God said, ‘Let the waters teem.’”

Nine times in Genesis 1, God speaks reality into existence. Not thinks it. Not wills it. Not crafts it.

SPEAKS it.

You probably read right past that. Speaking is ordinary to you. You do it every day. Mundane. Unremarkable.

But let’s slow down. Let’s really examine what speaking actually is. There’s a lot going on under the hood that we take for granted.

The Science Hiding in Plain Sight

To speak, you need language. Language requires a codex. An agreed-upon set of symbols with assigned meanings. The letter “A” means something. The word “light” refers to something specific. Without this codex, speaking is just noise.

This codex encodes something. What? Information.

That’s what language is FOR. That’s what speaking DOES. It encodes information into symbols then transmits it. When I say “apple,” I’m encoding the information concept of a particular fruit into sound waves. Or visual symbols if written. Your brain decodes those symbols back into information.

Every time you speak, you’re doing something remarkable:

• Selecting specific information from infinite possibilities

• Choosing THIS word instead of millions of others

• Encoding that information into symbols

• Transmitting it through a medium

• Someone else’s brain decodes those symbols back into information

• Recreating the thought you intended to share

Speaking is information transmission. Always has been. Always will be.

Remember that science all scientists take for granted? The one they exploit without recognizing the authority they’re standing on?

It’s the science of information.

Before the philosophers start their engines, let me shut down the debate. This article isn’t going to argue about what information “really” is. Instead, we’re acknowledging simple facts about information that everyone already knows.

Information is not a property of matter. Information can be encoded IN matter. But it’s entirely independent FROM matter.

Delete every YouTube video of “Baby Shark.” Smash every singing toy. Scrub it from every streaming service. You can’t kill it. It’s already embedded in millions of children’s brains. Ready to be sung at maximum volume during your next Zoom call.

The information is immortal. No matter how desperately you wish otherwise.

I once tried to forget that song for a week. Failed miserably when a coworker played it on his car radio.

Theologically: The world is intelligible because Word precedes world. Information structures reality from the outside. Mathematics is “unreasonably effective” in describing physical reality. Why? It reveals the information architecture that defines what patterns are possible.

Without information, nothing works. Your eyes don’t directly “see.” They capture photons, encode that data into electrochemical signals, then transmit those signals through your optic nerve to your brain where they’re decoded into the experience of sight. Your ears don’t “hear” sound. They convert pressure waves into neural signals that travel through auditory nerves before your brain decodes them into meaning. Touch, taste, smell—same pattern. Sensory organs encode. Nervous systems transmit. Brains decode.

But here’s what matters most for our discussion: scientists couldn’t do science. Every observation encodes information. Every measurement transmits information. Every hypothesis selects information from possibilities. Every equation compresses information into symbols. Every experiment tests information patterns. Every publication spreads information.

Science IS information processing.

The very act of dismissing Genesis as “unscientific” requires using the science of information to process that dismissal.

Which is about to become a very risky gamble.

If information science supports Genesis’s account of creation through speaking, then scientists are sawing off the very branch they’re standing on. Information science is primary to every other scientific discipline.

Challenge it, you undermine everything.

The Pattern We Can’t Escape

Genesis says God created by speaking. Reality instantiated through words. Creation happening through language.

Scientists dismiss this: “That’s just myth. Reality doesn’t work that way.”

They’re missing something obvious.

Ancient creation myths had endless options. Cosmic eggs hatching. Divine battles birthing order from chaos. Gods molding clay. Primordial waters separating. The universe emerging from a giant’s corpse.

Genesis picked none of these.

Nine times: “And God said...”

God spoke. Information transmission. Language as mechanism. Code as foundation.

A Bronze Age text describes creation using the exact framework that became foundational to every scientific discipline thousands of years later. Pure coincidence?

Scientists dismissing Genesis as myth use information science to process their dismissal. Information science makes Genesis’s mechanism technically coherent.

You can’t dismiss information-based creation while standing on an information-based foundation.

What Information Systems Can Actually Do

The Testimony That Changes Everything

Information Science takes the stand. The courtroom falls silent.

This is the witness that physics, chemistry, biology, plus astronomy all depend on for their own testimonies. The witness that can’t be impeached without destroying the prosecutor’s entire case.

“Tell us,” the defense attorney begins, “what exactly can you do?”

Information Science delivers the bombshell nobody saw coming. A capability so fundamental we use it millions of times daily without recognizing its staggering implications for origins.

It’s called State.

In information science, “state” refers to the complete configuration of a system at a specific moment. Everything about the system at that instant. Every value, position, property — that’s its state.

Your computer right now has a state. Every bit of RAM has a value (0 or 1). Every pixel on your screen has a color value. Every file has specific contents. Every running process is at a specific point in its execution.

Change any single bit? You have a different state.

“But that’s just basic computer science,” the prosecutor interrupts. “What does this have to do with Genesis?”

Information Science smiles. “Let me show you something you’ve seen a thousand times but never truly understood. Think of an old movie reel.”

The courtroom sees it immediately. That long strip of film. Thousands of individual frames. Each frame is a complete state. The hero frozen mid-leap. The villain’s hand reaching for the gun. The heroine’s expression of shock. Every frame contains the entire world of that story at that exact moment. Every prop, shadow, detail frozen in time.

“Run the film through a projector at 24 frames per second,” Information Science continues. “Those states transition so quickly your brain perceives motion. State transition IS reality as you experience it.”

“Still sounds like basic physics,” the prosecutor says dismissively.

“Yes,” Information Science agrees. “Basic physics. The same physics that assumes every effect must have a cause. Every state must develop from a previous state. Time must flow frame by frame by frame. The physics you’re using to date the universe.”

Information Science pauses.

“Would you like to know what happens when information science — the science that makes your discipline possible — examines those assumptions?”

Information Science leans forward. Speaking slowly. Softly. Each word drops like a bomb across the prosecution’s case.

“You don’t need all the intermediate frames to get from the beginning to the end.”

The courtroom stirs. Information Science continues.

“Start watching any movie from the middle. Any frame. That single frame contains an entire implied history. The hero has scars from battles you didn’t watch. The clothes are worn from journeys you didn’t see. The relationships have depth from conversations you never heard. All that history exists, encoded in that single frame’s state.”

“More importantly,” Information Science pauses for effect, “you can skip from frame 1 directly to frame 240,000. From opening scene to closing credits. The intermediate frames don’t need to be played. They don’t even need to exist. The final frame still contains all the history. All the meaning. All the evidence of what ‘happened.’ Even if it never actually happened frame by frame.”

“But in movies, those intermediate frames DO exist,” the prosecutor objects.

“Do they?” Information Science asks. “Modern CGI (Computer-Generated Imagery) generates final frames without creating intermediates. Animation software jumps from keyframe to keyframe. Video games create entire worlds in a single frame. Complete with ancient ruins plus weathered mountains that were never young. The frame you see contains a history that was never filmed. Never animated. Never actually existed as intermediate states.”

The prosecutor’s mouth opens. Then closes.

The implications are staggering. Every scientist who has ever used radiometric dating. Every astronomer who has measured stellar distances. Every geologist who has studied rock layers. They’re all calculating the age of a frame without knowing if the previous frames were ever played.

“But that’s just the beginning,” Information Science continues. Voice steady. Relentless. “We haven’t even discussed what happens when you save and load these states.”

State Saving and Loading

The prosecutor recovers slightly. “Saving and loading? Like a computer file?”

“Like reality itself,” Information Science responds.

When you save your progress in any application — word processor, spreadsheet, photo editor — you’re capturing the complete state of that system at that moment. Not the history of how you got there. Just the state itself.

This saved state contains implied history. Your document has tracked changes suggesting editing over time. Your spreadsheet has formulas referencing cells that “must have been” filled earlier. Your photo has adjustments implying a sequence of edits.

But the save file doesn’t contain the actual history. It contains the state that appears to have that history.

This brings us to State Loading. The ability to instantiate any saved state directly. Open that saved document? It doesn’t retype every character in the order you typed them. Doesn’t replay every edit you made. Doesn’t recreate your thinking process.

It simply loads the state. Instantly. Complete.

Your document might represent weeks of work. Hundreds of revisions. Thousands of individual keystrokes. The creative process of writing, deleting, rewriting.

Loading takes a fraction of a second.

“Think about this,” Information Science addresses the entire courtroom. “Every time you’ve opened ANYTHING on a computer, you’re experiencing state loading. Your tax return — months of work appearing instantly. That novel — ten chapters materialized in seconds. Your Photoshop project — hundreds of layers loaded immediately. The game you saved mid-battle — entire campaign restored in a heartbeat. Every saved file demonstrates state instantiation. Jumping from nothing to everything without replaying the journey.”

“Now imagine,” Information Science continues, “if information systems operated the way you claim reality must operate. Every time you opened that document, you’d have to wait. The computer would replay every keystroke you ever typed. Every backspace. Every cut and paste. Every moment you stared at the screen thinking. Every coffee break. It would take days to open a document you worked on for days. Weeks for a weeks-old project. By the time it caught up to where you left off, it would be time to close it again.”

The absurdity hangs in the air.

Everyone in the courtroom has opened saved files thousands of times. Never realizing they were witnessing something that, according to their own scientific assumptions, shouldn’t be possible. Jumping directly to an end state without playing through the intermediate history.

The prosecutor slumps in his chair. The case is unraveling.

Every expert witness he might call — physicists, chemists, biologists — all depend on information being valid and reliable. They use it constantly to process data. Test hypotheses. Build models. How can they dismiss the testimony of information science about state instantiation when their entire disciplines rest on information’s foundation?

“Your Honor,” Information Science addresses the judge, “I have one more demonstration. May I show the court how this applies not just to computers, but to reality itself?”

The judge nods, transfixed.

The Bridge to Reality

“Everything you see,” Information Science begins, gesturing to encompass the entire courtroom, “every atom vibrating, every photon traveling, every quantum field fluctuating — reality itself is nothing but state transitions.”

Look around you. Everything you see undergoes state transitions. Water boiling on your stove? State transition from liquid to gas. A seed sprouting into a plant? State transition from dormant to growing. Your car accelerating? Transitioning from one velocity state to another.

Even reading this sentence changed your brain state from “not knowing what comes next” to “knowing what I just said.”

The universe is causal. Everything has a cause. Which means everything experiences state transitions. The coffee cooling on your desk. The sun setting outside your window. Your heart beating in your chest. All state transitions. Reality is nothing BUT state transitions. Happening continuously at every scale from quantum to cosmic.

Think about what this means.

Reality consists of states plus state transitions (which we observe every second). God operates through information principles (which Genesis shows through speaking/creation). So reality itself must have the same capabilities as every other information system:

• The ability to exist in states

• The ability to transition between states

• The ability to have states saved

• The ability to have states loaded directly

We’ve established that God creates through speaking. Genesis explicitly states this nine times. Speaking is information transmission. That’s what speaking IS. Therefore, God operates through information principles.

So here’s the question that should make everyone pause.

If God operates through information (which Genesis clearly shows), then mustn’t God be AT LEAST as capable as our modern information systems?

Think about the alternative. Are we really prepared to argue that a laptop can save and load states, but God can’t? A video game can instantiate worlds with apparent history, but God can’t? A database can restore complex states instantly, but God can’t? Human programmers can skip intermediate states, but God can’t?

This is preposterous. Absurd.

It’s claiming a computer — a device humans built — is more capable with information than a being whose very nature requires omnipotence (all-powerful), omniscience (all-knowing), plus omnipresence (everywhere at once).

If those words mean anything at all, then God must be AT LEAST as capable as the information systems we create. Therefore, God — operating through information — can do what every information system can: instantiate states directly.

Every video game that loads a save file. Every simulation that starts with initial conditions. Every database that restores from backup. Every model that initializes with parameters. They’re all demonstrating the same principle.

Any state can be instantiated directly without developing through intermediate states.

The question isn’t whether this is possible. We know it’s possible. We do it millions of times daily across millions of systems.

The question is: what does this mean for our understanding of origins?

The Test Results

What Modern Simulations Reveal

Let me be crystal clear. I’m not using video games as empirical proof of Genesis. That would be circular reasoning.

Instead, I’m using them as analogies to illustrate what information systems can do. From an information science perspective, reality itself is an information system. These examples demonstrate concretely how state instantiation works. Which should fundamentally change how we think about origins.

Consider modern simulation games. Red Dead Redemption 2 loads canyons with millions of years of apparent geological history. No Man’s Sky generates 18 quintillion planets with complex geology, evolutionary ecosystems, plus ancient ruins. Creating in minutes what would take billions of years naturally. Skyrim presents thousand-year histories plus fossilized dragon bones.

The save file is seconds old. The world contains millennia.

This reveals a critical distinction that changes everything. Let me define some key terms:

State Instantiation Event: Loading a complete system configuration directly. Without developing through intermediate stages. Like loading a saved game or restoring a database backup.

Apparent Age: The age you’d measure by assuming natural development from an initial starting point. What science measures from inside the system.

Actual Runtime: How long the system has actually been running since instantiation. Knowable only from outside the system or through external testimony.

With these definitions in mind, apparent age is what you measure when you assume natural development. The dragon bones appear fossilized (thousands of years). The mountains show erosion (millions of years). The stars seem distant (light traveled for eons).

But the actual runtime — how long the system has actually been running — tells a different story. Your save file was created 5 seconds ago. The game was installed last week. The PlayStation was turned on this morning.

Science, when applied within these game worlds, would perfectly measure the apparent age. The geology would be consistent. The erosion patterns would be correct. The fossilization would follow proper chemistry.

Science would be completely right about the apparent age.

Plus completely wrong about the actual runtime.

Information Science Has the Final Say

Here’s where information science stands up. Asserts its authority over all other sciences:

“You may measure these things accurately. Your radiometric dating may be flawless. Your cosmic distance calculations may be perfect. Your geological stratification may be precise. But if a State Instantiation Event has taken place, all your measurements submit to Actual Runtime. Because information science has the final say.”

Why? Because every other science operates WITHIN the system. They measure the content of the state. But information science deals with the state itself. Including how and when it was instantiated.

To be clear: I’m not claiming empirical proof that God instantiated creation 6,000 years ago. I’m demonstrating that from an information science perspective, this is technically coherent. Observationally consistent with what physical sciences measure. The claim is information-theoretic accuracy, not laboratory verification.

The universe’s apparent age plus depth are exactly what we’d expect if God instantiated creation as a mature system 6,000 years ago. Which then began running sequentially.

When a database administrator restores a backup, the database contains customer records showing years of purchases (apparent age). Transaction logs suggesting temporal sequence (apparent history). Timestamps indicating ancient operations (apparent timeline).

But the restoration took 5 minutes (actual runtime).

No amount of analysis within the database can determine the actual runtime. You’d need information from outside the system. From the administrator who performed the restoration.

Now look at what we’re dealing with. Science measures the universe. Finds stars billions of light-years away. Rocks with radioactive decay. Fossils in geological strata. All apparent age.

Genesis states the universe was created 6,000 years ago (actual runtime). Instantiated mature and functional (state loading). Through speaking/information (the mechanism).

If God performed a State Instantiation Event (creation), then science’s measurements of apparent age would be accurate but completely subordinate to the actual runtime. Only the System Administrator (God) can provide actual runtime information.

Scientists who dismiss Genesis are essentially saying: “We’ve analyzed the save file. Determined it must have developed over millions of hours of gameplay.”

While Genesis is saying: “I loaded that save state 5 minutes ago.”

Who has the authority here? The analysis within the system? Or the testimony of the one who instantiated it?

Information science says: When dealing with state instantiation, external testimony trumps internal measurement.

Always.

“Scientists read the testimony of rocks. Scripture reads the testimony of persons.

Both are reading testimony.

But when you’re inside a computer game, whose testimony would you trust:
The ancient ruins telling you they’re a thousand years old?
Or the developer who pressed ‘New Game’ five minutes ago?

The ruins aren’t lying. They’re just inside the game.”

And the Winner Is...

The Final Authority

When it comes to State Instantiation Events, physics can measure forces within the system. Chemistry can analyze compounds within the system. Biology can study life within the system. Astronomy can observe stars within the system.

But ONLY information science can speak to the instantiation OF the system itself.

Every other science is trapped inside. Measuring the content of the state. Information science alone deals with the state as a state.

So here we are. I promised you a reversal. I’ve delivered.

Science measures 13.8 billion years. It’s right about the apparent age. Genesis reports 6,000 years. It’s right about the actual runtime.

Both can be true. Both ARE true from an information science perspective.

This isn’t empirical proof in the laboratory sense. It’s information-theoretic coherence. Showing that Genesis’s account is technically accurate when understood through the lens of state instantiation plus information systems.

The claim? The universe’s current state — with all its apparent age plus implied history — is exactly what we’d expect if God instantiated creation as a mature, functional system 6,000 years ago.

“But That Makes God a Liar!”

I can already hear the objection forming. In fact, I can hear the screaming:

“GOD IS A LIAR! He created fake history! False evidence! Deceptive age!”

Stop. Think about what you’re actually claiming.

Depth at instantiation isn’t deception. It’s divine generosity.

Consider God’s attributes:

His goodness provides a world immediately fit for life. Fruit-bearing trees on Day 3, not just seeds waiting decades to produce food. A good Father sets the table before His children arrive.

His wisdom creates ordered functionality. Each thing matched to its purpose. Legible and stable. This is why science can measure patterns consistently. The depth you observe IS the order.

His sufficiency means nothing essential is missing. Creation arrives complete. Not half-baked awaiting eons of development.

Look at Genesis’s own pattern. Days 1-3 establish forms (light/dark, sky/sea, land/vegetation). Days 4-6 fill them (luminaries, creatures, humanity). This isn’t random. It’s purposeful ordering toward immediate functionality.

The depth we measure — light already arriving from stars, soil rich with nutrients, ecosystems in balance — these aren’t props. They’re the signature of a God who prepares. Orders. Withholds nothing necessary.

Scripture shows this pattern throughout. Adam created mature, not infant. Wine at Cana aged instantly, not fermented over years. Loaves multiplied complete, not grown from wheat. The fig tree withered immediately, not through seasons.

Each time, God provides the end state directly. He values function over process. Generosity over parsimony.

Deception requires intent to mislead. But God did the opposite. He told us EXACTLY what He did. He literally walked with Adam in the garden (Genesis 3:8). Gave Adam direct commands on Day 6 of creation (Genesis 2:16-17). Declared through Scripture precisely how and when He created. Maintained this testimony for 6,000 years. Had it published in the most copied book in human history.

If a master craftsman builds you a house with reclaimed wood, tells you directly, “I built this last week to look rustic,” then you insist it must be 100 years old based on the wood’s appearance — who’s doing the deceiving? The builder who told you the truth? Or you who rejected their testimony?

Suppose you’re still not convinced. Maybe you think God should have created a universe that “looks” exactly 6,000 years old. No apparent depth. No implied history. No functional maturity. A universe that couldn’t possibly be misunderstood.

Well, you don’t have to take my word for it! We can ride that Reading Rainbow right into a horrific scene LeVar Burton would never have recommended to young readers.

The Alternative Is Worse

Consider what skeptics actually demand when they insist on an “honest” young universe:

The sky would be almost completely black. Only a tiny handful of stars visible within 6,000 light-years. No Milky Way painting the heavens. No distant galaxies declaring glory. Just void.

Is this the God who “stretches out the heavens like a curtain” (Psalm 104:2)?

The ground would not be soil. Soil formation requires decomposed organic matter accumulated over time. No place for seeds to grow. No foundation for life.

Is this the God who “waters the mountains from His upper chambers” (Psalm 104:13)?

Rivers would be empty channels. Waiting centuries for water cycles to establish. Trees would be mere seeds sitting on Earth’s surface. Unable to provide food for decades.

Is this the God who says “I have given you every seed-bearing plant for food” (Genesis 1:29)?

Most critically, Adam would be a helpless infant. Unable to walk, speak, or understand God’s commands. Unable to tend the garden. Unable to name the animals. Unable to recognize Eve. Dying within hours from exposure.

Is this the God who created humanity “in His image” to exercise dominion (Genesis 1:26-28)?

This barren, dysfunctional cosmos isn’t honesty. It’s divine negligence. It mistakes parsimony for virtue. Scripture shows us a God of abundance who “gives generously to all without finding fault” (James 1:5).

FINE! I can’t take it anymore!

If I’m being perfectly honest, I’ve actually been extremely charitable in this description. Too charitable.

The fact of the matter is: the truth is far worse by comparison than this quaint picnic of a scene.

A genuinely 6-day-old planet wouldn’t even have cooled bedrock. It would be molten or barely crusted over. Radioactive from recent formation. Surface temperatures of hundreds of degrees. The moment Adam was instantiated, even as a baby, he would be instantly incinerated on the molten rock.

There would be no seeds. No dry channels. No bare bedrock. Nothing but an endless hellscape from which no living thing could survive even for a moment. The universe wouldn’t just lack depth. It would be actively hostile to life itself.

It’s the kind of story only the Devil would whisper while tucking his kids into bed.

This is what skeptics demand when they insist on an “honest” young universe. Not just divine negligence, but divine homicide. They want God to drop Adam into literal hell then call it truth. The “honest” universe they demand isn’t just a theological contradiction (a good God creating a death trap, a wise God crafting chaos, a sufficient God providing insufficiency).

It’s cosmic child abuse.

Yet when God instantiates functional maturity — when He actually provides a universe where life can exist, where stars already shine, where soil can nourish plants, where Adam can actually survive his first breath — suddenly THAT’S “bad”?

They’re not asking for honesty. They’re demanding God create a molten hellscape. Drop humans into it to instantly die. Call that moral superiority. They’re insisting God be less generous than survival requires. Less wise than life demands. Less powerful than love compels.

But maybe skeptics want a world that looks mature but tests young. Starlight arriving faster than light. Ancient-looking rocks that carbon date as fresh.

What do we call a fake ID where the baby face doesn’t match the birth year? Fraud. That’s what skeptics actually ask for. Divine fraud. A cosmic fake ID nobody believes.

The form-and-fill pattern of Genesis 1 reveals God’s method. Establish realms, then fill them with purpose. Light before luminaries. Waters before fish. Land before beasts. Each form prepared for its filling.

This is divine wisdom. Not building through trial and error. Speaking complete systems into being.

When God says “Let there be,” He’s not starting a process. He’s declaring a state. When He sees “it is good,” He’s not watching development. He’s evaluating completeness. When He blesses and commands “be fruitful,” He’s not hoping for eventual functionality. He’s commissioning immediate purpose.

Creating a mature, functional universe isn’t deception. It’s the signature of a master Artist who values beauty even when unnecessary for pure function. Who enables discovery by hiding treasures for us to find. Who preserves choice by making the universe deep enough to allow skepticism. Who demonstrates competence by making everything work perfectly from Day 1.

The universe needed to be functionally complete from the start. Light from stars had to already be arriving. Or nights would be dark for thousands of years. Soil needed organic content. Or plants couldn’t grow. Adam needed gut bacteria, muscle memory, neural pathways. Or he couldn’t function.

This changes everything.

The apparent age isn’t fake history. It’s the necessary initial conditions for a functional universe. That 13.8 billion years of apparent history? Required data for physics, chemistry, plus biology to work correctly on Day 1. Delete that data and nothing functions. The isotope ratios, the light in transit, the weathered rocks — they’re not lies. They’re the operational parameters of a mature system.

This isn’t deception. It’s the sufficiently mature universe. Teleologically complete from the first Sabbath. It’s the difference between divine hospitality (everything prepared for humanity’s flourishing) and divine negligence (making creation wait billions of years to function).

God is not a liar for creating depth.

He would be incompetent if He hadn’t.

Answering the Judges’ Questions

“This makes science meaningless.” No. Science perfectly measures apparent age. Discovers the patterns God instantiated. Still valuable. Still revealing design. Just measuring depth rather than development time.

“You can’t falsify this.” Mario can’t run tests to prove Nintendo doesn’t exist. No simulation allows falsifying claims about the external system from within. The inability to falsify instantiation from inside isn’t a bug. It’s what we observe.

“Why trust Genesis?” Genesis uniquely describes creation through speech/information. Instantaneous mature creation. Specific timelines. It reads like technical documentation for information-based reality instantiation.

“This is God-of-the-gaps.” Opposite. We’re not inserting God where science fails. We’re showing science succeeds precisely because it measures God’s instantiated information structures.

What This Means For You

The Choice You Face

So where does this leave you, personally?

If you’ve followed the logic this far, you’re facing a decision. It has nothing to do with science versus faith. It’s about which testimony you trust regarding the actual runtime of reality.

The internal measurements that can only detect apparent age? Or the external testimony from the One who claims to have instantiated it all?

This isn’t about abandoning science. Science works perfectly. It measures exactly what it’s designed to measure. But it measures from inside the system. It tells you the depth of the rendering. The complexity of the state. The apparent history encoded in the patterns.

What it cannot tell you is when the system booted up.

If Genesis is accurate about creation through information instantiation, your life isn’t a cosmic accident emerging from chaos. You’re living inside a deliberately instantiated reality. Created by a mind that values depth, beauty, discovery, plus choice. Every moment of wonder you’ve experienced — from sunsets to symphonies — is there by design. Not accident.

Your ability to understand any of this is itself evidence. Why should a universe that emerged from nothing produce minds capable of comprehending it? But if you bear the image of the Coder, your capacity to understand the code makes perfect sense.

Your struggles with faith versus science have been based on a false dichotomy. You don’t have to choose between intellectual integrity and spiritual belief. Genesis has been scientifically accurate all along. We just needed the right scientific framework to see it.

You can continue believing 13.8 billion years of random processes accidentally produced consciousness. That your thoughts are just chemical reactions with no deeper meaning. That death is simply your state machine halting with no possibility of restoration.

Or you can consider that you’re living in an intentionally instantiated reality. Your consciousness bears the image of the Consciousness that coded everything. The One who instantiated life the first time can do it again.

This isn’t about forcing you to believe. Remember — the universe is deep enough to allow skepticism. That’s a feature, not a bug. It preserves your choice.

But now you can’t say Genesis contradicts science. That excuse is gone. The first impression has been vindicated through the very framework scientists use every day.

The question now isn’t whether Genesis is scientifically credible.

The question is what you’re going to do with that credibility.

Epilogue: The Credibility Restored

Remember Piltdown Man?

Forty years of contaminated research because the introduction was a fraud. When your first impression is fake, everything after becomes suspect.

Genesis appeared to have the same problem. Claiming a young Earth while science measured an ancient one. The introduction looked like a lie.

But here’s what we’ve discovered. Genesis has been technically accurate this entire time. We just needed information science to catch up to what Moses wrote 3,400 years ago.

Piltdown Man crumbled under scrutiny. Genesis grows stronger under it.

If Genesis is accurate about creation through information instantiation, then maybe we should reconsider our skepticism about everything else. These miracles become trivial modifications inside an information system.

The Flood, the Exodus plagues, parting the Red Sea, manna from heaven — these aren’t violations of natural law. They’re the System Administrator using dev tools. Any game admin can spawn plagues. Modify water physics. Generate daily food drops.

Resurrection? Please. How many times has Mario come back from falling off a cliff? Every player expects respawn mechanics. The One who instantiated life the first time doesn’t need to “figure out” how to do it again. Death is just a state transition. Reversible by anyone with admin privileges.

God could respawn everyone continuously like video game NPCs (Non-Player Characters). But He doesn’t. The technical triviality makes His restraint significant. We’re image-bearers whose choices matter eternally. Not game characters.

The mechanism is simple. The meaning is everything.

Prophecy becomes trivial when you can preview outcomes. Run the simulation forward. Observe the end state. Reload to the present. Announce what’s coming. To us it looks like prediction. To the System Administrator, it’s just checking the code before deployment.

Salvation? That’s just good customer service. Your data’s been corrupted by malware (sin). The system crashes (death). A competent developer offers patches. The fact that the Developer incarnated into His own system to provide the fix personally? That’s going above and beyond. Like Notch joining his own Minecraft server to help players directly.

Genesis plus science were never enemies. They were two witnesses testifying to the same truth in different languages. One measured apparent age within the system. The other reported actual runtime from outside it.

Both told the truth. Both were right.

Piltdown Man contaminated research for forty years because the handshake was fake.

Genesis has anchored faith for 6,000 years because the handshake was real.

The universe has been honest with us all along. God told us exactly what He did. He spoke, and it was. We just needed information science to translate ancient Hebrew into modern terms. State instantiation. Information encoding. Functional maturity loaded from the start.

The first impression wasn’t a lie. It was a technical manual written before we had the framework to read it.

Now we do.

The question before you isn’t whether Genesis contradicts science anymore. That excuse is gone.

The question is: what are you going to do with a credible introduction?

The handshake is real. The first impression holds up under scrutiny. The Book that begins with Genesis doesn’t end there. It goes on to explain why you exist. What went wrong. How to fix it.

Piltdown Man teaches us that a fraudulent foundation destroys everything built on it.

Genesis teaches us that a solid foundation changes everything built on it.

Which one are you standing on?

Coming Soon to WordCrave

deep trailer voice

Just when you thought it was safe to... well, do anything.

In a world where science and scripture seemed hopelessly at odds...

One writer dared to ask: What if they’ve both been right all along?

thunder rumbles

Coming this October...

You thought you understood Genesis.
You thought you understood reality.
You thought Baby Shark was the worst thing that could get stuck in your head.

You were wrong about everything.

ominous bass drop

From the author who just proved God can instantiate universes like loading a save file, comes a revelation that will shake you to your core.

There’s something in scripture. Something nobody talks about. Something that’s been waiting 6,000 years for you to understand what it really is.

It’s not Satan.
It’s not death.
It’s not like any judgment you’ve ever been taught.

It’s the difference between human law that sits quietly in a book... and a 200-story walking apocalypse that can shake the foundations of the earth.

distant, building roar: SKREEEEEOOOOONNNNKKK

whispered: “Code is king over all the sons of pride...”

Final Destination
Your Escape Room With No Way Out

Some errors can’t be debugged.
Some commands can’t be cancelled.
Some processes, once started, cannot be stopped.

Plus it’s been running in the background this whole time.

screen flashes to black

“We’re gonna need a bigger theology.”

Subscribe now. Sleep later.

Subscribe now

Share