Every time you start a new conversation with Claude, it starts completely fresh. No memory of last week, no knowledge of your workflows, no context unless you provide it. In this post, I walk through how to build a structured personal knowledge base that Claude can actually use: the right file formats, how to organise your folders, how to write documents Claude can navigate quickly, and how to connect everything through Google Drive so Claude searches it automatically.

Most AI projects don’t fail because of the model — they fail because the knowledge base behind it is messy, outdated, or impossible to retrieve from. Before embeddings, vector databases, or fancy architectures, the real work starts with how your documents are written, structured, and indexed.

In this piece, I break down what it actually means to prepare a knowledge base for AI agents in security, compliance, and risk environments. We’ll look at when indexing really matters, how to structure documents so AI can retrieve answers faster, and why clear titles, meaningful tags, and proper chunking often outperform more complex solutions.

I also share practical examples, a simple readiness checklist, and lessons learned from building AI systems that had to stand up to audits and incident reviews — not just demos.

If you wouldn’t trust a document in an investigation, your AI shouldn’t either.