The Author and the Object

There is an old question that has no comfortable answer: if God made everything, what was God doing before he made it? The question assumes there was a before — a stretch of empty time in which God waited, then decided, then acted. Augustine met this question in the fourth century and gave an answer that still holds: there was no "before," because time itself is part of what was made. God did not begin to act inside an existing clock. He made the clock.¹

But there is a deeper confusion underneath the question of when, and it is a confusion about what kind of thing God is said to be. Rowan Williams, the former Archbishop of Canterbury, put it cleanly in a public debate: God is "not as though God is a kind of extra item in the universe who might or might not be there. God is the condition of there being anything at all." The question of God, he said, "is not like the question of whether there's a cat in the garden. It is the question of why there is a garden, why there is a cat, why there is a 'why.'"²

That distinction sets the job of this article. The analogy I am about to offer is not a way of locating an Author somewhere inside the universe — you will never find him by searching the contents of the world, any more than you find a novelist by examining the furniture in his novel. The analogy is a way of seeing how a maker stands to a made thing: present to all of it, answerable to none of it, the reason there is a thing at all.

And I want to be clear about what an analogy is for. It is scaffolding, not foundation. It can help a person see how a claim could be coherent; it cannot prove the claim is true. I believe what the picture points to. I do not believe the picture proves it. Those are different statements, and I will keep them apart.

Why I Reach for Code

I should say plainly where this picture comes from, because the vocabulary in the rest of this article is not the usual vocabulary of theology, and I do not want it to arrive out of nowhere. I spend my working life in software and data. I think in systems that are designed and written, that run on their own once they are started, that keep a record of what they do, and that answer to whoever authored them. So when I try to imagine how a maker relates to a made thing, the image that comes to me first is not the potter or the painter — the older images Scripture and tradition usually reach for — but a program and its author.

That is a lens, and I would rather name it than pretend I do not have one. I am reaching for the tools I know best, and that carries a risk: the honest test is not whether a metaphor feels familiar to me but whether it illuminates the text or quietly bends it to fit my habits. Where it bends, I have tried to say so out loud. And if the technical words are unfamiliar to you, you do not need a background in any of this — here is everything you need to carry into the rest of the article:

The Author and the Object

Imagine a maker at work. Call the maker the Author. He writes Code, and the Code, when it runs, produces an Object.

Now map the picture onto the claim Genesis makes. The Author is God. The Object is the universe — matter, energy, physical law, life, and everything that runs inside it. The act of authoring is what Genesis calls creating: created (בָּרָא | bārāʾ | Heb - H1254), a verb the Hebrew Bible reserves almost exclusively for God's action and never pairs with raw material he had to use.³ And the most important piece: time is a counter internal to the Object. It is the loop the Object runs in, the sequence by which one state follows another. It belongs to the made thing, not to the maker.

"When God began to create the heavens and the earth…"

Genesis 1:1 · NRSVue (2021)

Most translations render the verse "In the beginning God created the heavens and the earth," which is fully defensible — the picture points the same way on either reading and leans on neither.

There is one more property worth naming now, because the rest of the article leans on it. A well-built program keeps receipts: a record of every state it passes through, change control not only over the code but over each action taken inside it. The Object logs itself as it runs. Scripture is full of this instinct — God "remembers" Noah, "remembers" his covenant, writes names in a book, keeps account. In the picture, history is the Object's own running log, and the question of what the Author does with that log turns out to be one of the deepest questions the analogy raises. Hold the thought; we will return to it.

John's Gospel reaches for the same structure with a different word. It opens not at the first event inside the sequence but behind it: "In the beginning was the Word (λόγος | lógos | Gk - G3056)." Logos means word, but also reason, account, the organizing logic of a thing.⁴ John places that organizing logic with God before the sequence starts — the Author and the source code, prior to the Object that runs from them.

Three Problems It Dissolves

1. Creation needs no "before"

