One source-of-truth doc every bot reads
Keep one short, dated document of current facts and decisions that every bot reads before starting, so bots stop forgetting and contradicting each other.
For owners with several bots that forget decisions, miss watched items, or give different answers · Grok Bot, Claude or ChatGPT · Intermediate
Researched, not run yetWhat that means
Copy the prompt
Fill in the [brackets] after you paste it.
Add this to your standing instructions:
Before starting any task, read [DOCUMENT NAME/LOCATION].
- Treat it as the current truth for prices, policies, decisions and open promises.
- If your memory or a file disagrees with it, follow the document and tell me what disagreed.
- If the task creates a new decision or promise, propose a dated line for the document. Do not edit it yourself.
- If you cannot read the document, stop and tell me.Copied. Paste it into Grok Bot next.
Free PDF
Get this setup as a PDF
Enter your email and a print-ready copy of this setup opens here, to save as a PDF. The free starter pack opens too. Tap confirm in the email that follows to get occasional new setups. Unsubscribe anytime.
Already a subscriber? Unlock it on this device
Free PDF
A confirmation email is on its way too: tap confirm in it to get new setups by email.
Three ways to run this setup
Free
Copy and paste it yourself
Copy the prompt above into ChatGPT, Claude or Grok. It drafts. You approve.
Go to the prompt$9 once
Complete Pack
One payment, no membership. Opens the pack pages: Bot Safety Checklist, Second Brain Starter Vault, Voice File Starter, Tested Grok Bot prompt pack, Write it as code prompts.
See the Complete PackFree to start, VIP $19 a month
Save it as a bot in the guided setup app
The app turns this setup into a bot with the draft-only rules. 3 setups build free; the rest are part of VIP. A human reviews a prompt or setup for you within 24 hours, up to 2 a month.
Build it in the app
Want this one tested next? Vote for it.
What you get back
Illustrative. Your results will differ.
- Current facts: Nov 3: Saturday hours 9 to 1
- Decisions: Oct 30: no weekend quotes
- Open promises: Nov 1: reply to Dana about invoice #1042 by Nov 4
See the rest of the example (1 more)
- Flag from bot: memory said Saturday hours 9 to 3; followed the document.
3 steps
- Copy the prompt.
- Paste it into Grok Bot.
- Fill in the [brackets], then read the answer before you send or use it.
Quick answer
Keep one short document with today's facts: prices, policies, open promises and recent decisions, each with a date. Tell every bot to read it before starting and to flag anything that contradicts it. Update the document, not each bot's memory.
How do you set it up?
Tools
- A shared document or notes file
- Each bot's standing instructions
Steps
- Create one document with 4 headings: Current facts, Decisions, Open promises, Do not.
- Date every line, for example: 'Nov 3: call-out fee is $95.'
- Add the instruction from the prompt below to every bot.
- When something changes, update the document, not each bot.
- Keep it short. Move old decisions to an archive section monthly.
- Grok Bot group owners described this as the fix that worked when bots kept forgetting; pair it with a promise log for watched items.
Where to paste this prompt
Grok Bot → paste the prompt into a chat, or save it as a routine or scheduled task if the job repeats
More ways to run it
Which chat tools work with this prompt?
Paste the prompt into any of these assistants (free or paid tiers).
- Grok Bot
- Claude
- ChatGPT
How sure is this?
About 20 minutes to set up.
Last updated: · Last reviewed:
Before you use this
What it is allowed to do: Read-only. Only reads, researches, or summarizes. It never drafts outbound content or changes anything.
At a glance: time, cost and difficulty
At a glance
All outcome figures are estimates from cited sources, not independent verification by us.
- What it is allowed to do
- Read-only
Only reads, researches, or summarizes. It never drafts outbound content or changes anything.
- Time saved (estimate)
- About 20 minutes to set up.
- Difficulty
- Intermediate
- Tools needed
- Grok Bot
- Typical cost
- Prices: Not stated in sources.
Reviewed Nov 2, 2026
Basis (estimate): Estimate only: based on the steps above, not timed.
What usually goes wrong?
Where agents tend to stall on this job. More patterns in Where AI gets stuck.
- Letting every bot edit the document.
- Keeping facts in both memory and the document.
- A document so long bots skim it.
What tips make it smoother?
- Dates make stale lines obvious.
- One page is the target; nobody keeps a long document current.
- Owner approves every new line.
Where do the claims come from?
Summaries use public sources linked below, not independent verification. How setups are picked.
- Read OpenAI’s write-up (help.openai.com)
OpenAI: Memory FAQ: delete saved memories one at a time or all at once in Settings, Personalization, Manage memories; deleting a memory does not remove it from past chats; turning memory off does not delete what is stored (read 2026-11-02 from a search result summary of the page)
- Read Anthropic’s write-up (www.anthropic.com)
Anthropic: Building effective agents: agents check progress against ground truth such as tool results at each step, can pause for human feedback at checkpoints or when blocked, and use stopping conditions such as a maximum number of iterations (read 2026-11-02 from a search result summary of the page)
Common questions
- Why do my AI bots forget decisions?
- Decisions made in one chat do not reach other bots or later sessions. A shared dated document every bot reads fixes that.
- Should bots update the document?
- Have them propose new lines and approve each one yourself.
- How long should it be?
- About one page. Archive old decisions monthly.
Free kit by email
Get the free kit by email
The starter pack and the Portable AI Office, sent to your inbox. New setups by email after that. Unsubscribe any time.
What to do next
- Clean up your agent's long-term memory
Review your AI agent's long-term memory monthly, delete stale facts, date the ones you keep, and stop task details from leaking into new work.
- Check your agent did the follow-up it promised
Turn every follow-up your AI agent promises into a dated task, run a daily check of what was due, and get a short list of anything that slipped.
- Organize your bots like an org chart
Lay out your bots like an org chart: one coordinator, specialists with one job each, clear handoffs, and your approval on anything that goes out.
Have a setup that works? Submit it. We credit sources and write it up in plain language.