docs: clarify temporal reference date wording

2026-05-13 00:16:43 +05:30
parent 97038bbb4b
commit 5559bf2dac
2 changed files with 2 additions and 2 deletions
@@ -13,7 +13,7 @@ Mem0 Platform v3 can now interpret time-aware memories and queries so assistants
 - **Time-aware search intent** — Queries like `last week`, `upcoming`, `right now`, and `as of March 2025` use temporal signals during retrieval
 - **Write-time temporal enrichment** — Dated events, future plans, ongoing states, relationships, and preferences are handled automatically when temporal structure is detectable
 - **Enabled by default** — No per-request toggle is required for v3 writes or searches
- **Deterministic relative queries** — `reference_date` anchors relative search phrases for tests, backfills, and reproducible demos
+- **Anchored relative queries** — `reference_date` anchors relative search phrases for tests, backfills, and reproducible demos
 - **Normal response shape** — Temporal reasoning affects ranking while preserving existing client response patterns

 See [Temporal Reasoning](/platform/features/temporal-reasoning) for usage details.
@@ -8,7 +8,7 @@ mode: "wide"

 **New Features:**
 - **Memory:** Added Temporal Reasoning for Platform v3 to improve ranking for time-aware queries such as `last week`, `upcoming`, `right now`, and `as of ...`
- **Search:** Added `reference_date` support to anchor relative temporal queries for deterministic tests, backfills, and reproducible demos
+- **Search:** Added `reference_date` support to anchor relative temporal queries for tests, backfills, and reproducible demos

 **Improvements:**
 - **Memory:** Temporal enrichment runs asynchronously by default after v3 writes and feeds retrieval ranking once available