Add grounded (grounding-enforcement guardrail plugin)#293
Open
Hyde (hyde0395) wants to merge 1 commit into
Open
Add grounded (grounding-enforcement guardrail plugin)#293Hyde (hyde0395) wants to merge 1 commit into
Hyde (hyde0395) 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 grounded to Code Quality & Testing.
grounded is a Claude Code plugin that deterministically blocks agent actions that lack evidence — editing files never read this session, installing packages that don't exist on npm/PyPI/crates.io (19.7% of LLM-recommended packages don't exist per a USENIX Security 2025 study), and citing dead URLs. PostToolUse hooks accrue evidence into a local ledger; PreToolUse hooks demand it before acting. No LLM in the judgment path, Python stdlib only, MIT, 200+ offline tests, demo GIF of a real blocked session in the README.
Checklist per contributing guidelines: real use case (hallucinated installs / blind edits), no duplicate of existing entries (closest is lint/review tooling — grounded gates actions at runtime instead), tested (203-test suite + live plugin-mode verification).