Harden Core public verification and claim boundaries - #7
Draft
Riverbraid wants to merge 13 commits into
Draft
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
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
fixtures/README.mdwith the rule that fixtures require a declared consumer, contract, expected behavior, and evidence relationship.claim-ceiling.jsonas a machine-readable allowed/refused-claim declaration.package.jsonwith Node20.11.0and npm10.2.4, while adding boundedverifyandverify:compatibilitycommands.Proposed Phase 15from current authority vocabulary.ubuntu-24.04,actions/checkout@11d5960a326750d5838078e36cf38b85af677262, andactions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020.Exact-head validation
Current head:
GitHub Actions run
30285743307completed successfully.The
verify-core-live-compatibilityjob completed:20.11.0setup;This supports only the exact claim that the PR head's live mutable-default-branch compatibility workflow executed successfully in the observed environment. It does not convert that workflow into the pinned Evaluation Kit profile.
Boundaries
This PR does not claim certification, production readiness, external audit, complete AI safety, absolute security, registry freshness, adoption, full-constellation verification, independent reproduction, or absence of defects.
It does not mutate Evaluation Kit registry pins, releases, tags, repository settings, or the F0–F4 control package.
The documentation and workflow-classification portion of issue #6 is addressed. Any future pinned Core compatibility profile remains a separate evidence and authority decision.