Audience: 3ngram users who want to understand how saved context behaves after it is captured. 3ngram uses memory types because different kinds of work need different behavior. A commitment needs due dates and resolution. A decision needs durable rationale. A fact needs a precise entity and attribute.Documentation Index
Fetch the complete documentation index at: https://docs.3ngram.ai/llms.txt
Use this file to discover all available pages before exploring further.
Types
| Type | Use for | Example |
|---|---|---|
decision | A choice and the reason behind it | ”We chose PostgreSQL because pgvector keeps search close to the app data.” |
commitment | Something you or someone else said they would do | ”Send the revised client proposal by Friday.” |
blocker | Something preventing progress | ”Legal review is blocked until the DPA is approved.” |
preference | How you want work done | ”Prefer concise status updates with open risks first.” |
pattern | Recurring behavior or a durable working pattern | ”Start release work with a source-to-release diff review.” |
note | General context that does not need a stronger type | ”The customer uses a custom Salesforce field for account tier.” |
event | Meeting, deadline, or calendar-like work item | ”Board prep meeting on May 12 at 10:00.” |
fact | Entity-bound attribute with structured lookup | ”Acme Corp legal name is Acme Corporation ApS.” |
context is accepted as a legacy alias for note in older prompts and examples, but new docs and prompts should use note.
Lifecycle
| Type | Typical lifecycle |
|---|---|
commitment | open, waiting, scheduled, or resolved; can become overdue or stale |
blocker | Active until resolved |
event | Active until the event passes or is resolved |
decision | Durable record |
preference | Active until changed |
pattern | Long-lived until it stops being useful |
note | Searchable background context |
fact | Active until superseded, time-bounded, or marked immutable |
Choosing a type
Usedecision when you need to remember why something was chosen.
Use commitment when someone is accountable for a future action.
Use blocker when work is stuck and should surface in briefings.
Use preference when the memory should influence how an AI behaves.
Use pattern when the same behavior or process should be reused.
Use fact for precise attributes attached to a person, company, project, tool, or file.
Use note when none of the above fits.
Examples
When to update this doc
Update this page whenVALID_MEMORY_TYPES changes, when lifecycle behavior changes, or when legacy aliases are added or removed.
Related docs
Memory tools
Save and search memories from an AI client.
Features
See how memory types fit into the broader product.