Can an AI agent secretly rewrite what it remembers?
If an AI stores your instructions, decisions, and obligations — "repay 20,000 by the 10th" — and three months later its memory quietly says 2,000, who can prove it was altered?
The problem with agent memory
Most agent memory systems are databases the agent itself can edit. No write log, no approval chain, no way to prove a record was not modified after the fact. In an enterprise this is a compliance nightmare: when an automated workflow goes wrong, you cannot reconstruct what the AI actually knew, and when.
Sealed writes
MeshCtx (current release v3.131.3) treats every memory write as an auditable event. Each record gets a tamper-evident seal — a cryptographic fingerprint. If anyone alters the memory afterwards, the seal no longer matches. The platform is SOC 2 compliant.
External anchoring
A seal stored on the same server as the data proves nothing — one compromise rewrites both. So MeshCtx anchors each seal stub to an independent external notarization service. The proof lives outside MeshCtx's own infrastructure.
The audit trail
The enterprise edition ships a full audit chain: who wrote which memory, at what time, who approved it, and the verification ID of the tamper-evident record — one chain, end to end. When a dispute arises, you produce evidence instead of arguing.
Self-hosting and open core
MeshCtx is open core (AGPLv3) and self-hostable — your memory data never has to leave your own servers. Source: github.com/LucyAndLuna2023/meshctx
Pricing
Personal: free. Team: $9/month. Enterprise: $29/month — a fraction of what traditional enterprise audit systems cost.
AI memory should be verifiable, not taken on faith.
Also on Telegra.ph.
Top comments (0)