Six kinds of memory
Store each kind of context in a form that matches how it will be used.
A transcript, a reusable procedure, and the context for a task are not the same thing. Minds separates these roles so an application can retain useful information without treating every input as an interchangeable text chunk.
Episodic: what happened
An episode records an experience: an observation, decision, action, or outcome. Use it when the order and circumstances matter. A support assistant might record that a customer tried a fix and whether it worked.
Procedural: how to do it
A procedure represents a reusable routine. Use it for a sequence that should be available again, such as a troubleshooting process. A stored procedure is not proof that the system has successfully executed it in every environment; retain the context and outcomes that support reuse.
Resource: the material behind the work
Resource memory represents source material and its metadata. Use it to keep the document behind an answer, rather than only its summary. Chunk retrieval is an incomplete handler in the current source; consult the endpoint notes before designing ingestion around it.
Vault: sensitive values
Vault has a separate interface for sensitive entries. Access policy still matters: do not place secrets in ordinary chat, logs, or public examples. The current vault access-log handler returns a placeholder empty response, so it cannot provide a verified audit trail yet.
Working: what the current task needs
Working memory manages active context and attention. Think of the information on the desk while a task is underway, rather than the whole archive. Configuration operations can require internal operator authority even when ordinary memory reads are permitted.
Associative: recognize a pattern
Associative memory stores patterns and recalls related content from a partial cue. It supports a different retrieval mechanism from fetching a known record ID. Its input representation and dimensions must match the specific operation you are calling.
Combine them deliberately
A customer interaction can become an episode. The source document can remain a resource. A reliable resolution can inform a procedure. The current conversation uses working context. Your application decides how those writes and links happen; storage in one category does not automatically populate every other category.