Verifier Assurance (PCS-VA) schemas, validators, and docs#26
Merged
Conversation
Establish PCS-VA scope, ownership ADR, and explicit non-claims so later schema and validator work has a stable product boundary.
Introduce the profile contract and shared defs so downstream VA artifacts can pin verifier identity and capability claims portably.
Define the v1 result envelope so ACCEPT/REJECT/INDETERMINATE outcomes carry profile-bound commitments without replacing VerificationResult.v0.
Capture reward evidence as an integrity-bound envelope so optimization and assurance flows can audit reward provenance separately from results.
Encode optimization cohorts and adjudication commitments so release-grade assurance can require explicit campaign structure and human/automated rulings.
Provide the offline report surface that rolls profile, results, rewards, and adjudications into a rebuildable assurance artifact.
Extend PCS-VA with producer pin artifacts so OVK can vendor invocation/mutation/replay records without forking the core six-artifact family.
Register VA artifact classes and enforce semantic rules so schema-valid payloads still fail closed on profile, reward, and campaign invariants.
Deterministically rebuild report digests from campaign inputs so offline assurance packages can be verified without trusting producer-side aggregation.
Give operators a first-class pcs entrypoint and suite runner so VA validation and report rebuilds are exercisable in CI and local gates.
Ship valid/invalid fixture trees and a generator so conformance dialects and docs examples stay regenerable from one source.
Mirror Python VA semantic checks in pcs-core so Rust consumers enforce the same fail-closed assurance invariants.
Expose VA schema detection and semantic validation in @pcs-core so TS runtimes can gate the same artifact family as Python and Rust.
Pin cross-language digests for the VA family so Python, Rust, and TypeScript stay byte-identical on canonical hashing.
Cover semantic rejection cases and shared-hash agreement so VA regressions fail in language CI before release.
Complete operator-facing PCS-VA guides and changelog so producers can migrate, pin schemas, and understand threat and non-upgrade boundaries.
Run VA conformance and related gates on PR and release so the new artifact family cannot ship without automated checks.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| const negative = trimmed.startsWith("-"); | ||
| const body = | ||
| negative || trimmed.startsWith("+") ? trimmed.slice(1) : trimmed; | ||
| if (!body || !/^\d*\.?\d*$/.test(body) || (body.match(/\./g) ?? []).length > 1) { |
3 tasks
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
2 participants
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
*.v1schemas, and OVK pin-surface schemas (invocation, mutation, replay).Test plan
pcs conformance run --suite verifier-assurance