Skip to content

Require verifier in verify.receipt and finalize provenance wording#4

Merged
GsCommand merged 1 commit intomainfrom
codex/require-verifier-in-receipt-schema-and-clean-provenance
Mar 19, 2026
Merged

Require verifier in verify.receipt and finalize provenance wording#4
GsCommand merged 1 commit intomainfrom
codex/require-verifier-in-receipt-schema-and-clean-provenance

Conversation

@GsCommand
Copy link
Copy Markdown
Contributor

Motivation

  • Ensure verification receipts always identify the auditing actor so no anonymous or ambiguous verifier can validate a receipt.
  • Remove provisional provenance wording from the repository so the provenance document reads as a completed, repository-backed release artifact.

Description

  • Add verifier to the top-level required array in schemas/v1.1.0/commercial/verify/verify.receipt.schema.json and constrain it to the existing actor shape while requiring role: "verifier" via an allOf refinement.
  • Rewrite SECURITY_PROVENANCE.md to remove “pending” / “CID later” language and state the repository-backed release integrity posture (current line, checksums, canonical schema paths) without asserting external pin/mirror state.
  • Regenerate checksums.txt so the recorded SHA-256 digests match the updated schema artifact.
  • No example files required changes because existing current-line examples already include a verifier.

Testing

  • Ran npm run validate which completed successfully.
  • Ran npm run validate:examples which completed successfully and reported all current-line examples validated.
  • Ran npm run generate:checksums to refresh checksums.txt and it wrote updated checksums successfully.

Codex Task

@GsCommand GsCommand merged commit b5699f9 into main Mar 19, 2026
1 check passed
@GsCommand GsCommand deleted the codex/require-verifier-in-receipt-schema-and-clean-provenance branch March 20, 2026 01:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant