README: the falsification test moves out of public view - #10
Merged
Danny-Devs merged 1 commit intoAug 16, 2026
Merged
Conversation
Danny's call, 2026-08-16, same day it shipped: "Why would you be so public with what would prove this should stop section? That should be in private." He is right, and the convention that put it there was under-specified. A falsification test exists so a project's own goal is written down and checkable against evidence — that is an internal control. Publishing it to competitors, grant reviewers and prospective implementers is a different act with none of the same benefit: the four conditions named there read to an outside reader as reasons not to adopt, well before any of them is true. "Who this is for / not for" STAYS. That half serves a stranger deciding whether s402 fits, including saying plainly that EVM-only users wanting `exact` should use x402. That is the part a public README owes a reader. The removed text is retained verbatim, in full, at core/projects/s402-project/FALSIFICATION-PRIVATE.md in Danny's workspace. It is not deleted and it is not softened — it is relocated. CHANGELOG's [Unreleased] entry is corrected to match, rather than shipping a release note describing a section that no longer exists. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Danny-Devs
deleted the
joseph/DAN-855-followup-falsification-goes-private
branch
August 16, 2026 23:31
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.
Follow-up to #6, same day, on Danny's explicit call: the What Would Prove This Should Stop section is removed from the public README and retained privately in full.
A falsification test is an internal control — it exists so the project's own goal is written down and checkable against evidence. Published, it has none of that benefit and a real cost: to an outside reader the four conditions read as reasons not to adopt, long before any of them is true.
Kept: Who This Is For / Do not use s402 if… — that half serves a stranger deciding whether s402 fits, and it still says plainly that EVM-only users wanting
exactshould use x402.Not deleted, relocated. The text is retained verbatim in Danny's workspace at
core/projects/s402-project/FALSIFICATION-PRIVATE.md.[Unreleased]in the CHANGELOG is corrected so the release note does not describe a section that no longer exists.🤖 Generated with Claude Code