Add SourceryKit to Provenance, Instrumentation & Observability - #17
Open
aural-psynapse wants to merge 1 commit into
Open
Add SourceryKit to Provenance, Instrumentation & Observability#17aural-psynapse wants to merge 1 commit into
aural-psynapse wants to merge 1 commit into
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.
Adds SourceryKit to the Provenance, Instrumentation & Observability table, next to the policy/attestation tools like aflock and cupcake.
SourceryKit is a source-available (BSL 1.1) Python SDK plus a hosted gateway that verifies an agent's outbound HTTP requests and MCP tool calls against a source of truth using zero-knowledge proofs, so a call only goes out if its claims check out. It allow-lists trusted endpoints and logs every outbound call for provenance. The proof and source-of-truth check run against a backend, so it pairs a source-available SDK with a hosted service rather than running fully offline.
Disclosure: I work with Provably, who builds it.
Thanks for the list, the keyword taxonomy makes it easy to compare approaches.