The opening question disappears. Asking what the Author did "before" he wrote the Object is like asking what happened in chapter zero, or on the line of code before line one. There is no such chapter and no such line — not because we cannot find it, but because the sequence is part of the thing that was written. The Author is prior to the Object, but prior in the sense of source, not in the sense of an earlier date. This is exactly Augustine's move: God is the maker of time, so there is no time in which God had not yet made.¹

2. Acting inside time without changing

How can a timeless, unchanging God respond to events, answer prayers, and grieve over a city without thereby changing? The picture offers a clean image. The Author can attend to one part of the Object and then another, can care about a character, can speak into a moment — and none of this alters who the Author is. The relation runs one way. The Object is genuinely related to its maker; the maker's essence is not made or unmade by the Object. This is close to what Aquinas argued: the creature is really related to God, but God's relation to the creature adds nothing to God and takes nothing away.⁶ The Author's attention can move; the Author's nature does not.

3. Miracles as authorship, not law-breaking

A miracle is usually framed as God breaking the laws of nature. The picture reframes it. The laws of nature are the Object's normal operating rules — the physics the Author wrote. A miracle is the Author acting on the Object directly: either a line already written into the program from the start, which looks like an interruption only to those reading from inside, or an edit reached in from outside the running process. Either way it is not the maker violating the work. It is the maker making. The wonder is not that a rule got broken; it is that the one who wrote the rules is still present to the page.

Three Places It Reaches Its Edge

An analogy that is only displayed at its strongest is being sold, not examined. Here are the three points where this one reaches its edge — two where it genuinely bends, and one where it simply stops, because our knowledge does.

Plan A, and the Object That Modified Itself

If the Author is the condition of the world's being, then the world's story is not a series of patches over a design that went wrong. It is the design running. Consider the garden. The Author set the program going with a boundary written into it — one tree withheld. And then an Object did something to itself: through the use of another Object, the human changed its own state, and the change propagated. In the language of code it looks like inheritance — a modification in one instance handed down to every instance descended from it. "Sin came into the world through one man," Paul writes, "and so death spread to all."⁸

Here is the part that matters for the picture, and the part I am willing to hold without resolving. The Author knew this would happen — not because he reached in and forced the keystroke, but because he wrote the system, instilled the agency, and understands how inheritance works in a world of free Objects. Foreknowledge of what a freely-acting Object will do is not the same as making it do so. And the texts present the response to the garden not as an improvisation but as something already intended: the redemption was, in Peter's phrase, "destined before the foundation of the world, but … revealed at the end of the ages."⁸ This is Plan A continuing, not Plan B beginning.

How He Shows He Is Good, Present, and Near

The second part of Plan A is one of the most visible things in the Hebrew Bible, once you look for it. The Author does not run the program in silence. He speaks, warns, questions, argues, relents — and, most striking of all, he builds Objects that begin to speak back with his own heart. What follows is a pattern, not a proof. But the pattern is remarkably consistent, and it is the texture of a present and conversational maker, not an absent or merely verdict-issuing one.

Cain. Before the first murder, the Author comes alongside the angry man and reasons with him: "Why are you angry? … If you do well, will you not be accepted? And if you do not do well, sin is lurking at the door; … but you must master it" (Gen 4:6–7). Warning before the act. Then, after it, a question — "Where is your brother?" Cain denies knowing; but the deed has already written its own receipt into the world: "Your brother's blood is crying out to me from the ground" (Gen 4:10). This is the receipts idea appearing in the text itself — the act logs itself, the ground keeps the record, and the Author reads what is written there even as the doer denies it. A proportioned consequence follows — and then, remarkably, a mark of protection even for the murderer. The Author does not force-quit the bad Object. He stays in the conversation.

Hagar. An enslaved, discarded woman runs into the wilderness with no standing and no future, and the Author meets her there — the one person in the narrative nobody else is watching. He sees her, names a future for her son, and she gives God a name in return:

"So she named the LORD who spoke to her, 'You are El-roi'; for she said, 'Have I really seen God and remained alive after seeing him?'"

