# Explore memory

Choose the memory view that matches the information you are looking for.

Source: https://docs.minds.sh/docs/workspace/memory



The memory area separates information by its role in a task. This makes it easier to distinguish an experience from a reusable routine, or a source from the context currently in use.

| View           | Look here for                                         | Instance reference                                   |
| -------------- | ----------------------------------------------------- | ---------------------------------------------------- |
| Episodic       | Events, decisions, observations, and outcomes         | [Episodic](/docs/api/instance/episodic-memory)       |
| Procedural     | Stored routines that describe how to perform a task   | [Procedural](/docs/api/instance/procedural-memory)   |
| Resource       | Source documents and their metadata                   | [Resources](/docs/api/instance/resource-memory)      |
| Vault          | Sensitive values handled through a separate interface | [Vault](/docs/api/instance/vault)                    |
| Working Memory | Context slots and attention for active work           | [Working memory](/docs/api/instance/working-memory)  |
| Associative    | Stored patterns and partial-pattern recall            | [Associative](/docs/api/instance/associative-memory) |

## Inspect before editing [#inspect-before-editing]

Select a ready Mind, open the appropriate memory view, and inspect an item. Check the identifier, source, timestamps, and scope before changing it. Similar-looking text can represent different events or sources.

For an application write, keep the returned identifier. Read the item again independently and use the memory-specific search operation to test whether it can be found in the intended way. A record appearing in one UI view does not prove it participates in every retrieval strategy.

## Choose what to retain [#choose-what-to-retain]

Store durable decisions and useful outcomes deliberately. Do not assume every chat turn should become a permanent memory. Keep transient task state in working context and attach source information where the schema supports it.

The current resource-chunk and vault access-log handlers have implementation gaps. An empty response there must not be interpreted as proof that no chunks or access events exist. [Coverage](/docs/api/instance/coverage).