Explore memory
Choose the memory view that matches the information you are looking for.
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 |
| Procedural | Stored routines that describe how to perform a task | Procedural |
| Resource | Source documents and their metadata | Resources |
| Vault | Sensitive values handled through a separate interface | Vault |
| Working Memory | Context slots and attention for active work | Working memory |
| Associative | Stored patterns and partial-pattern recall | Associative |
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
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.