Genesis 16:13 · NRSVue

El-roi — "the God who sees me." The maker of the whole Object turns toward the one person no one else thought to look for. That is data about his character, deliberately recorded.

Jonah. The Author relents toward a violent foreign city when it turns, and then — when his own prophet sulks about it — does not strike him down but argues with him, using a withered plant as a teaching aid, and ends the entire book on an open question: "And should I not be concerned about Nineveh, that great city, in which there are more than a hundred and twenty thousand persons who do not know their right hand from their left?" (Jonah 4:11). The Author would rather reason an Object into seeing than override it.

Balaam. The Author is not confined to the channels we expect. He speaks through a pagan diviner hired to curse Israel, turns the curse into blessing, and opens the eyes of a man — and of a donkey — to see a reality that was there all along (Num 22–24). The picture's Author is not trapped in his own expected interfaces; he can address an Object through any part of the program he likes.

Moses at the mountain. This is the most arresting of all. After the golden calf, the Author says to Moses, "Now let me alone, so that my wrath may burn hot against them" (Exod 32:10) — and in the very act of saying let me alone, he leaves the door open for Moses not to. Moses argues back, appealing to the Author's own reputation and promises. And the text says:

"And the LORD changed his mind about the disaster that he planned to bring on his people."

Exodus 32:14 · NRSVue

The Hebrew is changed his mind (נָחַם | nāḥam | Heb - H5162) — to relent, to be moved to a different course.⁹ Whatever we decide about how an unchanging Author can "change his mind," the plain shape of the scene is unmistakable: the Author has written a world in which the voice of an Object genuinely counts. He invites the argument. Moses' intercession is not theater.

Moses in despair (Numbers 11). Crushed by the weight of the people, Moses prays one of the rawest prayers in Scripture: "I am not able to carry all this people alone, for they are too heavy for me. If this is the way you are going to treat me, put me to death at once" (Num 11:14–15). The Author does not rebuke the despair. He answers it — distributing the spirit that was on Moses among seventy elders so the burden is shared. Lament is heard and met, not punished.

Korah, and a man who acts on his own (Numbers 16). A rebellion ends in judgment, and a plague breaks out among the people. Then something happens that is easy to read past. Moses tells Aaron, on what reads as his own initiative, to take his censer and run:

"Carry it quickly to the congregation and make atonement for them. For wrath has gone out from the LORD; the plague has begun. … He stood between the dead and the living, and the plague was stopped."

Numbers 16:46–48 [Heb 17:11–13] · NRSVue

