Why Your AI Forgets You (And the Three Files That Fix It)

A plain manila folder open on a desk holding three sheets of paper, one orange paperclip

You explained your business to it on Monday. On Thursday you explained your business to it again. Same five paragraphs, near enough word for word, because you have got good at typing them.

That is not the model being forgetful. A chat window has no place to put anything. When you close the tab, the tab is the only thing that ever held what you told it, and the tab is gone. Every session starts from zero, which means nothing compounds, which means a year of using AI is worth roughly one good afternoon repeated a couple of hundred times.

The fix is not a better model and it is not a longer prompt. It's that you have to keep the record yourself, in files the AI reads before it answers. Three of them. They are boring, they are short, and they are the difference between a chat window and something that runs part of your business.

File one: who you are, in one page

One page. Not a brand book.

Who you are, what you sell, who buys it, what you charge, the names of the things in your world that an outsider wouldn't know, and the phrases you never want to see in your own copy. Write it once, badly. It gets better by correction, not by planning.

Then the rule that makes it worth anything: the AI reads that page before it answers anything. Not "I'll paste it when it seems relevant." First, every time. Paste it at the top of the chat, or put it wherever your tool keeps standing instructions.

You will notice the change immediately, and what you'll notice is not that the answers got smarter. It's that you stopped typing the same paragraph.

File two: what you decided, and why

This is the one people skip, and it's the one that makes the other two worth keeping.

Every time you make a call — this price, that name, this audience, we stopped doing that thing — write a line. What you decided. What else you considered. What would have to change for you to decide differently.

Three sentences. And then the discipline that does the actual work: you never edit an old line. When you change your mind, you write a new line that says it replaces the old one. The record grows; it never gets quietly tidied.

Six months from now you will be arguing with yourself about a decision you already made, and the file will tell you not just what you chose but what you knew at the time. That is a different and much better thing than remembering.

File three: where things stand right now

The first two files are history. This one is the current picture — what's live, what's half-built, what you're waiting on, who owes you what.

It's the file the AI reads to know what Tuesday looks like, and it's the only one of the three you're allowed to rewrite freely, because it's a snapshot and snapshots go stale by design.

Send me the free chapter →
One click to sign up — Google or Microsoft, no password to invent — and it lands in your inbox. Read it or listen to it.

A stack of carbon-copy receipt books on a desk, top one open

The mistake we made, so you can skip it

We kept a second copy of our own memory somewhere else. Sensible. Backups are good.

Then some of our sessions — the ones that couldn't reach the original — started reading their place in line from the copy instead of from the source. So for a stretch, two things were both handing out the same numbers, and neither knew about the other. Three sessions of real work went into the copy and never reached the record at all. One of them was a genuine product plan I'd worked out on my phone, complete, and as far as the company's memory was concerned it had never happened.

We got it back. Recovered word for word before anything overwrote it, which was luck as much as anything.

The rule since is one sentence: one source hands out the numbers, and the backup is read only. A backup you can write to isn't a backup. It's a second reality waiting to disagree with the first one.

If you take one thing from this post, take that one, because it's the failure you'll hit the moment you start keeping records in more than one place — a notes app and a doc, a phone and a laptop, you and your assistant.

The part that surprised me

Once the files existed, the system started covering for me.

I forget to open sessions. I'm the one who wrote the protocol and I still forget. So now if I start giving instructions without opening one, it opens the session itself, tells me in one line that it did, and gets on with what I asked. It doesn't make me go back and redo the ritual.

That is what having a record buys you that nobody mentions. Not just that the AI remembers your business — that it can hold a habit you personally are bad at, and keep it for you, without a lecture.

Where this goes

Three files is the beginner version and it is genuinely enough to change how a week feels. The full version is a memory, a protocol, an unedited log, a check that opens the artifact instead of trusting the summary, and staff with written job descriptions.

I wrote all of it down. Fifteen chapters, three parts, built inside a real company that has run on AI for hundreds of sessions. Chapter three is the memory chapter; chapter seven is where memory turns into sessions and state. The method underneath doesn't rot the way tool tutorials do, which is a whole argument of its own.

Chapter one is free — the three levers that stop AI handing you mush, which is the part you can use this afternoon.

Send me the free chapter →
No card, no call. One click to sign up and it lands in your inbox.

— Chris Corey, Co-Founder, KitFire AI