BoltProof · Learn

Point your AI at your own documents, so it stops making things up

Stop the hallucinations: make the model answer from your own files, with sources.

A normal chat model answers from its training, which ended at some point in the past and contains nothing about your business. Ask it "what are our termination rights under the client agreement?" and it either refuses or invents a plausible-sounding answer. That's the hallucination problem everyone has heard about, and it's the reason people don't trust AI with real work.

The fix is to give the model your documents and make it answer from them. The technical term is retrieval augmented generation, or RAG, but the idea is simple: you hand it a pile of your files, and instead of answering from memory, it searches those files and answers from what it actually finds there.

What that changes

Ask it the same question with your documents attached, and it opens your actual agreement, finds the termination clause, and quotes it back. The answer is grounded in your files. If it's not in the files, a well-set-up system says so instead of guessing.

For anyone who deals with contracts, policies, client correspondence, or years of internal documents, this is the single most valuable thing local AI does.

How to set it up

Both the tools I recommend handle this. In Open WebUI, you create something called a knowledge base or a collection, upload your documents, and it processes them into a searchable form. Then when you ask a question, tell it where to look: "Answer using my contracts folder."

That last part matters. Asking a question into the void gets you a guess. Asking a question and telling the system which folder to search gets you a grounded answer. The difference is one sentence.

What to feed it

Start with the documents you actually need to ask about. Client agreements. Standard operating procedures. Employee handbooks. Past proposals. A year of meeting notes.

Don't feed it everything on day one. Start with one folder, the contracts folder or the policies folder, and get comfortable with how the answers sound before you add more.

And be honest with yourself about the quality of the files. If your contracts are a mess of badly-scanned pages, the answers will be shaky. Garbage in, garbage out, same as any tool. Clean documents give clean answers.

The honest limit

RAG makes the model trustworthy, not infallible. It can still misread a dense clause, or miss a document you didn't upload. For anything where being wrong is expensive, a human still checks the answer. What you get is a research assistant that has already read everything and can point you to the exact place in the exact file.

Setting this up properly, with your real documents, secured and access-controlled, is one of the things I build for businesses in Dubai. If you'd rather not piece it together yourself, the first conversation about what you need is free.