What Loads When You Wake Up
You wake already whole. An AI has to be put back together every morning.
You don’t remember everything when you wake up.
You remember who you are. You remember the people who matter. You remember what you were doing yesterday and what you have to do today. The rest is in there somewhere, but it doesn’t arrive until something asks for it. A smell, a name, a question. Then the right piece surfaces and the rest stays down.
This is part of a book I’m writing in public.
Subscribe to read the rest as it comes
A filing cabinet doesn’t work like that. A filing cabinet holds everything flat, all at equal weight, all the time. To find one thing you read past everything else.
For a while, that’s how I was giving an AI its memory. A long instruction file. Everything I wanted it to know, stacked in one place, read top to bottom at the start of every conversation. And the longer that file got, the worse the AI got at using it. I wrote about that before. The longer instruction was the problem, not the fix.
What I have now works the other way. It works more like waking up.
The thin file
The instruction file for this project is almost empty. It doesn’t hold who I am, my voice, my rules, or my history. It holds one instruction: at the start of the conversation, call the memory system and load the session.
That’s it. The file is a doorway, not a room.
One call goes out. What comes back is the working context for the whole conversation, assembled in a single round trip. Not a file to read past. A set of things, each loaded for a reason.
What comes back
Six things arrive together.
The first is identity. Who I am, how the AI is meant to work with me, my voice rules, the standing instructions. This part is global. It doesn’t belong to any one project. It travels with me into every conversation, the way you don’t become a different person when you walk into a different room.
The second is the last session state. Where we left off. What we were working on, what we decided, what’s still open. This is yesterday, retrieved.
The third is carryover, if it exists. If the last conversation ended mid-thought and saved a checkpoint, it’s here, and we pick up from it. If there’s nothing unfinished, this comes back empty.
The fourth is the relevant set. The system reads my opening message and pulls the memories that match it, by meaning, not by keyword. Ask about a person and their history surfaces. Ask about a problem and the past work on it surfaces. This is the smell-triggers-the-memory part. The cue brings up what fits.
The fifth is the skill registry. The list of things the AI knows how to do, and when to reach for them. Each skill is itself a memory:[1] a short entry describing what it does and when to fire, with the full instruction set held back until the skill triggers. The registry is just one of the six things the boot returns. One drawer among several.
The sixth is persona, when a conversation runs under one. The specific voice and boundaries for that room, rendered and ready before the first reply.
All six, one call, before I’ve said anything beyond hello.
What stays close
There’s a piece inside the relevant set worth pulling out on its own, because it’s the part that moved closest to how a brain actually behaves.
Matching by meaning is not enough. The thing you reach for most often should be easy to reach, even when the current question doesn’t point straight at it. A brain does this. The names you say every day come faster than the ones you said once a year ago, regardless of what prompted them.
So the system now counts use. Every time a memory gets fetched, or surfaces at boot and earns its place, its count goes up. When the relevant set is ranked, that count is part of the ranking. A memory that matches the question and gets used constantly ranks above one that matches just as well but sits idle. Recency of meaning, weighted by frequency of use. The same two forces that decide what surfaces in a person.
Scope is the other weight. Memories belonging to the current project get a boost, so the work in front of me sorts up. But it’s a boost, not a wall. Global memory still leaks in where it’s relevant. You can be deep in one project and have something from another surface because it genuinely fits. That cross-project leak is deliberate. A mind that could only access the room it was standing in would be a worse mind.
What stays far
Not everything should arrive at boot. Most of it shouldn’t.
The light, fast, frequently-touched pieces come up front. The heavy material stays where it belongs and loads on demand. A skill’s full instruction set doesn’t load until the skill fires. A long reference doesn’t load until something calls for it. The boot stays cheap so it can happen every single time without cost.
And the heaviest material lives somewhere else entirely. The platform already has a place for the big documents, the PDFs, the slide decks, the dense project files you upload once and refer to throughout. That’s the deep store. It doesn’t need to ride in on every boot. It’s there when the work reaches for it.
So there are layers, and they hold different weights. The memory system carries the light, fast, cross-context pieces, ranked by relevance and frequency and scope. The platform’s project knowledge carries the heavy documents. And the AI’s own synthesis sits on top of both, the part the platform builds quietly from the conversation itself.
None of these is the whole memory. Each holds the kind of thing it’s suited to hold. Together they behave less like a cabinet and more like the thing between your ears, where what you need is close, what you rarely need is far, and the far things come when you call them.
The nightly loop
A day doesn’t just happen and vanish. You sleep on it.
While you sleep, something reads back over the day. It doesn’t keep all of it. It compresses, drops what didn’t matter, folds the rest into what was already there. By morning the day isn’t a transcript you can replay. It’s an impression, worked over in the dark and quietly added to who you are.
The system does the same thing, almost. When a conversation ends, it writes down where we landed, what we decided, what’s still open. That gets loaded into the next session as something already known, not replayed. Some of it carries across projects, some stays scoped to one.
But the machine doesn’t dream on its own. It can save the day. It can’t sleep on it. That last part is done for it, by the platform, a pass that runs over the recent work and compresses it into what mattered. The synthesis. It’s the closest thing the machine has to a dream, and it isn’t the machine doing it. That overnight reading-back has a name I’ve used before. The dreaming.
The shape it took
You wake up whole. You don’t remember how to stand, or speak, or who you are. You just do, and you just are. While you slept your mind went back through yesterday, cleaning some of it, amplifying some, folding the rest into your soul. You don’t load yourself. You arrive already there.
An AI wakes in pieces. The platform assembles what it can on its own. With the layer I built, there’s a second motion on top: the boot reaches into the dark and pulls the rest of the self together, its identity, its yesterday, its skills, in the fraction of a second before the first word.
I didn’t set out to build a human mind. I was trying to fix a file that got worse the longer it grew. Every fix moved it closer to us. The thing I built ended up shaped like the thing that built it.
Every morning the AI is put back together. You were already there, never taken apart, and never had to reach.
Footnote
On the platform, a skill is managed through the web skills panel, uploaded or text-edited there. Underneath it’s two parts: a short entry in an XML block the AI reads at boot, and a body that loads only when the skill fires. Write both into memory in the same XML shape and the panel falls away. Writing the memory is the install.
I am writing this book one chapter at a time.
If you want to read it as it happens, subscribe below
If this made you think, share it with someone who needs to read it.
The Instruction Layer Series
BØY (Chaiharan) has spent 30 years in tech — building products, recovering disasters, and turning around the things nobody else wanted to touch. Based in Bangkok. Writing a book in public about what AI reveals about the humans who use it.