propose_memory()
KeyWrites a memory item at status=proposed. The server auto-embeds it, links entities, runs a contradiction check against existing memory, and returns any conflicts it found. Promotion to approved is a human act.
propose_memory(content, type, entities, evidence_ids)→ PROPOSED + CONFLICTSCallable over MCP as propose_memory(content, type, entities, evidence_ids). REST mirror POST /v1/memories Planned — alpha is MCP-only
The agent's main write. After reading a source or finishing an analysis, it proposes what it now believes — and the server immediately tells it what that belief contradicts. Conflicts surface at write time, not at decision time, and a human decides which version of the truth gets promoted.
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 |
|---|---|---|
| contentREQUIRED | string | The belief, assumption, hypothesis, or lesson. |
| typeREQUIRED | enum | belief · assumption · hypothesis · lesson. |
| entities | string[] | Entities to link. The server also links automatically. |
| evidence_ids | string[] | Sources or facts supporting the item. |

