DocGuard — Zero-Hallucination Docs Support Bot

ou've seen the hallucination problem. Someone asks how to configure auth timeout. The bot confidently answers — wrong flag, nonexistent option, made-up default. Developer follows the instructions. Breaks their production config. Files an angry issue. Now you're spending 40 minutes debugging something that never existed.

DocGuard works differently. Point it at your docs folder, drop it in your Discord or Telegram support channel. Every question triggers a real search — semantic memorySearch first, grep fallback second — before a single word of response is composed. The answer includes the exact file path and line number where the information was found. If nothing matches: "I checked the docs and couldn't find this." Full stop.

What you get:

• Mandatory retrieval before every answer — the lookup runs before response composition, not as an afterthought. This is enforced at the architecture level, not by a polite instruction.
• File + line citations — every answer ends with Source: docs/api/auth.md:34. Users can verify instantly. Trust compounds.
• Honest not-found responses — "I searched your docs folder and this isn't documented" is a complete, useful answer. It tells maintainers exactly where the gaps are.
• memorySearch + grep fallback — semantic search runs first for accuracy. If it misses, DocGuard tries 3 grep keyword variations before declaring not found.
• Multilingual — DocGuard answers in whatever language the user writes in. Cited paths stay as-is.
• Not-found tracking — every unanswered question is logged. Review memory/history.json to find your documentation gaps before your users find them for you.
• Zero hallucination guarantee — DocGuard has no concept of "I think" or "typically". If it can't cite a source, it doesn't answer.

Setup in 2-3 minutes:

1. Install: openclaw agents add docguard
2. Copy workspace: cp -r workspace/* ~/.openclaw/agents/docguard/workspace/
3. Send /new to your DocGuard bot
4. Answer 4 questions: docs folder path, file format, channel (Telegram/Discord), project name
5. Optionally add your docs folder to memorySearch.extraPaths in openclaw.json for semantic search — grep still works without it

Who this is for:

• OSS maintainers tired of answering the same 15 questions in GitHub issues
• API / SDK teams whose docs are authoritative and hallucinations are a liability
• SaaS teams running Discord or Telegram support channels without a full-time support engineer
• Developer tools where wrong answers cause real damage (auth flows, deployment configs, data migrations)

Your docs are the source of truth. DocGuard makes them the only source of answers.