# The Resolution Layer — Why Your AI Gets Confused > How to turn meetings, email, and documents into a memory you can trust — by sorting out who and what before the AI says anything. The one step everyone skips, and the gate that makes the rest of the AI stack defensible. 20 slides, 30 minutes. *WS·08 · Module WORKSHOPS — Workshops · The CEO AI Playbook by Stephen Forte* Canonical: https://academy.buildclub.com/workshops/company-brain ## Thesis Before an AI can answer questions about your company, it has to know who and what you are talking about. Get that wrong, and every answer sounds confident — and can't be trusted. ## Key Takeaways - Before an AI can answer questions about your company, it has to know who and what you are talking about. Get that wrong, and every answer sounds confident — and can't be trusted. - Which pile of documents do I already feed to AI? Name the one workflow where you most rely on AI summaries today. That's the pile worth resolving first. - How to turn meetings, email, and documents into a memory you can trust — by sorting out who and what before the AI says anything. The one step everyone skips, and the gate that makes the rest of the AI stack defensible. 20 slides, 30 minutes. ## The Playbook 1. **Same person, many names** — 'Stephen,' 'Steve,' and 'the CEO' become three different people in the AI's head. The resulting org chart is wrong before any decision is made on top of it. 2. **Lost track of 'he'** — 'He said the client wasn't ready' — but who is he, and which client? Pronoun resolution fails across paragraphs, then across documents, then across weeks. 3. **Invented connections** — The AI claims a link the conversation never actually made. The model fills the gap between two sentences with a plausible relationship that was never there. 4. **No two answers agree** — Ask the same thing twice, get it sorted differently each time. The output looks confident both times. Neither answer is reproducible. 5. **Old news stays current** — A decision that was reversed in April still shows up as the latest word. Without time-aware resolution, the system treats every fact as eternal. 1. **Pick one pile you already use** — One client's meetings, your own inbox, or one contract folder. Not the whole company. The smallest unit of work that is still useful — usually one engagement, not one department. 2. **List the names first** — Write down the people, systems, and companies in that pile before asking the AI anything. Twenty entries on a single page. This is the seed registry. The system grows from here. 3. **Turn on 'ask, don't guess'** — Make your AI ask when it's unsure — and never let it rewrite the original. If your current tool cannot do this, you are using the wrong tool. This is the test. 4. **Keep a visible waiting list** — One place for open questions, so none get lost. A shared document, a Notion page, a single Slack channel — the medium does not matter. The visibility does. 5. **Scale only once it works** — Add more once the loop runs smoothly on one pile. Resist the urge to onboard a second engagement until the first is producing trustworthy answers for two consecutive weeks. 1. **Sort out who and what first** — Before any summary, any extraction, any answer. This is the step everyone skips — and the step that decides whether the rest is trustworthy. 2. **When unsure, ask — don't guess** — A system that asks beats one that confidently guesses wrong. The clarification cost is paid once; the wrong-answer cost is paid forever. 3. **Never rewrite the original** — Keep the source so any answer can be traced back and checked. Resolution is additive — annotations on top of the source, never a replacement for it. 4. **Start small, then scale** — One pile of documents, one habit, one visible list. Prove it before you expand. The companies that win at AI memory are the ones that crawled, then walked. ## What to Do Monday - Which pile of documents do I already feed to AI? Name the one workflow where you most rely on AI summaries today. That's the pile worth resolving first. - When my AI tool is unsure, does it ask me — or quietly pick one? If you don't know, the answer is almost certainly the second one. Find out this week. - Could I ask 'what did we decide about X, and when?' — and trust the answer? If the answer is no, the resolution layer is missing. The fix is operational, not a vendor purchase. - Who would own the list of names, and who reviews changes? The clean facts registry needs an owner. Not a committee. Pick the person. - What's the one pile I could prove this on by Friday? Pick the smallest viable scope. One engagement, one inbox, one folder. Start there. ## FAQ **What is the core idea of The Resolution Layer — Why Your AI Gets Confused?** Before an AI can answer questions about your company, it has to know who and what you are talking about. Get that wrong, and every answer sounds confident — and can't be trusted. **What should a CEO do Monday morning after reading The Resolution Layer — Why Your AI Gets Confused?** Start here: Which pile of documents do I already feed to AI? Name the one workflow where you most rely on AI summaries today. That's the pile worth resolving first; When my AI tool is unsure, does it ask me — or quietly pick one? If you don't know, the answer is almost certainly the second one. Find out this week; Could I ask 'what did we decide about X, and when?' — and trust the answer? If the answer is no, the resolution layer is missing. The fix is operational, not a vendor purchase. **What are the steps in The Resolution Layer — Why Your AI Gets Confused?** 1) Same person, many names; 2) Lost track of 'he'; 3) Invented connections; 4) No two answers agree; 5) Old news stays current. **Where do the claims in The Resolution Layer — Why Your AI Gets Confused come from?** The playbook cites Internal workshop source material; Obsidian graph view reference; GraphRAG documentation. ## Sources - [Internal workshop source material](https://buildclub.com) - [Obsidian graph view reference](https://obsidian.md) - [GraphRAG documentation](https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/) --- Work with BuildClub: https://buildclub.com/company-brain