Built for memory you can defend in a review.
Enterprise memory questions are not marketing questions — they're review-board questions, and they deserve structural answers. Here is what the system enforces today, each guarantee mapped to the review question it answers, followed by an honest account of what we don't hold yet.
Every event is write-once, enforced at the database level — history can't be edited in place, only corrected forward. Combined with the audit log and per-answer retrieval traces, 'what happened' is always reconstructable: what was written, what was recalled, what was injected, and what was filtered.
The review question it answers: “Show me exactly what the agent knew when it acted.”
Every store takes a workspace identifier on every data method; a read outside its scope returns nothing. Hosted endpoints resolve tenancy from authentication — no endpoint accepts an org identifier from the request. Cross-user isolation is a structural property, re-verified by a zero-leak gate on every release.
The review question it answers: “Prove one customer's memory can't surface for another.”
User-scoped erasure is an operation with evidence, not a manual project: derived memory is deleted with its supersession chain repaired, the append-only event record is redacted in place (content scrubbed, structure preserved), and the erasure itself lands in the audit trail. Governed forgetting extends it: memories carry validity intervals and expire, suspect memory can be quarantined without destroying the record, and secrets can be scrubbed.
The review question it answers: “What happens when a user exercises their right to be forgotten?”
TLS 1.3 in transit; AES-256 at rest on the managed deployment. API keys are bearer tokens stored only as hashes — a database leak doesn't expose usable keys — and authenticated calls land in the audit log.
The review question it answers: “How is data protected in transit and at rest?”
The governed read path prefers explicit uncertainty over unsafe recall — it abstains when memory is missing, conflicting, stale, or out of scope, and the abstention is visible in the trace. An agent that sometimes declines is cheaper than one that confidently acts on a contradiction.
The review question it answers: “What does it do when it's not sure?”
The governance model behind these — born-pending approval, supersession with lineage, governed forgetting — has its own deep dive on /governance, with the measured guarantee figures.
What we hold, what we don't, and what we'll show you instead.
Managed and invite-first while we finish the hosted product; design partners can run memomee in their own environment today — same engine, same gates.
Design-partner deployments pin the store to your environment and region; residency requirements are part of the design-partner conversation, not a checkbox we pre-fill.
We don't hold SOC 2 or ISO certifications yet, and we won't imply otherwise. What we can show today is stronger than a roadmap slide: the enforcing machinery and the gates that re-verify it on every release.
Availability and support terms are agreed per design partner. We'd rather commit to terms we can keep than publish numbers we haven't earned.