Make the hook trust trade-off explicit on the install card and in the README#17
Merged
Merged
Conversation
… README The context layer is truly zero-setup for anyone who clones, but the enforcement hook asks each developer to approve it once (Claude Code's own safety gate). State that plainly so an enterprise evaluator isn't surprised — and frame it as the feature it is: a cloned repo shouldn't run commands unattended, which is the exact ambient-execution risk docket exists to catch. - Site: an "One honest detail" note at the foot of the install card, separating "rules and record travel instantly" from "mechanical enforcement is one click per person." - README: the enforcement bullet is now tagged "(one-time approval per developer)" with the same precise two-layer explanation. Docs-only; 118 tests green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uc3rGARtDBoXkqMFgppaP4
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.
An enterprise evaluator reading "add it to the repo, every agent governed" deserves the precise distinction between the two layers, not a surprise on first run:
Site: a muted "One honest detail" note at the foot of the install card — rules and record travel instantly; mechanical enforcement is one click per person.
README: the enforcement bullet is tagged (one-time approval per developer) with the same two-layer explanation co-located with the claim.
Turns a potential gotcha into a trust signal. Docs-only; 118 tests green.
🤖 Generated with Claude Code
Generated by Claude Code