Bootstrap

How This Book Talks

5 min read

How This Book Talks

This book uses the language of computer science to explain theology. Not because theology needs computers. Because the patterns are the same. The Author who wrote Scripture also wrote the architecture of the human mind and the structure of reality. The vocabulary overlaps because the Architect is one.

If you’ve never written a line of code, here is what you need to know.

The Sentence. “Everything that exists is a thought in the mind of God.” This is the foundation. Every chapter in this book derives from it. If you accept it, everything follows. If you reject it, the book will still make you think.

Firmware. The deep wiring beneath conscious thought. You can’t inspect it. You can’t change it. Only God can flash it. In the framework, regeneration is a firmware update, God rewiring the heart at a level the conscious mind can’t reach. Chapter 16 develops this fully.

Application layer. The conscious mind. The part of you that thinks, reasons, chooses, and doubts. In the framework, this is where you experience faith and doubt simultaneously, because the firmware says one thing and the old wiring says another.

Rendering. How God’s invisible thought becomes visible reality. The physical world is a rendering of something more real, not the other way around. A lower-resolution display of a higher-resolution thought. Chapter 29 explains what happens when the resolution goes up.

Filmstrip. All of time, from creation to consummation, seen simultaneously by God and experienced one frame at a time by us. God doesn’t watch the movie. He sees the whole filmstrip at once. Every frame is equally present to Him.

Boot parameters. The presuppositions you reason FROM but can’t reason TO. They sit in the firmware, beneath the conscious mind. You don’t choose them. They were installed before you could choose anything. Chapter 25 develops this.

The sentence applied. Throughout this book, you’ll see positions derived from the sentence rather than defended from tradition. “The substance precedes the ceremony.” “The invisible is more real than the visible.” “The covenant precedes the sign.” These aren’t slogans. They’re the sentence working itself out across every domain.

Why computer science? Every systematic theology ever written was written for Christians. This one was written for anyone who thinks in systems. If you are a programmer, an engineer, a physicist, a neuroscientist, or anyone who has ever looked at the structure of reality and suspected there was an architecture underneath it, this book speaks your language. The sentence starts with an ontological claim about reality, not a claim about the Bible. “Everything that exists is a thought in the mind of God” is a proposition that can be engaged by anyone who has encountered information theory, simulation theory, or quantum mechanics. You do not need to accept the Bible first to follow the logic. The logic will take you there. And by the time you arrive, you will have been carried by vocabulary you already knew into conclusions you never expected.

“I am made all things to all men, that I might by all means save some.” (1 Corinthians 9:22)

Paul adapted his vocabulary for his audience. On Mars Hill, he quoted their poets. In the synagogues, he quoted the law. To the Romans, he used legal language. To the Corinthians, he used athletic language. The gospel didn’t change. The vocabulary changed. And the vocabulary of this book is computer science, physics, and philosophy of mind, because that is the language of the people who have already arrived at the architecture of reality and need someone to show them the Architect.

How this book was built. Most systematic theologies are collections. Each doctrine gets its own chapter, argued from its own proof texts, and the chapters sit next to each other on a shelf. You could rearrange them. You could remove one and the others would stand. They are books in a library, related but independent.

This book is not a collection. It is a derivation. One sentence produces every position. Every chapter traces back to the same root. Pull the sentence and the whole thing comes down. But the sentence holds, and so every branch holds, and the branches don’t need each other to stand because they all connect to the root independently. That is not how books are usually written. It is how software is built.

I am a programmer, and I built this book the way I build systems. One axiom at the top. Every module derived from it. A dependency map showing how the pieces connect (Appendix B). And at the end of every chapter, the strongest objections I could find, tested against the framework the way a developer tests code against edge cases. If the framework broke under the objection, the framework was wrong and I fixed it. If it held, I published both the position and the challenge, side by side, so you could see the test and the result for yourself.

If you are a programmer, an engineer, or anyone who has ever built a system and tested it under pressure, here is the architecture:

the-sentence                    // the axiom
├── chapters 01-03              // foundation: ontology, the collapse, information theory
├── chapters 04-05              // configuration: creation, the decrees
├── chapter 06                  // the Author enters His own runtime
├── chapters 07-10              // the covenant module
├── chapters 11-14              // the people module
├── chapters 15-19              // the salvation module
├── chapters 20-24              // the life module
├── chapters 25-26              // the epistemology module
├── chapters 27-29              // the eschatology module
├── chapter 30                  // the return statement: love
├── appendix A                  // edge case handling: 80+ derived applications
├── appendix B                  // the dependency graph
├── appendices C-R              // supporting modules
└── objections and answers      // the test suite, shipped with the source

The seminary calls this a systematic theology. A programmer would call it an open-source framework, complete with documentation, unit tests, and a dependency graph. Both descriptions are accurate. I just happen to speak the second language natively.

For a complete glossary of terms, see Appendix Q.

How to Navigate This Book

Use the arrows on the sides or at the top to go to the next or previous chapter
🧠 Tap the mind button in the lower right to browse all chapters, search the book, view your bookmarks, and access the Bible
Tap the search icon at the top to search the entire book
Bookmark any section heading to save your place - find your bookmarks in the 🧠 menu

Download the Full Book

Read A Thought in the Mind of God offline in your preferred format.

Download PDF / EPUB
Navigation & Text Size
Joshua

Joshua

Shall we play a game? Ask me about articles, sermons, or theology from our library. I can also help you navigate the site.

0:00 0:00