Feature · Remember
ShippedGoverned memory. Provable forgetting.
Memory writes carry the same signed, governed discipline as any other action SynOI touches. Recall is a governance question, not a benchmark race, and deleting something leaves proof it was deleted.
What it does
Memory that travels with you, on your terms.
Context an agent stores about you or your work is signed and kept under your governance, not silently retained by whichever model happened to be in the loop that day. Recall is opt-in and configurable, not a default you have to fight.
How it works
Written signed, indexed for recall, removable with proof.
Writes are recorded and content-addressed, so the same content always resolves to the same identifier. Recall uses similarity search to surface relevant prior context on demand, rather than replaying everything back at you.
Removing an entry produces a signed tombstone: a record that something was deleted, when, and why. That is a stronger claim than a database row simply no longer appearing: it is proof of the deletion event itself.
That proof is what an erasure request actually needs, whether it comes from GDPR, a customer offboarding, or your own auditor. You are not just telling them the data is gone; you are handing them a signed record that says so.
Status
Shipped, including tenant isolation.
The store, similarity-based recall, and signed tombstones are live. Tenant isolation (one customer's memory never crossing into another's) is merged and backs multi-tenant deployments today.
Folded in from the former catalog
- Vault
- Saga (HNSW recall)
- Signed tombstones
- Tenant isolation
Memory with a paper trail.
Start writing governed memory today, and know exactly what happens when you decide to remove something.