feat: add qualified entity decision task v2 - #22
Merged
Conversation
abrichr
marked this pull request as ready for review
July 29, 2026 21:44
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
1 participant
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.
Summary
Add a signed
HumanDecisionTaskV2without changing V1. V2 binds the qualification project, revision, contract digest, and exact step to a constrained qualification-approved entity label andrecordoritemfallback.The schema has no runtime evidence, OCR, screenshots, parameter values, or model-inference fields. V2 uses a separate schema ID and HMAC domain.
Validation
PYTHONPATH="$PWD" ../../.venv/bin/python -m pytest -q(252 passed)PYTHONPATH="$PWD" ../../.venv/bin/python scripts/check_source_boundary.pyNo Flow, Cloud, or Desktop changes. No package release.