# Memory types (/docs/memory/memory-types)
A memory carries three kinds of type. You choose one, Docklee assigns one, and recall reports one. Each answers a different question.

| Type | Set by | Answers | Where you see it |
| --- | --- | --- | --- |
| Capture type | You, with `type` | Where should this event go? | The request |
| Memory type | Docklee | What kind of memory is this? | The dashboard |
| Storage class | Docklee | How is this record stored? | `memory_type` in recall results |

## Capture type [#capture-type]

The `type` you pass to `capture` tells Docklee what you're sending. When a `Dock` declares both a container and a memory space, the type decides where each event goes.

| Type | Use it for | Goes to |
| --- | --- | --- |
| `conversation` | Messages and turns from a chat or call. This is the default. | Memory space |
| `event` | Something that happened, such as a renewal or a ticket. | Memory space |
| `preference` | How a person likes things done. | Memory space |
| `entity` | A person, company, or product your app tracks. | Memory space |
| `document` | Longer written content. | Container |
| `knowledge` | Reference facts for an engine. | Container |

<CodeTabs items={['Python', 'TypeScript']}>
  <Tab value="Python">
    ```python
    dock.capture("Maya prefers email.", type="preference")
    dock.capture("Maya works at Northwind.", type="entity")
    dock.capture("Maya renewed her plan.", type="event")
    ```
  </Tab>
  <Tab value="TypeScript">
    ```ts
    dock.capture('Maya prefers email.', { type: 'preference' });
    dock.capture('Maya works at Northwind.', { type: 'entity' });
    dock.capture('Maya renewed her plan.', { type: 'event' });
    ```
  </Tab>
</CodeTabs>

## Memory type [#memory-type]

Docklee reads every memory and assigns a type that describes it. Types aren't a fixed list, so a memory gets the label that fits it best.

| Common types | Example |
| --- | --- |
| Fact | "Northwind has 40 seats." |
| Preference | "Maya prefers email." |
| Event | "Maya renewed her plan." |
| Decision | "We chose the annual plan." |
| Policy | "Refunds need manager approval over $500." |
| Relationship | "Maya reports to Omar." |

The memory type drives how Docklee treats a memory. Policies and decisions are kept in full detail. Events are the first to be summarized when they grow old. See [Consolidation](/docs/memory/intelligence/consolidation).

## Storage class [#storage-class]

Recall results carry a `memory_type` field (`memoryType` in TypeScript). It's the storage class of the record, not the memory type above.

Memories written through `Dock` have the storage class `entity`. The other storage classes are `episodic`, `document`, `system`, and `derived`.

<Callout type="info">
Rank and filter recall results by `confidence`, not by `memory_type`. Most memories you write through `Dock` share the same storage class.
</Callout>

## Next steps [#next-steps]

You know how types work. Attach your own data to memories next.

<Cards>
  <Card title="Metadata" href="/docs/memory/essentials/metadata" description="Store your own keys alongside a memory." />
  <Card title="Consolidation" href="/docs/memory/intelligence/consolidation" description="Which types are summarized, and which never are." />
  <Card title="Capture memory" href="/docs/memory/capture-memory" description="Every capture option." />
</Cards>
