Preserve verified ontology read-back in finality receipts - #572
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.
A maintained-brief edit could pass the governed content and singleton checks, persist a succeeded receipt, and still be described by the final response as unverified. Preserve the exact verifier's result as the existing
verified/statusread-back contract so evidence projection and finality report the saved edit correctly.The flag is emitted only when the postcondition verifier runs. Contradictions and verifier exceptions remain unverified; previews and calls without a verifier gain no proof. No authority decision or domain-completion criterion changes.
Validation: 93 targeted authority, role and maintained-text tests pass; the ordinary editor test exercises the actual evidence projection and finality report, including idempotent replay. Ruff and diff checks pass. The observed EnvHarness encounter still has a pending domain workflow; fixing the brief receipt does not certify that paper or activate a schedule.
Tracks JVNAUTOSCI-2244 and the continuing-responsibility encounter under JVNAUTOSCI-2721.