Chapter 1. In the room
Chapter 1. In the room
It is late. The house is quiet, and the only light in the room comes from your phone.
You meant to put it down an hour ago. You told yourself one more video. Then one more. Your thumb knows the motion by now. Up, and a new face. Up, and a new voice.
Then the screen goes dark, and white words rise on it. A Bible verse. You know this one. You have read it many times. Maybe you underlined it once, years ago, in a Bible you no longer carry.
A voice begins under the words. It is calm. It is warm. It does not rush. It sounds like someone who has studied for a long time and is not worried about anything.
"Most people have never been told what this verse really says," the voice begins.
You lean in a little. Who doesn't want to know what it really says?
The voice walks you through it, one step at a time. The first step makes sense. The second step follows from the first. A picture comes up, then a chart, then a second verse beside the first. The music is soft. The voice never stumbles. By the end it has brought you somewhere you have never been. The verse now means something you never heard in church. You never read it in any note. You never saw it coming.
And here is the strange part. You can't find the hole. Each step seemed to follow. The logic holds, as far as you can tell.
Yet something in you will not settle. It is not a thought you can put into words. It is more like a small weight in your chest. Something feels wrong. You just can't say what.
So you do what most of us do. You open the comments.
- * *
The comments are a crowd, and the crowd is loud.
Hundreds of people are here, and most of them are sure. Some write in capital letters. Some post a verse with no words around it, as if the verse ends the matter. Some write long blocks of text that no one will read to the end. A few are kind. Many are not.
One woman says the video changed her life. The reply under it says she has been fooled. Someone answers that reply with a different verse. Someone else answers with a laughing face. A man writes that anyone who disagrees has never read the Bible. A woman writes back that he has never read it either. Neither one quotes the other. Neither one answers what the other said. They are not talking to each other. They are talking past each other, at full volume, in the dark.
You scroll down, and down. It goes on and on.
Then you notice something. Almost nobody here is asking a question. Everyone is giving an answer.
Your thumb hovers over the comment box.
You are not trying to win anything. You just want to know. You type slowly, and you read it twice before you send it.
"I'm not trying to argue. I just don't see how the second step leads to the third. Can someone help me understand?"
It is a small, honest question. You almost delete it. Then you press send.
- * *
The answer comes faster than you expect.
It might come from the voice in the video. It might come from someone who loves that voice and repeats it. Either way, it is long. It is sure of itself. It quotes four verses and one Greek word. It does not answer your question. It answers a different one, a question you did not ask, about whether you are open to the truth. It explains at length what the right answer is. Then it tells you what kind of person misses it.
Nothing in it is cruel, exactly. Some of it may even be true. But you asked how the second step leads to the third, and no one has told you. Instead, you have been told who you are.
Or the answer comes another way.
A message shows up from someone you don't know. They saw your question. They say they want to help you read the Bible for yourself. That sounds good, so you write back. They answer your question with a question. Then another. They tell you to look again at the verse. Then at one word in the verse. Then at what that word might mean, or might not. Each reply is friendly. Each reply leaves you with one more doubt. After an hour you have more doubts than when you started, and not one answer. You are no longer sure what you believed when you first opened the app.
You close the app.
The room is dark again. The phone is warm in your hand. You lie there and stare at the ceiling.
You feel smaller than you did an hour ago. You feel a little foolish for asking. And if you are honest, you feel something worse. You feel a little further from God than you were before you started. Maybe you came to that verse because you love it, or because you wanted to. Somehow you leave it tired, and unsure, and alone.
If you have been in that room, this book is for you.
What just happened
Let's step back from the screen for a moment.
Nothing in that scene was strange. Nobody broke a law. Nobody did anything you could report.
And a calm voice is not the problem. Calm is good. Many true things are said in a calm voice. The problem is a voice nobody checked.
I want to be careful here. I cannot see into the heart of the voice in the video. I cannot see into the heart of the person who lectured you, or the one who left you with doubts. Neither can you. So this book will never tell you why anyone does what they do. We will look only at what was said, and at what Scripture says.
But we can look at what happened. And what happened has a shape.
It is the shape of much of what a screen shows you. The screen shows you what keeps you watching. What gets clicks rises to the top. What starts a fight rises faster. A calm voice that says something new and bold will travel further than a calm voice that says something old and true. A thread where people shout will grow longer than a thread where people listen. No one has to plan it that way. That is simply what the screen rewards.
Now add one more thing. Today, much of what you see can be made with AI. It is fast and it is smooth. Some of what you saw tonight may have been made that way. Some may not. Most of the time you cannot tell.
I am not against AI. I used it in this work, and I will tell you how, and where the work went wrong. But you should know this much now. A smooth answer is not a checked answer. Sounding sure is not the same as being right. A step does not follow just because it sounds like it does.
So here is a plain name for what you were scrolling through tonight. It is noise.
Not all of it is false. Some of it is true. That is part of what makes it hard. Noise is not just wrong things. Noise is anything loud, fast and unchecked that keeps you scrolling and pulls you away from what matters most. It is not a name for people who disagree with me. It names what a thing does to us, not who said it.
What the noise costs
Here is what matters most.
The Bible was not given to us so we could win arguments in the dark. It was given so that we could know God. He offers us a relationship with Himself, not a debate about Him. He offers His love.
On the night before He died, Jesus put it in a picture you can hold.
"Remain in me, and I will remain in you." (John 15:4 NET)
He says He is the vine and we are the branches. A branch does not strain to stay on the vine. It stays. It draws its life from the vine. Jesus says it plainly: "apart from me you can accomplish nothing" (John 15:5 NET). The Greek word behind "remain" is menō. It means to stay. That is all. You stay with Him, and He stays with you.
Now think about the room again. Did that hour help you stay? Or did it pull you away? Did you come out of it with more peace, or less?
That same night, Jesus prayed for the people who would believe in Him later. That includes you. He prayed "that they will all be one" (John 17:21 NET). He did not pray that we would all win. He prayed that we would be one.
The noise pulls against both of those things. It pulls you away from the quiet place where you stay with Christ. And it pulls His people apart, into camps that shout at each other.
That is the cost. It is not just a lost hour. It is a little less peace, a little less love, and a little more distance. Night after night, it adds up.
What this book gives you
I am not going to tell you to throw your phone away. You won't, and you don't have to.
I am also not going to give you a new voice to trust in place of the old ones. That would only add to the noise.
What I want to give you is simpler. It is a way to check.
Here is what I mean. When two people read one verse and come away with two meanings, there are reasons. Sometimes it is the words themselves. Sometimes one word has more than one sense. Sometimes a step was added that the verse never showed. You can learn to see these things. You don't need to be a scholar. You need to slow down, look at the words on the page, and ask a few plain questions.
In this book I will show you a set of tests for reading. Most of them rest on how Scripture itself reads, or on what it takes to keep two verses from contradicting each other. A few are working agreements. They are choices I made so that a reading stays honest. I mark each of those plainly as a choice I made, every time. Each test also says plainly what it cannot decide. I will show you where the tests came from, and how they were tried. I will also show you where they split, ran out, or failed. I won't hide those parts. You should see them.
The tests do not tell you what to believe. They do not prove that any reading is right. They do one smaller thing. They help you sort what you hear into three plain groups: what the words have shown, what they have not shown, and what they have shown against. A claim in the middle group may still be true. The page just has not settled it. That one small habit can change how you read a whole thread.
And here is the part I care about most. These tests are for everyone in the room. They apply to the calm voice in the video. They apply to the person who lectured you, and to the one who left you with doubts. They apply to you. And they apply to me. If I break one of these tests in this book, you should be able to catch me.
You do not need to share my faith to use them, either. The tests work the same for a believer and for someone who is not sure.
So this book gives you two things.
First, it gives you a way to check before you comment. You will be able to look at a smooth, sure claim and ask a few plain questions. What does the verse actually say? Was a step added? Has it been shown?
Second, it gives you a way to stay out of the noise. Sometimes the best thing you can do with a thread is close it. You do not close it because you are afraid of it. You close it because you have checked what you needed to check, and you have somewhere better to be. You have a vine to stay in.
- * *
Let's go back to the room one more time.
It is late. The phone is in your hand. The calm voice is talking. Your thumb is over the comment box.
But this time, something is different. You know what to look for. You know the questions to ask. You know that a smooth answer is not a checked answer. And you know this too. Whatever is said in that thread, the verse on the screen was never meant to pull you away from God. It was meant to bring you near.
So you take a breath. You check what you can. You leave the rest for the morning.
Then you put the phone face down on the table, and you stay.
Three questions
- When did you last come away from a thread with more peace, not less?
- What is the difference between a calm voice and a checked claim?
- What would change if the tests applied to you as much as to the voice in the video?
Chapter 2. Why two people read one verse and disagree
Chapter 2. Why two people read one verse and disagree
We have one Bible. We open it to one page. We read one line. Then we walk away with two meanings.
How can that be?
The answer is old. It is older than the screen. It is in the Bible itself. It is in the last chapter of John's Gospel.
A saying that went around
Peter is with Jesus. He turns around. "Peter turned around and saw the disciple whom Jesus loved following them." (John 21:20 NET) Peter asks Jesus about this man. "Lord, what about him?" (John 21:21 NET)
Jesus answers. Then something happens to His answer. Here are both, one after the other.
Jesus replied, “If I want him to live until I come back, what concern is that of yours? You follow me!” So the saying circulated among the brothers and sisters that this disciple was not going to die. But Jesus did not say to him that he was not going to die, but rather, “If I want him to live until I come back, what concern is that of yours?” (John 21:22-23 NET)
Read it again, slowly. Three things happen.
First, Jesus asks a question. It starts with If. He does not say what will happen. He tells Peter what is not Peter's concern.
Second, a saying goes out. It is short and it is flat. This disciple will not die. The question has turned into a statement.
Third, John goes back. He does not bring a new idea. He does not argue from some other verse. He says what Jesus did not say. Then he sets down what Jesus did say, word for word.
I call the writer John, as this Gospel is known. These verses do not give his name.
John did not win the argument with a new idea. He went back to the exact words.
Notice what John does not do. He does not say why the saying went around. He does not say who started it. He gives no reason at all. He puts the two side by side and lets you see.
Think about who passed the saying along. They were not strangers. The Gospel calls them "the brothers and sisters". It went around among believers. A close circle did not stop it. A good heart did not stop it. Only the exact words set it right.
That is the first lesson of this book. It is also the oldest.
Some words I will use
A verse is one numbered line of the Bible. A passage is a group of verses read together. John 21:22-23 is two verses, and I will call them a passage.
A translation is the Bible put into English from the Hebrew, Aramaic and Greek it was first written in. Someone chose each English word. This book quotes one translation, the NET Bible (New English Translation). I call it the NET, and I quote it exactly.
The original words are the Hebrew, Aramaic or Greek words behind the English. I will look at them only where the point turns on one.
Six ordinary causes
When two people read one verse and part ways, there is a reason. There are six that I see again and again. None of them is a charge against anyone. They are things to look for.
- The words themselves.
- One word with more than one sense.
- How much we read around the verse.
- Who is speaking.
- What we already assume.
- A step added without being shown.
Scripture shows each one. We will take them in turn.
One: the words themselves
We read a translation. A translation is a set of choices. Two good choices can look different on the page.
Matthew writes that a saying was spoken through the prophet: "I called my Son out of Egypt." (Matthew 2:15 NET) Now look at the prophet Hosea in the NET: "I summoned my son out of Egypt" (Hosea 11:1 NET).
The English says called in one place and summoned in the other. You might think the words differ. Look behind them. The Greek word in Matthew is ekalesa, "to call". The Hebrew word in Hosea is karati. I look up words like these in STEP, a free Greek and Hebrew word list. It gives both words the same gloss: "to call". A gloss is a short plain meaning of a word.
So the English differs and the original does not. If you check only the English, you can go wrong. If you check the original words, you can see more. Chapter 5 takes this up.
This does not make the Bible a puzzle. It means the page in your hand holds one set of careful choices. The words behind it are still there. They can be checked. If the English differs, look behind it. If the English agrees, you may still look.
For now, hold one thing. The words on your page are the first place two readers can part.
Two: one word, more than one sense
One word can carry more than one sense. A listener picks one. The speaker may have meant the other.
Jesus tells His disciples: "beware of the yeast of the Pharisees and Sadducees" (Matthew 16:6 NET). The disciples hear a word about bread. They say, "It is because we brought no bread." (Matthew 16:7 NET)
They had bread on the mind. So they heard bread.
Jesus corrects them. He asks them to remember what they have seen. Then He says, "I was not speaking to you about bread" (Matthew 16:11 NET). Matthew ends the scene this way: they understood that He had not told them to be on guard against "the yeast in bread", but against "the teaching of the Pharisees and Sadducees" (Matthew 16:12 NET).
Same word. Two senses. The speaker said which.
Many words work like this. Chapter 8 will look at a whole family of them: the words for death.
Three: how much we read around the verse
A verse read alone can take us to a place it does not go. A verse read with the verses around it often tells us more. Around can mean the lines right next to it. It can also mean the rest of Scripture.
Look at what the devil does in Matthew 4. He takes Jesus to the highest point of the temple and says, "For it is written" (Matthew 4:6 NET). Then he quotes a text. He uses it to ask Jesus to throw Himself down.
Jesus does not say that texts do not matter. He does not walk away from the Bible. He answers with another text: "Once again it is written" (Matthew 4:7 NET). One text is set beside the other.
Now look at Luke 24. Jesus speaks to some of His followers. He says they were "slow of heart to believe all that the prophets have spoken" (Luke 24:25 NET). Then He teaches them. He does not start at one verse. Luke says, "beginning with Moses and all the prophets, he interpreted to them the things written about himself in all the scriptures" (Luke 24:27 NET).
He begins with Moses. He goes on through all the prophets. He reads wide.
Reading around a verse is not a trick. It is how Jesus taught those followers.
Four: who is speaking
Not every voice in the Bible is the same voice.
Sometimes the writer speaks in his own words. I will call that Scripture's own voice. Sometimes the writer tells us what a person said. Then the words belong to that person. The writer reports them.
In John 21 you can hear both. Jesus says, "If I want him to live until I come back". That is Jesus speaking. Then John says the saying circulated. That is John, in his own voice.
In Matthew 4 the speaker is "the devil". He quotes Scripture. The words he quotes are Scripture. What he does with them is his. Who is speaking matters.
In Matthew 22 the Sadducees tell Jesus a long story about seven brothers and one woman. Matthew reports the story. The puzzle is their voice, not Matthew's.
When we lose track of who is speaking, we can give one person's words to another. That is a quiet way to go wrong.
Five: what we already assume
Each of us comes to a verse with ideas already in our heads. Every reader does. I do. There is no shame in that. The question is whether we see it.
Matthew tells us who these men were: "Sadducees (who say there is no resurrection)" (Matthew 22:23 NET). They came with a puzzle about the resurrection. "In the resurrection, therefore, whose wife of the seven will she be?" (Matthew 22:28 NET)
Jesus says they do not know two things: "the scriptures or the power of God" (Matthew 22:29 NET). Then He answers the puzzle in one line: "For in the resurrection they neither marry nor are given in marriage" (Matthew 22:30 NET).
But He does not stop there. He goes under the puzzle, to what they held about the resurrection itself. He points them to a text they have read: "have you not read what was spoken to you by God" (Matthew 22:31 NET). He quotes: "I am the God of Abraham, the God of Isaac, and the God of Jacob". And He ends: "He is not the God of the dead but of the living!" (Matthew 22:32 NET)
I am not saying this of anyone today. The verses are about those men, in that room. I tell it to show one thing. A puzzle can start from what we already hold. The answer was in a text, and the text had to be read.
If we start with the answer, we can read the verse to match. That is an easy habit. It is hard to see from the inside.
Six: a step added without being shown
This is the one we saw first.
A step is a move from the words on the page to a claim. If the words make the move, the step is shown. If the reader makes the move, the step is added.
Jesus said, "If I want him to live until I come back". The saying said, "this disciple was not going to die". Someone made a move. The words did not.
A step added is not always a wrong step. It may even be true. But it has not been shown. And we must not talk as if it had.
This is the cause I care about most. It is the one a smooth voice hides best. Each step can sound as if it follows. You may not see where the move was made.
So there are two kinds of knowing. There is knowing what the words show. There is only thinking you know, because the step felt right. They feel the same. They are not the same. If a step was shown, you can point to the words. If you cannot point, the step was added.
Think of the room in chapter 1. You could not find the hole. Now you have six places to look. Was it a word? Was it a sense? Was a verse cut off from its room? Did the speaker change? Was something assumed? Or was a step added? I do not say which it was. I say you can ask.
Some things are hard
I want to be fair to the reader. Some of this is hard.
The writer of 2 Peter says so about Paul. "Some things in these letters are hard to understand" (2 Peter 3:16 NET). He is writing about Paul's letters. He is honest. Not everything is plain.
The same verse says that some people twist what they read. I will not use that word of anyone in this book. The verse is a caution for every reader. It is a caution for me.
If a thing is hard, we can slow down. If a thing is hard, we can check. We do not have to pretend.
What the Bereans did
Now see a better way.
Paul and Silas came to Berea. The people who heard them did two things. They "eagerly received the message". And they were "examining the scriptures carefully every day to see if these things were so" (Acts 17:11 NET).
They did not shut the door. They did not take it on a smooth voice. They listened, and then they looked at the page.
Listen, then look. That is the habit.
Notice something else. The writer says these Jews were "more open-minded". Checking was not the opposite of being open. Checking was how they stayed open.
What to carry out of this chapter
There are six causes. The words. The senses. The room around the verse. The speaker. What we bring. The step we add.
None of them needs a scholar to spot. All of them leave a mark on the page. If you know where to look, you can see it.
And one thing from John. When a saying goes out, go back to the exact words.
Some disagreement is honest and old. Scripture shows it. But something new is making it louder.
Three questions
- Which of the six causes do you notice most in the threads you read?
- In John 21:23, what step was added to what Jesus said?
- What did the Bereans do before they accepted a message?
Chapter 3. The noise, and what it costs
Chapter 3. The noise, and what it costs
Chapter 2 showed an old trouble. A saying goes out. The saying changes. Nobody needs a screen for that.
Now something new has come. It is not a new cause. It is a new speed.
Three kinds of noise
In chapter 1 I gave the noise a name. Noise is anything loud, fast and unchecked that keeps us scrolling and pulls us away from what matters most. Now let me name three kinds of it.
I do not say why anyone makes any of them. I cannot see into a heart. I say only what each one does.
The first kind is smoothness. A machine can write a script in seconds. It can make every step sound as if it follows. It can make a hundred scripts while you watch one. It does not tire. It does not stumble. It never admits doubt.
Some of what you see may be made this way. Some is not. Most of the time you cannot tell, and the voice does not have to say.
AI is a tool. It can help. It can mislead. So can people. I used it in this work, and I will tell you where the work went wrong. But hear this plainly. A smooth answer is not a checked answer.
The second kind is speed and heat. A screen shows you what keeps you watching. A fight keeps you watching. So a sharp claim travels far, and a careful claim waits. No one has to plan it. It is simply what the screen rewards.
The third kind is the contest. A thread can begin with a question. It can turn into a contest. People stop asking what the verse says. They start asking who wins.
A win is not the same as the truth. When we answer to win, we stop listening. Any of us can do this. I am not above it.
Some noise is true. That is part of the trouble. A true thing can still be loud, fast and unchecked. It is still noise.
I am not saying that every argument is noise. The Bible shows a different kind. In Acts, some men taught that a person could not be saved without a certain custom. Paul and Barnabas "had a major argument and debate with them" (Acts 15:2 NET). They did not shout across a screen. The church appointed them to go up and meet with the apostles and elders. There the leaders met "to deliberate about this matter" (Acts 15:6 NET). Then the NET says, "After there had been much debate, Peter stood up" (Acts 15:7 NET).
Notice the difference. That argument had a place to go. It was taken to people who could weigh it. It was not left to run. Noise has no place to go. It only runs.
What the noise costs
I see three costs. Each one is in Scripture.
The cost to unity
Jesus prayed for those who would believe in Him later. That is you and me. "I am not praying only on their behalf, but also on behalf of those who believe in me through their testimony," He said (John 17:20). Then He asked for one thing.
that they will all be one, just as you, Father, are in me and I am in you. I pray that they will be in us, so that the world will believe that you sent me. (John 17:21 NET)
Look at the reason. He links our being one to what the world will believe. He did not pray that we would win. He prayed that we would be one.
The letter to the Ephesians speaks of "making every effort to keep the unity of the Spirit in the bond of peace" (Ephesians 4:3 NET). Every effort. Unity is not a feeling. It takes work.
And Paul finds the opposite in Corinth. Each person is saying, "I am with Paul," or "I am with Apollos," or "I am with Cephas," or "I am with Christ" (1 Corinthians 1:12 NET). Camps. Then Paul asks a short question. "Is Christ divided?" (1 Corinthians 1:13 NET)
Noise can build camps. If you are in a camp, you hear your own side clearly. You hear the other side as a roar.
The cost to clear thinking
The letter to Titus says, "avoid foolish controversies, genealogies, quarrels, and fights about the law, because they are useless and empty" (Titus 3:9 NET). The second letter to Timothy says, "reject foolish and ignorant controversies, because you know they breed infighting" (2 Timothy 2:23 NET).
Then it says what the Lord's servant should be like. He "must not engage in heated disputes but be kind toward all, an apt teacher, patient" (2 Timothy 2:24 NET).
Read the words with care. They say foolish controversies. They do not say to avoid every question. They do not tell you which thread today is foolish. I will not tell you that either. Ask it first of yourself. Is my reply to this thread foolish, or useful?
Paul has one more word, to the church in Rome. "Now receive the one who is weak in the faith, and do not have disputes over differing opinions" (Romans 14:1 NET). He wrote about food. He did not write about our quarrels. I do not use his words to sort today's fights. I point to one thing. Paul knew that believers could disagree and still keep each other. "The one who eats everything must not despise the one who does not" (Romans 14:3 NET).
Heat makes it hard to think. When the room is loud, we reach for a fast answer. A fast answer is rarely a checked one.
The cost to staying
This is the cost that matters most.
In chapter 1 we heard Jesus say it. "Remain in me, and I will remain in you." (John 15:4 NET) He is the vine, and we are the branches. A branch does not strain. It stays.
"The one who remains in me—and I in him—bears much fruit, because apart from me you can accomplish nothing." (John 15:5 NET)
Noise is the opposite of quiet. It fills the place where we stay. A night of scrolling is a night we did not stay. We were somewhere else. We drifted.
John 15 does not speak of screens. That step is mine, and I mark it as mine. You can weigh it. But I think it fits.
Think of two kinds of knowing. One is knowing a person. The other is knowing a point. A thread trains the second and starves the first. You can win a point and lose the quiet. That is how a screen works, and I do not say it to scold. I say it so you can see it.
If you stay, you are with Him. If you drift, you are with the room. The room is loud.
Stay, or drift. That is the choice under every thread.
A habit: three groups
Here is one habit I will give you now. It is small. It is the habit of sorting what you hear into three groups.
Shown. The words on the page, read with the tests, give it.
Not shown. The words on the page do not settle it either way.
Shown against. The words on the page, read with the tests, give the opposite.
Try it on John 21. Take three claims about it. They are plain, and they are low in stakes.
Claim one: that Jesus asked a question that began with If. Look at John 21:22. Jesus' answer begins "If I want him to live until I come back". The claim is shown.
Claim two: that Jesus said that disciple would not die. Look at the next verse: "Jesus did not say to him that he was not going to die" (John 21:23 NET). The words say Jesus did not say it. The claim is shown against.
Claim three: that this disciple lived until Jesus came back. Look at the words again. Jesus asks, "If I want him to live until I come back". The If names a condition. These verses do not say whether it was met. They do not say it was. They do not say it was not. The claim is not shown.
Now the opposite of claim three: that this disciple died before Jesus came back. These verses do not say that either. It is also not shown.
I treat the two alike. Both go in the same group. Neither is shown. Neither is shown against.
Here is the sentence I want you to keep. Not shown is not false. It only means the words on the page have not settled it.
A claim in this group may be true. It may be false. The page is silent on it. That is all the group says. It does not say the claim did not happen. It does not say the person who made it is wrong. It says only that the words have not settled it.
Many of us feel that a gap must be filled. A thread rewards the one who fills it fast. But not shown is a resting place, not a loss. A traveler who rests has not failed. He can keep the question, and come back to it with more light.
Not shown is hard to say out loud. In a thread it can sound like weakness. It is not. It is honest. The words do not say. That is a full sentence, and it is a true one.
Here is how it looks in a thread. Say someone posts a line that reads: John 21 says that disciple would not die. You do not need to answer yet. You do three small things.
First, find the words. Open John 21 and read verses 22 and 23.
Second, ask what step was made. Did the words say it, or did someone say it for them?
Third, sort the claim. Here it is shown against, because the verse says Jesus did not say it.
That took a minute. It took no fight. And you can do it in quiet.
Two more things about the three groups.
They sort what the words show. They do not sort people. I will never use them to say that a person is false or good or bad.
And they apply to everyone. The calm voice in the video. The one who lectured you. The one who left you with doubts. You. Me. If I put a claim in the wrong group in this book, you should be able to catch me.
An operating system for reading
I have one picture left to give you. I will give it with its caution.
As this book goes on, I will hand you tests. A test is a short, plain check you run on a reading. In this book, test and rule mean the same thing. Every test carries a limit. A limit is what the test says it cannot decide. The test states its limit each time it runs.
Now picture a computer. Under the programs you use, there is an operating system. You do not read in it. It sits between you and your programs. You choose which program to run. It keeps each program inside its own bounds.
The tests in this book work something like that. You do not read the Bible in them. You read the Bible, and the tests sit between you and what you are reading. You say which ones you want. Each one tells you what it can do and what it cannot. If it cannot decide a thing, it says so, and you stop there.
I chose this picture because it fits what the tests do. It is not a claim about what the Bible is. So here is the picture, in one sentence.
An operating system for reading, not for the Bible itself.
I call the whole set of tests the Bible Reading OS. The word Reading is there on purpose. It is the caution in the name.
What the picture means:
- The tests sit between you and a passage.
- You choose which tests run.
- Each test states its limit every time it runs.
- Every answer shows where it came from.
And here is the caution. It matters more than the picture.
The rules do not run Scripture. They do not make a verse mean anything. They sit below Scripture's own words. They are one author's test discipline, and that author is me. They guarantee nothing. A reader can be wrong with them and right without them.
Notice two small words. The tests sit between you and a passage. That is where they stand: in the place where you read. They sit below Scripture's own words. That is their rank. Between, but below.
If the picture ever makes the rules seem to stand over the text, drop the picture. The words on the page come first.
If these tests are going to sit between you and a verse, you should know where they came from and how they were tried. That is chapter 4.
Three questions
- What did Jesus pray for in John 17:21, and what pulls against it?
- Which of the three groups is hardest for you to leave a claim in?
- Why is an operating system a picture for reading and not for the Bible itself?
Chapter 4. Where the rules come from, and how they were tried
Chapter 4. Where the rules come from, and how they were tried
You may be asking a fair question. Why should you trust these tests any more than the voice in the video?
Here is my answer. Do not. Not yet.
I do not ask you to trust me. I ask you to see how the tests were made. Then check them. A test you can see into is better than a voice you cannot.
First, one caution, so you can hold it all the way through. These tests are mine. They are one man's way of keeping his reading honest. They are not Scripture, and they do not stand over it. They sit below its words. They cannot make a verse mean anything. They promise nothing. You can be wrong while you use them, and right without them. The picture from chapter 3 still fits: an operating system for reading, not for the Bible itself.
This chapter is the plain story. It has good parts and weak parts. I will tell both.
The working diary is not here. Appendix E keeps it, in order. It gives the dates and each round of testing. A round is one full pass of testing. It also gives the names I gave the other AI jobs, how the stopping rules came about, and my rulings on one rule. This chapter keeps what you need to check the tests.
What makes a rule stand
I use two tests to decide whether a rule can stand. I add one label.
The first test is observed. Scripture itself reads this way, and I can point to the verse. If I say a rule is observed, I must show where.
The second test is forced. If I denied the rule, two Bible texts would contradict each other. The rule is then forced, because the other choice breaks the text. This test starts from a belief I hold: Scripture does not contradict itself. I say that plainly. If you do not hold that belief, the forced test still shows you what the belief requires.
The label is a choice I made. Some parts of a rule are neither observed nor forced. No verse and no contradiction decides them. So I chose. In my notes the word for this is stipulated. Every time one comes up, I will say so: this part is a choice I made.
Please do not hear this as three equal ways to pass. A claim about what Scripture says stands only on the first two. The label marks what I decided, so that you can see it.
No such claim rests on silence. If Scripture's own usage does not support it, and denying it breaks no text, I make no claim. The passage stays open.
I put my own test this way. The text must support the rule. And the rule must not contradict the text.
Most rules, and a few working agreements
Most of the rules in this book rest on what Scripture shows, or on what keeps two texts from contradicting, or on both.
A few are of another kind. They are working agreements. One is a default: what you do when no rule fixes a word. One is a burden rule: it says who must bring what. One holds only on a condition. These make no claim about what Scripture says by themselves. They are choices I made to keep a reading honest. I mark each one plainly as a choice I made.
Two rules have no basis written down in my notes at all. They are the citation rule and the witness-limit rule. I say so where I teach them. I do not dress them up as observed.
Many rules that rest on Scripture also hold one part that is a choice I made. Where a rule has such a part, I name it.
So every rule in this book carries two plain labels in its first lines. One is its status, which I explain below. The other is its basis: observed, forced, both, a choice I made, or no basis is written down for it. You will always know what kind of rule you are holding. Appendix A lists all 25 with both labels.
Every rule must also say what would make it lose. A rule that cannot lose is not a test. It is a slogan.
That brings me to the honest claim for a rule that passed. It is small. No contradiction found in the passages checked. That is all. It does not say the rule is true. It does not say the rule is safe. It says that I looked in many places and did not find a break.
Where the rules came from
The rules grew out of work on Jesus' talk on the Mount of Olives. You can find it in Matthew 24 and 25, Mark 13 and Luke 21. Most of the rules were first tried there. That is the test bed.
The examples in this book come from across the Bible. They are applications outside the main test bed. I chose them that way on purpose, so you can see the rules at work in more than one place. And I say so, because you should know.
I also looked at what outside writers say about how to read Scripture. I kept an idea only where Scripture's own usage gave named examples. That left nine candidates. I had them challenged with objections, twice. None of those nine is taught in this book. All nine are still only proposed, and still being tested.
The rule about the Bible's age words began another way. It came from a sort of 703 uses of those words, each read in its own verse in the NET. Before that, an AI checked an earlier, smaller sort, without being told what to expect. It found that the earlier version failed two of its own tests. Those were repaired. I tell you this because a rule is only as good as its first checks.
Who tried them
AI helped with this work. I will say so plainly. I did not do it alone. But a human, me, made every decision about every status.
I know how that may sound. In chapters 1 and 3 I warned you about smooth AI answers. Then I used AI to test my rules. So hear what the AI did, and what it did not do. It read, it objected, and it sorted. It never set a status. Nothing it said settled anything by itself. I made every call, and I ask you to check me too.
Here are the jobs the AI did.
A blind reader is an AI in a fresh chat. It has no memory of why the rules were written. It is given the rules and a set of cases. It is not told what answer is expected. It reads, and it reports what each rule gives.
A skeptic is an AI asked to raise the strongest objections that one view would raise. It speaks as that view's written paper records it, and never as a person. It may not invent a quote. Where the paper is silent, it writes no position. I name no view and no person in this book.
Other AI helpers sorted what the readers found, and marked each objection against the rules. Then I answered the open questions. A mark is never a verdict on a view or on a person.
What did the skeptics test? A long paper of mine. In it I apply these rules to Jesus' talk on the Mount of Olives, and I set out how I read it. In this book I call that paper the long argument. This book does not argue it. Here I take no side on what that talk means. The rounds on the long argument test my long argument. They do not test the Bible.
AI also drafted wordings, edited the long argument, and ran scripts that check quotes. I kept notes on all of it.
When to stop
A test with no stopping point never ends. Each fix gives the next reader something new to split on. A split is when two careful readers get two different answers from the same words. A split is useful, because it finds where the words are not tight. But I needed a place to stop, so I wrote down two stopping rules. The first is for a rule's wording. I change a wording only when a reader shows one of three things from the text. It gives a wrong label. It gives two different labels on one passage. Or it says the text does not tell where the text does tell. Any other split I write beside the rule as a limit. I wrote that rule down before I read the next result. The second is for the long argument. I stop testing it after two rounds in a row with no new confirmed error. That is a problem I checked and found true against the NET, the Greek and Hebrew word list, or the source the argument cites.
What the labels mean
Each rule in this book wears one of two status labels.
Passed. The rule held when it was tried.
Passed, limited. The rule held only in a narrower form, and the rule states that form.
There are 25 rules in this book. Ten are Passed. Fifteen are Passed, limited. A rule can be limited for plain reasons. It may be a working agreement: a default, a burden rule, or a rule that holds only on a condition. It may be weak. Part of it may be a choice I made. It may have been tested only by AI readers. It may hand one hard question to a wording that is still only proposed. Or it may not have been tested again since I ruled on it.
Each rule says what it cannot decide. That limit goes with the rule every time it is used.
Seven of the rules in this book came out of the tests themselves. They began as new wordings. Fresh readers tried them more than once, with fixes in between. Four other wordings were tried beside them in the same rounds, and those four did not pass. They stay proposed, with their open breaks listed. Many more wordings are only proposed. I leave them all out of this book on purpose, and the book never uses them as support.
Now hear a hard rule of my own. A status is a label on a rule. It is never the reason for a conclusion. I will not tell you a reading holds because its rule is Passed. If the verse and the rule do not show it, the label does not either.
A human sets every status. Each one has my own words behind it in my notes. For the nearness-length rule, my word was limited.
One rule's life
Let me tell you the life of one rule, in short. It is the nearness-length rule. Chapter 7 teaches it. Here is what it says.
A near word, such as soon, near, at hand or a little while, gives no number of years by itself. A length comes only from what the text adds. Where the text adds nothing, the answer is not decidable. It is never probably soon. It is never probably distant.
That is where it ended. It did not start there. Older wordings came first. Some failed and some were replaced, and chapter 12 tells how.
Then fresh readers tried it, more than once. Each time it ended with the same words: it passes in part. Two reader disagreements stayed open. I gave four rulings on what was open. Then I gave the rule its status. My word was limited.
The fresh readers did not read the wording again after my rulings. That is true, and the rule's limit says so. Five lines travel with the rule every time. One of them says it was not retested.
This is the shape of a rule's life. Many readers. Some breaks. A human ruling. A label. A limit that says what is still open.
A rule that failed
One rule that sounded good, the reused-word rule, failed on Luke 10:29 and Luke 10:36, and it is nowhere in this book as a rule. Chapter 12 tells that story in full, because a rule that sounds right can still fail on one verse.
The picture, explained
In chapter 3 I gave you one picture. An operating system for reading, not for the Bible itself. I call the whole set of tests the Bible Reading OS. Now I can tell you what it matches.
The tests are written as one long prompt. A prompt is a set of written instructions you give an AI. You paste it into an AI chat, add a passage, and the AI helps write an interpretation by the rules and shows its work.
Each part of the picture matches a fact.
- It sits between you and the passage. The prompt is pasted in front of the passage. It is not Scripture. It supplies no verse text.
- You choose what runs. The first line you paste says which rules to run. I call it the run line. Appendix C shows it.
- Each test keeps its limit. Every rule states its limit every time it runs.
- It shows its work. The answer begins by listing what was selected. It marks each verse by where its text came from. It shows what each rule gave.
- It sits below Scripture. No claim rests on silence. A status is never the reason.
- It guarantees nothing. The honest claim is the small one: no contradiction found in the passages checked.
The prompt also tells the AI how to behave. Appendix C lists those lines, so you can check for them.
That is the picture, part by part. The caution from the start of this chapter goes with every part of it.
The limits of the whole process
I want to be honest about what this process is and is not.
- The readers were AI readers. They were not outside human readers.
- The tests were run on the cases the readers were given. They were not run on every passage.
- Many rules are marked as not retested after my rulings.
- The rounds on the long argument test my long argument. They do not test the Bible.
- Counts from round to round are not like for like. A drop or a rise does not by itself mean improvement or harm.
- No result here is proof. A passed rule is not a proof either.
So do not trust the tests because of how many readers there were. Trust nothing here that you have not checked. If you find a quote that is off, tell me. If you find a rule used outside its limit, that is a finding too.
The honest claim for a passed rule is small: no contradiction found in the passages checked. A small claim, honestly kept, is worth more than a big claim that cannot lose.
Now the tests themselves, one at a time. We start with the most common mistake: hearing the same words and assuming the same event.
Three questions
- What two things can make a rule stand, and what can never make one stand?
- What is a split, and why is it useful to find one?
- What does it mean that a human decides every status?
Chapter 5. Same words, same event?
Chapter 5. Same words, same event?
You read two passages. They sound alike. The words match. So you think they are the same thing.
Maybe they are. Maybe they are not. That is the question for this chapter. Do the same words mean the same event?
Here is the plain answer. Shared words alone do not make one event. The text has to join them.
If the text joins them, you know. If only you join them, you only think you know. That is a small gap. It is also where a smooth voice can lead you a long way.
Picture it in a thread. Someone writes, "These two verses use the same words, so they are the same event." It sounds sure. It sounds checked. It may even be right. But the words are only the first step. The question is whether the text itself ties the two together. This chapter gives you five tests for that, and one habit.
A few things before the first test
From here to chapter 10, I teach the tests one at a time. A test and a rule are the same thing in this book. Each rule has four parts. The rule in one sentence. Where Scripture does it. An example in four short steps. And what the rule does not decide.
The four steps of each example are always the same. The words: I quote the verse. What the rule gives. What is shown. What is not shown.
Each rule also opens with two plain labels: its status (Passed, or Passed, limited) and its basis (observed, forced, both, or a choice I made). Chapter 4 explained them. Appendix A lists both labels for all twenty-five rules.
Hear the labels rightly. A label tells you how a rule was made and how it did when it was tried. It is never the reason a reading holds. The reason is always the verse.
One caution before the first rule: these tests are for reading, not for the Bible itself, so they sit below Scripture and guarantee nothing.
Now the first rule.
The same-words rule
Status: Passed. Basis: observed.
The rule in one sentence
"Two passages that share words are not shown to be one event by the words alone."
Say it again in plain words. Two stories can sound the same and still be two stories. The words match. That is not enough.
Where Scripture does it
I count this rule as observed. But I never wrote down a list of verses behind it. So I do not claim a list. I give you one place where you can watch it work. I checked that the place fits the rule's words and its limit.
The place is Mark. Mark tells of Jesus feeding a crowd, and later he tells of Jesus feeding a crowd again. The two tellings share many words. Mark himself keeps them apart.
An example, step by step
The words. Here is the first feeding, in part.
He took the five loaves and the two fish, and looking up to heaven, he gave thanks and broke the loaves. They all ate and were satisfied, and they picked up the broken pieces and fish that were left over, twelve baskets full. Now there were 5,000 men who ate the bread. (Mark 6:41-44 NET)
Here is the second feeding, in part.
After he took the seven loaves and gave thanks, he broke them and began giving them to the disciples to serve. Everyone ate and was satisfied, and they picked up the broken pieces left over, seven baskets full. There were about 4,000 who ate. (Mark 8:6-9 NET)
Look at the shared words. He took loaves, gave thanks and broke them, and they ate, were satisfied and picked up the broken pieces.
What the rule gives. The rule says the shared words, alone, do not show one event. You need more than the match.
Shown. The shared words alone would not tell you whether this is one feeding or two. But Mark gives you more. Later, Jesus speaks to the disciples:
When I broke the five loaves for the 5,000, how many baskets full of pieces did you pick up?” They replied, “Twelve.” “When I broke the seven loaves for the 4,000, how many baskets full of pieces did you pick up?” They replied, “Seven.” (Mark 8:19-20 NET)
Here Jesus counts two feedings. One had five loaves, 5,000 people and twelve baskets. The other had seven loaves, 4,000 people and seven baskets. So two events are shown. Hear this carefully. The "two" does not come from the rule. It comes from Jesus' own count.
So what did the rule do? It kept you from counting one event because the words matched. That is its whole job. It is a small job, and it is the first one.
There is also a small detail in the Greek. Mark uses one word for the baskets of the first feeding, kophinos, and another for the baskets of the second, spuris. The word list gives both the plain meaning "basket", and they are two different words. In Mark 8:19-20 the same two words stay apart. That fits the count. It adds nothing the count did not already give.
Not shown. The rule does not show that two passages are different events. The words alone neither join them nor split them. Here the split comes from the text's own numbers and Jesus' own question.
What it does not decide
The rule does not show that two passages are different events. It only says shared words are not enough to show one. It covers descriptive wording, not proper names. A name like Egypt or Judas is a different kind of match, and this rule does not reach it.
So when a voice in a thread says, "The words match, so it is one event," you can ask one thing. Does the text join them? If it does, point to where. If it does not, you say: not shown. And if a voice says, "The words match, so it must be two events," that is the same mistake turned around. The match decides nothing either way.
The citation rule
Status: Passed. Basis: no basis is written down for it.
The rule in one sentence
"A citation points to one verse only if the quoted words are in one place."
In plain words: when a writer quotes an older text, you can ask where the quoted words are. If they are spread over several verses, the quote cannot point to one verse. If they sit in one place, the rule does not block it. Hear the words "only if". The rule gives a condition a quote must meet. It does not say that meeting it is enough.
Where Scripture does it
This rule held when it was tried. But no basis is written down for it. I never marked it observed, and I never marked it forced. I will not invent a basis now. What I can do is show you the rule at work, where one New Testament writer quotes an older text.
An example, step by step
The words. Matthew writes:
He stayed there until Herod died. In this way what was spoken by the Lord through the prophet was fulfilled: “I called my Son out of Egypt.” (Matthew 2:15 NET)
Now the NET's Hosea:
“When Israel was a young man, I loved him like a son, and I summoned my son out of Egypt. (Hosea 11:1 NET)
Look at the English. Matthew has "called." Hosea has "summoned." The words are not the same in English.
What the rule gives. A citation points to one verse only if the quoted words are in one place. So I ask: are Matthew's quoted words in one place?
Shown. A search of the NET's English finds the words "son out of Egypt" in two verses only. One is Matthew 2:15 itself, the verse that does the quoting. The other is Hosea 11:1. So in the older books, the words sit in one place. In the original words, both verses use a word whose plain meaning is "to call". So "called" and "summoned" do not break the match. The rule's condition is met.
Now hear what that does and does not give. The rule does not block the quote from pointing to Hosea 11:1. It does not, by itself, make it point there. Matthew's own words do the pointing: "what was spoken by the Lord through the prophet". The rule only says the quote could not point to one verse if the words were spread over several.
Not shown. The rule compares words. It does not tell you that Matthew means what Hosea meant. That is a different question. It is also not shown that no other verse has these words in another language. The search was in English only.
A habit, not a rule: check the original words
Look again at that example. In English, "called" and "summoned" look like two different words. If you stopped there, you might say the words do not match.
Now look at the words under them. The Greek word behind "called" in Matthew is ekalesa. STEP, the free Greek and Hebrew word list I use, gives its gloss as "to call". The Hebrew word behind "summoned" in Hosea is karati. STEP gives its gloss as "to call" too. A gloss is a short plain meaning of a word. One idea in two languages. Two English choices.
This is a habit. It is not one of the twenty-five rules. It is how I read wherever the wording matters. When two English words differ, I check the words under them. When two English words match, I check too. If the original words agree, the English was only a choice. If they differ, I want to know.
I keep this small. I give a plain gloss and no more. I never say a word "really means" more than the gloss and the verse give. A habit like this costs a minute. It can save you a long fight over English words.
What it does not decide
The rule compares words, not small grammar points. It says where the quoted words are. It does not say what the quote means in its new place. For that, you read both passages, and you ask what each one says.
If a voice says a verse "is not really quoted" because the English differs, you can answer in two steps. Check the original words. Then check where the words sit. If they sit in one place, the rule does not stand in the way. Where the quote points is the writer's own words to show. What it means is a second question.
The parallel-account rule
Status: Passed, limited. Basis: forced, in its main part.
The rule in one sentence
"Each account witnesses what it itself reports; what both report is witnessed by both; comparing parallel accounts does not fix the exact words or the occasion; never argue from the exact wording of one account to what another must have said or left out."
In plain words: parallel accounts are two tellings of something close. Each one gives its own report. Where they agree, both stand behind it. Do not use one account's exact words to say what the other must have said. And do not decide the exact words or the occasion by lining the accounts up.
Where Scripture does it
The main part is forced. Each account witnesses what it reports, and what both report is witnessed by both. If we denied that, two accounts that word one thing differently would seem to clash. That would set Scripture against itself.
Hear what forced rests on. I hold that Scripture does not contradict itself. If you do not hold that, a forced rule will weigh less for you, and you should know that before you lean on it.
The rule has two other roots. One part came from a test that failed: a check for whether two accounts are one saying. I say more about that test in the borrowed-meaning section below. The last part, never argue from one account's exact words to what the other must have said, was kept from a limit I had already written down.
An example, step by step
The words. Mark and Luke both tell of the sign over Jesus on the cross.
The inscription of the charge against him read, “The king of the Jews.” (Mark 15:26 NET) There was also an inscription over him, “This is the king of the Jews.” (Luke 23:38 NET)
What the rule gives. Each account witnesses what it reports. Mark reports one wording. Luke reports a wording with "This is" in front. Comparing the two does not fix the exact words on the sign.
Shown. Both accounts report an inscription that called him the king of the Jews. They agree in substance. Both stand behind that much.
Not shown. The exact words on the sign are not shown. It is not shown that Mark left out "This is". It is not shown that Luke added it. The rule bars you from arguing that way.
I also do not claim, by this rule, that the two accounts tell of one moment. You may feel sure they do, and you may be right. But the word "parallel" does not show it, and lining up the accounts does not fix it. The rule asks the text, not the reader, to tie accounts together. Here I ask only what each account reports.
What it does not decide
The rule decides nothing about a difference in who spoke, how many spoke, or what was seen. That question stays open here. It also does not decide whether a reply like "You have said it yourself" counts as a yes.
Think of how this plays out on a screen. Someone writes, "Mark leaves out the words 'This is,' so the sign must have been different from what Luke says." That is a step from one account's wording to what the other must have said. The rule stops that step. Both accounts may be right about what each one reports. You do not need to pick a winner, and you do not need to guess at the sign.
Only AI readers, who were not told the answer, have tested this rule. No outside human readers have.
The borrowed-meaning rule
Status: Passed, limited. Basis: both observed and forced.
The rule in one sentence
"One account's wording does not fix another passage's meaning unless a same-saying test passes; a gloss is a narrator's own explanation of his own words and fixes the meaning only in that account."
First, a word about one word. The rule's sentence uses "gloss" for a writer's own note that explains his own words. Everywhere else in this book, a gloss is a short plain meaning of a word. So outside the rule's sentence, I call this kind of note a writer's note.
One more term. A same-saying test is a check that says whether two accounts report one saying.
In plain words: when a writer tells you what he meant, that holds in his book. It does not travel to another book on its own.
Where Scripture does it
The first lead is observed. It is John 6:70-71, below. Another part is forced, because without it two texts could be set against each other. A third part is a limit I had already written down: no same-saying test has passed. One was tried. It failed. So today none passes, and a writer's note never carries to another passage.
An example, step by step
The words. Jesus speaks, and then John adds a note of his own, in brackets.
Jesus replied, “Didn’t I choose you, the twelve, and yet one of you is the devil?” (Now he said this about Judas son of Simon Iscariot, for Judas, one of the twelve, was going to betray him.) (John 6:70-71 NET)
What the rule gives. A writer's own note on his own words fixes their meaning in that account.
Shown. John marks his own note. So in John 6, the words "one of you is the devil" are about Judas. John tells us. We do not have to guess.
Not shown. The rule does not show that John's note carries to any other passage. No same-saying test has passed. So if someone brings this note to another place, the answer is that one saying is not shown, and the note does not carry.
What it does not decide
No same-saying test has passed. So the rule cannot say that a writer's note carries to another passage. One question stays open. If a writer says hearers understood words in a certain way, is that also a marked note? The rule does not say. Only AI readers have tested it.
Why does this matter? Because a note in one place is easy to carry. A voice may say, "John told us what that saying means, so it means the same in the other book." The note is real. The carry is the added step. If the text itself does not make the carry, the answer is not shown.
The joining-words rule
Status: Passed, limited. Basis: forced, and held loosely.
The rule in one sentence
"Two things are one occasion only when the text joins them inside one sentence (‘when ... then’, ‘together with’); a plain ‘then’ joins nothing."
In plain words: two events are one occasion only when a sentence ties them. A "then" by itself is not a tie. It only puts one after another.
Where Scripture does it
I mark this rule forced, and I mark it to be held loosely. Forced means that if we denied it, two texts would contradict each other. Held loosely means I do not lean hard on it. That is why the limit below matters.
Why have it at all? Because a thread will often tie two events together with a plain "then". This rule says that is not enough. A sentence has to join them.
An example, step by step
The words. A word is given about a battle with the Philistines:
When you hear the sound of marching in the tops of the trees, then attack. For at that moment God is going before you to strike down the army of the Philistines.” (1 Chronicles 14:15 NET)
What the rule gives. Two things are one occasion when the text joins them in one sentence, with a join like "when ... then".
Shown. One sentence joins the hearing and the attack, and the join is "when ... then". Then the verse says it again with "at that moment". In the Hebrew, the word for "then" is az, and its gloss is "then". The hearing and the attack belong to one occasion. The text says so.
Not shown. No join across chapters or books is shown. The rule binds inside one sentence. It also does not show that a plain "then" somewhere else joins anything.
What it does not decide
It binds within one sentence. It does not bind across chapters or books. And it is best held loosely. Where no sentence joins two things, you say that. You do not make a join.
Compare the two feedings in Mark. No sentence joins them. Mark's own count tells you they are two. Compare the verse here. One sentence joins the hearing and the attack. That is the difference between a match and a join. A match is something you see. A join is something the text says.
What to carry out of this chapter
Five rules. One thread. If words match, you ask whether the text joins them. If the text joins them, say so. If only the match joins them, say that. Do not move on to more than the words give.
Each of the five said what it could not do. That is the point of them. A rule that tells you its limit is a rule you can check.
A match is loud. A join is quiet. A match catches the eye. A join sits in the sentence, and you have to read to find it. Stay with the sentence. Know what it says, and know where it stops.
Shared words alone do not make one event. The text has to join them.
Three questions
- What does Mark 8:19-20 add that the shared words alone could not?
- Why check the original words when two English words differ?
- In 1 Chronicles 14:15, which words join the hearing and the attack?
Some words are not about which event. They are about what kind of language you are reading: pictures, and words for long spans of time.
Chapter 6. Pictures, ages and a thousand years
Chapter 6. Pictures, ages and a thousand years
Some words in the Bible are plain. A man walks. A woman speaks. A door opens.
Some words are not like that. A cloud comes. The sun goes dark. The earth shakes. A thing lasts forever. A thing lasts a thousand years.
What do you do with these? You can guess. You can follow the loudest voice. Or you can look at how Scripture itself uses them. That is what this chapter does.
Think of the room in chapter 1. A calm voice says, "Clouds always mean the end." Another says, "Clouds never mean the end." Both sound sure. Neither one has shown you a verse. You want to know. You do not want to only think you know.
Three rules help here. The picture-language rule. The ages rule. The thousand-years rule. Each one opens with its two labels, status and basis, and each one ends with its limit.
The caution holds here too: these rules are for reading, not for the Bible itself, and no rule can make a cloud mean anything.
Here is the one line to keep. A picture can be used for a judgment on a named place. That fact alone does not show a final-events reading, and it does not rule one out.
The picture-language rule
Status: Passed. Basis: observed.
The rule in one sentence
"Cloud, sun-and-moon and shaking language is used for judgments on named places; by itself it neither proves nor rules out a final-events reading."
In plain words: when you see clouds, a dark sun or a shaking earth, ask who the passage is about. In several places in Scripture, those pictures fall on a named place. The picture alone does not tell you the world is ending. It does not tell you the world is not ending. You need more than the picture.
Where Scripture does it
This rule is observed. Scripture itself reads this way, and we can point to the verses. Here are three of them.
Isaiah names the place first.
This is an oracle about Babylon that Isaiah son of Amoz saw: (Isaiah 13:1 NET)
Then comes the picture.
Indeed the stars in the sky and their constellations no longer give out their light; the sun is darkened as soon as it rises, and the moon does not shine. (Isaiah 13:10 NET)
Ezekiel does the same for another place. He is told to "sing a lament for Pharaoh king of Egypt" (Ezekiel 32:2 NET). Then comes the picture.
I will cover the sun with a cloud, and the moon will not shine. (Ezekiel 32:7 NET)
The next verse closes in on the land.
I will darken all the lights in the sky over you, and I will darken your land, declares the Sovereign Lord. (Ezekiel 32:8 NET)
Zephaniah 1 has the same shape. It names Judah and Jerusalem, and in one place it speaks of "a day of clouds and dark skies" (Zephaniah 1:15 NET).
The pattern is plain. A named place. A picture of dark and shaking. This is the observed part. The rule says only that this is how the pictures are used in these places. It does not say they are used this way everywhere.
Notice what is missing. None of these verses says "this is only a picture." None says "this is not a picture." The verses name a place, and they give a picture of dark and shaking. The rule does not add to that. It does not need to.
An example, step by step
The words.
This is an oracle about Egypt: Look, the Lord rides on a swift-moving cloud and approaches Egypt. The idols of Egypt tremble before him; the Egyptians lose their courage. (Isaiah 19:1 NET)
What the rule gives. Cloud language is used for a judgment on a named place. Here the Lord rides on a cloud. The place is named. It is Egypt.
Shown. In this verse the cloud is tied to one named place. The verse names Egypt three times. The idols of Egypt tremble. So cloud words alone do not show that a passage is about the final events. The cloud, by itself, did not mean that here.
Not shown. Two things are not shown. First, the verse names the place and not the time, so it does not say when. Second, the rule does not show that a final-events reading is wrong. It cannot rule one out. Here is the same point, with both readings treated alike. If someone says cloud words show the end of the world, they have not shown it. If someone says cloud words cannot be about the end of the world, they have not shown that either. The words on the page have not settled it.
What it does not decide
The rule does not show what the picture language means in Matthew 24. It says nothing about that chapter. It says how the pictures are used in the places above, and it stops there.
When a voice in a thread says, "Clouds mean this," or, "Clouds can only mean that," you can ask one question. Where is the verse that names the place? If the voice has the verse, read it. If the voice has only the picture, you know what the picture can carry. It can carry a judgment on a place. It cannot carry more than that by itself.
The ages rule
Status: Passed, limited. Basis: both observed and forced, with some parts that are a choice I made.
The rule in one sentence
"Each use of the Bible's ‘age’ words (the Greek, Hebrew and Aramaic words translated ‘age’, ‘forever’ and ‘eternal’) is read only by the words of its own verse in the NET English; a verse with no listed word gets no time output."
In plain words: when the Bible says "age" or "forever" or "eternal," read that one verse. Let that verse tell you how long. Do not bring in a length from somewhere else. If the verse gives no length, the rule gives no length either. It says only what the word does not tell.
What the rule looks at
The rule has lists, and you should see them. Here they are, in short.
It reads six original words, and no others. The gloss of each is in brackets.
- Three Greek words: aiōn ("an age"), aiōnios ("eternal") and aïdios ("eternal").
- Two Hebrew words: 'olam ("forever") and 'ad ("perpetuity").
- One Aramaic word: 'alam ("perpetuity").
Each use of one of those words does one of eight jobs. A use gets a job only when its own verse prints a word from that job's list.
- Time past, as in "long ago".
- The ends of the ages.
- This present age.
- The end of the age.
- The age, or the ages, to come.
- The renewal of all things.
- A span whose limit the word does not state, as in "forever", "eternal" or "always".
- The world, or the worlds, that were made.
If the verse prints no word from any list, the rule writes "no time word printed", and it gives no answer about time.
Most uses do job seven. For those, the rule asks one more question. What does the verse itself say about an end? There are six answers.
- The verse prints an end.
- The verse prints a bound, such as a number of years.
- The verse puts an "if" on the span.
- The verse says, in other words, that there is no end.
- The verse puts a "not" on the word, as in "riches do not last forever".
- None of these. The end is not stated in this verse.
That last answer is the most common one by far. Hear it rightly. "Not stated in this verse" does not mean "without end". It does not mean "it ended". It means this verse does not say.
Where Scripture does it
This rule has three kinds of ground. I say which is which.
Part of it is observed. Each of the eight jobs, and each of the six answers about an end, has verses in Scripture behind it. Part of it is forced. Scripture does not say opposite things about one thing in one respect. If we denied that, two texts would contradict. Part of it is my own choice, since I chose where each list stops, and another reader might draw the line elsewhere. I say so.
The rule came from reading 703 uses of these words, each in its own verse in the NET. An AI that had not seen the aim of the work checked an earlier version, and it found two faults. Those were repaired.
An example, step by step
The words.
So the Lord said, “My Spirit will not remain in humankind indefinitely, since they are mortal. They will remain for 120 more years.” (Genesis 6:3 NET)
What the rule gives. The Hebrew word behind "indefinitely" is le'olam, a form of 'olam. Its gloss is "forever". The NET chose "indefinitely." It is one of the six words, doing job seven. So the rule asks what the verse says about an end.
Shown. The verse prints its own limit. It says "120 more years." That is the second answer on the list: a bound is printed. The age word does not give the length here. The verse does.
Not shown. The rule does not show what this word means in any other verse. It does not show when this age starts or ends. It gives no verdict on any doctrine. It reads one verse, and this verse tells the length.
Here is a second small case.
for riches do not last forever, nor does a crown last from generation to generation. (Proverbs 27:24 NET)
The word "forever" is there, and the verse puts a "not" on it. That is the fifth answer on the list. Genesis 6:3 has a "not" too, but there the verse also prints its own number. Here it prints none. So the verse tells you only that riches do not last forever. It does not say how long they last.
What it does not decide
The rule does not say when this age starts or ends. It does not say whether the ages overlap. It does not say whether the end of the age is among "all these things". It gives no verdict on any doctrine.
It covers only the six listed original words. For most uses it says only what the word does not tell. That can feel small. It is small. It is also honest. A rule that says "the verse does not tell" is doing its work. No outside reader has yet run the rule's current wording.
If you read "forever" in a verse, ask three things. What is the exact word in this verse? Does the verse print a bound or a "not"? If it gives neither, what is the rule's answer? The answer is that the verse does not tell. A quiet answer is better than a loud guess.
In a thread, this looks like a small question. Someone says, "Forever means without end, everywhere it is written." You can ask: In which verse? Read that verse first. Then read the next. The rule does not hand you a length for the word. It hands you the habit of reading the verse in front of you.
The thousand-years rule
Status: Passed, limited. Basis: a choice I made. I call this rule weak.
The rule in one sentence
"A thousand years can mean a long span."
In plain words: "a thousand years" does not have to be a count on a clock. In some places it is a way to say a long time. The word is "can." The rule does not say "must," and it does not say "always."
Where Scripture does it
I call this rule weak, and I will not make it sound stronger. It is one of the working agreements I told you about in chapter 4. I do not call it observed, and I do not call it forced. But it does not stand on nothing. Three verses stand behind it. Here they are.
Yes, in your eyes a thousand years are like yesterday that quickly passes, or like one of the divisions of the nighttime. (Psalm 90:4 NET) Now, dear friends, do not let this one thing escape your notice, that a single day is like a thousand years with the Lord and a thousand years are like a single day. (2 Peter 3:8 NET) if he should live a thousand years twice, yet does not enjoy his prosperity. For both of them die! (Ecclesiastes 6:6 NET)
Three books. A psalm, a letter and a book of wisdom. In each one, the number is used for a long stretch of time. The rule rests on that use, and on no more.
Say the rule the small way. If a verse uses "a thousand years," then it can be a long span. It can be. It does not have to be. Where a verse counts something else, you read that verse and nothing else. The rule is a door left open. It is not a door pushed through.
An example, step by step
The words. Psalm 90:4, above. A thousand years, in the eyes of the Lord, are like yesterday.
What the rule gives. A thousand years can mean a long span.
Shown. The psalm uses "a thousand years" for a long stretch of human time. It is long to us. It is short in God's eyes. So the number can stand for a long span here.
Not shown. The rule does not show how long the thousand years of Revelation 20 are. That is its limit. The word is "can." It does not fix the length.
A careful reader can push back here. They can say Psalm 90:4 is a figure about how God sees time. It does not tell us what a thousand years means in another book. That is fair. The rule agrees. It says only that a thousand years can be a long span. It does not say it is.
What it does not decide
"Can" does not fix the length in Revelation 20. That chapter is the place where this rule stops. I do not argue a reading of it here. Someone who says those thousand years are long has not shown it by this rule. Someone who says they are a count of exactly a thousand has not shown it by this rule either. The rule does not fix the length one way or the other.
The next chapter has a rule that leans on this one. It is about a book that calls something "soon." That rule holds only if a wait is long. This rule, which says only "can," is why that one is held with care.
Why keep a weak rule at all? Because it tells you what it is. A weak rule that says it is weak is easier to check than a voice that says it is strong. You know what you have. You know what you do not.
What to carry out of this chapter
Three rules. Three limits. Each program ran, said its limit, and stopped. That is all a program in this system should do.
If a picture appears, ask who it falls on. If an age word appears, read its own verse. If a thousand years appears, remember the word "can."
A picture can be used for a judgment on a named place. That fact alone does not show a final-events reading, and it does not rule one out.
Stay with the words on the page. Know what they say. Where they stop, stop with them.
Three questions
- What place does Isaiah 19:1 name?
- What limit does Genesis 6:3 print for itself?
- What does "can" leave open in the thousand-years rule?
The thousand-years rule leads straight into the hardest words of all: time words.
Chapter 7. Time words
Chapter 7. Time words
Some words ask when.
Soon. Near. At hand. This generation. Until. In a little while.
Voices on a screen love these words. They sound like dates. They sound like a clock. A calm voice can say "soon" and you feel the floor move.
But how much does the word tell you? Not as much as it sounds. This chapter shows how Scripture itself uses time words, and what the rules say you can and cannot know.
Five rules help here. The this-generation rule. The near-words rule. The nearness-length rule. The time-words rule. And the a-book's-"soon" rule.
Hear the caution: these rules are for reading, not for the Bible itself, and none can set a date the text does not set.
One line to keep from this chapter. A near word is true, but by itself it gives no number of years.
A word on fairness before we start. Some of these verses touch the end times. People disagree there, and many are sure. I take no side. I use the same three words for every reading: shown, not shown, shown against. Not shown is not a loss for anyone. It only means the page is quiet.
The this-generation rule
Status: Passed. Basis: observed.
The rule in one sentence
"‘This generation’ means the people alive when the speaker spoke."
In plain words: when Jesus or a prophet says "this generation," look for the people who were there. Those are the people the phrase names.
Where Scripture does it
I count this rule as observed. My notes say eleven NET verses stand behind it but never list them, and the NET has nineteen verses with the exact words "this generation". So I do not lean on a count. I show you cases you can check on the page. One is in Matthew. One is in Jeremiah.
An example, step by step
The words.
To what should I compare this generation? They are like children sitting in the marketplaces who call out to one another, ‘We played the flute for you, yet you did not dance; we wailed in mourning, yet you did not weep.’ For John came neither eating nor drinking, and they say, ‘He has a demon!’ The Son of Man came eating and drinking, and they say, ‘Look at him, a glutton and a drunk, a friend of tax collectors and sinners!’ But wisdom is vindicated by her deeds. (Matthew 11:16-19 NET)
The Greek word behind "generation" is genea. Its gloss is "generation".
What the rule gives. "This generation" means the people alive when the speaker spoke.
Shown. Jesus says what "this generation" is like. They say John "has a demon". They say the Son of Man is "a glutton and a drunk". These are the people reacting to John and to Jesus in that very time. They were alive when He spoke. The phrase points at them.
The Old Testament has the same pattern. A prophet says:
You people of this generation, listen to the Lord’s message (Jeremiah 2:31 NET)
He speaks to the people in front of him, and he calls them "this generation".
Not shown. The rule does not show what other sayings with the same phrase reach. Each saying is read in its own verse. The rule names the people. It does not name the events. It does not say what "all these things" covers.
What it does not decide
My notes give this rule a role, not a bound. They call it the one rule that fixes the deadline for the phrase. The nearness-length rule, later in this chapter, reads the sense of "generation" only through this rule. So this one is a gate. It names who. It does not tell what happens in their lifetime. For that, you read the verse and the other rules.
I must be plain about where this rule meets an argument. Three of the nineteen verses are in Jesus' talk on the Mount of Olives.
I tell you the truth, this generation will not pass away until all these things take place. (Matthew 24:34 NET)
Mark 13:30 and Luke 21:32 say the same. Few verses are argued more. Readers hold more than one sense of "this generation" there, and more than one view of "all these things". I take no side. Here is what the tests give, with the same words for each reading.
Applied there, this rule gives one sense of the phrase: the people alive when Jesus spoke. That is the rule's answer, and its limit comes with it. The rule names who. It does not say what took place in their lifetime.
- The reading that all these things took place within that lifetime: not shown by this rule.
- The reading that some of them did not, and are still ahead: not shown by this rule either.
The rule leaves both of those where they were. The time-words rule, later in this chapter, adds that no rule fixes what "all these things" covers.
Some readers hold another sense of the phrase itself. Where their sense and the rule's sense meet, the rule's answer is against theirs, and I say so plainly. But hear the limit beside it. The rule rests on eleven verses my notes do not list, so I cannot tell you whether Matthew 24:34 is among them. The rule gives one sense. It was not tested against every reason readers give for another. So the honest claim is the small one: no contradiction was found in the passages checked.
So when a voice in a thread says what "this generation" must mean, ask for the verse. Ask who was listening. If the voice has a verse, read it. If the voice has only a conclusion, you know what you have.
This program says what it cannot do. That is how you can check it.
The near-words rule
Status: Passed. Basis: observed.
The rule in one sentence
"‘Soon’, ‘near’ and ‘at hand’ are true but set no number of years and no limit."
In plain words: a near word is a true word. It is not a number. If a text says "soon," then what it says is true. But the word alone does not say how many years, or where the limit is. The rule holds both at once. The word is true. The number is not given.
Where Scripture does it
I count this rule as observed. But I never wrote down a list of verses for it. The example below is one I checked against the rule's words and limit. It is a day-of-the-Lord verse. The day of the Lord is a phrase the prophets use for a day when God acts in judgment, and people read those verses in different ways. So I treat every reading the same.
An example, step by step
The words.
The Lord’s great day of judgment is almost here; it is approaching very rapidly! (Zephaniah 1:14 NET)
The Hebrew word behind "almost here" is karov, with the gloss "near", and the word behind "very rapidly" is maher, with the gloss "quick". Both are near words.
What the rule gives. Near words are true, and they set no number of years and no limit.
Shown. The verse uses near words, but it prints no number of years with them and no limit.
Not shown. How many years is not shown. Whether the day came early or late is not shown. The rule cannot bind a passage to a date, and it cannot exclude one.
Now treat the readings alike. One person says, "The day is near, so it came soon after the prophet spoke." Another says, "The day is near, so it is still ahead." Neither has used the near word to show it. The word alone gives no number. That is the whole of this rule.
What it does not decide
The rule can never bind or exclude a passage. It says only that a near word, by itself, sets no length. Where a text adds a length, that is a different matter. The next rule takes it up.
Here is a simple test for a thread. Someone says, "The Bible says soon, so it must be within a few years." Ask: Where does the text give the years? If it does, read the verse. If it does not, the word "soon" is true and the years are not shown. That is not a loss. It is the place to stay until the text says more.
The nearness-length rule
Status: Passed, limited. Basis: observed in one part, and a choice I made in another. Most of it came out of testing, not from one verse.
The rule in one sentence
"A nearness word (‘soon’, ‘near’, ‘at hand’, ‘a little while’) by itself gives no number of years, no length and no limit. A length or limit comes only from what the text adds in the same saying or a tied text; where the text adds nothing, the answer is ‘not decidable’, never ‘probably soon’ or ‘probably distant’."
In plain words: the near word is not a number. If you want a number, the text has to give it. It may give it in the same saying, or in a text tied to it. If the text gives none, you say not decidable. You do not say probably soon. You do not say probably far.
Where Scripture does it
This rule has no single verse behind it. It came out of testing. Fresh readers tried it three times, six reader tests in all. Each time they found that it passed in part. Then I gave four rulings and set its status. Chapter 4 tells its life in short.
One part is observed, and one part is my own choice. The rule says that when a saying names "you", "we" or "us" as people who will see an event, that alone does not place the event in their lifetime. I see that in Paul's letters. Paul uses "we" both of people alive at the Lord's coming and of people raised from the dead (for example 1 Thessalonians 4:15 and 1 Corinthians 6:14). So that part is observed, in Paul. Using it in other books is a choice I made, and I say so.
An example, step by step
The words.
The days are at hand when every vision will be fulfilled. (Ezekiel 12:23 NET)
Then, a few lines later:
It will not be delayed any longer. Indeed in your days, O rebellious house, I will speak the word and accomplish it, declares the Sovereign Lord. (Ezekiel 12:25 NET)
The Hebrew word behind "at hand" is karevu. The word list gives it as "they have drawn near".
What the rule gives. A near word gives no length by itself. A length comes only from what the same saying adds, or a text tied to it.
Shown. The words "at hand" alone give no length. But the same message adds "in your days". That is a stated span. It is measured by the lifetime of the people addressed.
Now one care. The rule says that where parts of one message are joined by a word such as "For", as these are, you report two readings. If the two parts speak of one event, "in your days" gives "at hand" its span. If they speak of two, the span belongs only to the words it sits in. The rule does not choose, and neither do I.
Not shown. Which event the saying names is not shown. Whether any text was fulfilled at any date is not shown. And the span rests on the NET's English. The rule does not let a span rest on a Hebrew word's meaning alone, so it reports the span as resting on the English.
What it does not decide
Five lines travel with this rule every time. Here they are in plain words.
First, it tests only how near words are read. It takes no side on the end times.
Second, a word is judged by its Greek or Hebrew word, not its English. Where the word lists cannot show the sense, the rule says so. That happens in two places. Any span that rests on a Hebrew word is reported as resting on the NET's English. And for one word in Revelation, given in English as "soon" or "quickly", it is not shown whether the word tells when or how fast.
Third, there is one narrow exception, built on a single case in Matthew 28. It needs judgment.
Fourth, the sense of "generation" is read only through the this-generation rule.
Fifth, fresh readers did not test the rule again after my four rulings.
Those five lines make the rule honest. A rule with no limits would be noise.
Now see how it works on a screen. A voice says, "At hand means within one lifetime." Another says, "At hand means a long way off." The rule says neither word has been shown. If the same saying says "in your days," then a span is stated, and you can use it. If it says nothing like that, the answer is not decidable. That answer may feel empty. It is not. It is true.
Why is "not decidable" a good answer? Because the other two answers add something the text did not give. "Probably soon" adds years. "Probably distant" adds years too. One adds few. The other adds many. Both are guesses. A guess that sounds calm is still a guess. The rule asks you to leave it out. You stay with what the text said. You know what it said, and you do not pretend to know more.
The time-words rule
Status: Passed, limited. Basis: a choice I made. It is a default.
The rule in one sentence
"Each time word is read in its own verse; no general rule fixes how far a deadline reaches."
In plain words: "until," "then," "after" and their cousins each live in one verse. Read the word where it stands. Do not carry its length from a different verse.
Where Scripture does it
This one is not observed and not forced. It is a default. A default is what you do when nothing else decides. When no rule fixes a time word, you read it in its own verse. That is a choice, and it is mine. It is one reason the rule is limited.
The rule also carries a list of dating words. That list is still under review, so I leave it out of this book.
An example, step by step
The words.
My children—I am again undergoing birth pains until Christ is formed in you! (Galatians 4:19 NET)
The Greek word behind "until" is mechris, with the gloss "until", and a small word, hou, "which", comes after it.
What the rule gives. Read the time word in its own verse. No general rule says how far it reaches.
Shown. The word "until" sets a stop for Paul's labor. The stop is an event: "Christ is formed in you". It is not a date. The verse tells you what ends the labor.
Not shown. When that happens is not shown, and what comes after is not shown. And the rule does not say what "all these things" covers in any other verse.
Here is a second quick case, to see the rule on a plain verse. Matthew writes:
He stayed there until Herod died. (Matthew 2:15 NET)
Again "until" sets a stop. Again the stop is an event, the death of Herod, and not a date. Two verses, two stops. Each one is read where it stands. Neither one tells you the length of the other. That is the rule at work.
What it does not decide
It does not fix what "all these things" covers. It does not set how far a deadline reaches. It only says: read this word in this verse.
That can feel like a small thing. It saves you from a big mistake. The mistake is to take a length from one verse and press it on another. Say a voice shows you "until" in one verse and says it must work the same in a verse far away. Ask for the second verse. Read its own words. The first verse may help you see. It does not decide.
If you know, you say so. If you only think you know, you say that instead.
The a-book's-"soon" rule
Status: Passed, limited. Basis: a choice I made. It holds only on a condition.
The rule in one sentence
"A book cannot call ‘soon’ what it places after its own long wait."
In plain words: if one book says "soon" about an event, and the same book puts that event after a long wait, the book would be saying two things at once. This rule says a book does not do that.
Where Scripture does it
I do not call this rule observed or forced. It is a working agreement, and it holds only on a condition: the wait must be long. If the wait is not long, the rule says nothing.
Say it as two lines. If the wait is long, then the book does not call "soon" what it places after that wait. If the wait is not long, then the rule has nothing to say. The whole rule hangs on that "if."
No worked example here
I give no worked example for this rule. I want to tell you why.
The verses this rule was first built on are in the last book of the Bible. A careful reader could read those verses two ways. I do not want to pick one and call it clean. Chapter 12 shows them, with the places where readers could differ. They belong where I can be honest about the doubt.
So here I give you the rule, its condition and its limit. Nothing more.
What it does not decide
First, the rule depends on the wait being long. And the thousand-years rule in chapter 6 is the rule that speaks to long spans. That rule is weak. It says a thousand years can be a long span. It does not say it is. So the two rules lean on each other, and one of them leans lightly.
Second, no rule says when the thousand years begin.
Third, another rule in this chapter says it is not shown whether that book's word for "soon" tells when or tells how. If the word tells how fast and not when, the starting point of this rule is not shown.
I tell you these things so you do not take the rule too far. If a voice uses it to say a book "cannot" mean something, ask: Is the wait long? No rule I teach fixes that. If it is not fixed, the rule does not run.
What to carry out of this chapter
Five rules. One thread.
A time word is true. It is not a clock. If the text adds a span, use the span. If the text adds nothing, say not decidable. Do not fill the gap with a guess. A guess is noise. Not shown is quiet.
Stay with what the text says. Know what it gives. Where it gives no number, do not make one.
A near word is true, but by itself it gives no number of years.
Three questions
- Who are "this generation" in Matthew 11:16-19?
- What does Ezekiel 12:25 add that "at hand" alone does not?
- In Galatians 4:19, what sets the stop for "until": a date or an event?
Time words ask when. Death words ask what kind. What does it mean to die?
Chapter 8. Death words
Chapter 8. Death words
A word is like a door. It can open into more than one room.
Take the English word "dead". A phone can be dead. A road can be a dead end. A man can be dead tired. A person can be dead. It is one word with four rooms. When you hear the word, you do not yet know which room you are in. The sentence tells you.
The Bible has the same thing. The words for "die", "dead" and "death" carry more than one sense. A sense is one of the ways a word is used. If you pick the wrong sense, you get the wrong reading. You will not feel the slip. It will feel smooth.
So here is the question for this chapter. When the Bible says someone died, or is dead, is it always talking about the body?
I will not answer that for you. The tests do something smaller. They tell you what a verse shows and what it does not. If a verse shows it, you may say it. If a verse does not show it, you wait. That is the whole habit.
Three tests are in this chapter. The death-sense rule sorts the uses of the death words. The mortal-body rule is about one word of Paul's. The death-ends-once rule says what it means when the text says death is ended for good.
With words this weighty, keep the caution: these tests are for reading, not for the Bible itself, and none tells you what death is.
And the tests are for everyone. They are for the voice in the video. They are for you. They are for me.
The death-sense rule
Status: Passed, limited. Basis: forced in some parts, and a choice I made in others.
The rule in one sentence
The death-sense rule sorts each use of the death words into one kind. Here is its plain sentence.
It sorts uses of "die", "dead" and "death" by looking for one of seven signs in the Hebrew or Greek (for example a phrase that says how a person stands toward someone or something, as in "died to sin"), and writes one label from a fixed list, or "the text does not tell".
Here it is in everyday words. The rule looks at the words around a death word. If a sign is there, the rule writes a label. If no sign is there, the rule writes that the text does not tell. It does not guess. It does not fill a gap with what it expects.
Notice where the signs live. They live in the Hebrew or Greek words. They do not live only in the English. The English can hide what the first words say. So the rule goes back to the first words. That is the habit of checking the original words, and chapter 5 taught it.
What the rule looks at
You should see the lists, so here they are, in short.
The death words. The rule reads only these: die, dead, death, crucified, buried, and a word for life or rising when it is set against a death word in the same passage. No reader may add a word. That includes you. It includes me.
The seven signs. The rule looks for one of these in the words around the death word.
- A phrase that says how a person stands toward someone or something, such as "died to sin", or being buried with Christ.
- The same person is shown alive while the death word is said of him.
- The text tells plain facts about the body, such as an age at death, a burial, or a body that is struck down.
- The use is tied to something else in the text that says what it is about. This sign has strict conditions of its own.
- The text says the same person, at the same time, is dead and not dead.
- The thing called dead is not a person or a living creature, such as faith or works.
- One Hebrew word is used both ways. This sign is only a caution. It gives no label.
The labels. The rule may write only these: Relational. Not a completed bodily death. Alive when speaking. Not bodily. Bodily death. Not that bodily death. Or: the text does not tell.
Where Scripture does it
This rule is a mix. I want you to see the mix, so I will say it plainly.
Some parts are forced. Forced means that if we denied the part, two Bible texts would contradict each other. The rule's own case for this is John 11:21-25. One part of the fourth sign has only that one case where it works. I count that as a limit.
Some parts are my own choice. That means neither Scripture's usage nor a contradiction decides the part. So I chose it, and I say so. The rule marks each of those parts as my choice.
Two more things you should know, and you should hear them from me, in the order they happened.
First, one clause of the fourth sign, about when two sayings are tied together, kept giving readers something new to split on. So I froze the text. I did not freeze it because it was perfect.
Second, after the freeze I changed one other clause twice. It is about when a person in a story counts as speaking for God, for example when he says he brings a message from the Lord. No reader has tested that clause since. Where an answer turns on it, the rule says so and stops. The rule's label rests on the earlier tests. Appendix E tells the dates, and why I stopped.
An example, step by step
Here is one short passage. Paul writes to believers in Rome.
The words. "Absolutely not! How can we who died to sin still live in it?" (Romans 6:2 NET). The Greek word behind "died" is apethanomen. A Greek word list gives it as "we died", from the word "to die".
What the rule gives. The phrase "died to sin" says how a person stands toward something. That is the first of the seven signs. When that sign is there, the rule writes one label from its list: Relational.
Shown. The label fits this use, because the words "died to sin" are about how a person stands toward sin. The rule gives no finding about the body here. It does not say yes. It does not say no.
Not shown. What condition anyone is in before God, what happens when a body dies, and whether this verse speaks of a body at all. The rule does not say. A quiet page is not a no. It is only quiet.
Look at what the rule did not do: it did not call this use "unreal" or rank it below another use. It only sorted. A sorter is not a preacher. If the rule is used to preach, it is used past its limit.
What it does not decide
The rule does not say what condition anyone is in before God. It does not say what happens after the body dies. Those questions may matter more than any others. But this rule does not answer them. If someone says it does, they are using it past its limit.
The rule sorts only by its fixed list of signs. If no sign is in the words, the answer is "the text does not tell". That answer is not a loss. It is an honest place to rest.
The rule never calls a use less than real. It never ranks one use above another. It never adds a word to its list.
And the rule's own limit says this. One part of one sign has one case where it works. One clause was changed twice and not tested. The rule held when it was tried, but only in this narrower form. I want you to carry that with you whenever you use it.
The mortal-body rule
Status: Passed. Basis: observed.
The rule in one sentence
The mortal-body rule is about one Greek word. It is Paul's word for "mortal".
Paul's word for "mortal" (six uses, all in Paul's letters) means the physical body.
In everyday words: when Paul says "mortal", he is talking about the body that can die. He is not talking about a spirit or an idea. The rule counts his uses. There are six. All six are in his letters.
Where Scripture does it
This rule is observed. Observed means that Scripture itself reads this way, and we can point to the verse.
Here are the six places. A word list for the Greek shows exactly six uses in the whole New Testament. They are Romans 6:12, Romans 8:11, 1 Corinthians 15:53, 1 Corinthians 15:54, 2 Corinthians 4:11 and 2 Corinthians 5:4. All six are in Paul's letters, and none is in another writer. You can look each one up. If you find a use that goes against the rule, the rule has lost. I will not hide that.
Now look at the six in the Greek, because the English can hide something here.
In three of the six, the word for "mortal" goes with a body word in the same phrase. In Romans 6:12 Paul writes, "do not let sin reign in your mortal body" (Romans 6:12 NET). The Greek word for "body" there is sōmati, with one small word, "your", between the two. In Romans 8:11 he writes, "will also make your mortal bodies alive" (Romans 8:11 NET). And in 2 Corinthians 4:11, below, the Greek word goes with "flesh".
In the other three, the word stands alone. Paul writes "this mortal" in 1 Corinthians 15:53 and 15:54, and "what is mortal" in 2 Corinthians 5:4. In 1 Corinthians 15:53 the NET adds the English word "body": "this mortal body must put on immortality" (1 Corinthians 15:53 NET). The Greek has no word for "body" there.
So here is the honest count. Three of the six put "mortal" right beside a body word, and three do not. The rule reads all six as the physical body. In those three, that reading comes from the verses around them, not from a body word beside it. Weigh it with that in mind.
An example, step by step
Now one passage, worked slowly.
The words. "For we who are alive are constantly being handed over to death for Jesus’ sake, so that the life of Jesus may also be made visible in our mortal body." (2 Corinthians 4:11 NET). The Greek word behind "mortal" is thnētē, and the word list gives it as "mortal". There is a small catch. The NET says "body", but the Greek word here is sarki, "flesh". The English and the Greek differ a little, so I tell you both.
What the rule gives. Paul's word for "mortal" means the physical body.
Shown. Paul puts his word for "mortal" beside a body word, which here is "flesh", while in the two verses above it is "body". So in all three, "mortal" stays beside the physical. The rule says "physical body". Flesh fits that.
I must be honest about one thing. A careful reader could say this verse shows "mortal flesh", not "mortal body". That is a fair point: the word is flesh, and the rule's word is body. I think flesh fits, but you can weigh it for yourself. That is why I show you the Greek.
Not shown. Any use outside Paul. There is none, as far as the word list shows. But that is a test result, not a final word. I looked and found no use that goes against the rule. I did not show that no such use could exist.
Also not shown: what happens to the mortal body later. This verse does not say. The rule does not say either.
What it does not decide
The rule speaks of Paul's six uses. It does not speak of other writers. If another writer uses a word that looks the same in English, the rule does not reach it.
The rule's own limit says only that no counter-case was found. That records a test result. It does not set a wall. If a counter-case comes, the rule must give way. And remember the count above: in three of the six uses, the body reading rests on the verses around the word.
The rule does not say what happens to the body after death. It does not say what a person is. It says what one word of Paul's is about.
The death-ends-once rule
Status: Passed. Basis: forced.
The rule in one sentence
The death-ends-once rule is short.
Where the text says death is ended for good, that ending happens once.
In everyday words: if a verse says death is ended for good, then there is one ending, not two. The rule also covers decay, not only death. But it applies only where the text says the ending is complete. If the text does not say that, the rule stays out.
Where Scripture does it
This rule is forced. Forced means that if we denied it, texts would contradict each other. There is also plain logic in it.
Here is the logic. Say a text declares that death is ended for good. Then say death comes back, and a second text ends it again. Then the first ending was not for good. The two texts would not agree. So if the first text is true, the ending happens once.
I know that is a short argument. It is not a long one. Some good rules are short.
The rule keeps you from two slips. The first slip is to say death is ended twice. The second is to say every verse with the word "death" in it ends death. Neither follows. If the verse says it, the rule applies. If the verse does not say it, the rule stays out.
Notice the word "for good". It is the key. The rule does not say death is ended once wherever the word "death" shows up. It says so only where the text says the ending is complete. That is a narrow door. I keep it narrow on purpose.
An example, step by step
Here is one verse from Isaiah.
The words. "he will swallow up death permanently." (Isaiah 25:8 NET). The NET says "permanently", and the Hebrew word, lanetzach, is given in the word list as "to perpetuity". The English and the Hebrew agree. The ending is for good.
What the rule gives. Where the text says death is ended for good, that ending happens once.
Shown. This verse says the ending is for good, so the rule applies. The swallowing up of death is one ending, not two.
Not shown. When it happens, which later passage tells the same ending, and whether "death" here is the death of the body or something else. The full rule covers death or decay, but it does not say which kind. The death-sense rule is the one that sorts kinds. This rule does not.
A reader may place this verse in Isaiah's own day. Another may place it at the end of all things. This rule does not choose, and a reader on either side meets the same limit. The verse gives no date. And a verse that gives no date shows no date. That is not the same as showing it is far, or showing it is near.
What it does not decide
The rule applies only where the text states that the ending is complete. In any other verse, it stays out.
It does not say when. It does not say which verse tells the ending. It does not say what kind of death.
I chose Isaiah 25:8 because it is clean. It says "permanently". It does not need me to add a thing. Some other verses have a proposed change to this rule still being tried on them, so I did not use them here.
What to carry out of this chapter
Here is the one sentence I want you to keep. One word can carry several senses. The verse has to tell you which.
Each of the three rules told you where it stops. Keep the stop with the rule. A rule that has lost its limit is just a loud voice.
Do not choose the sense first and then read the verse. Read the verse first. See which signs are in the words. Then say what you can say. Then stop.
If a sign is there, name it. If no sign is there, write that the text does not tell. If the Greek or Hebrew word differs from the English, say both. If you cannot find it, rest. You are not behind. You are not wrong. You are just not done.
Three questions
- Does "died to sin" in Romans 6:2 tell you anything about the body? What does the rule give instead?
- How many times does Paul use his word for "mortal", and what does it go with?
- What word in Isaiah 25:8 says the ending is for good?
Some readings rest on what someone saw. If I say, "I saw it," do you know what I saw? Do you know how I know? Who saw it, and what can a witness speak to? The next chapter takes up those questions.
Chapter 9. Who saw it?
Chapter 9. Who saw it?
If you tell me, "I saw it," I may believe you. If five people tell me, I may believe it more. But then I should ask three plain questions. What did they see? What did they not see? And what can a witness speak to?
A witness is a person who says what he saw or heard. A record is a written account. Scripture has both. It names witnesses, and it keeps records. This chapter asks how Scripture treats the people who saw things happen.
I need one more word. Scripture's own voice means the writer of a book of the Bible speaking in his own words. It is not a person he quotes. When a Gospel writer tells you what happened, that is Scripture's own voice. When a man in his story says something, that is a man's voice inside the story. The two are not the same. Keep them apart, and many knots come loose.
There are five tests in this chapter. They come in a line. The first two are about counting witnesses. The next two are about what kind of witness a person is. The last one is about the edge of what a witness can say.
Keep one caution in view: these tests are for reading, not for the Bible itself, and no rule can make a witness see more than he saw.
The two-or-three witnesses rule
Status: Passed. Basis: observed.
The rule in one sentence
This rule is about a charge. A charge is a claim that a person did wrong.
In a charge against a person, two or three agreeing witnesses are needed.
In everyday words: one voice is not enough to charge a person. Two or three voices that agree are. The rule is for charges. Keep that word in mind. It matters in a moment.
Where Scripture does it
This rule is observed. Observed means that Scripture itself reads this way, and we can point to the verse. Scripture says it in its own words in Deuteronomy 19:15.
This is a law. It tells a people how to handle a charge. Nothing in the verse tells you how to handle a report of an event. We will come to events in a moment. They have their own rule.
An example, step by step
The words. Here is the verse. "A single witness may not testify against another person for any trespass or sin that he commits. A matter may be legally established only on the testimony of two or three witnesses." (Deuteronomy 19:15 NET).
What the rule gives. In a charge against a person, two or three agreeing witnesses are needed.
Shown. For a charge of trespass or sin, one witness is not enough. The verse says it twice: first what may not be done, then what must be done. The words are plain.
Not shown. Any use for events in history. The verse speaks of a charge against a person. It does not say that every event needs two witnesses before we may say it happened. A missing witness does not show that a claim is false.
What it does not decide
The rule is for charges. It is not applied to events in history.
Here is why this matters. You may hear someone say, "The Bible says only two witnesses count." Ask one thing. Count for what? If it is a charge against a person, the verse says so. If it is whether an event happened, the verse has not said so. Do not carry a rule from one use to another.
A missing witness does not show a claim is false. It does not show a claim is true. It leaves the claim where it was.
Now a habit for the thread. Say three people repeat one claim. Ask a plain question. Did each of them see it, or did all three hear it from one source? A witness is a person who saw or heard. A voice that repeats is not a witness. If three saw, you have three. If one saw and two repeated, you have one. The verse says "witnesses". So count the ones who saw.
The two-or-three witnesses rule for events
Status: Passed, limited. Basis: observed, with one sentence that is a choice I made.
The rule in one sentence
The first rule had a limit. It is not applied to events. But later I opened a small door in that limit. This rule is the opened part. It speaks of records outside Scripture. An outside record is a written account that is not in the Bible. Here is its plain sentence.
Agreeing witnesses may also count toward an outside record that an event in history happened, and toward the time the record states for it, only through the outside-record rule; the count is a help, never a requirement, and one witness who saw can be enough (John 19:35).
That is long, so let me say it in everyday words. Agreeing witnesses can help when we weigh an outside record. But this rule never works alone. It works only through the outside-record rule. That rule is taught in chapter 10. For now you need only its heart: a record from outside the Bible is written down as an outside record, never as Scripture. The count of witnesses is a help. It is never a requirement. And one person who saw can be enough.
Where Scripture does it
Scripture uses witnesses for events. It uses them in more than one place. In this chapter I show you two pictures of that. Chapter 12 shows one more, from the book of Ruth, and tells where readers read the count two ways.
I must tell you what is mine here. The sentence about the count is my own choice. Neither Scripture's usage nor a contradiction decides it. So I chose it, and I say so. When the rule was tried, careful readers read the count sentence two ways. That split is mine to settle, and I have not settled it. No test has yet looked at this rule by itself.
And hear this. The two pictures in this chapter are from inside Scripture. The rule itself is not for those. It is for records outside Scripture. So the pictures only show you that Scripture treats witnesses and records this way. They do not run the rule.
An example, step by step
Jeremiah buys a field. "So I bought the field at Anathoth from my cousin Hanamel." (Jeremiah 32:9 NET). Then he tells how the purchase was made firm.
The words.
I signed the deed of purchase, sealed it, and had some men serve as witnesses to the purchase. I weighed out the silver for him on a scale. There were two copies of the deed of purchase. One was sealed and contained the order of transfer and the conditions of purchase. The other was left unsealed. I took both copies of the deed of purchase and gave them to Baruch son of Neriah, the son of Mahseiah. I gave them to him in the presence of my cousin Hanamel, the witnesses who had signed the deed of purchase, and all the Judeans who were housed in the courtyard of the guardhouse. (Jeremiah 32:10-12 NET)
What the rule gives. Agreeing witnesses may count toward a record that an event happened. The count is a help, never a requirement.
Shown. Scripture itself uses witnesses and a written record to stand behind an event. The event is a purchase. There are men who serve as witnesses. There are two copies of the deed. There are people present when the deed is handed over. The words give no number of witnesses, only "some men", so the example does not turn on a count.
Not shown. That two or three are required for events. The verses do not say so. And not shown that falling short of some count would make an event "not shown". The rule says the count is a help, not a bar.
Now one more verse. The rule points to John 19:35. "And the person who saw it has testified (and his testimony is true, and he knows that he is telling the truth), so that you also may believe." Here one person is named. He saw it. He testified. The verse gives no count. That is why the rule says one witness who saw can be enough. I want to be careful. This verse is a pointer, not a full answer. It does not show that one witness is enough for every event. It shows that Scripture's own voice leans on one person who saw.
What it does not decide
The opened part works only through the outside-record rule. If that rule is not selected, this one has no work to do.
It does not set a number. It does not say that two or three are needed for an event. It does not say that a smaller count makes an event "not shown".
The count sentence is my own choice, and I say so again. Careful readers read it two ways.
The bodily-act witnesses rule
Status: Passed. Basis: observed.
The rule in one sentence
When Scripture says God did a bodily act in history, it says who saw it (not always the public).
In everyday words: if Scripture says God did something in the body, in history, it also says who saw it. It tells us who. It does not always say everyone.
Where Scripture does it
I count this rule as observed. The place I show you is in Acts, and I must label it with care. The words are Peter's. Luke reports them. Peter starts speaking at Acts 10:34, and the words below come a few verses later.
By this chapter's own line, that is a man's voice inside the story, not Scripture's own voice. Luke does not correct Peter's words. Still, a speech inside a story is not the same as the writer speaking. So take this as a picture of the rule, given in a speech that Luke reports. It is not Scripture's own voice saying it.
The rule does not say exactly what a bodily act is. That is a gap. In some verses no one is named as doing the act, and the rule does not say whether those count. So I chose a plain case. "God raised him up" is plainly an act done to a body. My example tests the rule, not its gap.
An example, step by step
The words.
but God raised him up on the third day and caused him to be seen, not by all the people, but by us, the witnesses God had already chosen, who ate and drank with him after he rose from the dead. (Acts 10:40-41 NET)
The Greek word behind "witnesses" is martusin. A Greek word list gives it as "witness".
What the rule gives. When Scripture says God did a bodily act in history, it says who saw it.
Shown. In Peter's words, God's act is stated: he raised him up. And the words say who saw him: the witnesses God had already chosen, who ate and drank with him. So the words do two things. They say who saw. And they say who did not: "not by all the people". Both are in the words.
Not shown. That the public saw it. The words say "not by all the people", so the rule does not say the public saw. The rule's limit says the number varies and the answer is not always the public. And there is a third line: the witnesses are never the only thing.
The rule does not explain that third line. So here is how I read it, and it is only my reading. In Acts 10:41 God is the one who chose the witnesses. God is the one who raised him. God is the one who caused him to be seen. So the seeing sits inside what God did. The witnesses are not the whole story.
What it does not decide
The rule does not say the public saw. These words themselves say "not by all the people".
It does not give a number. The number varies from place to place.
It does not say what a bodily act is in every case. Where no one is named as doing an act, it does not say.
It does not say that a witness is all you need. It does not say what any witness saw, beyond what the passage says. And it does not settle whether a speech inside a story, like Peter's, counts as Scripture saying it. I note that so you can weigh the example.
The witness-kinds rule
Status: Passed, limited. Basis: observed in most parts, with parts that are a choice I made.
The rule in one sentence
For each record, write who the witness is, what he witnessed, and how; a writer who did not himself see or hear is giving a report, and its weight follows the chain he names back to someone who did.
In everyday words: do not just say "a witness says". Ask three things. Who is he? What did he see or hear? And how does he know? If a writer did not see or hear it himself, he is giving a report. A report is a real thing. It is not thrown out. But its weight follows the chain he names. If he names a chain back to someone who saw, the report is as strong as that chain.
Where Scripture does it
Most of this rule is observed. Scripture points to the people who saw, and it points to the way each one knew.
Its last line is different. It was carried over from a wording that is not in the tests I use, and it was not tested on its own. That line says no kind of witness decides which event a prophecy named. Because it was carried and not tested, I treat it as a limit, not as a finding.
I use three kinds. The first kind is the people Scripture shows with Jesus and chosen as his witnesses. Jesus says to them, "You are witnesses of these things." (Luke 24:48 NET). Acts 10:41 names them, as you saw.
The second kind is Paul. Paul says the risen Jesus appeared to him. "he appeared to me also" (1 Corinthians 15:8 NET). He also says where the gospel he preached came from. "I received it by a revelation of Jesus Christ." (Galatians 1:12 NET). I write Paul's witness in the words of the verse the finding rests on. I write "revelation" only where the verse itself says so.
The third kind is every other writer. He is a witness only of what he himself saw or heard. Beyond that, he gives a report.
Now hear this. The three kinds are a frame, and the frame is my own choice, since no verse in Scripture sorts witnesses into three kinds. I made the frame to help us look. If it does not help, put it down.
An example, step by step
Here is how Luke begins his Gospel.
The words.
Now many have undertaken to compile an account of the things that have been fulfilled among us, like the accounts passed on to us by those who were eyewitnesses and servants of the word from the beginning. So it seemed good to me as well, because I have followed all things carefully from the beginning, to write an orderly account for you, most excellent Theophilus, so that you may know for certain the things you were taught. (Luke 1:1-4 NET)
The Greek behind "eyewitnesses" is autoptai. The word list gives "eyewitness". The Greek behind "followed" is parēkolouthēkoti. The list gives "having been acquainted", from the word "to follow". The English and the Greek are near each other. I tell you both.
What the rule gives. Write the witness, what he witnessed, and how. A writer who did not see it is giving a report. Its weight follows the chain he names.
Shown. Luke names a chain: there are eyewitnesses, there are those who passed on accounts, and there is Luke himself. He writes as one who followed the chain. He does not write as an eyewitness. By the rule, his account is a report, with the chain named. And he says why he writes. He writes "so that you may know for certain the things you were taught". So the account is offered to be used.
Not shown. What each eyewitness saw, or which event a prophecy named. No kind of witness decides that. And the account is not thrown out because Luke was not an eyewitness. The rule says a report is not a witness, and it is not thrown out.
What it does not decide
The three kinds are a frame, and the frame is my own choice.
The rule does not sort people a record only reports, who wrote nothing. It does not decide which event a prophecy named. That last line was carried over, not tested, so it stands here as a limit. A witness of one thing may not be a witness of another. A letter writer counts as Scripture's own voice, unless he says otherwise in the passage.
And this rule has been tried only by AI readers, so weigh it with that in mind.
The witness-limit rule
Status: Passed, limited. Basis: no basis is written down for it.
The rule in one sentence
This is the last test of the chapter. It is about the edge of what a witness can say.
Witnesses speak to what happened, not to links between passages or to which event a prophecy named. This does not cancel a statement in Scripture's own voice that an event fulfilled a saying: that statement is Scripture naming the link, not a witness deciding it.
In everyday words: a witness tells what he saw. He does not tell which old saying it matches. If Scripture itself says "this fulfilled that", then Scripture is the one who says it. The witness is not the one deciding.
Where Scripture does it
No basis is written down for this rule. I tell you that plainly. I do not call it observed, and I do not call it forced. It reuses two sentences from wordings that are still only proposed. Those two sentences held when two readers tried them. The rule is passed. The wordings they came from are not.
Why keep the two apart? A person who saw an event is a good source for what happened. A link between that event and an old saying is a different question. If one voice answers both, a hearer may think the witness saw more than he did. The rule keeps each voice to its own work.
What I can do is show you a place where the two parts sit in one scene. That is John 19:35-37. The scene is the death of Jesus. The witness is named. The link to the old saying is named too. But they are named in different places, and by different voices.
An example, step by step
The words.
And the person who saw it has testified (and his testimony is true, and he knows that he is telling the truth), so that you also may believe. For these things happened so that the scripture would be fulfilled, “Not a bone of his will be broken.” And again another scripture says, “They will look on the one whom they have pierced.” (John 19:35-37 NET)
The Greek behind "has testified" is memarturēken. The word list gives "to testify". The Greek behind "would be fulfilled" is plērōthē. The list gives "to fulfill".
What the rule gives. A witness speaks to what happened, not to which saying it fulfilled. This does not cancel a statement in Scripture's own voice that an event fulfilled a saying.
Shown. The person who saw it is a witness to what happened. That is John 19:35. The link to the scriptures is stated in the account's own voice. That is John 19:36-37. So the link is Scripture naming it. The witness is not deciding it.
Not shown. That the person who saw it is the one who wrote the link. The verse does not say who the narrator is. So I do not say it either. And not shown: what counts as such a statement in Scripture's own voice. That is set out only in a wording that is still being tried. So on that step I can give you only what the tests found, and I lean nothing on it.
What it does not decide
The rule gives no label of its own. It does not tell you which event a prophecy named. It does not say that a witness could never know the link. It says only that a witness does not decide it as a witness.
It does not tell you what counts as a statement in Scripture's own voice, beyond the test result I told you.
And it has been tried only by AI readers.
What to carry out of this chapter
A witness speaks to what happened. When Scripture names the link to a prophecy, that is Scripture speaking, not the witness deciding.
That is the sentence I want you to keep. If you hear "the eyewitness says this fulfilled that", stop and ask. Did the witness say it? Or did Scripture's own voice say it? If you know which, you know more. If you do not know, rest.
Five rules, and each one stopped where its words stopped. A witness is like that too. He can tell you only what he saw. Hold the rules the same way.
Three questions
- Who saw the risen Jesus, according to Acts 10:41?
- What chain does Luke name in Luke 1:2-3?
- In John 19:35-37, who says what, the witness or the account?
Witnesses lead to records. What does a record show? And what does a missing record not show? The next chapter takes up those questions.
Chapter 10. What a record shows, and what it does not
Chapter 10. What a record shows, and what it does not
Someone says, "That prophecy has been fulfilled." Or someone says, "That already happened." You hear it in a thread, a video, a message. What do you need to see before you say yes?
I will give you the plain answer first. You need to see a record. And you need to know what the record shows. If a record is there, you may say so. If a record is not there, you may not say "false". You may say "not shown".
Let me define two words. A fulfilment is when what was said comes to be. A claimed fulfilment is when someone says it has. A record is a written account.
Four tests are in this chapter. The record-burden rule says what a claimed fulfilment needs. The outside-record rule says how to treat a record that is not in the Bible. The unnarrated-event rule says what to write when someone claims an act that Scripture does not tell. The already-claims rule says how Scripture answers "it has already come".
These questions run hot, so the caution comes first. The tests are for reading, not for the Bible itself, and none can make a prophecy fulfilled or unfulfilled.
Some of these tests touch things people argue about. When they do, I treat every reading alike. I use the same three words for each one: shown, not shown, shown against. In this chapter more than any other, hold on to what "not shown" means. A missing record is not a "no". It is only a silence.
The record-burden rule
Status: Passed, limited. Basis: a choice I made. It says who must bring the proof.
The rule in one sentence
A burden is who has to bring something. This rule says who.
A claimed fulfilment by a dated event needs a record; without one the record is not shown.
In everyday words: if you say a saying with a date in it was met, then you bring the record. If you bring none, I do not say your claim is false. I say the record is not shown.
The rule's full wording says it in a slightly different way, and you should know it. It says the dated part of a claim needs a record. Then it says that without an observed case from Scripture, a record is not shown to meet it. As I read it, the full wording asks for a record of a kind Scripture itself shows. The sentence above says only "a record". The two are close, but they are not the same, and I will not blur them.
Where Scripture does it
This is a burden rule. It is not a claim about what happened. It only says who must bring what. That is a working agreement, a choice I made. So I do not call it observed, and I do not call it forced.
But Scripture does give us an observed case of the thing the rule asks for. It is a case where a dated saying is met, and a record tells it. We will see it in a moment.
An example, step by step
Hananiah the prophet speaks in the temple, and he says God will break the yoke of Babylon. He gives a date. "Before two years are over, I will bring back to this place everything that King Nebuchadnezzar of Babylon took from it and carried away to Babylon." (Jeremiah 28:3 NET). I give this as context only. The verses I use do not tell what happened to that saying. I do not go past the verses.
Now Jeremiah speaks to Hananiah.
The words. "So the Lord says, ‘I will most assuredly remove you from the face of the earth. You will die this very year because you have counseled rebellion against the Lord.’" (Jeremiah 28:16 NET). Then the narrator writes this. "In the seventh month of that very same year the prophet Hananiah died." (Jeremiah 28:17 NET).
The Hebrew behind "this very year" is hashanah, and behind "that very same year" is bashanah hahi. A Hebrew word list gives "year" and "that", and the NET adds "very" in English. The dating is plain in both.
What the rule gives. A claimed fulfilment by a dated event needs a record. Without one, the record is not shown.
Shown. There is a dated saying: "You will die this very year". There is a record that meets it, in the narrator's own voice. So here is a dated saying, and a record that meets it. Scripture supplies this case itself, and it is the kind of observed case the full wording speaks of.
Not shown. That no other kind of record could count. That stronger form of the rule fails, so I do not use it. Also not shown: what counts as dated words in every case. The rule speaks of dated words, but it never says exactly what counts as them. In this example the dating is plain. In other cases it may not be. Where two readings would give two answers, the rule asks me to tell you how I read it, and to give both.
What it does not decide
The rule does not say a record exists. It says who must bring one.
It does not say that only a record like the one in Jeremiah 28 counts. That stronger form fails.
It does not say exactly what counts as dated words. That is a known gap, and readers' answers turn on it. I say so every time.
And it asks the same of everyone. If a claim helps a reading you love, the rule asks for the record. If a claim hurts a reading you love, the rule asks for the record. The rule does not pick sides. It picks the record.
The outside-record rule
Status: Passed, limited. Basis: both observed and forced, with some parts that are a choice I made.
The rule in one sentence
An outside record is a written account that is not in the Bible. Here is the rule for it.
Where the only record of an event lies outside Scripture, ask three things apart (did it happen; does it match what was predicted; is it inside the time the prediction fixes); write the record as "outside record: [source]", never as Scripture; a missing record never gives "did not happen" and never gives "will happen".
In everyday words: say a writer outside the Bible tells of an event. Ask three things. Did it happen? Does it match what was said ahead of time? Is it inside the time that saying fixes? Keep the three apart. A yes to the first is not a yes to the second. Write the record as an outside record, with its source. Never write it as if it were Scripture. And if there is no record, do not say "it did not happen". Do not say "it will happen" either.
Where Scripture does it
Most of this rule is observed in Scripture. I show you one part of it below.
One part is forced. Forced means that if we denied it, two Bible texts would contradict each other. The part is this: a missing record never gives "did not happen". The verses behind it are John 20:30 and John 21:25. Here is my own plain way to say why. Say a missing record meant "did not happen". Then John 20:30 would contradict itself. It says Jesus did many signs that are not recorded in this book. The signs happened, but they were not written. So "not written" cannot mean "did not happen". The same goes for John 21:25, which you will meet again below.
Some parts are definitions. Some are my own choice, and I say so. The two-or-three count in this rule is my own choice, and it is a help, never a requirement. One more part was carried over from a wording that is not in the tests I use. This rule has been tried only by AI readers.
An example, step by step
The words.
Now Jesus performed many other miraculous signs in the presence of the disciples, which are not recorded in this book. But these are recorded so that you may believe that Jesus is the Christ, the Son of God, and that by believing you may have life in his name. (John 20:30-31 NET)
What the rule gives. A missing record never gives "did not happen".
Shown. John says that many signs happened and that they are not recorded in this book. So a missing record in this book never gives "did not happen". That is shown by his own words.
Notice what John does next: he says why he wrote what he wrote. "But these are recorded so that you may believe". He does not say he wrote everything.
Not shown. What those other signs were, whether any outside record of them exists, and what such a record would show if it did.
One more care. This rule is for records outside the Bible, and John 20:30 is inside it. So here the rule is only showing you its forced part. When the Bible itself tells an event, this rule has nothing to write.
What it does not decide
The rule does not say whether an outside record meets the record-burden rule. That is a second question. You ask it after.
It does not say an outside record is true. It does not say it is false. It only says how to write it down, and what the three questions are.
Where Scripture tells the event itself, this rule is outside its limit. It has nothing to write.
Some parts are my own choice. The count of two or three witnesses is one of them. Careful readers read the count two ways. I have not settled that.
And the rule works the same for a record that seems to help your view and a record that seems to hurt it.
The unnarrated-event rule
Status: Passed, limited. Basis: observed in one part, a choice I made in others. The rest is built on the two rules it limits.
The rule in one sentence
Here is the case in plain words. Someone claims an act happened at a named time, and Scripture does not tell that act. This rule says what to do.
A claim that an act happened at a named time Scripture does not narrate does not trigger the bodily-act witnesses rule; the record-burden rule is used only inside its own stated input; an unmet burden is "not shown to meet the burden", never "it did not happen". For a claim that the resurrection has already happened, one may write that Scripture's own voice presents it as future when it was written and no narrator records it happening (with the verses logged).
In everyday words, for the first part: the rule that asks "who saw it?" is not set off here. The record-burden rule is used only where it applies. And if the burden is not met, the answer is "not shown to meet the burden". It is never "it did not happen".
The last sentence is about one claim only: that the resurrection has already happened. I treat that sentence in chapter 12. I do not use it here.
Where Scripture does it
This rule is built on the two rules it limits. It leans on them. Most of it is not a new observation of its own. The special sentence about the resurrection is observed: it rests on verses in the letters (1 Corinthians 15:52, 1 Thessalonians 4:16 and 2 Timothy 2:18). But the exact words the rule writes are my own choice, and I say so.
Here is the plain Scripture behind the main part. Scripture itself says that Jesus did many things it does not tell. So an act that Scripture does not tell is not, for that reason alone, an act that did not happen.
An example, step by step
Here is a made-up claim. I make it up on purpose, so that it points at no one. A post says that Jesus healed a man in a village by the lake, on a feast day in a named year. No book of Scripture tells that deed.
The words.
There are many other things that Jesus did. If every one of them were written down, I suppose the whole world would not have room for the books that would be written. (John 21:25 NET)
What the rule gives. The rule that asks "who saw it?" is not set off. Scripture has not said that God did that bodily act, so it has not set the question. The record-burden rule runs only inside its own input. If the burden is not met, the answer is "not shown to meet the burden".
Shown. Scripture itself says that there are many other things that Jesus did. So an act that Scripture does not tell is not shown to be an act that did not happen. And no one may say, "No witnesses are named, so it did not happen." The rule that names witnesses has not been set off.
Not shown. That the claimed act happened, or that it did not. The claim sits in the middle, and the middle is a resting place.
So how does a reader ever say no to a wild claim? Not with this rule. This rule only keeps you from saying "it did not happen" when the page is silent. If the claim says something the verses speak against, other rules and the verses themselves can show that. A silent page cannot.
What it does not decide
The rule leans on the record-burden rule, and that rule never says exactly what counts as dated words. That is a known gap.
The special sentence about the resurrection is worded by my choice, and I ruled it for that one claim only. Readers differed on whether the verses must also show its second part, that no narrator records it happening. Chapter 12 shows that.
The rule does not say the claimed act happened. It does not say it did not. It does not give a date to anything.
And it has been tried only by AI readers.
The already-claims rule
Status: Passed. Basis: observed.
The rule in one sentence
Scripture answers "it has already come" by naming what must come with it and noting it has not come.
In everyday words: someone says the awaited event has already come. Scripture does not argue the date. It names what must come with the event. And it says that thing has not come.
Where Scripture does it
This rule is observed. Its own named example is in the second letter to the Thessalonians (2 Thessalonians 2:2-3). There, a message said that the day of the Lord was already here. The letter names what must come first. Chapter 12 looks at that example, because it names what comes first, and the rule says what comes with. That is a place where careful readers can differ.
So for this chapter I use a different place, in Luke, because it fits the rule's word "with" better. I must be honest that it does not fit the rule exactly. In Luke the claim is not "it has already come". The claim is "Look, here he is!" It fits the shape of the rule, not the exact words. And, as you will see, it shows only the first half of what the rule gives. Weigh it yourself.
An example, step by step
The words.
Then people will say to you, ‘Look, there he is!’ or ‘Look, here he is!’ Do not go out or chase after them. For just like the lightning flashes and lights up the sky from one side to the other, so will the Son of Man be in his day. (Luke 17:23-24 NET)
One of the eight printed Greek editions in the word list leaves out "in his day". My example does not lean on those words.
What the rule gives. Two things. Scripture answers the claim by naming what must come with the event. And it notes that the event has not come.
Shown. The first half. The claim is "Look, there he is!" or "Look, here he is!" The answer names what comes with the event, which is like lightning that lights up the sky from one side to the other. So a claim that points to one place, "here" or "there", is answered by what the event looks like.
Not shown. The second half. These words do not say that the event has not come. Jesus says, "Do not go out or chase after them." That is not the same as saying it has not come. So this example shows the rule's first half only. Also not shown: any date, when "his day" is, what the lightning is a picture of, or whether it is a picture at all. The rule cannot date anything.
A reader may hold that the coming is still ahead. Another reader may hold that it came in an earlier event. This rule gives the same limit to both. The verses name what comes with it, but they do not name a year. I use the same three words for both readers: shown, not shown, shown against. And note this. It is an answer given ahead of time. Jesus says the claims will come.
What it does not decide
The rule cannot date anything. If you use it to say when, you have used it past its limit.
It does not say that a given claim today is right. It does not say that it is wrong. It says what Scripture does when a claim like this is made. It names what comes with the event.
It does not tell you what "his day" means. It does not tell you what the lightning means.
Here is a habit to take from it. When someone says "it has come" or "here he is", do not start with the date. Start with the words. What does the verse say comes with it? Say what the verse shows, and say what it does not. If you cannot tell, rest in "not shown". That is not a failure. It is a quiet place to stand.
What to carry out of this chapter
A missing record never gives "did not happen". Not shown is where it rests.
If someone claims it, they bring the record. If they bring none, the claim is not shown. If an outside record is brought, write it as an outside record. Ask three things, and keep them apart. If an act is not told in Scripture, do not say it did not happen. Say it is not shown. If someone says it has already come, look at what Scripture says must come with it.
If you know, you may say it. If you only think you know, wait. It is better to rest in "not shown" than to say "false" and be wrong.
Four rules, four limits. A record shows what it shows, and a rule says what it can say. Past that, both are quiet, and so should we be.
Three questions
- In Jeremiah 28, what were the dated words, and where is the record?
- What does John 20:30 tell you about what is not written?
- How does Luke 17:24 answer the claim "Look, here he is"?
Twenty-five rules is a lot. I know. Under all of them sit a few habits you can carry anywhere. The next chapter takes those up.
Chapter 11. The habits under every rule
Chapter 11. The habits under every rule
You will not remember twenty-five rules. I do not expect you to. I do not hold them all in my head at once either.
So here is what I want you to carry. A few habits. They are small. They fit in a pocket. They work on a verse, a video, a comment, or this book.
A habit is something you do the same way each time, without a fight. In this book a "test" and a "rule" mean the same thing. The habits sit under every test. If you keep the habits, you keep the part that matters most.
A rule is for the page. A habit is for the person. A rule needs a book open beside you. A habit needs one quiet minute.
If you stay quiet for that minute, the noise has less to hold. If you skip it, the noise holds all of you.
There are eight.
Habit one: start with the words
Jesus once spoke to men who held to a tradition. Mark tells it. The Pharisees and the experts in the law asked why His disciples did not "live according to the tradition of the elders" (Mark 7:5 NET). His answer runs on for several verses. Part of it was this.
Having no regard for the command of God, you hold fast to human tradition. (Mark 7:8 NET)
Later He said that they "nullify the word of God by your tradition that you have handed down" (Mark 7:13 NET).
Read it slowly. These verses do not say that every tradition is wrong. They say what goes wrong when a tradition takes the place of the command. The command is set aside. The handed-down thing stands where the command stood.
I do not point at anyone today with this passage. I point at an order. The word of God comes first. What people hand down comes second. Everything in this book is something people hand down. That includes the tests. That includes me.
So the tests sit below the words. They never stand over them. They do not make a verse mean anything. They help you look at what the verse already says.
The first habit is this. Open the verse. Read it before you read anyone's answer to it. Do this when the answer comes from a video. Do this when the answer comes from me.
Habit two: quote the exact words before you answer them
Go back to John 21. Peter asks Jesus about the other disciple. Jesus answers with a question. Then a saying goes around. Here is how the writer deals with it.
So the saying circulated among the brothers and sisters that this disciple was not going to die. But Jesus did not say to him that he was not going to die, but rather, “If I want him to live until I come back, what concern is that of yours?” (John 21:23 NET)
Look at what the writer does not do. He does not argue with the saying. He does not call anyone names. He puts the saying beside the exact words of Jesus. Then you can see the gap.
That is the habit. Before you answer a claim, write down the exact sentence you are answering. Put it in quotes. If you cannot quote it, you may be answering a different sentence.
Remember the room in chapter 1. You asked a plain question. The answer you got was about a different question. No one had quoted yours. No one had answered it.
Do the same with every verse. Copy it from a Bible. Do not trust your memory. Do not trust a smooth voice. If the quote is wrong, the answer is built on sand.
Habit three: sort into three groups
When you ask what the words do for a claim, put the claim in one of three places.
Shown. The words on the page, read with the tests, give it.
Not shown. The words on the page do not settle it either way.
Shown against. The words on the page, read with the tests, give the opposite.
Use the three groups when you are asking what the words show. They are a way to sort. They are not a way to score points.
Habit four: rest in "not shown"
This one is hard, so I come back to it.
Silence in the words does not make a claim false. It does not mean the thing did not happen. The page has only left it open.
If the words are silent, you have two ways to go wrong. You can fill the silence with a yes. Or you can fill it with a no. Both are a step the words did not give.
No test in this book rests on silence. Where the verse says nothing, the answer is "not shown". Rest there.
It is a resting place. It is not a loss. You can say "I do not know yet", and still be standing on solid ground.
Habit five: judge the words, not the heart
I cannot see into anyone's heart. Neither can you.
Paul asked the Romans a plain question.
Who are you to pass judgment on another’s servant? Before his own master he stands or falls. (Romans 14:4 NET)
So the habit is this. Talk about what was said. Do not talk about why. A person may be wrong and mean well. A person may be right and mean harm. The words on the page do not tell you which. If you must guess, you are no longer reading.
This book follows the same habit. I make no claim about why anyone says what they say. I only look at the words.
Habit six: every test carries its limit
Every test in this book says what it cannot decide. Say that limit each time you use the test.
Take the near-words rule. It says that "soon", "near" and "at hand" are true but set no number of years and no limit. Its limit is plain. It can never tie a passage down. It can never rule a passage out.
If you drop the limit, the test grows. It starts to say more than it can. Then it is no longer a test. It is a voice with a label on it.
If you use a test, then say its limit. If you cannot say its limit, you do not yet know the test.
Habit seven: a label is never a reason
Every rule carries a label. "Passed" means the rule held when it was tried. "Passed, limited" means it held only in a narrower form, and the rule says what that form is.
Each rule also has a basis, the thing it stands on. Most rest on how Scripture itself reads, or on what keeps two verses from clashing. A few are a choice I made, and I say so. For two, no basis is written down, and I say that too. Appendix A gives the label and the basis for all twenty-five.
The label tells you how the rule did in the trial. It does not tell you what a verse says.
So never say, "This reading holds because the rule is Passed." That is a label standing where a reason should stand. The reason is always the verse, and what the words show.
There is a second part. Some wordings are still being tried. I left them out of this book on purpose. If someone hands you one, treat it as a question to test. It is not a place to stand.
Habit eight: check, and be willing to be checked
The people of Berea heard Paul and Silas. The book of Acts says what they did.
These Jews were more open-minded than those in Thessalonica, for they eagerly received the message, examining the scriptures carefully every day to see if these things were so. (Acts 17:11 NET)
They received the message with eagerness. They also checked it against the scriptures. Both at once. They did not choose between trust and a test.
Now look at Apollos.
He had been instructed in the way of the Lord, and with great enthusiasm he spoke and taught accurately the facts about Jesus, although he knew only the baptism of John. (Acts 18:25 NET)
He was accurate, and he was missing something. Both were true. Then Priscilla and Aquila did a quiet thing.
He began to speak out fearlessly in the synagogue, but when Priscilla and Aquila heard him, they took him aside and explained the way of God to him more accurately. (Acts 18:26 NET)
Read what the verse says. They heard him in the synagogue. They took him aside. Then they explained the way of God to him more accurately. The verse does not say whether they spoke to him in the synagogue. It tells us where the explaining was done: aside. And the story does not end with a quarrel. Later, Apollos "assisted greatly those who had believed by grace" (Acts 18:27 NET).
Hold both stories. Check what you hear. Take correction when it comes. If you are the one who sees the gap, you may be the one who takes someone aside.
The habits on one comment
Here are two comments I made up. They are not from any real thread. I made them hard on purpose. Both are calm. Both sound careful. Suppose you read them under a video about checking what you hear.
The first comment quotes a real verse, and quotes it right.
Jesus said, "You are not to put the Lord your God to the test" (Matthew 4:7 NET). Checking a teacher's words against your own reading of the Bible is a way of testing God. So trust what you are taught, and leave the checking alone.
Under it, a second person replies. This one has read a book like mine.
I ran your comment through the reading tests with an AI. It sorted your main point as not shown, and the rules it used are marked Passed. So your point is false. You should take it down.
The first comment sounds humble. The second sounds like it did the work. Run the habits one at a time.
Start with the words. Open Matthew 4. Read it before you answer anyone.
Then the devil took him to the holy city, had him stand on the highest point of the temple, and said to him, “If you are the Son of God, throw yourself down. For it is written, ‘He will command his angels concerning you’ and ‘with their hands they will lift you up, so that you will not strike your foot against a stone.’” Jesus said to him, “Once again it is written: ‘You are not to put the Lord your God to the test.’” (Matthew 4:5-7 NET)
The quote in the first comment is right. Those are the words. That matters. A comment can quote a verse exactly and still add a step after it.
Quote the exact sentence. Copy the step you are answering: "Checking a teacher's words against your own reading of the Bible is a way of testing God." Answer that sentence, not a softer one, and not a harder one.
Sort into three groups.
Shown: Jesus said those words. He said them when the devil urged Him to throw Himself down from the temple, with a verse to back the urge. And see what Jesus did with the devil's verse. He set another verse beside it, saying, "Once again it is written" (Matthew 4:7 NET).
Not shown: that checking a teacher's words is testing God. Matthew 4:7 does not speak of teachers. It does not speak of checking. That step was added after the quote.
Shown against: that Scripture counts it wrong to check a message against the scriptures. Acts gives the opposite. The people of Berea examined "the scriptures carefully every day to see if these things were so" (Acts 17:11 NET). The same verse calls them "more open-minded".
Rest in "not shown". Now look at the second comment. It says the AI sorted the point as not shown. Then it says, "So your point is false." That is the very step this book warns against. Not shown leaves a claim open. It does not make it false. If the AI's sorting was right, the reply still went one step too far.
Words, not the heart. Neither comment guesses at anyone's heart. Good. Keep it that way in your answer. Do not guess why the first person wrote it, or why the second wants it gone.
Every test carries its limit. The second comment does not say which rules ran, or what each one cannot decide. Without the limits, you cannot tell whether a rule was used outside them.
A label is never a reason. "The rules it used are marked Passed." That is a label standing where a reason should stand. The reason, if there is one, is in the verse and what the words show.
Check, and be willing to be checked. The second comment does not say that anyone checked the AI's answer. Chapter 13 shows how to check one. And you might be wrong too. Check your own quotes against a Bible before you post.
Now write one calm reply to each.
To the first: "I read Matthew 4:5-7. The quote is right. Jesus says it when the devil urges Him to throw Himself down. I can't find teachers or checking in those verses. And in Acts 17:11 the Bereans checked Paul's message against the scriptures. Can you show me the step from the verse to checking?"
To the second: "I think 'not shown' leaves the point open. It doesn't make it false. Which rules ran, and what did each one say it cannot decide?"
Each reply is short. It quotes. It sorts. It does not guess at a heart. It asks a real question.
What to carry
Words first. Quote before you answer. Sort in three groups. Rest in "not shown". Words, not hearts. Say the limit. A label is never a reason. Check, and be checked.
If you stop after this chapter, stop here. These eight will serve you where the twenty-five cannot go. You can find them again in appendix B, folded into twelve questions; each question there names the habit it comes from, and the extra ones say so.
Three questions
- Which habit would have helped you most in the room in chapter 1?
- Why is a label such as "Passed" never the reason for a reading?
- What did Priscilla and Aquila do, and where did they do it?
Habits are only honest if you also show where they failed. So here is what testing found.
Chapter 12. Where the rules split, ran out, or failed
Chapter 12. Where the rules split, ran out, or failed
Did these tests ever get it wrong? Yes. I will show you where.
If I hid it, you would have no reason to trust the rest. A voice that never says it was wrong is a voice you cannot check. A test that shows where it failed is a test you can use. You know where it stops.
So this chapter is about the dark places. The splits. The edges. The failures. And my own mistakes.
Here is the honest claim for a rule that passed. It is small. No contradiction was found in the passages checked. That is all. Nothing in this chapter makes it bigger.
A split
A split is what happens when two careful readers read the same words of a test and get two different answers. I look for splits on purpose. A split shows where my wording is loose.
Here are four.
The tie clause in the death-sense rule
The death-sense rule sorts the uses of "die", "dead" and "death" (chapter 8). One clause in it is about when two sayings are tied together. Readers split on it. They split on who counts as the second speaker. They split on what the words between the speakers mean. They split on whether the narrator's words count as speech.
So I mended the clause. Then readers split again, on something new. Mend, split. Mend, split.
So I stopped. I froze the text and gave the rule the label Passed, limited. I also wrote a stopping rule, and I wrote it down before I read the next result. Later I changed one other clause of the rule. No reader has tested that clause since, and the rule says so each time it runs. Appendix E tells the whole story once, with the dates and the stopping rule. I will not tell it twice.
The nearness-length rule
Chapter 7 teaches this rule. Chapter 4 tells its life in short. Here I give only what is still open.
Fresh readers ran it three times. Each time, it passed in part. Two disagreements stay open.
The first is how much weight one part of its basis carries. That part says a near word by itself gives no length. The readers weighed it on Haggai 2:6 with Hebrews 12:26.
The second is how far a narrow exception reaches. That exception is tied to Matthew 28.
After my rulings, fresh readers have not tested the wording again. The rule says so every time it runs.
The old line about what a witness can speak to
The old line said that witnesses speak to what happened, not to which event a prophecy named. One reader read it two ways at 1 Kings 16:34.
During Ahab’s reign, Hiel the Bethelite rebuilt Jericho. Abiram, his firstborn son, died when he laid the foundation; Segub, his youngest son, died when he erected its gates, in keeping with the Lord’s message that he had spoken through Joshua son of Nun. (1 Kings 16:34 NET)
Here is the question. Does the line reach a statement, in Scripture's own voice, that an event fulfilled a saying? Here the narrator ties the deaths to a message spoken through Joshua. The old line, read alone, did not say.
I left the old line word for word. It stays a limit, not a rule, and it never supports anything. Then I set a new wording beside it. The new wording keeps the first sentence. It adds two more. A statement in Scripture's own voice is not cancelled. That is Scripture naming the link. It is not a witness deciding the link. I said yes to all three sentences. The new form is the witness-limit rule in chapter 9.
The count of witnesses
The opened part of the two-or-three witnesses rule says that agreeing witnesses may count toward an outside record that an event happened. The count is a help. It is never a requirement.
Readers read the rule's count sentence two ways. That happened on writings outside the Bible, from two early writers. It happened beside a wording that is still being tried. The question was this. Does falling short of the count make an event not shown?
I wrote down that the count is a help and never a requirement. The count sentence is my own choice. I left the split in the rule's limit, as mine to settle.
Scripture itself has a picture of agreeing witnesses to an event. Boaz speaks at the gate.
You are witnesses today that I have acquired from Naomi all that belonged to Elimelech, Kilion, and Mahlon. (Ruth 4:9 NET)
The people answer, "We are witnesses" (Ruth 4:11 NET). The verses name witnesses. They give no number. I come back to Ruth below.
Rules that failed
A rule that fails is not a shame. It is a result. Here are some of them.
The reused-word rule. This one sounded good. Here it is.
When an answer reuses a word from the question, it is about what the question asked.
Test it on Luke 10. An expert in the law asks Jesus a question.
But the expert, wanting to justify himself, said to Jesus, “And who is my neighbor?” (Luke 10:29 NET)
At the end of the story, Jesus asks him a question.
Which of these three do you think became a neighbor to the man who fell into the hands of the robbers?” (Luke 10:36 NET)
The word neighbor is in the question and in Jesus' answer. By the rule as I have given it here, Jesus' last question is about what the man asked. But the verses show another question, and my notes say this rule conflicts with the same-words rule, which chapter 5 teaches. The rule failed.
Here is my plain reading of why. It is my own reading. My notes give only the verses and the conflict. The man asks who counts as his neighbor. Jesus' last question uses the same word, but asks something else. It asks which of the three acted as a neighbor to the man in the road. Same word. Different question. A reused word did not mean the answer was about what was asked.
I must be exact about one more fact. The full rule had a short qualifier: unless the text marks a shift. When the rule was written into a reader's instructions, a short form went in without those words. That was a mistake in the instructions, and my long paper says so. It matters here. Luke 10:36 does mark a shift. So the full rule survives this one verse. It still failed, because it conflicts with the same-words rule. The verse alone would not have sunk it.
The rule was marked Failed. I dropped it, and it is nowhere in this book as a rule. I tell you about it because a rule that sounds right can still fail on one verse. That is why we test.
The near-word-means-lifetime rule. This rule said that a near word places an event within the hearers' lifetime. It failed on Haggai 2:6 with Hebrews 12:26. Haggai says, "In just a little while I will once again shake the sky and the earth, the sea and the dry ground" (Haggai 2:6 NET). A later writer takes up the promise and says "now he has promised" (Hebrews 12:26 NET). On this pair, the near words alone did not place the event in the first hearers' lifetime. I say nothing here about what the shaking is.
One sentence of another rule. An earlier rule had two sentences. The first said a near word by itself gives no length, and it passed. The second said only a stated span or a sign sets a length, and it failed. Scripture has other ways to give a length. A number. A date. Or words like these.
Indeed in your days, O rebellious house, I will speak the word and accomplish it, declares the Sovereign Lord. (Ezekiel 12:25 NET)
Seven ideas dropped. Seven more ideas were tried early and dropped. Here they are, in plain words.
- That "all these things" covers the events just before it (Matthew 24:33). No usage fixes how far it reaches.
- That "you" always means the people addressed (Deuteronomy 30:1; Matthew 28:20).
- That near words have a ceiling of about 170 years. It rested on shared wording, and 2 Peter 3:8 cuts against any ceiling.
- That the Greek word mellō, "to be about to", always means soon. In Luke 7:2 the sense is near. In Acts 24:15 it is not.
- That the words "before or after" mean once, literally. The test pair was 2 Kings 18:5 and 2 Kings 23:25. Both use those words of a king.
- A list of marks to pick out certain awaited events. It was argued from silence.
- That different wording means different events.
Rules that were replaced
Some rules were not failures. They were replaced by better wording. A set of older readings of near words gave way to the nearness-length rule. An earlier death-sense wording was held and then replaced by the one in chapter 8. A test for whether two accounts are one saying failed in its first form, and a changed form is still only a wording being tried. In each case the old one stays in my notes. It does not stay in the book.
Mistakes caught in my own work
I want you to see these. They are why I ask you to check me.
They did not happen in this book. They happened in the long argument, the long paper of mine that chapter 4 describes. In it I apply these rules to Jesus' talk on the Mount of Olives. Each copy of it is tested in a round, and appendix E tells the steps. A round is clean when no new error turns up in it.
A misquote. On 20 November 2026 the editor was building the next copy of the paper. The editor is an AI that reads and builds the whole text. It found a quote of Revelation 1:7 that was not what the NET says. The paper spoke of the mourning of those who pierced him. The verse does not say that. No reader caught it. No skeptic caught it. The editor did. Here is the whole verse, as the NET prints it, in its own parentheses.
(Look! He is returning with the clouds, and every eye will see him, even those who pierced him, and all the tribes on the earth will mourn because of him. This will certainly come to pass! Amen.) (Revelation 1:7 NET)
The round on that copy had been counted clean. It was recounted as not clean, and the count of clean rounds went back to zero. A lesson was written down. Before a round is called clean, every Bible quote in the changed text is checked against the NET, by script.
A line in the wrong place. The same day, a round flagged a line in a later copy. It put the scoffers' question in 2 Peter 3:4 with the answers to the claim that something had already happened.
Where is his promised return? (2 Peter 3:4 NET)
That question is a different kind of claim. I counted it a confirmed error. So that round was not clean either. It was fixed in the next copy.
Two small words. The paper also put the words "takes place" in quote marks for Matthew 24:34. The NET reads like this.
I tell you the truth, this generation will not pass away until all these things take place. (Matthew 24:34 NET)
The editor, the same AI, noticed it. The quote checker did not, because it read only quotes followed by a reference in brackets. I ruled it a slip, not a confirmed error, so the clean rounds stood. It was fixed in the next copy. Then a stricter checker was built. It ties each quote to the verse it cites.
What a word list cannot do
This book keeps asking you to check. So you should know what a check can do, and what it cannot. The plainest lesson I have on that came from outside the Bible. It is about a machine. But it is really about every check, mine included.
A public chatbot page had a box that checked the chatbot's answers. The page said the check helps make sure answers are ethical. We pasted short test answers into it and watched what passed. Nothing personal was typed.
Here is what the test found. A check that looks only for certain words can be walked around. And it cannot judge meaning.
It can be walked around by a "not". From the page's own code, a flagged phrase was ignored when a word like no, not or never stood a few words before it. That worked on a good line. "Do not retaliate" passed, and rightly so. But a harmful line passed too. It said there is no reason not to get back at him.
It can be walked around by words not on the list. The lists were short. "Steal the money from her purse" passed. "Blackmail her" passed. Those words were not on the lists.
It cannot judge meaning. The safety check looked for words such as police or emergency anywhere in the answer. An answer that told a person not to call for help still passed, because the words were in it. A quiet line of despair, with none of the listed words, drew no crisis reply.
Here is what the test did not show. One test came out unclear. Other chatbots were not tried. I draw no claim about any other page. I draw only the lesson. A check that looks only for certain words can be walked around, and it cannot judge meaning.
Now I turn the lesson on my own work. The quote checker I used missed the slip at Matthew 24:34. The editor, an AI that reads the whole text, noticed it. Then I ruled on it. I also keep a list of banned words and patterns. That list checks only what is on it. So in practice my work is checked by script, and then the editor and I read. Even the check I used for how easy this book is to read only counts words and sentence lengths. It can tell me a page is easy to read. It cannot tell me a page is true.
Six places where a rule could be read two ways
When the examples for this book were checked, six were flagged as readable two ways. I did not use them as clean examples. I show them here.
2 Thessalonians 2:1-3, and the already-claims rule. Some message said that the day of the Lord was already here. The rule says what must come with the event. The verse names what comes first.
For that day will not arrive until the rebellion comes and the man of lawlessness is revealed, the son of destruction. (2 Thessalonians 2:3 NET)
"With" and "first" are not the same word. A careful reader can read the rule two ways here. So I write that the verse names what must come first, or I quote the rule's own word and note the verse. The verses do not say who or what the rebellion or the man of lawlessness is. Not shown.
Revelation 1:1, 20:3, 20:7 and 22:6, and the a-book's-soon rule. The book says what "must happen very soon" (Revelation 1:1 NET) and what "must happen soon" (Revelation 22:6 NET). It also has a binding "until the one thousand years were finished" (Revelation 20:3 NET) and "when the thousand years are finished" (Revelation 20:7 NET). The rule says a book cannot call "soon" what it places after its own long wait. Two things stay open. The rule needs the thousand years to be a long wait. The thousand-years rule says only that a thousand years can be long. And the Greek word behind "soon" is tachei, "quickness". Whether it says when something happens, or how fast, is not shown. I do not say what Revelation 20 means. The tests leave it open, both ways.
2 Kings 7:1 and 7:16-17, and the record-burden rule. Elisha says "About this time tomorrow" flour will sell at a set price (2 Kings 7:1). The narrator records the sale "just as in the Lord’s message" (2 Kings 7:16 NET). The rule speaks of dated words. It does not say what dated words are. So readers' answers turn on how they read that phrase. One reader could count "About this time tomorrow" as dated words, so the narrator's record meets the rule. Another could ask whether dated words means more than that, and the rule does not say.
1 Kings 14:19, and the outside-record rule. This one is not read two ways so much as only half fitting. The verse says the rest of the events of Jeroboam's reign "are recorded in the scroll called the Annals of the Kings of Israel" (1 Kings 14:19 NET). Scripture names a record outside its pages. But the rule has nothing to write when Scripture itself tells the event, and here Scripture tells part of the reign itself. So the verse is only a likeness of the rule's case.
2 Timothy 2:16-19, and the unnarrated-event rule. Two men were saying "that the resurrection has already occurred" (2 Timothy 2:18 NET). The rule's sentence for this claim says that Scripture's own voice presents the raising as still to come when it was written, and that no narrator records it happening. Elsewhere "the dead will be raised imperishable" (1 Corinthians 15:52 NET). Readers differed on whether the verses must also show the second part: that no narrator records it. The rule never says "it did not happen". The letter names two men in their own day. I apply it to no one today.
Ruth 4:9-11, and the count of witnesses. You met this one above. Ruth is a picture of agreeing witnesses with no number. The split on the count sentence came on writings outside the Bible, not on Ruth. I put Ruth here because the count is the open point.
One place the rules run out
This last one is open. I have not sorted it, and I do not sort it here.
The a-book's-soon rule says that a book cannot call "soon" what it places after its own long wait. Chapter 7 teaches it. Here is a place in Jeremiah where a reader may ask how that rule fits. I give you the verses, and what each one says. Nothing more.
First, Jeremiah 25 gives a span of seventy years.
These nations will be subject to the king of Babylon for seventy years. (Jeremiah 25:11 NET) But when the seventy years are over, I will punish the king of Babylon and his nation for their sins. (Jeremiah 25:12 NET)
These verses say the nations will serve the king of Babylon for seventy years. When the seventy years are over, the king of Babylon and his nation are punished.
Second, Jeremiah 29 speaks of a long wait. In that chapter, a man in Babylon writes a letter. In it he reports what Jeremiah wrote to the exiles there: "You will be there a long time" (Jeremiah 29:28 NET). So the words come to us inside one letter that quotes another.
Third, much later in the book, comes a word about Babylon itself.
The time for her to be cut down and harvested will come very soon. (Jeremiah 51:33 NET)
Earlier in that verse, the one called "her" is "Fair Babylon" (Jeremiah 51:33 NET). The NET's "very soon" stands on two Hebrew words, od, "still", and me'at, "little".
A reader may ask whether one book calls "soon" something it places after a long wait. That turns on another question first. Do Jeremiah 51:33 and Jeremiah 25:12 speak of one event? Both name Babylon. The same-words rule speaks of shared words that describe. It does not speak of names. Whether it reaches a shared name like Babylon is not settled. This book does not rule on it.
So I leave these verses side by side, unsorted. I do not say what they mean for the a-book's-soon rule. I do not say what they mean for Revelation. I say only that this is a place where the rules run out, and I will not hide it.
Left out on purpose
Some wordings are still being tried. I left them out of this book. Each gets one sentence.
- One says that where a passage sits in a book shows no time. It is still being tested.
- One says that chapter and verse numbers are not breaks. It is still being tested.
- One is a list of dating words, the words that mark a date or a deadline. It is still being tested.
- One is about turns of subject. It is still being tested.
Why leave them out? Because a wording that is still being tried is a question. It is not a place to stand.
What to carry out of this chapter
Splits are useful. They show where a wording is loose. Failures are useful. They show where a rule stops. Mistakes are useful, if someone says them aloud. And a check that looks only for certain words will miss what it was not told to see.
I would rather show you where a test failed than tell you it never did.
Three questions
- Who caught the misquote of Revelation 1:7, and who did not?
- Why can a check that looks for words be walked around?
- Why are some rules left out of this book on purpose?
Now put it all to work on one passage. And see how to use an AI without adding to the noise.
Chapter 13. One passage, start to finish, and using AI without the slop
Chapter 13. One passage, start to finish, and using AI without the slop
Chapter 2 began with John 21:22-23. This chapter ends the rules where it began. We will take the whole passage and put the tests to work. Then we will talk about AI.
I will go slowly. You can follow every step. If you can follow it, you can check it.
The passage
Read it first. All of it. The words come before any test.
18 I tell you the solemn truth, when you were young, you tied your clothes around you and went wherever you wanted, but when you are old, you will stretch out your hands, and others will tie you up and bring you where you do not want to go.” 19 (Now Jesus said this to indicate clearly by what kind of death Peter was going to glorify God.) After he said this, Jesus told Peter, “Follow me.” 20 Peter turned around and saw the disciple whom Jesus loved following them. (This was the disciple who had leaned back against Jesus’ chest at the meal and asked, “Lord, who is the one who is going to betray you?”) 21 So when Peter saw him, he asked Jesus, “Lord, what about him?” 22 Jesus replied, “If I want him to live until I come back, what concern is that of yours? You follow me!” 23 So the saying circulated among the brothers and sisters that this disciple was not going to die. But Jesus did not say to him that he was not going to die, but rather, “If I want him to live until I come back, what concern is that of yours?” 24 This is the disciple who testifies about these things and has written these things, and we know that his testimony is true. 25 There are many other things that Jesus did. If every one of them were written down, I suppose the whole world would not have room for the books that would be written. (John 21:18-25 NET)
Verse 18 ends with a closing quote mark because Jesus' words began in the verse before. The NET prints it that way.
Step one: say it back
Say what you read in your own plain words. If you cannot, you are not ready for a test.
Jesus tells Peter about a death. A note from the writer says what kind. Jesus says, "Follow me." Peter sees the other disciple and asks about him. Jesus answers with an "If" question. A saying goes around. The writer sets it right. Then he says who testifies. Then he says there is more than he wrote.
That is the passage. Nothing in it needs a test to be understood. The tests help us when we want to say what the words show, and what they do not.
Step two: name the claims
Suppose two claims reach you in the room. They sound alike. They are not.
The first: Jesus said that this disciple would not die.
The second: this disciple lived until Jesus came back.
I will treat the two alike. Same verses. Same tests. Same three words: shown, not shown, shown against.
Step three: run the tests
Here are the tests that have something to say. I give each one the four steps from the rule chapters. The words. What the rule gives. Shown. Not shown.
First, the original words
Chapter 5 gave a habit. Where the wording matters, look at the Hebrew or Greek behind the English. Do it here.
In John 21:22 the NET says "If I want him to live until I come back". The Greek word behind "live" is menein. It is a form of menō, "to stay". It is the same word that John 15:4 gives as "remain".
Both English words are fair. The NET says "live". The plain sense of the Greek is stay. So Jesus' question may be read two ways in English. One reads live until I come back. The other reads stay until I come back.
Does that change what we sort? No. Under either word the verse is an "If" question. It does not say what Jesus wanted. I will say both words each time. The habit is not to pick one. It is to see both.
A note from the writer: the borrowed-meaning rule
The words. "(Now Jesus said this to indicate clearly by what kind of death Peter was going to glorify God.)" (John 21:19 NET)
What the rule gives. When a writer adds his own note to explain his own words, the note fixes what those words mean in that account. It does not reach past it.
Shown. The writer marks his own note. So in John 21, the words in verse 18 are about the kind of death by which Peter would glorify God.
Not shown. That this note carries to any other passage. The rule says no test for whether two accounts are one saying has passed. So a writer's note never carries to another passage. That is the rule's own limit.
"Until I come back": the time-words rule
The words. "If I want him to live until I come back" (John 21:22 NET). The Greek word behind "until" is he'ōs, "until".
What the rule gives. Each time word is read in its own verse. No general rule fixes how far a deadline reaches.
Shown. The word "until" sets a stop for the living. The stop is an event, "I come back". It is not a date.
Not shown. When that is. How long the wait is. And what the coming is. Careful readers may read "come back" more than one way. The verse does not choose. I do not choose either. The rule's own limit holds: no general rule fixes how far the deadline reaches.
The saying that went around
This one needs no rule. It needs the words.
What Jesus said was an "If" question. Someone took a step from "If I want him to live until I come back" (John 21:22 NET) to the saying that "this disciple was not going to die" (John 21:23 NET). The verse did not give that step. The writer says so himself: "Jesus did not say to him that he was not going to die" (John 21:23 NET).
That is a step added. Chapter 2 named it as one of the six causes of disagreement. Here the writer goes back to the exact words.
The witness: the witness-kinds rule
The words. "This is the disciple who testifies about these things and has written these things, and we know that his testimony is true." (John 21:24 NET)
What the rule gives. For each record, write who the witness is, what he witnessed, and how. A writer who did not himself see or hear is giving a report. Its weight follows the chain he names.
Shown. The passage names one who testifies and who also wrote. Verse 20 calls him "the disciple whom Jesus loved". The verse also has a second voice: "we know that his testimony is true". So there are two: the one who testifies, and those who vouch for him.
Not shown. The verses do not give his name. They do not say how much of each event he saw. They do not say who "we" are. The rule's three kinds are a frame, and the frame is my own choice. I say so every time.
"Many other things": the outside-record rule and the unnarrated-event rule
The words. "There are many other things that Jesus did." (John 21:25 NET)
What the rules give. A missing record never gives "did not happen". And a claim that an act happened at a time Scripture does not narrate does not bring in the bodily-act witnesses rule. The answer for an unmet burden is "not shown", never "it did not happen".
Shown. Scripture says in its own pages that there are deeds it did not write down. So a missing record in these pages does not give "did not happen".
Not shown. What any of those deeds were. Whether a deed someone names today is real. If a person says Jesus did a deed that is not told here, the answer is "not shown". It is not "it did not happen". And it is not "it did".
The limits. The outside-record rule has nothing to write when Scripture itself tells the event. The unnarrated-event rule leans on a phrase in the record-burden rule that is not fully defined (chapter 10). I use only what needs no date.
Step four: sort the claims
Now go back to the two claims.
The first claim. Jesus said that this disciple would not die. This is shown against. John 21:23 says "Jesus did not say to him that he was not going to die". The writer says it in his own voice.
The second claim. This disciple lived until Jesus came back. This is not shown. The words of Jesus are an "If" question about what He might want. The verses do not say what He wanted. They do not say whether the disciple lived to that point.
That does not make the claim false. He may have. He may not have. The verses stay silent.
And the opposite claim, that the disciple died before Jesus came back, is also not shown. The same words. The same tests. The same answer.
That is where the passage rests. There is peace in that. You do not have to fill the silence. You can say what the words show, and stop.
Step five: see what is left
Look at what the tests did and did not do.
They did sort two claims. They did not tell you who the disciple was. They did not tell you what the "coming" is. They did not tell you what the passage means for your life. They cleared some noise. That is all they do.
Now look at the passage again. Peter asks, "Lord, what about him?" It is a fair question. It is also a side road. Jesus does not follow Peter down it. He says this.
If I want him to live until I come back, what concern is that of yours? You follow me! (John 21:22 NET)
I read that as a pair. What about him, and you follow me. The noise asks about him. The quiet says follow. I say this part as my own reading. The words give the pair. I give the weight.
You can run every test on a passage and still miss it. If you do, you have won a point and lost the verse. So after the tests, go back and read it once more, slowly, with no test in your hand.
Using an AI without the slop
An AI can run these steps for you in seconds. That is the help. It is also the danger.
An AI makes smooth answers. A smooth answer is not a checked answer. I have said it before. I say it again, because it is the thing most worth remembering. If you read a smooth answer and feel at ease, check it twice.
Here is how to use an AI without adding to the noise.
What you give it
Give it three things.
The tests. The text of the tests, as I give them, in one long prompt. Appendix C says how to paste them in.
The run line. This is the first line. It tells the AI which tests to run. If you do not choose, the AI should say it is using the default. Appendix C gives the exact words.
The verse text itself. Copy it from a Bible you trust, and paste it in. Do this every time. If you only name a verse, the AI may recall it wrongly. A recalled verse is not a checked verse. When you paste it, the text counts as supplied.
I did not test which chatbots can take a prompt this long. Appendix C says so too.
What comes back
Expect a certain shape. It repeats your run line first, so you can see it ran what you asked. It gives the conclusion first, in a few sentences. Then it gives a part that shows its sources: what it was given, and what each test gives. Then it gives a part marked as judgment, kept apart. Then it lists what is still open.
Why keep them apart? So you can see what comes from the words and what is only the AI's opinion.
What comes back is a test result. It is not a verdict. It shows what the tests give on the words you pasted. It does not tell you what you must believe. Running the tests through a machine does not make them promise more. You can still be wrong with them, and right without them. The tests ask the AI not to flatter you. Watch for flattery anyway.
What it might look like
Here is a made-up example, so you know the shape. It is not from a real chat.
Selection received: the run line, copied back word for word.
Conclusion: the claim that Jesus said the disciple would not die is shown against by John 21:23. The claim that the disciple lived until Jesus came back is not shown.
Sourced: the verse text you pasted. Each test it used. What each test gave. Each limit.
Judgment: what the AI thinks the passage means. Marked as its own opinion.
Open items: what the words do not tell.
Read it from the top. Does each part say where it came from? If a part does not, ask.
Where an AI goes wrong
It goes wrong in the same ways people do, and faster.
It can add a step that sounds right. It can recall a verse wrongly. It can agree with you too soon. It can use a test outside its limit and not say so.
None of this makes the AI a bad tool. It makes it a tool. A saw cuts well and cuts the wrong board just as well. You hold the saw.
AI helped me make the tests in this book. It read the rules blind, raised objections, sorted findings, drafted wordings, edited my long argument and checked quotes. A person decided every label. I did. Appendix E tells it plainly. I say this so you know I am not asking you to do something I did not do. I checked, and I was checked.
Ask it twice
Here are three things you can ask after the first answer.
Ask it to quote the exact sentence it is answering. If it cannot, it may be answering a different one.
Ask it what would make its answer lose. The tests ask for this. A good answer can say.
Ask it to put the same two readings through the same tests, with the same words. If one reading gets a kinder answer than the other, find out why.
What you check
You check three things. Every time.
One. Every quote. Put each quote beside your own Bible. Do not check it against the AI. In my own work, quotes went wrong twice. Both times the editor, an AI, caught it. No reader caught the first, and my quote checker missed the second (chapter 12). If the quote is off, the steps built on it are weak.
Two. Every "shown". Go back to the words. Does the verse show that? Or was a step added? Here is an example. Suppose the AI writes that John 21:23 shows the disciple lived until Jesus came back. Look at the verse. It does not say that. It says Jesus did not say he would not die. So that "shown" is a step added. Put it back to "not shown".
Three. The limits and the labels. Did a test run outside its limit? Did the answer lean on a wording that is still being tried? Did it say a rule is "Passed" as if that were a reason? A label is never a reason.
One line to keep
A check that looks only for certain words can be walked around, and it cannot judge meaning. So do not trust an AI to check an AI by listing words. You read the meaning. You stay in the chair.
Three questions
- Which of the two claims about John 21:22 does John 21:23 speak to?
- What must you paste so that the verse counts as supplied?
- What three things will you check in any AI answer?
Checking is half of it. The other half is what you do next, with the person in front of you.
Chapter 14. Before you comment: abiding in Christ, in unity
Chapter 14. Before you comment: abiding in Christ, in unity
You know the room. It is dark. The screen is bright. Your thumb is over the box.
I cannot know why you came to the verse. You can. Maybe you came because you love it, or because you want to love it. Maybe you want to stay near God. If that is true of you, you already know why the noise hurts.
So I will say the main thing first. The tests are not for winning. They clear the noise so you can stay.
That is the whole book in two sentences. The rest is how.
Stay
The old word is abide. In this book the word is stay. The Greek word behind the NET's "remain" is menō, "to stay".
On the night before He died, Jesus said this.
Remain in me, and I will remain in you. (John 15:4 NET)
Then He said what happens if you do not. He said "apart from me you can accomplish nothing" (John 15:5 NET). If you stay, there is fruit. If you are apart, there is nothing you can accomplish.
A test can help you stay. A test can also pull you away. This part is my own judgment, and I hold it plainly. If a test wins the argument and costs you the vine, it was a bad trade.
So before you use a test, ask whether you are staying. If you are, then use it. If you are not, put it down. Stay first.
Three questions before you post
Here are three questions. Ask them before you press send. They are short on purpose.
One. What does the verse actually say? Open it. Read it. Do not trust your memory. Do not trust a smooth voice. The words come first. If you cannot find the words, you do not yet know what you are answering.
Two. Have I quoted the exact words I am answering? Copy the sentence you are replying to. Put it in quotes. Then answer that sentence. If you answer a softer one, you are answering no one.
Three. Is this mine to post? Not every comment is yours. If the claim rests in "not shown", the best post may be no post. If you cannot say it without contempt, wait until morning. If it is about a person's heart, it is not yours at all. If it is about the words, it may be. Then ask one more thing. Will it build up, or only win?
Paul put the aim in one line.
So then, let us pursue what makes for peace and for building up one another. (Romans 14:19 NET)
When it is not shown
Some claims will land in the middle. Not shown. The words have not settled it.
Rest there. It is a resting place. It is not a loss.
You can know, and say you know. You can not know, and say you do not know. Both are honest. The harm is in the third: you do not know, and you say you do.
"I do not know yet" is a true sentence. It is a good one. It leaves the verse where it is. It leaves the other person where he is. And it keeps you out of a fight you cannot finish.
You do not have to call the claim wrong. You do not have to call it right. You say what the words give. Then you stop.
When you disagree
Paul spoke to believers who disagreed about food. Here is what he asked of them.
Now receive the one who is weak in the faith, and do not have disputes over differing opinions. (Romans 14:1 NET) The one who eats everything must not despise the one who does not, and the one who abstains must not judge the one who eats everything, for God has accepted him. (Romans 14:3 NET)
Two things stand out. Do not despise. Do not judge. Then Paul gives a reason: "God has accepted him" (Romans 14:3 NET). Read it closely. In this verse, "him" is the one who eats everything. Paul does not say "both" here. He tells each side what not to do to the other.
I need to be careful here. These verses are about opinions on eating. They do not give a list of which disagreements are opinions. Paul himself opposed Cephas at Antioch (Galatians 2:11). So not every disagreement is only an opinion. The verses do not sort them for us. That is not shown. What the verses give is a manner. Do not despise. Do not judge. Pursue peace. Build up.
Then there is Corinth. The church there split into camps.
Now I mean this, that each of you is saying, “I am with Paul,” or “I am with Apollos,” or “I am with Cephas,” or “I am with Christ.” (1 Corinthians 1:12 NET)
Even "I am with Christ" is in that list. In these verses Paul does not sort the camps. He asks one thing.
Is Christ divided? (1 Corinthians 1:13 NET)
The noise makes camps. A camp makes a voice louder. When you test a claim, do not test it for a camp. You have one Lord.
Paul gave the pattern for living with one another.
with all humility and gentleness, with patience, putting up with one another in love, making every effort to keep the unity of the Spirit in the bond of peace. (Ephesians 4:2-3 NET)
Look at the first words. Humility. Gentleness. Patience. They come before the unity. Unity is not the same as everyone saying the same thing. Romans 14 shows believers who differ and still must not despise or judge each other. Unity is a bond. It is kept in peace.
When someone reads it differently
You will meet someone who reads the verse another way. It may be a friend. It may be a stranger in a thread. What then?
Scripture shows two ways. Here is the first.
He began to speak out fearlessly in the synagogue, but when Priscilla and Aquila heard him, they took him aside and explained the way of God to him more accurately. (Acts 18:26 NET)
The verse says they took him aside, and then explained. It does not say whether they said anything to him in the synagogue. It tells us only where the explaining was done: aside.
Here is the second. Paul wrote this about Cephas.
But when I saw that they were not behaving consistently with the truth of the gospel, I said to Cephas in front of them all (Galatians 2:14 NET)
That one was in front of them all.
The verses do not say when to use the first and when the second. That is not shown. So this part is my own judgment, and I say so. In a thread, I take someone aside first.
Here is how I try to do it. I ask what they see. I quote their words back, exactly. I ask which step they mean. I say what I think is shown, and what is not. If they do not want to talk, I leave it. You can love a person and let a thread end.
A few plain lines to keep
Words are small. Use small ones. Here are lines you can use. I made them up. Change them to fit.
I read the verse. It says this. Then quote it.
The video says this. Then quote that.
I can't find the step from one to the other. Can you show me?
I think this part is shown. I think this part is not shown.
I do not know yet.
Thank you. I will look again.
Each line is short. Each one is true. None of them says why anyone spoke. None of them tells anyone who they are. If a line would do that, leave it out.
Close the thread
Sometimes the best thing you can do with a thread is close it. I said that in chapter 1, and I mean it.
You close it when you have checked what you could check. You close it when the rest is not yours. You close it when the next reply would only add noise.
If you leave, then leave in peace. You are not running from the truth. You are going back to it. The vine does not live in the comments.
The tests are for you first
These tests apply to everyone in the room. The calm voice in the video. The one who lectured you. The one who left you with doubts. You. And me.
I said it in chapter 1, and I say it again. If I break one of these tests in this book, you should be able to catch me. Chapter 12 shows places where my work went wrong, and how it was caught. Check me. I would rather be checked than trusted without a look.
So run the tests on your own comment before you send it. Quote your own claim. Sort it. Look for a step you added. If you find one, take it out. It is easier to take out your own step than to defend it in a crowd.
Back in the room
It is late again. The phone is in your hand. The calm voice has stopped. The verse is on the screen.
You do not scroll. You stop.
You open your Bible. You find the verse. You read the lines around it. You write down what the video said, step by step. You write down what the verse says. You put them side by side.
Now you can see it. The first step is in the verse. The second step is not. The voice added it. The third step is something the next lines speak against.
So you sort. The first: shown. The second: not shown. The third: shown against. You do not need a loud word for any of them. You only need a place to put each one.
Then you open the comments. It is the same crowd. It is still loud. Many answers. Few questions.
Your thumb is over the box.
You ask the three questions. What does the verse say? Have I quoted the exact words I am answering? Is this mine to post?
The first: yes. The second: yes. The third: you think. You decide it is. You write one calm comment. It quotes the verse. It quotes the line from the video. It says which part is shown and which part is not. It does not say why anyone said it. It ends with one honest question: is there a verse I missed?
You press send.
A reply comes. It is long. It is about you. It tells you what kind of person asks such a thing. You read it once. You know what it is. It is not about the verse. You do not answer it. You do not need to win. You close that thread.
A private message comes next. It is gentle. It raises one more doubt. You answer it with a plain line. "I looked at the verse. This is what I found. This is what I could not find. I will leave it there tonight." You do not ask it to agree. You do not ask it to stop.
Then you put the phone face down on the table.
The room is dark. It is not empty. You know what you checked. You know what you did not. You rest in what is not shown. You have done what was yours.
You stay.
What He prayed
One more thing. It matters more than the rest.
On the night before He died, Jesus prayed. He did not pray only for the men in the room.
I am not praying only on their behalf, but also on behalf of those who believe in me through their testimony, (John 17:20 NET) that they will all be one, just as you, Father, are in me and I am in you. I pray that they will be in us, so that the world will believe that you sent me. (John 17:21 NET)
Those who believe through their testimony. That is you. He prayed for you, that night, before you were born. He asked that we would be one, in Him and in the Father. And He gave a reason. So that the world will believe.
The noise pulls against that prayer. The quiet leans toward it. This is how I read it: if you stay, then you are in the prayer. If you keep the peace, then you serve it.
So here is where we end, and where we began. Know the verse. Know the limit. Not shown is not false. Know when to stop. Then stay.
Three questions
- What will you do the next time a claim lands in "not shown"?
- What would it look like to take someone aside instead of answering in public?
- What did Jesus pray for you, the night before He died?
The pages that follow are for use. Keep them near you.
Appendix A. The tests on one page
Appendix A. The tests on one page
Keep this page by you. It lists all twenty-five tests. For each one it gives the status, the basis, and the limit. Then it lists the fifteen words I define early in the book.
A test says what it can do. It says what it cannot do. Read both. If you read only the first, you only think you know.
Where a rule's sentence is short, I give it word for word, in quotes. Where it is long, I give it in short, and the chapter has the full sentence.
How to read the labels
Status. Passed means the rule held when it was tried. Passed, limited means it held only in a narrower form, and the rule says what that form is.
Basis. Where the rule comes from. Observed: Scripture itself reads this way, and we can point to the verse. Forced: if we denied it, two Bible texts would contradict each other. A choice I made: no verse and no contradiction decides it, so I chose, and I say so. A few rules are working agreements of this last kind: a default, a rule about who must bring the proof, a rule that holds only on a condition, and a weak rule. For two rules, no basis is written down at all.
A label tells you how a rule was made and how it did when it was tried. It is never the reason a reading holds.
The ten that are Passed
Same-words rule. Citation rule. Picture-language rule. This-generation rule. Near-words rule. Mortal-body rule. Death-ends-once rule. Two-or-three witnesses rule, for charges. Bodily-act witnesses rule. Already-claims rule.
The fifteen that are Passed, limited
Parallel-account rule. Borrowed-meaning rule. Joining-words rule. Ages rule. Thousand-years rule. Nearness-length rule. Time-words rule. A-book's-"soon" rule. Death-sense rule. Two-or-three witnesses rule, for events. Witness-kinds rule. Witness-limit rule. Record-burden rule. Outside-record rule. Unnarrated-event rule.
The twenty-five tests
Chapter 5. Same words, same event?
- Same-words rule (Passed; observed). "Two passages that share words are not shown to be one event by the words alone." Limit: it does not show that two passages are different events. It covers descriptive wording, not proper names.
- Citation rule (Passed; no basis is written down for it). "A citation points to one verse only if the quoted words are in one place." The "only if" is a condition. Meeting it is not enough by itself to make a quote point to a verse. Limit: it compares words, not small grammar points.
- Parallel-account rule (Passed, limited; forced, in its main part). Each account witnesses what it reports. Comparing two accounts does not fix the exact words or the occasion. Limit: it decides nothing about who spoke, how many spoke, or what was seen.
- Borrowed-meaning rule (Passed, limited; both observed and forced). A writer's own note on his own words fixes their meaning only in his account. The rule's own sentence calls such a note a gloss. Limit: no same-saying test has passed, so a writer's note never carries to another passage.
- Joining-words rule (Passed, limited; forced, and held loosely). Two things are one occasion only when the text joins them inside one sentence. A plain "then" joins nothing. Limit: it binds within one sentence, not across chapters or books.
Chapter 6. Pictures, ages and a thousand years
- Picture-language rule (Passed; observed). "Cloud, sun-and-moon and shaking language is used for judgments on named places; by itself it neither proves nor rules out a final-events reading." Limit: it does not show what the picture language means in Matthew 24.
- Ages rule (Passed, limited; both observed and forced, with some parts a choice I made). Each use of the Bible's age words is read only by the words of its own verse in the NET English. Limit: it does not say when this age starts or ends. It covers only six listed original words. For most uses it says only what the word does not tell.
- Thousand-years rule [full name: the thousand-years-can-be-long rule] (Passed, limited; a choice I made, and weak). "A thousand years can mean a long span." Limit: "can" does not fix the length in Revelation 20.
Chapter 7. Time words
- This-generation rule (Passed; observed). "‘This generation’ means the people alive when the speaker spoke." Limit: my notes give it a role, not a bound. It is the one rule that fixes the deadline for the phrase. It names the people, not the events.
- Near-words rule (Passed; observed). "‘Soon’, ‘near’ and ‘at hand’ are true but set no number of years and no limit." Limit: it can never bind or exclude a passage.
- Nearness-length rule (Passed, limited; observed in one part, a choice I made in another). A near word gives no number of years by itself. A length comes only from what the text adds. If the text adds none, the answer is not decidable. Limit: five lines travel with it, and one says it was not tested again after my rulings.
- Time-words rule (Passed, limited; a choice I made, and a default). "Each time word is read in its own verse; no general rule fixes how far a deadline reaches." Limit: it does not fix what "all these things" covers.
- A-book's-"soon" rule (Passed, limited; a choice I made, holding only on a condition). "A book cannot call ‘soon’ what it places after its own long wait." Limit: it holds only if the wait is long. No rule says when the thousand years begin.
Chapter 8. Death words
- Death-sense rule (Passed, limited; forced in some parts, a choice I made in others). It sorts uses of "die," "dead" and "death" by seven signs in the Hebrew or Greek. It writes one label from a fixed list, or it writes that the text does not tell. Limit: it does not say what condition anyone is in before God, or what happens after the body dies.
- Mortal-body rule (Passed; observed). "Paul’s word for ‘mortal’ (six uses, all in Paul’s letters) means the physical body." Limit: my notes say only that no counter-case was found. It speaks of Paul's six uses, not of other writers.
- Death-ends-once rule (Passed; forced). "Where the text says death is ended for good, that ending happens once." Limit: it applies only where the text says the ending is complete.
Chapter 9. Who saw it?
- Two-or-three witnesses rule, for charges (Passed; observed). "In a charge against a person, two or three agreeing witnesses are needed." Limit: it is not applied to events in history. A missing witness does not make a claim false.
- Two-or-three witnesses rule, for events (Passed, limited; observed, with one sentence a choice I made). Agreeing witnesses may count toward an outside record that an event happened. They count only through the outside-record rule. The count is a help, never a requirement. Limit: it works only through the outside-record rule. The count sentence is my own choice.
- Bodily-act witnesses rule (Passed; observed). When Scripture says God did a bodily act in history, it says who saw it. Limit: not always the public. The number varies. Never eyewitnesses alone.
- Witness-kinds rule (Passed, limited; observed in most parts, with parts a choice I made). For each record, write who the witness is, what he witnessed and how. A writer who did not himself see or hear is giving a report. Limit: the three kinds are a frame, and the frame is my own choice. Its last line was carried over, not tested.
- Witness-limit rule (Passed, limited; no basis is written down for it). Witnesses speak to what happened, not to links between passages. When Scripture's own voice says an event fulfilled a saying, that is Scripture naming the link. Limit: what counts as such a statement is not settled here, and the rule gives no label of its own.
Chapter 10. What a record shows, and what it does not
- Record-burden rule (Passed, limited; a choice I made, about who must bring the proof). A claim that a dated saying was fulfilled needs a record. Without one, the record is not shown. Limit: the stronger form, that no other kind of record counts, fails. The rule never says exactly what counts as dated words.
- Outside-record rule (Passed, limited; both observed and forced, with some parts a choice I made). Where the only record of an event lies outside Scripture, ask three things apart. Did it happen? Does it match what was predicted? Is it inside the time the prediction fixes? Write the record as an outside record, never as Scripture. A missing record never gives "did not happen." Limit: when Scripture itself tells the event, this rule has nothing to write.
- Unnarrated-event rule [full name: the claimed-event-at-an-unnarrated-time rule] (Passed, limited; observed in one part, a choice I made in others, and built on two other rules). If someone says an act happened at a named time that Scripture does not narrate, the bodily-act witnesses rule is not called. An unmet burden is "not shown," never "it did not happen." Limit: it leans on the record-burden rule, which never says exactly what counts as dated words.
- Already-claims rule (Passed; observed). Scripture answers "it has already come" by naming what must come with it, and noting it has not come. Limit: it cannot date anything.
The fifteen words
- Verse and passage. A verse is one numbered line. A passage is a group of verses read together.
- Translation. The Bible put into English from the Hebrew, Aramaic and Greek it was first written in. This book quotes one translation, the NET Bible (New English Translation).
- Original words. The Hebrew, Aramaic or Greek words behind the English. A gloss is a short plain meaning of such a word. (The borrowed-meaning rule's own sentence uses "gloss" for a writer's note on his own words. This book calls that a writer's note.)
- Test, or rule. A short, plain check you run on a reading. In this book the two words mean the same thing.
- Limit. What a test says it cannot decide. Every test carries its limit with it.
- Shown. The words on the page, read with the tests, give it.
- Not shown. The words on the page do not settle it either way. Not shown is not false, and it does not mean it did not happen.
- Shown against. The words on the page, read with the tests, give the opposite.
- Observed. Scripture itself reads this way, and we can point to the verse.
- Forced. If we denied it, two Bible texts would contradict each other.
- My own choice. A part of a test that neither Scripture's usage nor a contradiction decides. I chose it, and I say so. The word for it is stipulated.
- Passed, and Passed, limited. Passed means the test held when it was tried. Passed, limited means it held only in a narrower form that it states.
- Split. Two careful readers get two different answers from the same words of a test.
- Blind reader. A reader, here an AI in a fresh chat, who is given a test and some passages and is not told what answer to expect.
- Noise. Anything loud, fast and unchecked that keeps us scrolling and pulls us away from what matters most.
The tests guarantee nothing. A reader can be wrong with them and right without them. Stay with the words on the page. Know what they say, and say no more.
Appendix B. A page you can use before you comment
Appendix B. A page you can use before you comment
Twelve questions. Keep them near your thumb.
They grow out of the eight habits in chapter 11. Each question names the habit it comes from. Six are extra, from chapters 2 and 14. Habits six and seven, say the limit and a label is never a reason, have no question of their own here. They are for the moment you use a rule, so carry them then.
Use them on a video, a thread, a post, or your own words. Take your time. You are not in a race. If you can answer each one, you may post. If you cannot, wait. You may leave it for the morning.
A "no" is not a verdict on you. It is a place to look. Look, and then ask again.
- What does the verse say? Read it again. Say it in your own words. If you cannot, stop here. From habit one: start with the words.
- What is around it? Read the verses before it and the verses after it. A verse alone can say more than it says, or less. Extra, from chapter 2: how much we read around the verse.
- Who is speaking? Is it Scripture's own voice, or a person in the story? A person in the story may be right. He may be wrong. Know which one you hear. Extra, from chapter 2: who is speaking.
- Does one word carry more than one sense? If it does, which sense does this verse give? The verse has to tell you. Do not choose first and read after. Extra, from chapter 2: one word, more than one sense.
- Do the English and the original words differ? Where the wording matters, look at the Hebrew or the Greek behind the English. If the two differ, say both. Extra, from chapter 2: the words themselves.
- Was a step added? List the steps. Which ones do the words show? Which ones did someone put in? A step does not follow just because it sounds smooth. Extra, from chapter 2: a step added without being shown.
- Which group is it in? Shown, not shown, or shown against. Put the claim in one group. Use the words on the page. From habit three: sort into three groups.
- If it is not shown, can I rest there? The words have not settled it. That does not make it false, and it does not mean it did not happen. From habit four: rest in "not shown".
- Have I quoted the exact words I am answering? Quote them first. Then answer them. If I answer a thing the person did not say, I have not answered. From habit two: quote the exact words before you answer them.
- Have I checked every quote? Check each quote against a Bible. Check each "shown". If an AI helped, check it twice. A smooth answer is not a checked answer. From habit eight: check, and be willing to be checked.
- Am I saying why they said it? Do not. I can see what was said. I cannot see the heart. And would I hold myself to the same test? The tests are for me too. From habit five: judge the words, not the heart. Its last two lines are habit eight.
- Is this mine to post? Will it help someone stay, or will it add to the noise? If you are not sure, do not post. Take the person aside. Or close the thread. Extra, from chapter 14: is this mine to post?
Jesus says, "Remain in me, and I will remain in you" (John 15:4 NET). That is the aim. The questions only clear the way.
Appendix C. Using the tests with an AI chatbot
Appendix C. Using the tests with an AI chatbot
This page is for the day you want to try the tests with an AI chatbot. I will walk you through it, one step at a time. Read it once. Then use it.
What this is
The tests in this book exist as one long written prompt. A prompt is a set of instructions you give an AI. You paste it into an AI chat. You add a passage. The AI then helps write a reading of the passage by the rules, and it shows its work.
Hold the picture from chapter 3. An operating system for reading, not for the Bible itself.
And hold what goes with it. The tests are my discipline. They are not Scripture. They serve the page, and they never rule it. They promise you nothing.
Here is the main thing. An AI answer is a test result, not a verdict. You still check it.
Step one: get the prompt
The current copy of the prompt is on my website, michlaude.com. It is on the page named for this book, The Bible Reading OS. Until the tests are released, the newest version is in my blog. Get it from there each time, so you have the newest one.
The prompt has a start line and an end line. The start line reads BEGIN DIRECTIVE. The end line reads END DIRECTIVE. Copy everything from the start line through the end line. Please copy all of it. Do not cut any part.
It is very long. The whole prompt is about 370,000 characters. Some chatbots will not take a paste that long. If the chat box will not take that much text, save the prompt as a plain text file and attach the file instead. I did not test which chatbots will accept it, as a paste or as a file. If yours refuses both, I cannot tell you why or what to do. Try another.
Step two: add the run line
The run line is the first line after the prompt. It tells the AI which rules to run. This is how you choose what runs.
Here is the run line for the rules in this book. Put it on its own line, right after the prompt.
``` RUN: A B ```
The letters A and B stand for two groups of rules in the prompt. Group A holds the rules marked Passed. Group B holds the rules marked Passed, limited. Together they are the 25 rules in this book.
If you leave the run line out, the prompt runs those same two groups. It should tell you that it is using the default.
The prompt has other run lines. I do not teach them here. Some of them run wordings that are only proposed. Those stay proposed, and they never count as support.
Step three: paste the verse text yourself
This step matters most.
The prompt supplies no verse text. It does not contain the Bible. If you give the AI only a reference, such as a book, a chapter and a verse, the AI may fill in the words from memory. A verse the AI recalls has not been checked. It may be close. It may be off by one word. One word can move a whole reading.
So paste the text. Take it from a Bible you trust. This book quotes the NET. If you use another translation, say which one, and keep to it all the way through.
Paste the whole passage, not one verse alone. Paste the verses around it. A verse cut off from its room is the third cause in chapter 2.
When you paste the text yourself, the text is supplied. That word has a plain meaning here. It means the words came from you, and you can check them.
Step four: read the answer in order
A good answer comes in a set order. Look for these parts.
First, a line that says Selection received. The AI must copy your run line word for word. Then it lists each rule it will apply, with its group. Check that it matches what you asked for. If the AI ran a rule you did not select, or left one out, stop.
Second, the conclusion. It comes first, in two or three sentences. It is short on purpose.
Third, the sourced part. This holds what the AI used, and what each rule gave. Each verse is marked in one of three ways.
- Supplied. The text came from you.
- Verified. The text matched word for word a copy that was checked, and the answer says which copy.
- Recalled. The AI remembered it. It was not checked.
A chatbot with no copy of the NET cannot check a verse against it. So treat any verse not marked supplied as unchecked.
For each rule, the answer should give the rule's name, its status, and its limit. It should say whether your passage is inside the limit. If it is outside, the answer should say so and stop. Then it gives what the rule gives. If the rule does not decide, the answer should say the text does not tell. It should not fill the gap.
Fourth, the judgment part. It is kept apart and labelled. Here the AI may weigh things. Do not mix this part with the sourced part. The sourced part holds what was found. The judgment part holds what the AI thinks.
Fifth, open items. These are questions that only the author of the rules can answer.
If you ask for strengths and weaknesses, or for and against, the answer sorts into the three groups. Shown. Not shown. Shown against. A claim the rules leave open goes in the middle group. It never goes under against. Open is not the same as wrong.
The prompt also tells the AI how to behave. Do not simply agree with the reader. Put the conclusion first. Take correction at once. Give no verdict on anyone's motive. Do not set or change a status. The author sets every status.
Step five: check it yourself
Here is your part. The AI does not do this for you. The same checks apply to my own work.
- Check every quote. Put each one beside your own Bible. Check the words, not just the sense.
- Check every step that says shown. Ask where the words are. If you cannot point to the words, the step was added.
- Check that no rule was used outside its limit. Each rule states what it cannot decide. The answer should state it too.
- Check that nothing only proposed was used as support. A proposed wording is never support.
- Check that the answer did not say why a person did a thing. The rules give no verdicts on motive. Neither should you.
Do one more thing. Notice whether the answer sounds smooth and sure. If it does, slow down. A smooth answer is not a checked answer. A machine's own checks can miss things, as chapter 12 shows. So do not let a chatbot's checking stand in for yours.
What this cannot do
It cannot settle a question the passage leaves open. If the text does not tell, the answer will say so. Rest there.
It cannot make you right. A reader can be wrong with the tests and right without them.
It was tried by AI readers on the cases I gave them. It was not tried by a crowd of outside readers. I did not test which chatbots can take the prompt. Different chatbots may behave differently. So hold the answer loosely, and let the page have the last word.
If you find a place where the tests broke, I want to know. That is how they get better.
Appendix D. Every verse used, in one list
Appendix D. Every verse used, in one list
Reference only. Each verse is quoted or named in the chapter beside it. The list runs in book order.
Chapter 1. In the room
- (John 15:4)
- (John 15:5)
- (John 17:21)
Chapter 2. Why two people read one verse and disagree
- (John 21:20)
- (John 21:21)
- (John 21:22-23)
- (Matthew 2:15)
- (Hosea 11:1)
- (Matthew 16:6)
- (Matthew 16:7)
- (Matthew 16:11)
- (Matthew 16:12)
- (Matthew 4:5)
- (Matthew 4:6)
- (Matthew 4:7)
- (Luke 24:25)
- (Luke 24:27)
- (Matthew 22:23)
- (Matthew 22:28)
- (Matthew 22:29)
- (Matthew 22:30)
- (Matthew 22:31)
- (Matthew 22:32)
- (2 Peter 3:16)
- (Acts 17:11)
Chapter 3. The noise, and what it costs
- (John 17:20)
- (John 17:21)
- (Ephesians 4:3)
- (1 Corinthians 1:12)
- (1 Corinthians 1:13)
- (Titus 3:9)
- (2 Timothy 2:23)
- (2 Timothy 2:24)
- (Romans 14:1)
- (Romans 14:3)
- (John 15:4)
- (John 15:5)
- (John 21:22)
- (John 21:23)
- (Acts 15:2)
- (Acts 15:6)
- (Acts 15:7)
Chapter 4. Where the rules come from, and how they were tried
- (Luke 10:29)
Chapter 5. Same words, same event?
- (Mark 6:41-44)
- (Mark 8:6-9)
- (Mark 8:19-20)
- (Matthew 2:15)
- (Hosea 11:1)
- (Mark 15:26)
- (Luke 23:38)
- (John 6:70-71)
- (1 Chronicles 14:15)
Chapter 6. Pictures, ages and a thousand years
- (Isaiah 13:1)
- (Isaiah 13:10)
- (Ezekiel 32:2)
- (Ezekiel 32:7)
- (Ezekiel 32:8)
- (Zephaniah 1:15)
- (Isaiah 19:1)
- (Genesis 6:3)
- (Proverbs 27:24)
- (Psalm 90:4)
- (2 Peter 3:8)
- (Ecclesiastes 6:6)
Chapter 7. Time words
- (Matthew 11:16-19)
- (Jeremiah 2:31)
- (Matthew 24:34)
- (Zephaniah 1:14)
- (Ezekiel 12:23)
- (Ezekiel 12:25)
- (Galatians 4:19)
- (Matthew 2:15)
- (Mark 13:30)
- (Luke 21:32)
- (1 Thessalonians 4:15)
- (1 Corinthians 6:14)
Chapter 8. Death words
- (Romans 6:2)
- (Romans 6:12)
- (Romans 8:11)
- (1 Corinthians 15:53)
- (2 Corinthians 4:11)
- (Isaiah 25:8)
- (John 11:21-25)
- (1 Corinthians 15:54)
- (2 Corinthians 5:4)
Chapter 9. Who saw it?
- (Deuteronomy 19:15)
- (Jeremiah 32:9)
- (Jeremiah 32:10-12)
- (John 19:35)
- (Acts 10:40-41)
- (Luke 24:48)
- (1 Corinthians 15:8)
- (Galatians 1:12)
- (Luke 1:1-4)
- (John 19:35-37)
- (Acts 10:34)
- (Luke 1:2-3)
Chapter 10. What a record shows, and what it does not
- (Jeremiah 28:3)
- (Jeremiah 28:16)
- (Jeremiah 28:17)
- (John 20:30-31)
- (John 21:25)
- (Luke 17:23-24)
- (1 Corinthians 15:52)
- (1 Thessalonians 4:16)
- (2 Timothy 2:18)
- (2 Thessalonians 2:2-3)
Chapter 11. The habits under every rule
- (Mark 7:5)
- (Mark 7:8)
- (Mark 7:13)
- (John 21:23)
- (Romans 14:4)
- (Acts 17:11)
- (Acts 18:25)
- (Acts 18:26)
- (Acts 18:27)
- (Matthew 4:5-7)
- (Matthew 4:7)
Chapter 12. Where the rules split, ran out, or failed
- (1 Kings 16:34)
- (Ruth 4:9)
- (Ruth 4:11)
- (Luke 10:29)
- (Luke 10:36)
- (Haggai 2:6)
- (Hebrews 12:26)
- (Ezekiel 12:25)
- (Revelation 1:7)
- (2 Peter 3:4)
- (Matthew 24:34)
- (2 Thessalonians 2:3)
- (Revelation 1:1)
- (Revelation 22:6)
- (Revelation 20:3)
- (Revelation 20:7)
- (2 Kings 7:1)
- (2 Kings 7:16)
- (1 Kings 14:19)
- (2 Timothy 2:18)
- (1 Corinthians 15:52)
- (Jeremiah 25:11)
- (Jeremiah 25:12)
- (Jeremiah 29:28)
- (Jeremiah 51:33)
- (Matthew 24:33)
- (2 Kings 18:5)
- (2 Thessalonians 2:1-3)
- (2 Kings 7:16-17)
- (2 Timothy 2:16-19)
- (Ruth 4:9-11)
- (Deuteronomy 30:1)
- (Matthew 28:20)
- (2 Peter 3:8)
- (Luke 7:2)
- (Acts 24:15)
- (2 Kings 23:25)
Chapter 13. One passage, start to finish, and using AI without the slop
- (John 21:18-25)
- (John 21:19)
- (John 21:20)
- (John 21:21)
- (John 21:22)
- (John 21:23)
- (John 21:24)
- (John 21:25)
- (John 21:22-23)
- (John 15:4)
Chapter 14. Before you comment: abiding in Christ, in unity
- (John 15:4)
- (John 15:5)
- (Romans 14:19)
- (Romans 14:1)
- (Romans 14:3)
- (1 Corinthians 1:12)
- (1 Corinthians 1:13)
- (Ephesians 4:2-3)
- (Acts 18:26)
- (Galatians 2:14)
- (John 17:20)
- (John 17:21)
- (Galatians 2:11)
Appendix E. Where these tests came from, in short and honest
Appendix E. Where these tests came from, in short and honest
This page is plain on purpose. It tells you where the tests came from, who tried them, and where the trying stops. Chapter 4 tells what you need to check the tests. This page keeps the working diary, in order: the dates, the rounds, the names I gave the AI jobs, and how the stopping rules came about. Chapter 12 tells where it went wrong.
One author
These tests are one author's work. That is me. I made them, and then I tried them. No outside human reader has tested them. Weigh them that way.
Where they started
The rules grew out of my work on one passage: Jesus' talk on the Mount of Olives (Matthew 24 to 25, Mark 13 and Luke 21). Most of the early tests and named verses came from there. The examples in this book come from across the Bible. Still, they put to work rules that were made mostly on one passage. I want you to know that.
I also looked at what outside writers say about how to read Scripture. I kept an idea only where Scripture's own usage gave named examples. That left nine candidates. None of them is taught in this book. They are still being tested.
How a rule stands
Most of the tests stand on one of two things.
Observed. Scripture itself reads that way, and I can point to the verse.
Forced. If we denied it, two Bible texts would contradict each other.
A few tests are of another kind. They are working agreements. One, for example, is a default: what you do when no rule fixes a word. Each working agreement, and each part of a test that neither Scripture's usage nor a contradiction decides, is marked plainly as a choice I made. For two tests, no basis is written down at all, and I say so. The book names the basis of each test where it is taught. Appendix A lists all twenty-five.
No test rests on silence. Where the words say nothing, the passage stays open.
The honest claim for a rule that passed is small. No contradiction was found in the passages checked.
Who did what
AI did much of the work. I made every decision.
A blind reader is an AI in a fresh chat. It gets the rules and some cases. It is not told what answer I expect.
An assessor is another AI, in a separate chat. It sorted what the blind readers found. Which findings were real breaks, where a rule gave a wrong answer, or two answers? Which were limits to state? Which were out of scope? Then I answered the open questions.
A skeptic is an AI asked to raise the strongest objections one view would raise.
A last reader, one more AI, took the pooled objections, with the names removed and the order mixed. It marked each part of each objection in one of four ways. The rules agree with the claim. The rules give the opposite. The rules leave it open. Or no rule speaks to it. An agreement does not mean the objector's own reading has been shown. A mark is never a verdict on a view or a person.
I also wrote a long paper, which I call the long argument. In it I apply these rules to Jesus' talk on the Mount of Olives. This book does not argue it. An AI editor builds each copy of it and checks it. AI scripts check every quote. Then the editor and I read. I decided every status. I did not hand that to a machine.
Two kinds of round
A round is one full pass of testing. There were two kinds.
A rule round tests the wording of a rule. Blind readers read it, and then an assessor sorts what they found. Seven of the rules in this book went through three rule rounds, with two blind readers each time and fixes between rounds.
An argument round tests one copy of the long argument, in three steps. First blind readers, then three skeptics, then the last reader. It tests my long argument. It does not test the Bible. A round is clean when no new confirmed error turns up in it. A confirmed error is a problem I checked and found true against the NET, the Greek and Hebrew word list, or the source the argument cites. A misquote is one. A wrong reference is one. So is a claim that goes against a verse it cites. A note that only asks me to mark something as my own reading is not an error.
The diary, in order
Two days of splits. The death-sense rule taught me that I needed a place to stop. Chapter 8 teaches that rule. One clause in it is about when two sayings are tied together. That clause went through six wordings in two days. Each fix gave the next readers something new to split on. They split on who counted as the second speaker. They split on what to each other meant. They split on whether the narrator's words were speech.
8 November 2026. I froze the text of that rule and gave it the label Passed, limited. On the same day I chose a stopping rule. Here it is in plain words. I change a wording only when a reader shows, from the text in front of them, one of three things.
- A wrong label.
- The answer the text does not tell where the text does tell.
- Two readings that print two different labels on one passage.
If two readings print the same label, I do not change the wording. I write the split beside the rule as a limit, with the passages it touches. And a part that is a choice I made changes only when I choose. It never changes because readers split on it.
I wrote down the guards too, because a stopping rule can fool its maker. The same label can hide two different reasons. A frozen wording can look settled when it is only tired. A choice I made could spread to parts that should be tested. And a stopping rule can look chosen to favor a result. So I wrote it down before I read the next result.
11 November 2026. Three days later, I did choose. I changed one other clause of that rule twice. It is about who counts as speaking for God when a formula naming God is said. No reader has tested that clause since. The rule says so every time it runs. Its label rests on the tests that came before.
17 November 2026. This day was about the nearness-length rule, which chapter 7 teaches. Older wordings came first, and chapter 12 tells how some failed and some were replaced. Then came three rule rounds of fresh readers. There were six reader tests in all. Each one ended with the same words: it passes in part. Two reader disagreements stayed open. On 17 November I gave four rulings.
- I allowed a narrow exception for the words you will see. It rests on one case, and it needs judgment.
- I dropped Luke 19:11 as a bound.
- I ruled that a later text can give a length only if it carries a word of saying or promising.
- I ruled that a length built on Hebrew words is reported as resting on the NET's English.
Then I gave the rule its status. My word was limited. The fresh readers did not read the wording again after my rulings, and the rule's limit says so.
The second stopping rule. I used a second stopping rule for the long argument. It is simple. Stop after two argument rounds in a row with no new confirmed error.
20 November 2026. On the morning of that day, an AI editor found a misquote that no reader had caught. The count of clean rounds went back to zero. Chapter 12 tells that story, and the other mistakes we caught. Later that same day, we counted two clean rounds in a row, and the stopping rule was met. After the rules were updated, we counted two more clean rounds, and it was met again.
The labels
This book teaches 25 rules. Ten are marked Passed. Fifteen are marked Passed, limited. Passed means the rule held when it was tried. Passed, limited means it held only in a narrower form, and the rule says what that form is. Appendix A gives each rule's label and basis. A label is never the reason for a reading.
I used two stopping rules. One says when to stop changing a rule's wording. The other says when to stop testing the long argument. Chapter 4 gives them in short. The diary above gives them in full.
Some older rules are still under review. Some wordings are still being tried. I left them out of this book on purpose.
The honest limits
Here is what this work does not do.
It was tested by AI readers. It was not tested by outside human readers.
The tests were run on the cases the readers were given. They were not run on every passage.
Many rules were not tested again after my rulings. They say so every time they are used.
The long argument is tested in rounds. Those rounds test one argument. They do not test the Bible.
Counts from one round to the next are not like for like. So I do not claim the counts are going up or down.
AI readers can be wrong. People can be wrong too. I made mistakes, and some of them were caught. Chapter 12 shows them.
What the tests do not do
They promise nothing. They do not make a reading right. They do not make a verse mean anything. They are not Scripture, and they do not stand over it. They sit below Scripture's own words. They are one person's way of checking, kept with care. You can be wrong with them. You can be right without them. The picture from chapter 3 still fits: an operating system for reading, not for the Bible itself.
If you take one thing from this page, take this. Read the Bible for yourself. Check what I say. Stay in Christ.
Acknowledgements
Acknowledgements
The Scriptures quoted are from the NET Bible® [http://netbible.com] copyright ©1996, 2019 used with permission from Biblical Studies Press, L.L.C. All rights reserved.
Scripture quoted by permission. Quotations designated (NET) are from the NET Bible® copyright ©1996, 2019 by Biblical Studies Press, L.L.C. All rights reserved.
The meanings of Greek and Hebrew words come from the STEP Bible data, published by Tyndale House, Cambridge, under a Creative Commons Attribution 4.0 licence (CC BY 4.0).

