Pedigrees, Generations, Naming, and Release Claims
Use unambiguous pedigree and generation records while preventing names and marketing claims from exceeding the evidence.
Use unambiguous pedigree and generation records while preventing names and marketing claims from exceeding the evidence.
Core science
A pedigree records biological ancestry and mating events. A product name is not a pedigree. Generation labels must state the mating that created them: F1 and F2 describe filial generations from a defined cross; S1 describes selfed offspring from one parent; BC1 describes the first backcross to a named recurrent parent. Industry usage is inconsistent, so every project should publish its controlled definitions and never infer stability from the label alone.
Individual, family, line, clone, accession, cultivar, and seed lot are different entities. A selected F2 individual can be preserved as a clone while its F3 seed family segregates. Two seed lots with the same cross can differ because of parents, pollen contamination, harvest, storage, and sampling. Reusing a name for changed parents or unverified generations destroys traceability.
Release claims should be supported by a frozen target product profile, parent and generation records, population sizes, trial environments, laboratory methods, disease or stress tests, uniformity and stability evidence, seed quality, legal status, and known limitations. “Stable,” “IBL,” “true breeding,” “resistant,” “feminized,” “autoflower,” and lineage percentages require definitions and evidence. Corrected pedigrees and failed claims should remain in revision history rather than being silently replaced.
Why this matters in cultivation
- Assign permanent IDs before names. Link every public description to a versioned release record and retained reference material.
Measure and record
Record 1
Assign permanent IDs to lines, crosses, clones, plants, and seed lots. Record each parent and role, every mating event, generation transition, population size, selected count, seed or clone source, and any identity test used.
Record 2
Link every public or internal name to the underlying permanent ID and version. Preserve trial, laboratory, pedigree, phenotype, and release evidence separately from marketing names so renaming cannot rewrite ancestry.
Record 3
At release, document the exact claim wording, its evidence scope, generation and mating history, environments tested, known limitations, approver, date, and correction history. Update claims when evidence changes without altering the original pedigree record.
Common misconceptions
Evidence limits and uncertainty
Pedigrees document declared ancestry and mating history; they do not by themselves prove genetic identity, ownership, trait transmission, uniformity, stability, or legal status.
Release claims should be limited to the populations, environments, methods, and evidence actually evaluated. Marketing language should never silently exceed the controlled evidence record.
Check your reasoning
- For "Pedigrees, Generations, Naming, and Release Claims", which records are required to make the result traceable and decision-ready, and which missing field would most weaken the conclusion?
- A learner claims, "A name proves a cultivar is genetically distinct." Use the lesson’s science and evidence limits to explain why that claim is unreliable, then name one observation or measurement that could separate the competing explanations.
- Applied case — Assign permanent IDs before names. Link every public description to a versioned release record and retained reference material. Build a verification plan using the lesson’s record set (Permanent line/cross/clone/lot IDs; parent IDs and roles; every mating and generation; population and selected counts; seed and clone sources; identity tests; trial and laboratory evidence; name/version; claim wording and scope; corrections, approver and release date.). What would you compare before and after the action, and what result would make you revise the original interpretation?
Require lesson-specific evidence, not memorized universal targets. Open the rationales after you have written or discussed your own answer.
Answer rationale 1: Mechanism / workflow rationale
- A strong answer should connect the response to the lesson objective: Use unambiguous pedigree and generation records while preventing names and marketing claims from exceeding the evidence.
- A pedigree records biological ancestry and mating events. A product name is not a pedigree. Generation labels must state the mating that created them: F1 and F2 describe filial generations from a defined cross; S1 describes selfed offspring from one parent; BC1 describes the first backcross to a named recurrent parent. Industry usage is inconsistent, so every project should publish its controlled definitions and never infer stability from the label alone.
- Individual, family, line, clone, accession, cultivar, and seed lot are different entities. A selected F2 individual can be preserved as a clone while its F3 seed family segregates. Two seed lots with the same cross can differ because of parents, pollen contamination, harvest, storage, and sampling. Reusing a name for changed parents or unverified generations destroys traceability.
- The most useful verification evidence includes Assign permanent IDs to lines, crosses, clones, plants, and seed lots. Record each parent and role, every mating event, generation transition, population size, selected count, seed or clone source, and any identity test used..
- Keep this limit explicit: Pedigrees document declared ancestry and mating history; they do not by themselves prove genetic identity, ownership, trait transmission, uniformity, stability, or legal status.
Answer rationale 2: Misconception rationale
- The shortcut is unreliable because the lesson explicitly teaches a more conditional explanation.
- Representative misconception: A name proves a cultivar is genetically distinct. Names are administrative or commercial identifiers unless supported by genetic, pedigree, or phenotypic evidence.
- A pedigree records biological ancestry and mating events. A product name is not a pedigree. Generation labels must state the mating that created them: F1 and F2 describe filial generations from a defined cross; S1 describes selfed offspring from one parent; BC1 describes the first backcross to a named recurrent parent. Industry usage is inconsistent, so every project should publish its controlled definitions and never infer stability from the label alone.
- A useful discriminator is Link every public or internal name to the underlying permanent ID and version. Preserve trial, laboratory, pedigree, phenotype, and release evidence separately from marketing names so renaming cannot rewrite ancestry..
- Do not overextend the conclusion beyond this limit: Pedigrees document declared ancestry and mating history; they do not by themselves prove genetic identity, ownership, trait transmission, uniformity, stability, or legal status.
Answer rationale 3: Applied verification rationale
- In practice: Assign permanent IDs before names. Link every public description to a versioned release record and retained reference material.
- Record before action: Assign permanent IDs to lines, crosses, clones, plants, and seed lots. Record each parent and role, every mating event, generation transition, population size, selected count, seed or clone source, and any identity test used..
- Also record: Link every public or internal name to the underlying permanent ID and version. Preserve trial, laboratory, pedigree, phenotype, and release evidence separately from marketing names so renaming cannot rewrite ancestry..
- After the action, repeat the same measurement or observation so the comparison is valid.
- Revise the interpretation if the result conflicts with the lesson limit or the expected response: Pedigrees document declared ancestry and mating history; they do not by themselves prove genetic identity, ownership, trait transmission, uniformity, stability, or legal status.
Related lessons
Sources and evidence
- Sawler et al. 2015 — The Genetic Structure of Marijuana and HempV20-SRC-008
Genome-wide differentiation and limitations of commercial strain ancestry labels.
- Lynch et al. 2025 — Cannabis pangenomeV20-SRC-010
Structural variation, population mosaic, sex chromosomes, and cannabinoid synthase diversity; research genomes do not replace line-specific testing.
- Developing and Testing Molecular Markers in Cannabis, 2021V20-SRC-013
SSR marker development, variety discrimination, diversity, and dioecy assessment; marker panels have population limits.
- FAO Genebank Standards for Plant Genetic ResourcesV20-SRC-030
Acquisition, drying, storage, viability monitoring, regeneration, documentation, safety duplication, and security benchmarks.
- Current cultivar, seed, intellectual-property, phytosanitary, and cannabis rulesV20-SRC-034
Naming, release, ownership, seed movement, testing, and legal status are jurisdiction- and date-specific.
Release-date jurisdictional review required
Downloads
No lesson-specific download is approved for this release. Use browser print/save-to-PDF when you need an offline reading copy.