Measure production memory delivery with auditable paired comparisons - #4
Merged
Merged
Conversation
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.
BrainBenchmark now compares persistent production MCP delivery and retains the evidence an agent actually receives. Paired observations include rankings, capsules, optional answerability metadata, latency, serialized response bytes, and supported Windows process-memory measurements.
The latest frozen comparison retained 24/27 positive hits while reducing unwanted injections from 15/18 to 3/18. Exact metadata matched 36/45 cases in both repeats. These are evidence-delivery results, not generated-answer accuracy or a new overall BrainBench score.
Validation of the implementation: 132 Rust tests and 18 Python tests passed; optimized harness build and paired runs completed. This publication commit only changes documentation. The harness uses parent-checkout path dependencies and requires the companion Kimetsu hardening branch.
Companions: Kimetsu implementation and audit, website documentation.