Add mem0 mutation assurance proof#536
Merged
Merged
Conversation
creatornader
force-pushed
the
feat/mem0-mutation-assurance
branch
from
July 19, 2026 11:18
4a5f20c to
ad9756c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@atrib/action-gate.mem0ai/oss@3.1.0proof that blocks identity-scope metadata, verifies an allowed update, and checks delete state.Why
A mem0 success response and the resulting memory state are separate facts. The helper signs the policy decision before a mutation and requires at least one read-back check after execution. A missing, failed, or false postcondition cannot be reported as verified.
Verification
pnpm --filter @atrib/integration typecheckpnpm --filter @atrib/integration test -- mem0-mutation-assurance.test.ts(6 passed)pnpm --filter @atrib/integration mem0-mutation-assurancepnpm doc-syncgit diff --checkThe full integration run reached 59 passing files and 246 passing tests, then two unrelated browser tests exceeded their existing 30-second limits. Both also timed out in isolation. Targeted ESLint could not start because the current TypeScript 7.0.2 and
typescript-eslint8.64.0 combination crashes insidetypescript-estreebefore file analysis.