Hypothesis

A hypothesis is a falsifiable claim about what should happen and why. It should be written before running the experiment.

A useful form is:

where is a metric, is the evaluation split, and is the minimum effect size that would matter.

Hypothesis Shape

Use a hypothesis to bind mechanism, intervention, evidence, and decision:

FieldQuestion
MechanismWhy should the change help?
Changed variableWhat exactly differs from the baseline?
BaselineWhat is the current reference system?
MetricWhat observable will judge the claim?
SplitWhere is the claim tested?
ThresholdHow large must the effect be to matter?
Failure conditionWhat result would make the hypothesis weaker or false?

Prediction Before Running

Before running, write the expected direction and failure mode.

PredictionExample
positivemetric improves by at least on the target split
nullchange does not move the metric beyond noise
negativemetric worsens, instability increases, or compute cost dominates
diagnosticimprovement appears only on an easy split or disappears under leakage checks

The prediction matters because it prevents a result from being reinterpreted after the fact.

Requirements

  • It names the baseline.
  • It names the metric and split.
  • It states a threshold for success.
  • It isolates one changed variable.
  • It can fail.
  • It states the expected failure mode.
  • It separates primary metric from diagnostics.
  • It names the dataset or benchmark version at the right level of precision.

Claim Strength

The same hypothesis can support different claims depending on the evidence.

EvidenceSupported Claim
small sanity runimplementation or mechanism is plausible
controlled ablationone component likely matters under that protocol
repeated seedseffect is less likely to be noise
stronger splitclaim may generalize beyond near duplicates
external benchmarkclaim may transfer to another data source

Do not write a broad claim if the hypothesis only tests a narrow split, small subset, or diagnostic condition.

Anti-Patterns

  • Writing the hypothesis after seeing results.
  • Changing the metric or threshold after the run.
  • Reporting only the best seed or checkpoint.
  • Combining multiple changes and claiming causality.
  • Treating a leaky split as evidence.
  • Confusing an engineering fix with a scientific mechanism.
  • Treating a negative result as useless instead of narrowing the hypothesis.