docs: add tomevault-io/ai-catalog-reference to implementations#90
Open
olijboyd wants to merge 1 commit into
Open
docs: add tomevault-io/ai-catalog-reference to implementations#90olijboyd wants to merge 1 commit into
olijboyd wants to merge 1 commit into
Conversation
Signed-off-by: Oli Boyd <oli@tomevault.io>
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 TomeVault's implementation to the list.
Apache-2.0, Python, covering the Trust Manifest layer: detached EdDSA JWS over JCS, subject binding, identity anchoring, freshness, and SSRF-safe fetch. It also ships a vector suite that runs the ADR-0009 substitution attack both ways, so the subject binding can be checked against running code rather than read in prose.
Disclosure: I work on TomeVault, where we find what has gone wrong in a team's AI instruction files, sign the corrected version, and keep watching for the next time it drifts. We do that across every tool and format, since no vendor checks another's, which is why a shared trust layer matters to us and why this exists.
Docs only, no specification text changed.