domains / families / research / colm-reproducibility

colm-reproducibility

separate

Use when hardening a COLM paper's reproducibility story — pinning open-weight checkpoints and tokenizers, handling API-model drift and deprecation honestly, versioning evaluation harnesses and prompts, disclosing compute, and writing availability statements that distinguish what is releasable from what is not.

When to use

• pinning open-weight checkpoints and tokenizers
• handling API-model drift and deprecation
• versioning evaluation harnesses and prompts
• disclosing compute and cost
• writing availability statements
• reporting training recipes
• pre-submission reproducibility audit

Skill page

Source