Forget a Profile
DELETE /namespaces/{ns}/profiles/{profile_id} forgets everything held about one profile — every memory, and the profile’s summary with it.
2xx means none of that profile’s memories remain, and there is no undo.
After Forgetting
The200 returns a report of what was removed (a report, not a strict audit):
- It drops out of
GET …/profiles, which only lists profiles that currently hold memories. GET …/profiles/{id}/memoriesandGET …/profiles/{id}/sourcesreturn an empty200, not a404— the same as any never-written profile.- There is no tombstone and no soft-delete, and no undo.
- The id stays reusable: the next
ingestorrememberre-creates the profile with fresh memories.
Forget One Session
A session is forgotten through its source, on the Sources page —DELETE …/profiles/{id}/sources/{source_id}. Use the source_id from the ingest 202, or look it up first with GET …/sources?session_id=. This forgets that one session and the memories derived from it, leaving the rest of the profile intact.
The 200 returns the same kind of report, scoped to the source:
404s on a direct GET. But source ids are deterministic — derived from the profile and the session (or, for a remembered fact, its text) — so re-ingesting the same session re-creates the source under the same id, and that 404 becomes a 200 again. The profile’s other sources and their memories are untouched.
You can forget a whole profile (here) or one session, by its source. Forgetting a single memory is not yet available.
Related
- Sources — forget one session by deleting its source
- Writing memories — how memories get in
- Recalling memories — reading a profile whole