memory_update
Update an existing memory record. Automatically regenerates vector embeddings when content changes, while preserving previous versions in history.
Instructions
Update an existing memory. If content changes, the vector embedding is automatically regenerated. Previous versions are preserved in history.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the memory to update | |
| content | No | New content (will re-generate embedding) | |
| title | No | New title | |
| metadata | No | Updated metadata (replaces existing) | |
| tags | No | Updated tags (replaces existing) | |
| expires_at | No | New full ISO-8601 expiration timestamp (e.g. 2026-03-01T00:00:00Z), or null to remove | |
| changed_by | No | Who made this change (for version history) | |
| importance_score | No | Reassign importance 0-1 (governance/criticality) | |
| verification_tier | No | Set/upgrade the verification tier after the fact (the main post-hoc use case — you verify a stored claim against live state later). Raises/lowers groundedness. | |
| verification_detail | No | Free text accompanying a verification_tier change. | |
| volatility | No | Manual override of the auto-derived volatility class. |