docs(temporal): remove temporal metadata from v3 search response docs

Temporal fields (event_date, memory_type, effective_plan_status, etc.)
are backend-only ranking signals and must not be documented as part of
the public search API response.

- temporal-reasoning.mdx: replace response-field table with a note that
  temporal reasoning affects ranking only; no metadata added to responses
- temporal-memory-assistant.mdx: remove temporal field reads from all
  three retrieval examples; update illustrative output blocks
- openapi.json: remove temporal fields from /v3/memories/search/ example
  response; remove temporal_boost from score_breakdown example
- add-memories.mdx: remove temporal_reasoning toggle from request params

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
agumpandey
2026-05-09 10:43:56 +05:30
co-authored by Claude Sonnet 4.6
parent b2d2c8a8ef
commit f864e9b871
4 changed files with 20 additions and 171 deletions
+1 -21
View File
@@ -2093,11 +2093,6 @@
"type": "boolean",
"default": true,
"description": "When `false`, stores each message verbatim without running the extraction LLM."
},
"temporal_reasoning": {
"type": "boolean",
"nullable": true,
"description": "Enable V3 temporal reasoning write-path metadata. Defaults to the deployment setting."
}
}
},
@@ -2240,11 +2235,6 @@
],
"nullable": true,
"description": "Optional query anchor time for relative temporal interpretation. Accepts Unix epoch, YYYY-MM-DD, or ISO datetime."
},
"temporal_reasoning": {
"type": "boolean",
"nullable": true,
"description": "Enable V3 temporal intent and temporal scoring. Defaults to the deployment setting."
}
}
},
@@ -2329,18 +2319,8 @@
"score_breakdown": {
"semantic": 0.78,
"bm25": 0.0,
"entity": 0.0,
"temporal_boost": 0.04
"entity": 0.0
},
"memory_type": "event",
"event_date": "2026-01-15",
"event_start": "2026-01-15",
"event_end": "2026-01-15",
"plan_status": null,
"effective_plan_status": null,
"time_precision": "day",
"temporal_surface": "Jan 15, 2026",
"reference_date_used": "2026-01-20",
"metadata": {},
"categories": [
"location"