Skip to content
GOCUX
Documentation
GOCUX / Documentationapi reference

Reference: delete a selected memory

Remove the intended retained memory through its own record identity.

Remove the intended retained memory through its own record identity.

Practical procedure

  1. Read the selected memory and confirm its content, scope and identifier before requesting removal.
  2. Use DELETE /memories/{memory_id} through the authorized user workflow. Keep deletion intent separate from editing a local cached copy.
  3. Refresh the memory view and any dependent task context after the operation. Do not report an unrelated record as deleted because its text looked similar.

Keep memory within its approved audience

Memory Graph separates a proposed memory from an approved one. The four scopes are session, user, project and company; choose the narrowest audience that needs the information. A manual proposal includes its reason, source reference and checksum, classification, retention and expiry. Corrections create a new version rather than silently replacing the history that a prior decision referred to.

Contract example

Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.

Operation reference for this workflow

GET /memories/{memory_id}

DELETE /memories/{memory_id}
Idempotency-Key: <unique-erasure-operation-key>

Inspect the result

Retrieve only memories that match the intended scope and query. Inspect their source and approval status before carrying them into a new task. A project memory supplies projectId and no sessionRef; a session memory supplies sessionRef and no projectId. User and company scopes carry neither target field.

What to keep explicit

Deletion requires an operation-specific Idempotency-Key and returns 204 on success. This deliberate retention action does not authorize a broad purge or erase every historical artifact that quoted the memory.

Handle incomplete and refused work

The retrieval limit is 1–20 and classificationCeiling is public or internal. An incorrect scope shape is refused. Decisions bind memoryVersionId and expectedRowVersion, so refresh after a conflict rather than approving a stale version. Deletion and retention can remove a previously available memory; a saved identifier is not a perpetual right to retrieve its content.

Bring this workflow into your workspace.

Set the scope. Review the evidence. Approve the steps that need it.

Open the workspace

Keep exploring