Repository navigation
litzki-systems-sovp: update listing to bridge 0.2.0 - #295
Merged
imran-siddique merged 1 commit intoOct 12, 2026
Merged
Conversation
Bump the pinned release to litzki-sovp-agentrust-bridge 0.2.0 (commit 935ace0), tested_against agentrust-trace 0.11.0 / agentrust-trace-tests 0.6.2, describe the new references entry that binds a record to the SOVP verdict document by digest, and link the evidence boundary page. The maintainer reproduction of 0.1.1 stays stated as such; 0.2.0 awaits re-review. Signed-off-by: Thorsten Litzki <268185082+litzki-systems@users.noreply.github.com>
litzki-systems
requested review from
a team,
carloshvp and
imran-siddique
as code owners
October 11, 2026 19:32
imran-siddique
approved these changes
Oct 12, 2026
imran-siddique
left a comment
imran-siddique
left a comment
Member
There was a problem hiding this comment.
Reproduced 0.2.0 from the README's "Run it" block in a fresh Windows Python 3.12 venv with the pinned PyPI releases: trace-tests verify --level 0 reports PASS (15 checks, 3 skipped) with TR-SIG "Ed25519 signature verified", and references[0].digest matches an independent recomputation, sha256:cc57734e…. Replacing that digest in the signed record fails TR-SIG, so the pointer is covered by the signature as §3.1.2 rule 2 requires.
infrastructure-trust is not a registered rel; §3.1.2 allows that. The red links check is a 503 from img.shields.io in examples/README.md, outside this PR.
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
2 participants
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.
Updates the litzki-systems-sovp listing to release 0.2.0 of the bridge (PyPI
litzki-sovp-agentrust-bridge0.2.0, commit935ace0).What changed in the bridge:
referencesentry (TRACE v0.2 §3.1.2):rel: infrastructure-trust,resolver: urn:sovp:litzki-systems-llc, and a SHA-256 digest over the RFC 8785 bytes of the whole document. The entry is a pointer, not evidence, and changes no assurance field. Level 0 stays the ceiling.What changed in this listing:
tested_against: agentrust-trace 0.11.0, agentrust-trace-tests 0.6.2 (the latest releases). The bridge CI also runs against 0.10.0 / 0.5.1, where the same record passes 8/8.935ace0and adds a one-line digest recomputation.Checks run locally:
scripts/validate_integrations.py(0 failures),scripts/generate_marketplace_catalog.py --check(current), and the schema tests.@imran-siddique, could you re-run the reproduction against 0.2.0 when you have a moment? Same steps as for #217, with the "Run it" block in the README. Happy to adjust anything in the listing.