docs: verify before asserting - #133
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Check it, get corroboration, and assert as fact only what that corroboration established. Anything not yet corroborated is verified before it is written, or written as an explicitly labelled hypothesis. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
toruiwasa
force-pushed
the
docs/verified-claims-rule
branch
from
September 5, 2026 10:58
fd765db to
ffb13e1
Compare
toruiwasa
changed the title
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 one bullet under Key Principles, beside Library-source-first debugging:
Stated as a positive obligation rather than a prohibition. The two are logically equivalent here, but the obligation names the action required, and it leaves labelled uncertainty available — a prohibition on unverified statements would also suppress hypotheses that are honestly marked as such, which was never the problem.
Documentation only: no code, no CI, no dependency change. Diff is one bullet.