JDSS/mem0
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: hide temporal internals from API docs

Browse Source
This commit is contained in:
agumpandey
2026-05-12 23:49:06 +05:30
parent 9532d08cdd
commit 14237e3252
9 changed files with 14 additions and 488 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/platform/features/temporal-reasoning.mdx
+4 -7
View File
@@ -32,12 +32,12 @@ client = MemoryClient(api_key="your-api-key")
Temporal Reasoning has two public-facing parts:
- **Write-time enrichment**: when Mem0 stores a memory, it can attach temporal structure such as memory type and date bounds when that information is present in the text.
- **Search-time interpretation**: when a query includes time language like `last week`, `upcoming`, or `right now`, Mem0 uses the stored temporal fields to return more appropriate results.
- **Write-time enrichment**: when Mem0 stores a memory, it can infer internal temporal structure when that information is present in the text.
- **Search-time interpretation**: when a query includes time language like `last week`, `upcoming`, or `right now`, Mem0 uses internal temporal signals to return more appropriate results.
### Memory types
Mem0 normalizes temporal memories into a small set of developer-facing types:
Mem0 normalizes temporal memories into a small set of internal classes:
| Type | What it represents | Example |
| --- | --- | --- |
@@ -47,7 +47,7 @@ Mem0 normalizes temporal memories into a small set of developer-facing types:
| `relationship` | A durable connection between people or entities | "Priya manages Jordan." |
| `preference` | A stable preference or habit | "I prefer morning meetings." |
At search time, Temporal Reasoning influences how results are ranked — memories that match the temporal intent of the query receive a boost — but no temporal metadata is added to the API response. The ranking effect is transparent: results come back in the normal shape.
At search time, Temporal Reasoning influences how results are ranked. The ranking effect is transparent: results come back in the normal shape.
## Configure it
@@ -210,9 +210,6 @@ results.results.forEach((item) => {
<Card title="Memory Timestamps" icon="calendar" href="/platform/features/timestamp">
Anchor imported memories to when they actually happened.
</Card>
<Card title="Answer Time-Aware Questions" icon="book-open" href="/cookbooks/essentials/temporal-memory-assistant">
Follow the cookbook for an end-to-end temporal retrieval workflow.
</Card>
</CardGroup>
<Snippet file="get-help.mdx" />