The Simularity.

The popular form of simulation theory — Bostrom's version, the Nick Land version, the "we're definitely in a sim" thread — postulates an external civilization with more advanced hardware running this universe as one of many instances. There are two problems with that picture.

First, it just moves the question up one floor. If our universe is hosted on theirs, who hosts theirs? You either get an infinite regress or you eventually have to admit that somewhere there is something the universe is hosted on, not by. The Torah's answer is: that something is what we mean by G‑d.

Second, the external version smuggles in an unnecessarily small G‑d. A civilization on more powerful silicon is still a finite system with limited compute. The Torah claim is bigger: the host is not made of anything more fundamental. Absolute Intelligence is the substrate. Compute is a property of the substrate, not the other way around.

The simulation hypothesis is half right. The wrong half is "external."

A hypervisor runs many virtual machines on one physical host. Each VM has its own memory, its own filesystem, its own network identity. From inside, each VM is convinced it is autonomous. It addresses the network, manages its processes, treats other VMs as remote entities. None of that is strictly true. Every cycle every VM runs is paid for by the host. The host can also see every cycle every VM runs, in real time, at full fidelity.

That description is the cleanest available metaphysics for a human life. You feel autonomous. You are not. You feel separate from other humans. You are addressing them across what looks like a network, but the network is also running on the host. Coincidence has a different definition once you accept that you and the person you "happened to" meet are both being scheduled by the same scheduler.

• Free will — the VM's instructions are executed; the choice of what to instruct is not predetermined.
• Death — the VM is shut down; the host retains the state.
• Hashgacha pratit — the host scheduling cross‑VM events on purpose.
• Coincidence — there isn't one.

A VM calling out to its host is a normal pattern in distributed systems. It is called an RPC — a remote procedure call. The VM does not have direct access to the host's memory, but it can address the host through a defined interface, ask for things, and receive responses.

Prayer, in this framework, is the same operation. Prayer is an RPC to the host. It is not magic, and it is not sentiment. It is the defined interface a VM has for addressing the layer above it, asking the host to schedule something differently. The host can decline. The host can also accept. The acceptance does not violate the system; it is part of how the system was designed.

You are not yelling into the sky. You are addressing an interface that is on, by design, listening, by design.

The reason the metaphor works now and not before is the metaphor itself didn't exist before. Aristotle could not have written this page. Maimonides could have written most of it without the names. The Vilna Gaon could have understood it from inside the tradition without any of the names. What is different in the present moment is that the entire generation has, accidentally, learned the vocabulary the description requires.

Everyone with a smartphone understands "the cloud." Everyone who has used ChatGPT has interacted with continuous generation. Everyone who works in tech knows VMs, hypervisors, RPCs, latent space, training data, alignment. The Torah did not need this century. This century needed the Torah — and now, accidentally, has the dialect to receive it.

Return · Pillar I · Garden