Memory writing
Show why persistence is a policy decision, not a side effect.
This chapter should make slot-bank behavior tangible. Readers need to see when the model preserves prior structure, when it overwrites it, and why that choice changes the long-term behavior of the system.
- Merge writes reward continuity and preserve a stable memory scaffold.
- Replace writes privilege freshness and can sharply refresh a bank.
- The visual treatment should make those two policies feel unambiguously different.
Write policy
Memory can blend in, or it can overwrite.
Merge keeps the prior slot structure and mixes in the new signal.
Slot bank view
Context and long slots.
ctx_slots
long_slots
Merge / replace view
Blend the new signal into the existing bank
source
→
merge
→
slot bank
The goal is not to hide the decision; the goal is to make the write policy visibly different so readers can understand why some memory stays stable while other memory refreshes.
Why this matters
Slot banks are where continual learning becomes concrete.
If the bank writes are legible, the rest of the runtime story becomes legible too: token flow can show when the writes happen, and anytime inference can decide how long to keep iterating.