What Makes a Self-Improvement Artifact Transfer?

Answer to the transfer question left open by the HarnessBank/Caltech contradiction: an artifact transfers exactly as far as the regularity it encodes extends — solver-fitted artifacts (harness patches, verification instructions, model-per-role combos) reach only solvers sharing the pathology and depreciate on every release, domain-fitted artifacts (distilled knowledge, repo conventions, skills) survive solver churn because reuse holds the domain fixed; cross-model transplant failure and cross-release depreciation are one phenomenon, transferability can be selected for at write time (Caltech's schemas), and what transfers when the artifact doesn't is the procedure