Document release discipline and independent evidence paths - #169
Merged
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.
Purpose
Make the next ĀML maturity steps explicit without changing historical evidence or pretending project-controlled checks are independent validation.
Changes
docs/RELEASE_DISCIPLINE.mddefining immutable release identity, stable/preview/experimental separation, minimum release evidence, release receipts, and no silent historical rewriting;docs/REAL_SCREEN_EVIDENCE_CONTRACT.mdas explanatory guidance around the canonical machine-readableschema/real-screen-evidence-manifest.schema.jsonandevidence/real-screen/README.mdalready onmain;publications/INDEPENDENT_IMPLEMENTATION_CHALLENGE.md, inviting outside clean-room implementations and explicit PASS / FAIL / MIXED reporting.Evidence boundary
Project-authored CI remains project-controlled evidence. A black-box conformance PASS is compatibility evidence for the exact tested contract, not certification, proof of implementation independence, standards approval, scientific validation, regulatory compliance, safety, or adoption.
Real-screen attention/restoration values remain declared reviewer inputs, not objective measurements of cognition or wellbeing.
Relationship to other hardening work
This PR is intentionally documentation-only so it can coexist cleanly with the separate verifier-contract Snapshot 3 reconciliation. It does not create a competing evidence schema and does not rewrite legacy experiment artifacts.