Release pf-core 0.7.0 reward-binding (multi-commit) - #1
Merged
Conversation
Record ownership boundaries for Lean model, schemas, CLI, and PCS adapter so release work has a single decision record.
Capture the starting scope, deliverables, and acceptance checklist that later VA steps build on.
Align product claims with what the Lean model and validator actually certify versus what remains out of scope.
Document A11-A14-facing assumptions and the release gates needed to ship pf-core 0.7.0 reward-binding.
Pin authority, environment, verifier profile, verification result, and reward evidence envelope schemas for adapter consumers.
Normalize PCS artifacts into trusted reward-binding inputs and ship a known-good fixture set for adapter and validator checks.
Define the trusted input shape validators consume, with valid and invalid examples plus schema-map documentation.
Evaluate binding, integrity, issuer, and profile checks in Python and emit structured decisions covered by unit tests.
Expose reward-binding validation through the pf-core CLI so operators can run the same predicates as the library API.
Formalize reward-binding structures and extend assumptions so later certificate and soundness theorems have a stable base.
Prove certificate well-formedness and soundness relative to the reward-binding model, including A11-A14-facing results.
Encode replayable golden cases that lock expected accept/reject behavior for the formal certificate path.
Serialize accepted reward-binding decisions into certificates that align with the Lean certificate shape for offline replay.
Map Lean theorems to runtime checks and clarify adversarial assumptions for reward-binding certificates.
Cover revoked issuers, trace substitution, profile conflicts, staleness, and related reject paths for adapter regression.
Provide handoff fixtures for LabTrust reward-binding wiring and OVK verifier-profile pinning without coupling release to those repos.
Spell out follow-on PR scope so parent repos can land schema and profile pins after pf-core 0.7.0.
Record the reward-binding release surface, security notes, and final inventory for PF-VA-08 closeout.
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.
Summary
Test plan