When your agent acts for a client, you have to answer for it.
The agent does something on a client’s behalf, and the client asks the one question you have to be able to answer: why did it do that? Most memory can’t tell you. It overwrote the evidence the moment the facts changed. OMEM is built so you can answer: prove why the agent believed and did what it did, and approve the risky moves before they run.
Self-hosted, so nothing leaves your client’s environment.MIT core · your infrastructure
Three things a client’s reviewer will ask for.
Accountability isn’t a feature you bolt on at the security review. It’s three properties the memory either has or does not, and OMEM was built around them.
- Provenance you can hand to a client
- Ask why the agent believed something and get the chain: which source, when, on what basis, and what it contradicted. Export it. When a client's compliance person asks "why did it do that," you send a record, not a similarity score.
- A human approves before it acts
- A risky action does not run on the model's say-so. It waits for a named approver, the approval is recorded under that name, and a plan the model proposes cannot name an action into existence. You decide what your agent is allowed to do to a client, in code, not in a prompt.
- A record that cannot rewrite itself
- We call it the testimony ledger. Every belief is recorded under a named source with its evidence, the log is append-only, contradictions keep both sides, and the engine that reads it is frozen: it must replay the record byte-identically, verified on every commit, so not even an upgrade can change what was said. A court does not trust a witness who can edit their statement. Neither does a security reviewer.
The belief-revision engine is how, not the pitch.
Under all of this is a memory that keeps contradictions, tracks what was believed at any past moment, and never decides on its own that two claims disagree. That’s what makes the audit trail trustworthy, but you’re buying the answer to your client’s question, not a memory model. If the engine is what interests you, the why() chain and the whole design are on the homepage and in the docs.
$1,500, and I wire it into your stack with you.
The software is free and MIT, so you are not paying for OMEM. You are paying for my time. A design-partner pilot is hands-on: over a couple of weeks I work with you to put the approval gate and the provenance trail into your agent, you walk away with a record you can show a client’s compliance team, and I get your feedback and, if it earns it, a reference. It’s small on purpose, and it carries its own guarantee: if the pilot does not produce a review-ready artifact, you do not pay.
Prefer to try it alone first? pip install omem-infrastructure and the whole thing runs on your laptop.