ĀML hardening: independent verification, release discipline, evidence corpus - #162
Closed
aruintelligence wants to merge 10 commits into
Closed
aruintelligence wants to merge 10 commits into
aruintelligence wants to merge 10 commits into
Conversation
Owner
Author
|
Superseded by #166. |
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
Consolidate the next ĀML hardening wave around independent verification, immutable release identity, and disciplined real-screen evidence.
Changes
conformance/verifier-challenge-cases.json, a language-neutral corpus using a narrow RFC 6901 JSON Pointer replacement profile.main.docs/RELEASE_DISCIPLINE.mdto separate stable, preview, and experimental states and define minimum release evidence.docs/REAL_SCREEN_EVIDENCE_CONTRACT.mdto standardize capture provenance, labels, policy binding, receipts, reruns, before/after evidence, and claim boundaries.publications/INDEPENDENT_IMPLEMENTATION_CHALLENGE.mdto invite outside clean-room implementations with PASS / FAIL / MIXED reporting.Evidence boundary
A project-authored test or GitHub Actions result remains project-controlled evidence. A black-box PASS is compatibility evidence for the exact tested contract, not certification, proof of implementation independence, standards approval, scientific validation, regulatory compliance, safety, or adoption.
The attention/restoration labels used in real-screen experiments remain declared reviewer inputs, not objective measurements of cognition or wellbeing.
Relationship to older PRs
This PR modernizes the useful language-neutral verifier-case idea from #68 against current
mainrather than merging that stale branch wholesale. The real-screen evidence from #152 is already present in currentmain; this PR adds a forward evidence contract rather than overwriting those historical packages.