feat: UEC as source of truth and adapter compliance - #18
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
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
This PR makes the UEC ExecutionEnvelope the single source of truth for comparing and verifying runs across all supported SDKs. It introduces a clean split between structural and parametric program hashes, canonicalizes measurement keys across bit orders, removes the legacy strict mode, and enforces a production-grade rule: adapter runs must always emit a valid envelope, while manual/replay runs can have an envelope synthesized from run artifacts. This prevents “silent” fallbacks that mask adapter bugs and makes diffs stable and comparable across SDKs.
Type of change
Changelog
changelog.d/Checklist
uv run pre-commit run --all-files)uv run pytest)uv.lock(uv lock) and committed it