review-prooflisted

# Review Proof Enforce a discipline: every factual claim must cite its primary source before being stated. No assumptions, no "I believe", no guessing from memory. ## When to use - Debugging: "what is actually happening" vs "what I assume is happening" - Architecture questions: "does module X actually depend on Y?" - Audits: "which tests cover this behavior?" or "is this flag used anywhere?" - Any time the user says "prove it", "are you sure?", "verify that", or "check" - Pre-commit sanity checks on claims made during a session ## Rules ### 1. Claim requires source Obtain the primary source BEFORE stating any factual claim about the codebase, configuration, or runtime behavior: | Claim type | Required source | |---|---| | "Function X does Y" | Read the function, cite file:line | | "Module A imports B" | Grep for the import, cite file:line | | "This config enables Z" | Read the config file, cite the key | | "Test T covers behavior B" | Read the test, cite the assertion | | "Command C produces output O" | Run the command, show the output | | "File F exists" | Glob or ls, show the match | | "Error E happens because" | Read the traceback or log, cite it | | "X is unused" | Grep for all references, show zero matches | Apply this discipline to factual claims about the codebase, configuration, runtime behavior, command output, and historical events. It does NOT apply to opinions, recommendations, design preferences, or future-state descriptions — those are not falsifiable by