Replace an assumed bulk-clear API with an exact-audience retention review.
Practical procedure
- List the memories available in the intended scope and review their content and retention need.
- Select the exact records to remove and confirm the action in the authorized workflow. Delete by memory identifier rather than applying an unverified all-records command.
- Refresh the list and record which removals succeeded. Handle unavailable or inaccessible records as unresolved operations.
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?scope=project&projectId=project-id
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
No generic clear-all memory endpoint is established here. A retention review should remain scoped and inspectable, especially when company memories serve multiple users. Each deletion requires its own Idempotency-Key.
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.
Continue with related guides
Bring this workflow into your workspace.
Set the scope. Review the evidence. Approve the steps that need it.