From bb53dfea9d723f1d14391bf8f5fde51af7fc5ba0 Mon Sep 17 00:00:00 2001 From: Vinta Chen Date: Sat, 15 Aug 2026 23:31:34 +0800 Subject: [PATCH] docs: require live verification of keep/drop reasons Qualitative keep/drop reasoning previously relied on training-data recollections that went unverified while only download numbers were checked live, as happened in the Data & Science preview. Key Rules now require every keep/drop reason to be verified against current online data at decision time. Co-Authored-By: Claude --- CLAUDE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CLAUDE.md b/CLAUDE.md index 402cf791..a951543b 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -28,4 +28,5 @@ An opinionated list of Python frameworks, libraries, tools, and resources. Publi - A shortlist, not a catalog: per use case, up to 3 obvious choices plus up to 2 challengers, hard maximum 5. - One project per PR. - One entry per commit when adding or deleting entries. Exception: a prune sweep is one commit per section, its body listing each removal with its reason. Format, wording, or categorization changes across multiple entries may be bundled in a single commit. +- Every keep/drop reason must be verified against current online data at decision time — download counts, repo activity and archived status, PyPI metadata, project docs. Training-data recollections alone are not evidence; verify before stating, and label anything unverifiable as a judgment call. - README.md is the single source of content truth.