Cursor/eval methodology guard provenance#1
Merged
Conversation
Publish anti-cheating eval docs, a deterministic dumb-reader ablation, conflicts-v1 stress tests, and retention traces so retrieval quality is separable from reader recovery; add Guard/Armorer with provenance tags and check_memory_use for external-action boundaries. Co-authored-by: Cursor <cursoragent@cursor.com>
Add read-only inspect_memory and richer recall evidence over MCP, align LongMemEval benchmark commands/defaults on n=40, and include MCPB packaging plus privacy policy updates. Tests: uv run --extra mcp --extra dev pytest tests/test_mcp_server.py tests/test_guard.py tests/test_capture.py tests/test_memory_supersede.py tests/test_sqlite_store.py Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
No description provided.