Add SourceryKit to resources/tools.md - #21
Open
aural-psynapse wants to merge 1 commit into
Open
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
resources/tools.mdusing the repository metadata format (resource type, producer, source, relevance, coverage, maturity, last checked, limitations), with the licence and backend requirement noted honestly. Placed with the runtime controls near Adrian and Armorer Guard.SourceryKit is a source-available (BSL 1.1) Python SDK that verifies an agent's outbound requests and MCP handoffs against a source of truth using a zero-knowledge proof, so a call only goes out if the agent's claims check out. It hooks the HTTP libraries the agent uses, logs every outbound call, and blocks any endpoint not on the trusted allow-list.
Disclosure: I work with Provably, the maintainers of SourceryKit. I noted the honest limitations, that it is source-available under BSL 1.1 rather than an OSI licence, and that the proof and source-of-truth check run against a backend so it is not fully offline. If you would prefer this go through an issue-template suggestion first per CONTRIBUTING, happy to do that instead.