docs(readme): lead with safety, not crypto#41
Merged
Conversation
🔒 Permission Protocol✅ Safe to merge — Pure documentation update focusing on product positioning and safety framing. What changed: README content updated to prioritize safety-first messaging and include a failure-modes matrix. 🟢 Approve this deploy →🔒 Permission Protocol · Pricing |
cgoldber82
force-pushed
the
docs/readme-safety-lead-20260430-1701
branch
from
10a7056 to
e12a398
Compare
|
✅ Permission Protocol: Approved |
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.
Rewrites the README to lead with safety/consequence framing (Safety > Crypto) per the Chad Bayer signal. Adds failure-modes matrix for v2. Spec: pp-os/specs/external-fix-05-readme-positioning.md