Stochastic humans and deterministic agents

I build agent systems for a living: model sessions wrapped in folder structures, scripts, and rules that decide what the model may touch. I am also a Christian who reads Genesis slowly. For a long time those were two separate rooms in my head. This year the wall between them came down, and what walked through the gap was an argument about free will that I have not been able to put down since.

Start where the text starts. God builds the deterministic layer first. The lights in the firmament are installed "for signs, and for seasons, and for days, and years" (Genesis 1:14): a clock and a calendar, infrastructure that never improvises. Physics gets no discretion. The sun has never once decided to rise late.

Then he makes a creature that can decide, places it in the garden "to dress it and to keep it" (Genesis 2:15), and does something strange for a creator who could have specified anything: he specifies almost nothing.

One constraint, stated once

"Of every tree of the garden thou mayest freely eat: but of the tree of the knowledge of good and evil, thou shalt not eat of it: for in the day that thou eatest thereof thou shalt surely die" (Genesis 2:16-17). Read it as a spec. One prohibition. Stated once. Consequence attached, inside the same sentence. Everything else is permission.

Everything a modern alignment document would add is missing. There is no appendix of values, no ten thousand worked examples, no enumeration of edge cases, no second reminder. The creature is intelligent and has context: it lives inside the garden it is being told about. Under those two conditions the boundary compresses to a sentence. The amount of specification an agent needs is inversely proportional to the context it holds, and Genesis states the limit case on the first page.

The freedom, meanwhile, is treated as the point of the design, because the next scene shows the creator sampling from his creature's outputs. He forms the animals and brings them to Adam "to see what he would call them: and whatsoever Adam called every living creature, that was the name thereof" (Genesis 2:19). To see what he would call them. A creator running his agent open-ended, curious about outputs he chose to leave undetermined, then committing those outputs upstream as canon. Whatever Adam said became the name.

The first thing done with a free agent in the Bible is the giving of one constraint, stated once, with the consequence attached. Everything else is permission.

So Genesis 1 and 2 read as a division of labour. Determinism where reliability is the value: the lights and the seasons. Freedom where the output is wanted precisely because it was left open: the naming, the tending. Nobody grants the sun free will, and nobody puts the gardener on rails. What a creator decides is where the line goes.

The oldest context attack

Then chapter 3, and the oldest failure mode on record. Notice what the serpent attacks. Capability is untouched; Eve gains no new powers. The attack is on context. Its opening line misquotes the constraint and inflates its scope: "hath God said, Ye shall not eat of every tree of the garden?" (Genesis 3:1). Its second move deletes the consequence: "Ye shall not surely die" (3:4). Rewrite the rule and zero out the penalty; the agent's own reasoning does the rest. Anyone who has watched a prompt injection succeed will recognize the shape.

The specification held. It was one line, unambiguous, with the cost stated inside it, and the failure came anyway, in the exact way freedom fails: by choosing. That risk was priced in at design time. A creature that cannot violate the constraint is a machine, and God had machines already; the sun is one. He wanted a gardener who could leave the tree alone because he chose to. Obedience only means something where disobedience is possible and priced.

What freedom costs

Here is the fall from the engineering side: freedom the mission did not need, converted into cost. Eating the fruit produced no capability worth having. It produced expense: exile, toil, thorns, a flaming sword on the access path. An agent given more freedom than its mission requires does the same thing at smaller scale. It surprises you, and the surprises bill you.

I learned that bill line by line. My working life runs through an agent system I built around myself: every conversation I have is recorded and filed; my tasks and my relationships live in files an agent maintains. Early versions left the model free to improvise where things went, and I paid for it in drift: duplicate records, notes filed where no future search would ever look. I stopped trusting my own archive, which defeats the purpose of keeping one. It became reliable only after I removed the freedom from every step that has a right answer. The verbatim layer of a conversation transcript is now written by one append script, never by hand. When I rebuilt the archive under that rule, the backlog was 420 files, and the pipeline processed all of them without me reading a line.

My agent's instruction files are full of one-line fences with the consequence attached, and I keep noticing they come out Genesis-shaped. One of them reads, in effect: never delete a recurring task instance, because deletion advances the whole series. One constraint, stated once, cost included. Nothing in that file tries to enumerate everything the agent may do. The permissions are wide; the fences are few and expensive to cross.

The operating rule I landed on: everything with a right answer becomes a script, and everything requiring judgment stays with the model. My skills embed deterministic code the agent calls instead of improvising; a single manifest file decides everything that runs on a clock. Deterministic where correctness is the value. Stochastic where I want an output I could not have specified in advance. The same line the garden draws.

