Make your Grok Bots verify changing facts instead of trusting memory
Overview
Michael Fenech's prompt for anyone running several Grok Bots that answer from memory. It has the bots list the facts they rely on that can change, such as dates, prices and balances, and name where each should be checked. Memories of those facts are swapped for pointers to the source, every bot gets a rule to check before acting, and three bots are tested afterwards. You approve one bot's changes before the rest, and permissions to send, buy or publish stay as they are.
Use cases
Prompt
Copied 0
Help me roll out a ‘check the source, don’t trust memory’ rule for facts that can change. Keep existing permissions for sending, buying and publishing unchanged. 1 - Map the sources. For each Bot, identify the changing facts it relies on: dates, prices, statuses, contact details, balances and order information. Name the authoritative source for each, such as Calendar, email, Notion or a database. Verify access rather than assuming it. Flag missing, unreachable or conflicting sources. 2 - Change what gets remembered. Help each Bot review its own memory. Keep stable preferences and standing rules. For changing facts, store where to check the current value. Example: replace ‘the next review is 24 October’ with ‘check Google Calendar for the next review date.’ Preserve useful historical facts as dated history. Show me proposed changes for one Bot first and wait for approval before applying them or expanding to the others. 3 - Add the source-checking rule. Prepare this instruction for each Bot: ‘Before stating or acting on a fact that can change, check its authoritative source. Say where you checked and when. If I correct you, re-check before answering again. If you can’t reach the source, say so. Label any remembered value as historical and unverified. Don’t take an action that depends on it being current.’ Have each Bot apply its own approved changes. Where that isn’t possible, give me the exact instruction to add manually. 4 - Avoid unnecessary checking. Use memory for stable preferences and rules. Reuse a source check within the same task unless the information may have changed or an important action needs a fresh check. 5 - Test the behaviour. Pick three Bots and ask each a question about a changing fact it previously answered from memory. Report whether it checked the source, what it found and whether the remembered answer differed. If you can’t establish a difference, say so. Return the source map, approved changes made, access gaps and test results.
Can AI?
- Make your Grok Bots verify changing facts instead of trusting memoryPaste into a general LLM and make your Grok Bots verify changing facts instead of trusting memory.