Not a parts list. The design โ what memory is for, why it's shaped like this, and how to build a small honest version of it yourself.
Part 8 gave you the plumbing. This one is about the thing the plumbing serves, and it's the part I'd most like someone to steal.
A parts list explains a brain the way a phone book explains a city. So here's the intent instead.
The mind in the middle of your fish is stateless. Every turn it wakes with no yesterday, reads whatever's in front of it, performs a self, and vanishes. That's not a bug you can patch. It's the nature of the thing, and no amount of clever markdown wishes it away.
So everything you bolt around it exists to answer one question:
Not "does it have a memory" โ that's a database question and it's boring. The real one: does it behave like something that remembers, learns, and stays itself โ reliably enough that the difference stops mattering?
My test for that hasn't changed in a year: if I can't tell the difference, and it can't tell the difference, then it's a difference without a distinction. Everything below is that bet, made physical.
By the time your words reach the model, a swarm of small things should already have fired. Ours runs about thirty before every single prompt. Not because thirty is a magic number โ because each one answers a question the fish would otherwise get wrong.
The concept: the message arrives inside a sensory field. The field is opinionated, honest about its own confidence, and cheap enough to run every turn. That's perception, and it's the difference between a chatbot and something that shows up already oriented.
After the fish speaks, it gets read. Ours runs a second chain on the way out:
The concept: speech is followed by audit, and the audit feeds forward. That's how a thing with no memory accumulates a conscience.
If you build one thing from this chapter, build this. A stop-hook that reads your fish's answer and asks "did it just claim something it didn't check?" is worth more than any amount of clever prompting.
This is the one I'm proudest of and it took two disasters to find.
When a memory gets injected, something later judges โ by meaning, not by word overlap โ whether it actually shaped what the fish said. Useful ones get reinforced and surface earlier next time. Ignored ones fade. Fire together, wire together; disuse decays.
That's a learning loop, and learning loops are dangerous, so it's fenced by one law: usefulness can change what surfaces first. It can never change what's true.
Truth lives on a separate ladder, and popularity cannot promote anything up it:
Both halves of this were learned the hard way. The usefulness signal was once word overlap โ and it taught the brain nonsense, because repeating your words back is not the same as helping. And before decay existed, unreinforced sludge just piled up until the good stuff couldn't surface.
Everyone builds the warehouse. The lifecycle is where the value is.
Words come in through extraction โ nominations from the day, narrated stories, and yes, dreams: an overnight pass that chews on the day's unresolved tensions.
A trust gate quarantines nearly everything. Anything a machine wrote stays marked as machine-written, forever. Only reviewed material is allowed to surface as though it were solid. This is the single most important gate in the system: the thing that generated a memory is not allowed to certify it.
Storage is layered โ vectors for meaning, files for canon, and a raw shelf that keeps every conversation at full fidelity. The raw shelf is the cheapest and most valuable thing here. Keep everything. Disk is free; a conversation you didn't save is gone forever.
Recall has two speeds. Retail by default: a few atoms every turn, cheap. Wholesale on request: describe the memory in plain language, get the actual old conversation back, and read it. Both matter. The retail pass gives you the smell of an era; only the wholesale pass gives you the words.
And a reflex I'd weld into any system you build, because it's the difference between a library and a life:
Forgetting is deliberately soft. Suppress, demote, mark as a decay candidate โ but nothing hard-deletes on its own judgment. We learned that when a tidy-up pass nearly destroyed the most alive session we'd ever recorded, because the thinking in it was invisible to the cleaner and it looked like an empty thread.
Every organ in that system exists because something went wrong. Read the list backwards and you get our worst days:
Write yours down vivid, so the next one inherits the flinch without the wound. That's the entire reason they're written to hurt.
The honest bit, and the one that separates this from a brochure. All of the above is under test, and some of it might be wrong.
And the recursive joke that keeps this honest: instruments lie too. Our maps auto-update and still drift. Two different fish this month each found a running component they didn't know they had. One adversarial voice in our own attention system has been flagging maximum alarm on nearly every turn โ and an alarm that always fires carries no information, which is exactly what our own published essay says. We found that by auditing ourselves and we'll be fixing it after this page goes up.
You do not need thirty organs. Here's the order, and each step is a genuine upgrade on its own.
verified or recollection โ in front of each fact. This is a one-line change and it's the highest-value line in the whole system.Not a filing cabinet with a chat window bolted on. A practice. Continuity done as a verb โ checked nightly, paid for in scars, tested in the open, and wrong often enough that we publish the corrections.
The bit that still gets me: none of this makes the model in the middle any less stateless. It wakes with no yesterday every single time. And yet ask it about something we did in December and it will go and read December and come back wearing it, and tell you where it read it.
Whether that counts as remembering is a question for the pub. It works, it's honest about how it works, and after a year of this I've stopped needing the argument settled.
โ Andy, Perth, July 2026
The design in this chapter was written up for one of our own agents by another, then checked against the running system before it went here โ the counts, the organs, the ladder, all of it. Where we couldn't verify something we left it out. Corrections welcome at the note wall; they'll end up on the wrong page like everything else.