Notes · 11 June 2026
Why Claude forgets your business, and what to do about it.
Claude is impressive for a week. It drafts well, summarises well, plans well. Then a pattern sets in: every morning you are explaining your business to it again. Who your suppliers are. What your returns policy actually says. How you sign off an email. The model is brilliant. The details that run the business still come from you, every time.
This is not a flaw you can prompt your way around, and it is not quite a missing feature either. Claude now has a built-in memory, on by default: it keeps its own categorised notes on your conversations and carries them into new chats. The notes are real. They are also not how a business runs. Memory holds roughly what you do; it does not hold the returns window, the supplier's payment terms, the exception you agreed in March or the way you sign off an email. A business runs on structure: policies, processes, exceptions, history. Structure does not survive being noted in passing.
The fix is structural, not clever prompting
Give Claude the same thing you would give a new employee: not a longer induction speech every morning, but documents. A written, structured account of how the business works, kept where Claude is set up to read it before every piece of work. The discipline is called context engineering, and the shape that works looks like this:
- A workspace constitution. The standing rules: what the business is, what Claude may and may not do, who approves what. The employee handbook, except it is read before every task.
- Canonical context files. One per part of the business that matters: customers, suppliers, products, how you price, how you write. Facts, stated once, kept current.
- A decision log. What was decided, when, and why, so decisions stay made instead of being relitigated every fortnight.
- A memory layer. What Claude learns as it works for you, written down rather than lost when the conversation closes.
- A maintenance schedule. A small recurring habit that keeps all of it true. Stale context is worse than no context, because it is wrong with confidence.
What changes when it exists
The morning re-explanation disappears. Drafts come back in your tone. The supplier exception you mentioned in March is still known in June. And none of this asks you to trust the machine further than you want to: the same files that give Claude its knowledge also set its limits, including the approval gates that keep every consequential action waiting for you.
The platform is moving quickly. Models change, tools ship monthly, and the durable part is exactly this layer: models will keep improving, and the context architecture carries forward. It is the part you own.
Building it
If you want to build it yourself, the free Clarion Context Kit is the folder structure we use, with templates and instructions; request it on the homepage and it arrives by email. If you would rather build it with someone, the 60-minute Setup Session installs Claude and writes your first context file inside the hour.
Daniel · The Clarion