Allele/Genotype Frequency from Pedigree Counts implementation

Binding contract

This record describes what an executable surface must bind and validate. It does not claim that a public calculator, package, or production route is deployed.

Record owner

Guth Instruments

Lifecycle

verified-clean

Evidence ID

t5-133

Effect

Computation or source lookup only

Input and validation requirements

The N=0 vector produces a 0/0 division and all downstream outputs are undefined; the instrument must reject it. The convention probe also exposes an unvalidated mismatch between supplied N and the sum of genotype counts.

Required corrections

No binding erratum is attached to this unique-name record. Implementers must still preserve the declared units, domain, and failure behavior.

Inspectable interface fixture

The sample below is evidence for interface and validation tests, not a production implementation.

{
  "inputs": {
    "AA": 36,
    "Aa": 48,
    "aa": 16,
    "N": 100
  },
  "expected_outputs": {
    "p": 0.6,
    "q": 0.4,
    "expected_AA": 36,
    "expected_Aa": 48,
    "expected_aa": 16
  },
  "working": "Check N: 36+48+16=100. A-allele count = 2×36+48=72+48=120. Total allele count = 2×100=200. p=120/200=0.6. q=1−0.6=0.4. HWE expected_AA=100×0.6²=100×0.36=36. expected_Aa=2×100×0.6×0.4=200×0.24=48. expected_aa=100×0.4²=100×0.16=16."
}

Other records

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• VERIFIED_LEDGER.json
• evidence-tranche5/tranche5-results.json