Reconcile language-neutral verifier cases as Snapshot 3 - #170
Merged
aruintelligence merged 1 commit intoSep 14, 2026
Merged
Conversation
This was referenced Sep 14, 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.
Purpose
Replay the vetted Snapshot 3 verifier-contract work cleanly on top of current
main, after the licensing, real-screen evidence, and release-discipline hardening landed.What this changes
conformance/verifier-challenge-cases.jsonas a language-neutralaml-verifier-challenge-cases/1corpus;Rebase safety
This is a clean one-commit replay of the intended #160 file states onto the current
main. The intervening main-side hardening did not modify these verifier-contract paths, so no newer main changes are intentionally overwritten.Evidence boundary
A black-box PASS is compatibility evidence for the exact tested project-defined contract. It is not certification, proof of implementation independence, standards-body approval, scientific validation, regulatory compliance, safety, production suitability, or adoption.
Reference implementations maintained in this repository remain project-controlled evidence. Independent credit requires the separate provenance/independence conditions documented by the project.