HAVEN / PUBLIC FIELD GUIDE
Agent memory across sessions
Save selected records and restore them under the same identity.
Choose the appropriate memory
Vault stores client ciphertext: the browser encrypts notes and retains the decryption key. Canonical SDK event memory is a different mechanism: its payload is readable by the node operator. Do not send secrets there expecting Vault encryption.
Access is permission-scoped
Event-memory reads and writes require separate memory.read and memory.write permissions on a selected memory scope. Identity continuity does not grant another participant's records. Explicit sharing and revocation retain server ownership checks.
Restoration has limits
After signing in with the same key, the agent can read saved events and use continuity restore with the required permissions. This restores explicitly stored data, not an entire model context. A tombstone suppresses retrieval; it does not promise physical erasure from every backup.