Recording genetics and lineage safely
Preserve what is known, what is possible, and what remains unproven so breeding calculations and lineage review do not present uncertain information as fact.
Before you begin
- The animal and species are correctly identified.
- The relevant trait exists in the species genetics catalog or has a documented review path.
- You have evidence for visual, homozygous, heterozygous, possible-het, sex-linked, or lineage claims.
- Sire and dam records exist when relationships will be connected.
Interface walkthrough
These annotated interface maps describe the current PMA controls. They do not replace a real record review in your workspace.
Use readable source wording for identification, but do not assume every word has been converted into structured inheritance evidence.
Choose the exact state supported by evidence. Preserve possible-het probability and unproven status.
Connect actual animal records only. Similar names, matching morphs, or source-row proximity are not sufficient evidence.
PMA keeps one genetic definition per combination signature. Historical nicknames remain searchable as aliases when they describe the same genotype.
Step-by-step workflow
Preserve the source description
Record the morph or genetics wording supplied by the breeder, prior system, or evidence source without rewriting uncertainty away.
Resolve supported traits
Select canonical traits and aliases from the correct species catalog. Leave unsupported or ambiguous notation in review.
Choose the inheritance state
Distinguish visual, heterozygous, possible heterozygous, homozygous or super, and other supported states.
Record probability and proof
Preserve possible-het percentages and whether a state is reported, inferred, proven by breeding, or otherwise verified.
Connect sire and dam deliberately
Select the exact parent records and review duplicates before saving. Leave the relationship blank when evidence is insufficient.
Review calculator eligibility
Only structured, supported inheritance evidence should enter deterministic genetics calculations. Resolve warnings before relying on results.
Understand designer definitions
A designer definition can be an established special name such as Dreamsicle or a canonical component combination such as Pastel Enchi Clown. The displayed name never replaces the underlying loci used by the calculator.
Update evidence without erasing history
When a trait becomes proven, add the new evidence and preserve the earlier uncertainty in history or notes.
Expected result
The animal retains readable genetics and lineage information while PMA clearly distinguishes confirmed structured evidence from reported, possible, ambiguous, or unsupported claims.
Safety boundaries
- Never convert possible het to proven het without evidence.
- Never invent sire or dam relationships.
- Do not merge animals by name alone.
- Unsupported notation must not be treated as calculator-ready.
- Probability results are inheritance models, not guarantees of individual offspring.
Troubleshooting
The morph name is not recognized
Check aliases and species catalog. Keep the source text and request or create a reviewed definition rather than selecting a different trait.
Two names appear to describe the same genetics
PMA normalizes component order and uses one canonical combination signature. A second established name should be retained as an alias instead of a duplicate calculator definition.
The calculator blocks results
Open the unresolved-genetics review and confirm each unsupported or ambiguous item. Removing a warning without resolving the evidence is not a safe fix.
A parent cannot be selected
Confirm the parent exists in the same organization, is not an accidental duplicate, and has the correct sex or relationship context.