REST API — Memory

Method	Path	What it does
GET	/api/memory	List this workspace’s memory, newest first. Filter by kind and status (a retracted entry appears only when status=retracted); q searches by meaning (hits below SEARCH_SCORE_THRESHOLD are left out, so an unrelated query finds nothing), falling back to plain text when semantic search is unavailable.
POST	/api/memory	Add an entry to this workspace’s memory, authored by the caller. A commitment’s owner defaults to the caller and must be a member.
GET	/api/memory/export	Export the ledger as the caller sees it, history included: retracted entries and the earlier versions of revised ones; other members’ private entries are not theirs to export.
GET	/api/memory/{entry_id}	One entry of this workspace’s memory.
PATCH	/api/memory/{entry_id}	Always refused (entry_immutable): the ledger is append-only. Revise an entry instead, which records a new version.
POST	/api/memory/{entry_id}/retract	Retract an entry: it stays in the ledger, marked retracted, and leaves lists, recall and reminders. Its author or the workspace owner.
POST	/api/memory/{entry_id}/revise	Record a corrected version of an entry. The earlier version stays in the ledger and drops out of lists and recall. Its author or the workspace owner only.
POST	/api/memory/{entry_id}/status	Mark an open commitment done or cancelled; it is no longer chased. Its owner, its author or the workspace owner.