research-proof

Purpose

Turn research work into a proof program: define the object, freeze the verifier, seek counterexamples, and update a ledger as evidence changes. Use the Output Contract headings inside each answer, even for brief yes/no reviews. Sources inspire the method; they do not prove the claim.

Core Discipline

Start from a falsifiable proposition, not a favorite mechanism:

For domain D and baseline B, candidate family C wins only if metric M improves by delta, guardrails G stay within budget, hidden costs H are charged, and transfer test T survives.

Evidence labels: PROVEN only inside an explicit verifier; SUPPORTED for scoped evidence; REJECTED for failed gates; OPEN when untested or under-specified. Before implementation, require Claim, Verifier Boundary, Baseline / Candidate Family, Enemy Terms, and Rejection Gates; if missing, produce them first and stop planning.

Method Selection

Route by task type, then load the smallest reference that can falsify the claim.