fix(wcm): waive evidence verification explicitly in mock demos - #127
Merged
Merged
Conversation
The next WCM release requires cryptographic evidence verification unless the manifest waives it (WCM #159). Mock attestation has nothing to verify, so the demos say so. No-op on 0.28.4, which lacks the field. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Companion to agentrust-io/weight-custody-manifest#159. The next WCM release requires cryptographic evidence verification unless a manifest waives it, and meets GPU confidential-compute mode only with a verified report. These demos run on
SoftwareProvider, which nothing can verify, so their manifests now waive both explicitly._mock_attestation.waive_mock_verification()addsrequire_evidence_verification: falseandrequire_cc_mode: falseonly when the installed SDK has the new field. On 0.28.4 it does nothing, since that release rejects the unknown field. That lets this merge first; WCM's requireddownstream-examplescheck runs against this repo'smain.Wrapped: closed_model_e2e, open_model_e2e, refuse_and_wipe, revocation_kill_switch, sovereign_self_custody, real_open_model, real_lora_custody.
run_demos.pyskips_-prefixed helpers.Checked with
run_demos.py --no-testson PyPI 0.28.4 and on a wheel from the WCM branch: every offline demo passes on both. Before this change five failed on the branch wheel.refuse_and_wipestill refuses on "measurement not in accepted_measurements". Not run here:provenance_model_signingand the pytest files, because Windows Application Control blocks arfc3161_clientDLL on this machine; CI runs them.Once WCM 0.29.0 is out, the helper can go and the waivers can be inlined.
Generated with Claude Code