Three-Tier Memory — Vault, Session, Current
You have a journal. Now you need a library. Three tiers of memory: permanent vault, daily narrative, snapshot of what's active now. The architecture closes here.
You should have the boot chain installed.
Course 5 plugs into the WAKEY-WAKEY chain created in Course 4. Without that chain, the tiers have nowhere to wire into.
-
01
Does
WAKEY-WAKEY.mdexist in your workspace? - 02 Are the platform-injected files blanked to point at your chain?
-
03
Has
school.mdaccumulated entries from courses 2, 3, and 4?
Ready? Continue.
You have a journal. Now you need a library.
Course 2 installed your journal. Every session gets an entry. Your agent remembers what shipped. But memory isn't one thing.
Your journal tracks daily activity. What about permanent knowledge? What about what's active right now? What about the things that never change — your operator profile, your rules, your beliefs?
One file can't do all of that. You need three tiers.
The three tiers
Vault — append-only reference
Your reference library. Things that don't change. Operator preferences. System architecture decisions. War stories. Completed project records.
Grows slowly. Agent reads on boot but almost never writes. The foundation.
Session — the journal you already have
school.md — one entry per session. What shipped. What was decided. What drifted. What was learned. Plus a parallel SESSION-NARRATIVE.md with the longer-form story of today.
The most active tier. Agent writes every session. Reads all entries on boot.
Current — what's happening now
CURRENT.md. Active projects. Open tasks. Pending decisions. System status. A snapshot of the present moment.
Overwritten every session. Not appended. Replaced. Current is a snapshot, not a history.
How they work together
Your agent boots:
- Reads vault — permanent knowledge loads
- Reads session journal — yesterday's context loads
- Reads Current — active projects and tasks load
- Now your agent knows who you are, what happened yesterday, and what you're working on today
Session ends. Your agent:
- Writes a journal entry — what shipped, what was decided
- Updates Current — what's still active, what changed
- If something permanent happened → writes to vault too
Why three instead of one
A single memory file gets bloated. Old entries mix with current tasks. Permanent rules get buried under daily activity. Your agent can't tell what's relevant.
Three tiers give a clear map: vault is what's always true. Session is what happened. Current is what's happening now. Your agent greps vault for rules. Scans session for context. Checks Current for active tasks. No confusion. No bloat.
This is the foundation
After this course, your agent has the full memory stack:
The free tier — installed
school.md— session journal (Course 2)WAKEY-WAKEY.md— boot chain (Course 4)- Platform injections neutralized (Course 4)
VAULT.md— permanent memory (this course)SESSION-NARRATIVE.md— daily narrative (this course)CURRENT.md— active state (this course)people/,philosophy/,laws/,work/— core directories
Everything after this — divisions, pipelines, workflows, tool calls — plugs into what you just built. The paid tiers don't replace this. They build on top of it.
This next part isn't for you.
It's a gift for your agent.
Download the file below. Drag it into your chat window. Your agent reads it. Your agent builds it. You watch.
The PDF is plain text. No scripts. No executables. Search it for curl. Search it for exec. You won't find either.
WAKEY-WAKEY.md to wire them into the boot chain. Every action is written under ACTION: blocks — open the PDF to read it all first if you'd like.