Document Value Map testing and benchmarks - #6
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
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.
Summary
Adds a short public-facing explanation of how Value Map is tested and where its reproducible benchmark record lives.
The note explains that evaluation combines deterministic lineage and evidence gates, metamorphic tests, staged smoke cases, and a controlled live inverse benchmark. It also states the important limitation: passing a synthetic fixture validates that mapping boundary, not general accuracy across products or conversations.
Why
The public README already explains how Value Map works, but did not give readers a concise way to distinguish evidence-backed testing from a broad scientific claim. This adds that distinction without exposing internal research detail or changing the released skill.
Verification
python3 -m unittest discover -s tests -v— 7/7 passgit diff --checkDependency
The benchmark link targets the record introduced by operatorstack/intelligence-flow#51. Merge that PR before or alongside this documentation change so the link resolves on the default branch.