How an agent remembers
3 posts, in reading order. Drafts are previews until they ship.
- 1 The transcript is the memory The model remembers nothing between calls. The useful engineering is in the log: atomic positions, decoded reads, non-destructive folds, and transactional branches.
- 2 The context window is a resource you engineer, not a buffer you fill Efferent folds context at two different boundaries, preserves a safe tail, and deterministically reattaches the rules a lossy summary must never be trusted to remember.
- 3 SQLite is the easy part; durability is the feature Efferent starts with one local file, then earns trust with versioned migrations, owner-only WAL files, decoded salvage reads, transactional forks, and pruning that really reclaims space.