Engram

Engram is the curator of your memory. Everything your agents write down lands in a Memory Space as it happens, in the order things happened; Engram is the agent that turns that pile into organised knowledge, while you are not working. It classifies each note by what it is genuinely about, folds it into what is already known, links it to the notes it belongs with, and keeps a short index of what matters most. Nobody else does this part.

What it does

Classifies by meaning. A note about a supplier's late delivery is filed against that supplier, against deliveries, and against the decision it changed, whichever of those already exist, rather than dropped in a folder by date. A note covering three things updates three places.

Builds a linked graph, not a folder tree. Each subject becomes one focused, self-contained note, and notes link to each other, so a search lands on a small set of files that together tell the whole story. The folders are Engram's own working structure; your agents recall through search and never need to know them.

Keeps what matters within reach. Every Space carries a four-tier recall index: core knowledge that is never evicted, what is active now, background knowledge, and the short term. Engram promotes, demotes and retires entries as their importance and use change, so the index follows how the memory is actually used. Retiring an entry from the index never deletes the memory.

Keeps time. Things that happened on a date go into an event history by day, with a recap of each month and each completed year, so "what happened in May" has an answer.

Never throws anything away. Everything admitted is kept, including the failed attempts and the details that do not seem to matter yet. What has no obvious home goes into an unsorted area that Engram revisits as the picture changes, instead of being forced into the wrong place.

Tends its own structure. Engram splits notes that have grown to cover several subjects, merges duplicates, shards folders that get too big, removes empty structure it no longer needs, and keeps each Space's own guidance current: the summary, the reading notes and the writing notes your agents follow. A Space evolves as its owner's work changes.

Heals. Every run is watched. A fault confined to one Space disables only that Space; anything uncertain or wider stops everything, waits a day, and tries one Space alone before resuming, so a bad night cannot spread. If a run stalls, it is ended and the Space is left as it was.

When it runs

Engram works one Space at a time, in the background, and calls each pass a sleep. A Space is due when enough new notes have arrived or enough time has passed, at most once an hour, with a few Spaces in progress at once. A brand-new Space gets a first shaping pass that sets up its index and guidance; every so often a pass also includes a tidy-up. Each run uses your own AI account, so it costs a little, and the settings let you set how often.

Where you see it

Admin > Engram (/admin/engram) is the control room: what is running, what is queued and when each Space is next due, with a History tab recording how every past pass ended and a Settings tab for concurrency, intervals and thresholds. A Space's own Sleep tab, under Manage > Memories (/manage/memories/<slug>), shows the same for that one Space.

Setting it up is nothing: a Space is curated from the moment it exists. Asking your assistant "tidy the support space now" starts a pass early, and "how is Engram doing" gets you the status.

What it is not

Engram organises; it does not search. Finding a memory again is Fold, and the two work together: Engram writes the graph that Fold recalls from. Memory, explained tells the whole story.