The number that changed its meaning

Create an input contract with units and a missing-data policy. Supply at least one valid and two invalid cases.

Hypothesis and criterion

Name the expected effect, metric and what would count against the hypothesis.

Method and reproducibility

Record fixtures, source, version, parameters, units, controls and how cases are split.

Paired evidence

Case and split Baseline result Changed result Interpretation

Counterexample and revised design

A double conversion produces valid numbers but incorrect meaning, so simply adding a conversion step is insufficient.

Record your new case and rerun the original cases after redesign.

Individual defence

Explain the mechanism, one exact result and what would overturn your conclusion.

Remaining uncertainty and handover

A contract prevents these declared errors only; acceptable conversions must be designed explicitly.

Next test: _ . Project filename: _ . Work that is mine and tools I used: ____ .

Keep your work

Use fictional data. Download a resumable project before changing devices. On a shared device, turn remembering off and clear your work when finished.