Repository navigation
fix(validation): leave unjudged worklist validity unanswered - #295
Merged
Merged
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chubirka The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
smith-xyz
force-pushed
the
fix/unjudged-worklist-validity-qjd5zssc
branch
from
October 28, 2026 13:58
609a5a4 to
2bde499
Compare
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.
Classifier plan 05 — unjudged worklist validity
Target development, not main. Required reviewer @smith-xyz; retain the merge hold and no auto-merge.
Existing-contract repair
Cluster drift and validation-benchmark outputs are unjudged worklists, not canonical validity decisions or full modern audit reports. Omit the deprecated
validation_status: not_verifiedlabel rather than inventing confirmation/refutation or an evidence grade.cluster_state_diffcandidates.5bd3ae9b8604d72852e20014b648c388552a6159, which does the same for benchmark claims. The existing direct Core override is unchanged.Verification
sweep benchmark ... planandpython -m traust.cli.cluster_state_diff diff ...generated four benchmark claims and one drift candidate without validity labels. No cluster operation or canonical state write was performed.Scope / rollout
Merge Engine #115 first, then this adoption. This is independent of the pending finding-kind batch (Core #242/App #293); preserve both sets of pins/release metadata when reconciling parallel merges.
The finite closeout checklist separately records remaining audit-report no-answer/revision validator alignment, triage-kind representation and SDK legacy-wire owner gaps. Removing an unused worklist label does not activate a new report gate, retire historical source schemas, rewrite reports, or declare the whole validity family/plan05 closed. No vocabulary, schema, OWASP-methodology, table/column or Core decision-policy change.