Repository navigation
Allow independent verification of finalized Evidence and release 0.20.3 - #87
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.
Finalized workflow proof previously blocked collected Evidence from receiving independent verification. Allow its first additive verification while preserving the original observation, Markdown, attachments and prior verification across occurrence, Attestation, Exception, audit population and amendment proof owners.
Validate committed verification against its first commit's time, timezone and Person inventory. The guided editor preserves model-allowed hidden fields, including Component attachment paths, and protected-proof rejections return HTTP 400 with a useful message.
Validation: independent combined code/security review; cross-owner, tamper, historical chronology and guided serialization regressions; fresh local browser acceptance/rejection; full Node 24 validation; package dry runs; fresh consumer validation; npm audit with no vulnerabilities.