Repository navigation
Allow owner-reviewed evidence without a blanket second-person gate - #105
Merged
Merged
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.
Completed reviews could freeze collected supporting evidence and then reject a substantive review by its collector. Generated instructions also told every owner to find a second person. Allow the actual collector to review and finalize evidence, while retaining collection/review separation, source and date checks, artifact integrity, historical metadata, and specifically required independent approvals.
The UI labels the existing verified state Reviewed. JSON fields, statuses and CSV headers remain compatible. Vendor assessments still accept collected supporting proof; packet delivery still requires actual review. Policy, governed-content, risk-assessment, reporting-configuration and CPA independence remain intact. Both published packages are coordinated at 0.21.11 with no model migration.
Validation: full CI=true npm run validate on Node 24; owner-review/history and policy/risk regression tests; real-browser collector review/save, status filter and packet rendering; a fresh generated consumer using the packed engine; package inspections; npm audit with no vulnerabilities; combined code/security reviews.