Repository navigation
fix(lineage): require signed TRACE evidence for authenticated verification - #198
Merged
Merged
Conversation
…ucture Signed-off-by: Imran Siddique <imran.siddique@opaque.co>
imran-siddique
requested review from
a team,
carloshvp and
zohebk8s
as code owners
September 23, 2026 22:42
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Merged
imran-siddique
added a commit
that referenced
this pull request
Sep 25, 2026
Bump ca2a-runtime from 0.2.1, which never shipped, to 0.3.0. The minor bump is for two breaking changes since 0.2.0: offline delegation verification now requires an explicit trusted root (#132), and verify-dag exits 1 on unsigned structure unless --structural-only is given (#198). Close Unreleased into 0.3.0 and add the entries it was missing: #159, #166/#167, #143, #119, #120. Point the site status line and the two example READMEs that depend on #132 and #185 at 0.3.0. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Sep 29, 2026
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.
The native
verify-dagcommand reportedverified: truefor unsigned execution histories, including substitutions whose parent hashes had been recomputed around an unchanged valid credential chain. It now reports structural consistency separately. Authenticated lineage uses the existing signed TRACE path through the newverify-lineagecommand.verify-lineagerequires a credential chain and independently configured trusted root, verifies that chain before trusting delegate keys, verifies TRACE signatures and signed parent links, then cross-checks each hop against the chain. Nativeverify-dagsuccess returnsverified: false,structural_verified: true,code: UNAUTHENTICATED_LINEAGE, and exit 1. Explicit--structural-onlypermits exit 0 for diagnostics without changing the authenticity result. Examples, ACTION fixture assertions and migration documentation reflect this intentional CLI compatibility change.Refs #168. Keep the issue open: this authenticates submitted signed declarations, not task completion, history completeness, uniqueness or continuity of a particular live request. The existing root TRACE record binds its delegate key but carries no credential ID.
--at-timecontrols credential validity/revocation, not the TRACE clock. Unsigned Python helpers keep their structural-only contract and return types. No new signature format or automatic conversion of native records is introduced.Validation: 747 unit/conformance tests passed, 2 skipped. The new 18-case suite covers valid signed paths, substituted native histories as expected refusals, CLI migration, signatures at every hop, credential mismatch, signed reparenting, untrusted roots and malformed input. Original CLI fails the native-success regression. Removing signature verification produces 3 targeted failures; removing the credential cross-check produces 1. Ruff, format checks, mypy (47 source files), Bandit and diff checks passed. Hardware paths were not exercised.
Please review the acceptance contract and compatibility change independently before merge.