Harden selective verification and complete competitor matrix - #35
Merged
Conversation
added 16 commits
August 1, 2026 10:36
samarth1412
marked this pull request as ready for review
August 8, 2026 15:17
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.
What changed
semantic_core_v2andsemantic_core_v2_1verification, schemas, limits, concurrency isolation, and source-condition diagnosis.Why
The verifier needed safer selective behavior, stronger source-condition attribution, reproducible external comparisons, and explicit separation between visible development measurements and untouched evaluation evidence. The interrupted RefChecker run was caused by an Ollama auto-update from the pinned 0.32.1 runtime to 0.32.5; it was resumed and completed using the exact pinned runtime.
Impact
This gives ContextTrace a reproducible development baseline and stronger implementation safeguards without publishing a release, touching sealed labels, or claiming SOTA. CRAG remains an agreement/proxy track rather than an accuracy evaluation.
Validation
git diff --checkpassed.