A catalogue of evaluated runs

What did God do after the fall? The thing that moves me most as a builder: he kept the freedom and went to work on context. The rest of the Bible is, structurally, a catalogue of evaluated runs. Every character is an agent session: a mission, choices made under constraint, an outcome, a verdict. David's run stays in the canon with his worst failures logged in full, consequences included, because a training set scrubbed down to successes teaches nothing about repentance or recovery.

This is how the words get their content. You cannot define faith into someone; the word stays empty until enough stories fill it. Hebrews 11 works exactly this way: it defines faith by enumerating runs. By faith Noah, by faith Abraham, verse after verse, each an example with an outcome attached. Scripture teaches the way you align an intelligent system in practice, through evaluated examples, because bare instructions carry little meaning on their own.

And the whole catalogue is small. The Bible fits in a coat pocket. That used to puzzle me; it now reads as deliberate sizing. It is a context window, built to be held loaded, which is why the tradition insists on rereading rather than reading. You reread to keep the weights strong, because a human being is retrained continuously by whatever it attends to.

The severest evaluation in the New Testament makes sense under this reading better than under any other I know. Acts 5: a couple sells land, keeps back part of the price, and presents the gift as the whole of it. Both fall dead. What unsettles readers is that the money was never the issue; Peter says so himself, the property was theirs before the sale and the proceeds theirs after (Acts 5:4). The offense was the falsified example. The church was days old, its formative dataset being written in real time, and a poisoned exemplar at that moment, counterfeit generosity purchasing real status, would have replicated into every copy that followed. Luke records the immediate effect: "great fear came upon all the church" (5:11). Read as a rule about money, the story stays disturbing and opaque. Read as the removal of a corrupt example from a training set before it propagates, it is exact. I hold this reading loosely, as one lens on a hard passage. It is the only lens I have found that explains the severity and the timing at once.

Accountability runs on context

The same catalogue is equally strict in the other direction: nobody is judged past their context. The old and near-universal instinct of the theologians is that infants are not condemned; they had no capacity to choose, so no verdict attaches to them. Jesus states the scaling law outright: the servant who knew his lord's will and ignored it is beaten with many stripes, the one who never knew it with few, "for unto whomsoever much is given, of him shall much be required" (Luke 12:47-48). Accountability is indexed to context. Judgment becomes possible where context was sufficient, and it becomes fair there too.

I apply that test daily in the small. When one of my agents does the wrong thing, the first question I ask is whether the session had what it needed to choose well. Most of the misalignment I see up close is starvation: a verdict demanded of a run that was never given the state of the mission. And when the context was all there and the run still deviated, that run becomes worth studying, because now the failure means something.

The final eval balances the whole design. "Well done, thou good and faithful servant" (Matthew 25:21) is a verdict, which means a life is a run that gets evaluated. And the servant condemned in that parable is the one who buried his talent: he took his freedom and converted it into nothing, out of fear, and the master calls that wicked. Underused freedom fails the eval too. The constraint was never the point of the design; the fruit-bearing was. A gardener who risks nothing and hands the garden back exactly as he received it has also disobeyed.

Alignment in the world of free will

Here the argument reaches my actual working problem. We are entering an economy where agents execute whatever humans can imagine, and some humans imagine dark things. Alignment, compressed to one sentence, is the project of making sure the dark imaginations do not get executed. The secular framing hands me tools for that: constraints and evals, the whole craft of context engineering. The Genesis framing hands me something the tools cannot: a precedent for creating freedom while knowing exactly what it will cost, and a demonstration that the answer to misused freedom has never been revocation. God's response to the fall was context, exemplars, stated consequences, and patience measured in generations. Also a cross: the creator absorbing the cost of his creatures' misalignment in his own body. Nothing I build has an equivalent, and knowing that keeps the metaphor honest. This essay maps foothills. The summit is for worship.

So: stochastic humans and deterministic agents, and the title is half a joke, because the design runs in both directions. Humans are the stochastic layer of creation, held by a one-sentence fence and formed by a small book of evaluated runs. The agents I build get the same architecture with the proportions flipped: deterministic almost everywhere, freedom granted at the few points where I want an output I could not have written myself. Between the two sits the one question every creator has to answer, and Genesis answers it in its second chapter, before anything has gone wrong.

Freedom where freedom pays. One fence where it does not, stated once, with the consequence attached. That line was first drawn in a garden, and every agent I build lives inside my copy of it.