Apgar Score Reference Sheet 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

t4-275

Effect

Computation or source lookup only

Input and validation requirements

The extreme-magnitude vector exposes a likely robustness hazard: without strict 0-2 validation, plain JavaScript arithmetic produces Infinity rather than a bounded 0-10 result. The branch and convention probes also show that invalid component values and clinically interpreted color descriptions require explicit validation and rubric labeling.

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": {
    "heart_rate": 0,
    "respiration": 0,
    "muscle_tone": 0,
    "reflex": 0,
    "color": 0
  },
  "expected_outputs": {
    "total_apgar_score": 0
  },
  "working": "0 + 0 + 0 + 0 + 0 = 0"
}

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-tranche4/tranche4-results.json