No command from the Author is recorded here. Moses sees the wrath, grasps what must be done, and sends Aaron into the middle of it to stand between the dead and the living. This is the second part of Plan A working exactly as designed: the Author has so formed his Objects that they begin to move with his own concern — interceding, atoning, putting themselves into the breach — without needing to be told. The maker who keeps entering the conversation has made creatures who enter it back. (That Moses acts here without explicit instruction is a reading of the narrative's silence, not a claim the text makes outright — but it is a fair and striking one.)

The Author Could Revert. He Largely Doesn't.

Return to the receipts. If the Object logs every state, then the Author, in principle, holds a complete version history of the world — and a maker who holds the full history of a running thing can, in principle, roll it back. He could revert to a prior state, overwrite a branch, reload from a save. Picture him starting the program, stepping away for coffee, returning, and finding he could undo whatever ran while he was gone. The analogy says he can. Power over the Object includes power over its log.

And yet the testimony of the texts is that he largely doesn't. He works within the sequence — warning, conversing, interceding, even entering the program himself — rather than force-quitting and reloading. The great near-exception, the flood, is instructive precisely because of how it ends: with a covenant never to roll creation back that way again, a bow set in the clouds as a permanent change-control note to himself (Gen 8:21–9:17). After that, the pattern is restraint.

Does the Author Read the Receipts First?

Now the thought we were holding comes due. When the Author attends to the Object, does he already know everything written in its log — having, in effect, the whole history before him at once — or does he genuinely engage an outcome still open from within the sequence? The conversational scenes make the question sharp rather than settling it. When the Author "changes his mind" at Sinai, is he moving along a story he has always fully seen, or responding to a future not yet fixed?

I hold the conversation to be real and significant on either reading — the God of these texts argues, warns, and relents rather than merely executing. What I have not resolved is whether the receipts are read before they are written. The analogy makes the fork vivid; it does not choose for me, and I will not pretend the text forces one answer. (Unsettled. Stated as a question, not a position.)

The Object That Was Always There

Plan A reaches its point not with an edit from outside — and, this matters, not with the writing of a brand-new Object either. The Object was always there. John's Gospel is emphatic: "In the beginning was the Word, and the Word was with God, and the Word was God" (John 1:1) — the Word already is, with the Author and as the Author, before the sequence begins to run. The creeds later guarded exactly this in their own idiom: "begotten, not made" — not something the Author authored at a moment, but one eternally of him. So what happens at a point in the program is not that a new Object is created. It is that the Object who was always there is invoked into the running world — the eternal Word takes on flesh and runs as one of the Object's own, addressing the others from inside their runtime, in their own language: my maker is the same as yours; but now he stands among you and speaks directly.

And the invoking did not arrive unannounced or out of nowhere. It was named in advance — the prophets carry the notice, from Isaiah's promised sign-child onward (Isaiah 7:14: "the young woman is with child and shall bear a son" — the Hebrew young woman (עַלְמָה | ʿalmah | Heb - H5959) names a young woman of marriageable age, which does not exclude virginity; the Greek Old Testament rendered it explicitly as "virgin," the reading Matthew follows). That is Plan A showing its hand: the moment was set in the design from early on, even though the One it concerned always was. And when the moment came, it came through the system rather than around it — the eternal Word instantiated within an existing Object by the Author's own Spirit, then carried and born and grown like any other:

"The Holy Spirit will come upon you, and the power of the Most High will overshadow you; therefore the child to be born will be holy; he will be called Son of God."

Luke 1:35 · NRSVue

So the eternal Word entered on the clock, by the world's own processes rather than dropped in over them. What I am not claiming is that the analogy solves what this is. The old question — how one person can be at once fully the maker and fully one of the made — is a matter for doctrine, and it would overreach to say a code-image settles it. But notice the caveat is about the theology, not the picture. The analogical move is coherent as far as it goes: a maker can write into his own world a way to be present within it, and then be present — a doorway opened into the running framework, the author stepping through to stand among his characters on their own ground, never ceasing to be the one who wrote them.

"And the Word became flesh and lived among us, and we have seen his glory, the glory as of a father's only son, full of grace and truth."

John 1:14 · NRSVue

There is still an "and then" buried in the move — he opened the way and then stepped through — and "and then" borrows the Author's own sequence again, the same boundary named in the first strain: we have no grammar for God's time except the one we live in, so we describe it from inside our own clock and make no claim about how it looks from his. And there is a deeper edge than that one. The doorway image gets you a maker present in the world he wrote; what no analogy reaches is the step the claim actually makes — not a visitor wearing the world like a costume, but the maker becoming a real one of his own, fully: flesh, and clock, and death. No ordinary author can do that. That is exactly why the picture breaks here — and if it did not break, it would be describing something smaller than the thing it points at.

Scaffolding, Not Foundation

This picture is old furniture rearranged. Dorothy Sayers built a whole book on the maker analogy, reading the creative act of an author as a worn human image of the Trinity.¹¹ C.S. Lewis used the novelist directly to explain divine timelessness: the author can put down the pen, and the time it takes him to do so is no part of the story's time at all.¹² I have changed the register from page to program because code makes the internal clock — and the receipts — explicit. The lineage is honest and worth naming. I am not claiming a discovery. I am offering a clarification.

And the clarification has a limit I keep returning to, because Williams names it better than I can. Faith, he said, "isn't a theory about the world; it's a way of being in the world. It's a way of holding the world, precisely in its brokenness and its mystery, and saying, 'This is held by something that is not just an accident.'" The analogy can show a careful person that this way of holding the world is coherent — that a maker outside time, present to his work, conversing within it, able to enter it, is a thinkable thing and not a contradiction. It cannot show that there is such a maker. For that you do not need a better analogy; you need to stand inside the framework, and the inside is entered by trust before it is confirmed by sight, and then "realized step by step, day by day."

The scaffolding is honest. I believe every plank of it. But it is scaffolding, and the house it stands against is not "a maker is conceivable." It is a person, with a name and a history, who is said to have written himself onto the clock he made — and who, the texts insist, is still keeping the conversation open. That is the part the analogy cannot reach and the part that matters most: not that the world has an Author, but that the Author is still speaking, and still waits to be received.

Arguments Against This Picture

An analogy that cannot survive its own criticism is not worth offering. Here are the strongest objections.

It proves coherence, then is used as if it proved existence. The article admits this in its third strain and again in the conclusion, but the admission does not remove the risk: a reader can finish feeling that the existence of an Author has been supported when only its thinkability has. Coherence is a low bar. Many false claims are coherent.

The "condition of being, not an item" move can shade into unfalsifiability. Defining God as the ground of there being anything — rather than as an item that might or might not be found — protects the claim from exactly the kind of disconfirmation that tests ordinary claims. A critic (Philip Goff and others press versions of this) can fairly say that a God who by definition cannot be found inside the world has been placed beyond the reach of evidence, and that "you wouldn't expect to find him anyway" is too convenient. The article leans on Williams' framing; it should concede that the framing answers one objection by inviting another.

The garden-and-inheritance framing sharpens the problem of evil rather than easing it. Saying the Author "knew it would happen because he designed the system" raises the obvious question of why he designed a system whose foreseen output was suffering and death on this scale, and the appeal to "Plan A, not Plan B" can sound like rebranding the difficulty as intention. Foreknowledge-without-coercion is a real and defensible distinction, but it does not by itself answer the theodicy question, and the article does not pretend to — it should be read as declining that question, not resolving it.

The flood is a rollback the article cannot fully absorb. The "change control" section claims the Author keeps faith with his design and largely declines to overwrite free Objects — and then must concede that the flood is exactly such an overwrite. The "pruning that preserves" and "exception that defines the rule" replies are reasonable but partial; a critic can fairly say the analogy's central virtue (a maker who respects the integrity of what he made) is contradicted by one of the tradition's foundational stories, and that naming the tension is not the same as resolving it.

Narrowing the time claim may look like moving the goalposts. The article concedes it does not explain God's time and asserts only that our time differs from his. That retreat is defensible — the "no before" point genuinely needs nothing more than our time being internal — but a critic can fairly say the picture's tidy appeal oversells what survives: it dissolves the puzzle only for our side of the clock and declares God's side off-limits, and "we cannot know God's time" is a stopping point, not an answer. A residual hazard remains that the narrowing does not remove: a maker who "writes," "revises," and acts "and then" is so thoroughly a temporal image that it can still train intuition toward a God who deliberates in sequence — exactly what the classical "eternal now" denies.

The free-will account still owes a mechanism. Saying "the Author can instill agency — Objects that freely originate their own actions" names the mystery in friendlier words rather than explaining it. The compatibility of authored wills, divine intervention, and divine knowledge is asserted as holdable; the article grants the knot is untied. A reader is entitled to find that thin.

"Leaving the omniscience fork open" can be evasion. Molinism (middle knowledge) and Boethian timeless-knowledge accounts are live options the article does not stage, and declining to choose between classical theism and open theism may be humility — or unwillingness to do the harder work. Naming a tension is not the same as resolving one.

These objections do not sink the picture. They locate its limits, which is the most an honest analogy asks for: that it be used for what it can do — clarifying a coherent claim and the character of the God a tradition confesses — and not for what it cannot — establishing that the claim is true.