Deleting
Deleting: forget the content, keep the proof
Deleting erases what the memory said but keeps a record that it existed and was deleted.
What happens when you delete
- The text, tags, source and text fingerprint are erased.
- The erased data is wiped from the database files on disk, not just hidden.
- The memory is marked deleted, with the time.
- A “forget” entry is added to the log.
Why not remove every trace
If deleting removed every trace, nobody could ever check whether a deletion was legitimate, or answer “was this ever stored?” during an incident review. Keeping a small, empty record keeps that proof while the content itself is gone.
Expiring is different from deleting
You can give a memory a lifetime in seconds. After it expires it no longer appears in search, but it is not erased. Delete it if you need the content gone.
Your copies
Copies outside AETHER-33, such as your exports, backups or the agent's own conversation, are yours to delete. This helps with erasure requests; it is not legal advice.
AETHER-33 is a product over CAIN-42's governed-memory stack, not a new architecture moat.
Memory never carries authority: every response is annotated
grants_authority: false.
No third-party audit has been performed. Limits ·
FAQ · what is live now