Repository navigation
Constrain ambiguous signature cohorts with independent source evidence - #43
Merged
Merged
Conversation
This was referenced Oct 27, 2026
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.
Distinct STL and compiler-generated routines can share their complete byte patterns. Expand the independent source counterexamples and constrain existing ambiguous cohorts using complete reference requirements or incoming context queries.
The capture receipt records 43 configurations, 107 reproduced objects and their assembly/header evidence; the selector audits 228 unpruned source collections across x86, x64, ARM and ARM64. Historical provenance remains intact. In the changed packs, global scan records decrease from 1,425,169 to 1,423,736; additional source declarations use the name index.
Validation with NeverD #1861:
Complete source hashes, accuracy counts, losses/gains, native output hashes and performance controls are in
validation/library-features/expanded-collision-{capture-receipt,refinement}.json. These bounded checks do not establish exhaustive recognition or competitor superiority.