I'm a programmer, not a theologian. A few years ago I was agnostic, a deconverted Christian, and willing to ask one question: if a creator exists and stays hidden (because I don't see anyone watching), what would that look like?
The closest model we have today is a simulation, and it's opened up an entirely new category of questions we can ask about our reality. It may be a bounded world that the maker can see into but the people inside can't see out of. Think of The Sims: You can see them, but they can't see You. But in this series, we are The Sims.
I thought about it for months and devised a probable set of markers to look for in ancient religious texts. Several texts showed several of them. I knew the Christian Bible best, so I started there. I already knew the basics, but I never had considered simualtion with it. I emptied my head of all theology and started at the beginning. I looked at what God said and did.
If anyone is gathering meaningful data, the rules, judging by what we actually observe around us, are these: stay deniable, intervene minimally, and never reveal the mechanism or the test. Under those rules, religion makes the perfect interface.
Here is what I found, as simply as I can put it.
Genesis 1: The Build#
Light, then sky, then land, then life, then people. Each step depends on the one before it, and each ends with a check: "and God saw that it was good."
That's what a build looks like: the environment is assembled in order, and each layer is tested before the next one goes on.
Genesis 2: Deployment and First Test#
Man is formed and placed into the finished environment. Then comes a test of novel output: God brings the animals to Adam "to see what he would call them" (Genesis 2:19). The maker doesn't supply the names. He waits to see what the new system produces on its own.
Then man is branched. Woman is taken from Adam's side, a copy made from the now verified and tested original that can then run independently, and together they can populate the environment.
Genesis 3: The Deviation Test#
There is one instruction: don't eat from one tree. They even repeat it. The humans eat anyway. They can deviate, and that's the point. A test of choice only means something if the wrong choice is possible.
Then God asks three questions. For an all-knowing being, these are strange questions, unless each one is doing a job.
"Where are you?" (3:9). The observer wasn't present when the choice was made. The decision happened unobserved, so it wasn't distorted by the subject knowing they were being watched. (Researchers call that distortion the Hawthorne effect.)
"Who told you that you were naked?" (3:11). Verifying the new awareness didn't come from outside the enviroment.
"Have you eaten from the tree?" (3:11). This confirms the deviation on the record, with the subject's own admission.
Genesis 4: The Scale Is Set#
Cain and Abel bring offerings. One is accepted, one isn't. God warns Cain: "sin is crouching at the door… you must rule over it" (4:7). Cain kills his brother anyway.
Deviation now has a range, from a missing the mark all the way to willful rebellion. By the end of the chapter, Lamech boasts that his vengeance is seventy-sevenfold (4:24). The scale is not only set; it's climbing. Sacrifice appears here too, as a way of accounting for deviation.
Genesis 5–10: Saturation and Backup, Reformat, Restore#
Deviation spreads until "every intention of the thoughts of his heart was only evil continually" (6:5). The system is saturated.
So it goes through the standard recovery sequence:
Backup: the last good state is saved. Noah, "blameless in his generation" (6:9), his family, and the animals go into the ark.
Reformat: the flood wipes the corrupted environment.
Restore: the backup is brought back out onto clean ground (8:15–19), and chapter 10 lists the nations as the restored system repopulates.
Genesis 11: Babel and the Firewall#
People learn to make baked bricks and use bitumen for mortar (11:3). It's the first manufactured building material, the beginning of industrialization.
God sees where it leads: "nothing that they propose to do will now be impossible for them" (11:6). That's a trajectory toward god-like capability inside the test.
The response isn't destruction. It's encryption. Language is confused (11:7), so knowledge can no longer move freely between groups. Humanity is split into firewalled segments that can't pool what they know.
With saturation looming again, there's no second flood. The firewall slows the climb instead and buys millennia before the system reaches that point again.
And it leaves humanity segmented into groups.
Genesis 12–Malachi 4: The Test Group#
With humanity now separated into compartmentalized groups, God selects one man, Abraham, and through him one people group, Israel. From here, the Bible becomes the record of a test group. It documents their choices, their deviations, the corrections, and the gradual elimination of variables, over centuries.
Revelation 20–22: Audit and Migration#
The end of the Bible closes the loop the beginning opened.
The audit: "the books were opened… and the dead were judged by what was written" (20:12). Everything recorded is reviewed.
Pass: those who pass are migrated to a clean environment, "a new heaven and a new earth" (21:1), where "nothing unclean will ever enter" (21:27).
Fail: the corrupting agents are removed and destroyed (20:10, 14). They don't come along to the new system.
A test needs a start and an end. This one has both: initialization in Genesis 1–3 and a final state in Revelation 20–22.
What This Is, and What It Isn't#
This isn't an argument that Christianity is true, or that any particular reading of the Bible is correct. Other explanations fit the same stories, and some passages don't fit this one neatly. I'd rather name those than hide them.
It's a narrower observation. If a hidden architect ran a test of free choice and left documentation behind, it would need a build, a deployment, a way to deviate, a scale, a restore, a firewall, a test group, an audit, and a migration. Genesis and Revelation contain every one of those, in roughly that order.
Turn it around and the fit is just as close. If we set out today to deploy a test of free choice, this is close to how we'd design it: a clean build, a single instruction, unobserved decisions, backups, segmentation, a selected test group, and a final audit. And somewhere inside the environment, we'd leave a readme.txt, written in the users' own language, explaining just enough to guide them without exposing the machinery. The Bible reads a lot like that file.
That's strangely cohesive for texts written thousands of years before anyone had built a simulation.
Don't take a programmer's word for it. Read Genesis 1–11 yourself with this lens, and see whether it holds.
Remember the Definition Of Simulation#
Google defines it as: a simulation is the imitation or re-creation of a real-world system, process, or event using a model, to see how it works or how it behaves over time.
Or, as I define it throughout this series: a substrate-agnostic, bounded test environment designed to allow variables to collide with consequences, where the results are observable, auditable, and meaningful to an external architect.
Either way, the idea is the same.
And if your first reaction to reading this is "We aren't in a simulation" remember, that's exactly what a well-designed simulation would want you to think. Seriously, though, I'm not saying we are. I'm saying that if we were, it would look like this,