Why I use AI in these studies
I use AI to help research and draft the studies on this site. You deserve to know that, and to know exactly what that does and doesn't mean — so here it is in one page.
The short version
AI is a research assistant, not an author and not an authority. It reads the languages I can't yet read, checks the translations I can't hold in my head at once, and tells me quickly when an idea I liked doesn't survive contact with the text. Every claim is grounded in an actual source, and nothing goes on this site that I haven't read, checked against Scripture, and owned as mine.
What it actually buys me
The original languages come within reach. I am not formally trained in Biblical Hebrew, Aramaic, or Greek — I'm at the start of that road, not the end of it. Working through a passage's morphology, lemmas, Strong's numbers, and semantic domains by hand would take me days per chapter, if I could do it reliably at all. Querying a structured dataset makes it minutes, and the result is checkable. When a study tells you that a word is חֶסֶד (chesed) and points at its range of meaning, that came out of a lexical database, not out of a guess dressed up in confident prose.
Many translations at once. A single English translation is one committee's set of decisions. Comparing the Masoretic Text and Septuagint against several English renderings surfaces the places where translators disagree — which is exactly where a study should slow down and say so rather than quietly pick the reading that suits the argument.
Thoughts get structured fast. A half-formed idea becomes an outline, a set of questions, and a list of passages to test it against, in an evening rather than over months. Speed here isn't about producing more; it's about being able to finish the thought instead of abandoning it.
Assumptions get disproved. This is the benefit I did not expect and now value most. More than once I've come to a passage sure of what it said, asked for the counter-evidence, and watched the idea fall over. An assistant that can find the case against me quickly is worth far more than one that agrees with me pleasantly.
Depth I could not have reached alone. Feast cycles, calendars, Ancient Near Eastern custom, Second Temple background — tackling complex topics with real cultural and linguistic depth behind them has been the best part of this. Connections I would simply never have found on my own are now traceable, cited, and out in the open where you can check them.
The risks, and what I do about them
I'd rather name these plainly than pretend they aren't there.
| Risk | Why it matters | The guardrail |
|---|---|---|
| Hallucination — a fabricated lexical claim, a misquoted verse, a citation to a work that doesn't exist | This is the headline failure mode of language models, and in a Bible study it is not a small error — it is putting words in God's mouth | Research is grounded in structured Bible databases held in this repo — original-language text, morphology, Strong's, semantic domains, cross-references, drawn from open-licensed scholarly sources. A language claim has to resolve to a real entry in a real dataset. It is not permitted to come from recollection |
| Fluent, confident, wrong | Machine-generated prose sounds authoritative regardless of whether it is correct. Smoothness is not accuracy | Every substantive claim carries a citation, and translations are always named. If you can't trace it, it shouldn't be here — and you should tell me if you find something that isn't traceable |
| Agreement bias | These tools lean toward building the case you asked for. Ask leadingly and you'll get a confident yes | The study method deliberately runs exegesis before conclusions and requires the counter-case to be sought. "The one who states his case first seems right, until the other comes and examines him" (Proverbs 18:17 (ESV)) |
| Doctrinal flattening | A model's instincts reflect whatever is most common in its training data, which drifts toward a vague consensus and away from any defined position | Studies are written from a stated position, not a model's default. See the Statement of Faith; interpretive commitments are declared up front rather than absorbed silently |
| Mishandling others' work | Scholarship is someone's labour, and lifting it wholesale is theft whoever does the typing | Sources are partitioned by licence. Open-licensed data is used and quoted freely; commercial reference works are cited by name with short, attributed quotations only, never reproduced at length |
Underneath all of them sits one non-negotiable: a human reviews every line before it is published. Not a skim — a read against the text. That gate does not move.
How a study actually gets made
The process is written down and enforced, not improvised per study. Exegesis first — what the text meant, then and there — and only afterwards what it means here and now.
flowchart TD
A[Passage or question] --> B[Historical & literary context<br>author, audience, occasion, genre]
B --> C[Original-language word study<br>grounded in local lexical data]
C --> D[Cross-references &<br>translation comparison]
D --> E[Commentaries consulted last<br>to check the reading, not to form it]
E --> F{Human review<br>every line, against Scripture}
F -->|Doesn't hold up| B
F -->|Verified & owned| G[Published]The loop back to context matters more than the arrow forward. If a conclusion won't stand on the passage in its own setting, it goes back — it does not get published with softer wording.
What this is not
It is not content generation. Nothing is published here because it was easy to produce. If a study has nothing to say, it doesn't get written up to fill a gap in the navigation. Volume is not the goal and never has been.
It does not replace prayerful, thoughtful study. AI speeds up the research; it cannot do the part that matters. "Open my eyes, that I may behold wondrous things out of your law" (Psalm 119:18 (ESV)) is not a database query. The Spirit of truth is the one who guides into truth (John 16:13 (ESV)) — a machine retrieves, He teaches.
It has no spiritual authority whatsoever. AI is not converted, not indwelt, not accountable to anyone, and has no discernment — only pattern. It cannot pray, cannot be convicted of sin, and cannot be taught by God. Nothing it produces carries weight because it produced it.
The wrestling is not outsourced. Sitting with a hard passage until it changes you is a large part of why anyone should study Scripture at all. Hand that over to a tool and you end up with a better page and a poorer soul. So the tool does the fetching, the collating, and the checking — the sitting with it stays mine, and the working out of what it demands stays mine too.
Errors here are mine. Not the tool's. If something on this site is wrong, I published it.
Be a Berean about this site
The Bereans were commended for checking the Apostle Paul himself against the text (Acts 17:11 (ESV) — "examining the Scriptures daily to see if these things were so"). If Paul's teaching was fair game for verification, mine certainly is, and so is anything a machine helped me assemble.
So: test everything; hold fast what is good (1 Thessalonians 5:21 (ESV)). The citations on these studies are there precisely so you can go and check. Please do — and if I've got something wrong, tell me.
Scripture is the authority. This site is one person's working out of it, assisted by a tool that is very good at retrieval and utterly incapable of faith.