Rag

I had just added six commentary volumes to my Bible search. I asked it a question about the fruit in the garden of Eden. The answer came back with sermons and Bible verses. Not one of the six new books was among the sources. The books were in the database. The search just did not pick them. The Need: A Source You Added Must Be Able to Appear If a new source never shows up, you cannot tell whether it is broken or simply ranked low. You only see the answer, and the answer looks fine. It is easy to think “the system works” and move on. ...

I have a lot of Bible material that I cannot search together. Sermon recordings turned into text. A commentary that I scanned page by page. A few Bible translations. Each one has its own search, or no search at all. When I wonder “what did the Bible and the preachers say about this?”, I open four things and read. So I built one box where I type a question, and it answers using all of them, with a number after every claim that points to the exact source. ...

In an earlier post I turned hundreds of hours of recorded Bible teaching into text. AI transcription is good, but not perfect — it mishears words, especially names and rare terms. So the obvious next step was to ask a smart language model to clean up the mistakes. These models have basically read the whole Bible, so I figured fixing a few scripture typos would be easy for them. It wasn’t. And the way it failed taught me something that goes well beyond transcripts — to anyone using AI to correct text against a trusted source. ...

You’ve probably felt this. Someone mentions a technology — Cloudflare Tunnel, RAG, Termux, vector search — and a small door closes in your head. “That sounds powerful,” you think, “but it’s not for me. I’m not an engineer.” For most of my life, that feeling was right. Knowing the name of a technology got you almost nowhere. Between the name and a working result there were months of study, and a level of skill I was never going to reach. ...