Delete a memory

Nothing is deleted. The route exists so that a client that tries gets the reason, not a 404.

501 {"detail": {"error": "append_only",
                "why": "nothing is deleted from the ledger",
                "see": "spec/endpoints-v1.md 2.7: POST /v1/memories/{id}/invalidate (v1.x)"}}

To correct a belief, write a new block and connect it with a SUPERSEDES edge. To make a block invisible from some instant on (who, when, why), wait for invalidate in v1.x. That too is append-only: an as_of before the invalidation still sees the block.

Overview

Memories

Retrieval

Declarations and ops

Delete a memory