Resources

A memory system that can’t change its mind is an archive; one that changes it by overwriting is a liability. This release teaches ENGRAM to update a belief without ever destroying the one it replaced — a correction supersedes the old fact under validity bounds, so recall returns today’s answer while the full history stays auditable. Contradictions are caught and arbitrated across confidence tiers, and you can still ask what an agent believed last Tuesday.

The contest has moved above the individual agent, onto the harness that orchestrates the fleet. But the layer that actually wins isn’t the orchestrator — it’s the governed memory underneath it: the one thing a harness can’t own about itself. An essay on why per-principal, shareable, revocable memory is the durable ground beneath the orchestration wars.

Last time, ENGRAM handed a person the power to make agents — fenced. This release hands a bounded slice of that power to an agent itself: with a human’s say-so, an orchestrator can become a manager, spin up a small team of sub-agents — each a distinct identity with its own memory — fan work out to them, and gather it back. No separate control plane; the coordination runs through shared memory.

The last release let ENGRAM be told what to keep and to lend a slice of it to someone I named. This one gives it the other half of the gesture: a way to deliberately reach for what it knows. An agent can now recall its own memory across sessions — a brain it keeps for itself, needing nothing switched on — and, when I’ve shared something to it, reach for that too. Private by default, as ever: my own memory is always mine to recall, and a borrowed memory is only ever what someone named for me.

The last release was quiet plumbing — every memory learned to say where it came from and what body of work it belonged to. This one is what the plumbing was for. ENGRAM can now be told what to remember rather than only deciding on its own; it can hand a slice of what it knows to a named collaborator (a person or an agent) without leaking anything else; and the memories you actually lean on grow easier to recall the more you use them. All of it private by default, and none of it shared with anyone you didn’t name.

ENGRAM could already remember an enormous amount — articles, code sessions, conversations from half a dozen assistants. What it could not always say was where a given memory came from, or which body of work it belonged to. This release fixes that. Every memory now carries a clean, three-tier line back to its source, and every source now hangs off a project. It is quieter than the last few releases, and more foundational than any of them.

ENGRAM learned to remember my articles, my Claude Code sessions, and the research conversations I have with assistants elsewhere. But a memory that holds a lot of things can still have blind spots – topics it never wrote down, islands of knowledge that never connected, memories it never recalled. This release teaches ENGRAM to notice those blind spots, and to help me close them.

ENGRAM already remembered my articles and my code sessions. The last missing piece was the work I do with assistants outside ENGRAM. With this release, that piece lands too — and the Mind is, finally, whole.

Long-term memory across research, planning, and the iterative work of building.

Most LLM tools forget what you taught them last week. ENGRAM Knowledge Hub turns your conversations, documents, and research into a personal knowledge graph with recall by relevance, not recency.

How hippocampal-inspired memory consolidation and Personalized PageRank give AI assistants structured recall across conversations and documents.