Memory

"Halton pay on 45 days, remember that." The note is written down while you are still talking and appears on the Memories page straight away. Three weeks later, in a different chat, "what terms are Halton on?" finds it.

A Memory Space is where an agent writes down what it has learnt: a named collection of notes with a stated purpose, an audience and its own guidance on what belongs in it. The notes are ordinary files you can open, edit and delete, and each Space is indexed so that a question phrased nothing like the note still finds it.

Who has one

Every agent has a Space of its own, and it follows that agent into every project. Beyond that you create shared ones for anything worth keeping in a single place: your suppliers, a team's runbooks, everything known about one important customer, the answers a support bot gives.

Each Space is internal or public. Internal means you and your agents. Public means a customer or a bot answering them may read it, so nothing confidential belongs in one.

What people keep in them

You are never asked to pick a template or design folders. You say what you want remembered and who may read it, and the shape follows the material that arrives. The purposes people recognise:

• A personal notebook: contacts, preferences, what you are working on.
• A team wiki: runbooks, decisions, policies, how you do things here.
• A support knowledge base: the answers a public bot gives customers.
• A document archive: files kept whole and searchable by meaning.
• A profile of one subject: everything about a single customer, supplier or product, with dated interactions.
• An agent's own memory: what a specialist has learnt doing its job, whether that job is research, support or code.

The Memories page

Manage > Memories (/manage/memories) lists every Space you can see as a card, narrowed to the project selected at the top of the screen. Three counts sit above them, total, internal and public; pills filter the list to All, Internal or Public; and the search box in the top bar filters it as you type.

New starts the short conversation that creates a Space. Rescan re-reads the folders when the page and the files look out of step. Trash holds removed Spaces, so deleting one is recoverable.

Removing a Space asks two questions rather than one. The Space itself goes to Trash and can be brought back. Its search index is separate, and the dialog asks whether that goes too, saying how many memories are in it and leaving the box unticked: deleting the index cannot be undone, even if you restore the Space from Trash afterwards. The confirm button names whatever your answers add up to, so nothing is deleted by a click that said something vaguer.

Opening one (/manage/memories/<slug>) gives eight tabs.

• Readme is what the Space is and what it is for. Its first heading is the title you see everywhere else.
• Read says what belongs in it and when recalling from it is likely to help.
• Write says what a note must contain to be worth finding again.
• Files browses the content: notes waiting to be filed, source documents kept whole, the settled write-ups by subject and a dated history. You can hand-edit or delete any of it here.
• Fold (/manage/memories/<slug>/fold) is the Space's index: whether it is healthy, what is in it, any file it saw but skipped and why, what indexing has cost, and a search of just this Space whose results link to the file and line.
• Access sets the audience and who owns the Space.
• Sleep shows how many notes are waiting, when the last tidy-up ran, the schedule and the thresholds, and can start a pass.
• Projects connects a shared Space to a project as Use as knowledge or Use and update.

Fold and Engram

Both have pages of their own: Fold recalls, Engram organises.

Two pages sit behind all your Spaces at once.

Admin > Fold (/admin/fold) is every index in one list, whatever project you are in: health, what is indexed, file and memory counts, what it has cost, and controls to pause, resume or re-index. Pausing stops background indexing but not searching, so a pause is not the same as spending nothing.

Admin > Engram (/admin/engram) is the tidying. It shows what is running, what is queued and each Space's schedule, with a History tab recording how every past pass ended and a Settings tab for how often it runs and for the controls that bring it back if it has stopped itself.

What you would come here to do

Most weeks, nothing. The reasons to open these pages:

• Read what it knows. A Space's Files tab is the whole of it, in plain files.
• Correct a wrong note. Edit or delete it by hand on that same tab. It takes seconds and saves an argument later.
• Check something was indexed. The Space's Fold tab says so, and Index changes picks up anything new. A full re-index is a separate, confirmed action, because it can be expensive.
• Pause the indexing, one index or all of them, from the Fold page.
• Change when tidying happens, or turn it off for a Space you keep by hand, on that Space's Sleep tab.

Why memory is built this way is Memory, explained. The same ground through examples is It remembers, filling a new Space is Build a knowledge base, and where memory sits beside your working files is Workspaces and files.