A model-family history is a record of related designs and their development paths. It needs branches whenever variants or upgrade programs coexist rather than replace one another in a single sequence.
Ancestry and chronology
Design ancestry asks which pattern a variant develops from. Chronology asks when development, production or fielding occurred. A later date does not establish that one model directly descended from the immediately preceding entry on a list.
The Canadian C7A2 is described as a mid-life upgrade of C7 and C7A1 variants, while C8A3 belongs to the C8 carbine’s upgrade path. Placing the names in one date-sorted list would not adequately describe those relationships.
A branching account preserves both the parent design and the event affecting it.
Upgrades within a branch
The Army’s M4-to-M4A1 improvement program began in 2011. That program milestone is distinct from the M4’s entry into service in 1994. A variant’s history therefore includes both its relationship to a predecessor and the stages of a particular implementation program.
An upgrade designation also does not establish that every earlier example was modified at once. The model relationship and the distribution of actual configurations among users require different records.
Several variants from one basis
The AK-100 family was developed from the AK-74M basis for several cartridge families. This is a branching relationship, not a claim that every later-numbered model replaced the previous one.
The AK-74’s 1974 adoption and the AK-74M’s later introduction likewise identify changes within a wider family. A family name can persist while configuration and program history change.
A usable model record
Each entry needs the model identity, its documented relationship to other models and dated events such as introduction or modification. The relationship should specify whether it concerns design ancestry, a formal upgrade or replacement in a role.
What remains common is family membership; what varies is the branch and its implementation history. This structure prevents a chronology from implying universal replacement, component interchangeability or a direct line of descent that its dates alone cannot establish.