CV Recipe Transfer

Port published CV work onto customer data without inheriting the silent bugs that make the resulting numbers meaningless.

The core idea

This work splits into two phases with fundamentally different epistemic status:

• Phase A (Port) — get the official code running faithfully. There is external ground truth here: the authors' released checkpoint and reported number.
• Phase B (Transfer) — move the recipe onto customer data. There is no external ground truth. The paper's number stops being meaningful the moment the dataset changes.

Everything verifiable must be verified in Phase A, because the safety net disappears at the boundary. Once you are in Phase B, an implementation bug and a genuine domain mismatch produce identical symptoms: a mediocre number with a clean-looking loss curve.

Two consequences that drive everything below: