supersede_memory()
KeyRevision the append-only way: writes the new row, closes the old one, and links them with a supersedes edge — in one transaction. History is never overwritten (invariant I1).
supersede_memory(memory_id, content, reason)→ REVISIONCallable over MCP as supersede_memory(memory_id, content, reason). REST mirror POST /v1/memories/supersede Planned — alpha is MCP-only
When a belief stops holding, the agent doesn't edit it — it supersedes it. The old row stays, closed and linked, so any past decision that relied on it still reconstructs exactly. Revision without revisionism.
Over MCP, your agent invokes it on its own when the moment calls for it — just describe the situation. A Python SDK for headless runtimes is planned; this is what the call will look like.
| Param | Type | Description |
|---|---|---|
| memory_idREQUIRED | string | The memory item being superseded. |
| contentREQUIRED | string | The revised content. |
| reasonREQUIRED | string | Why the old item no longer holds. |

