Pigeonhole & Counting Principle Demonstrator 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

t6-076

Effect

Computation or source lookup only

Input and validation requirements

Invalid counts are hazardous: hole_count = 0 makes the formula undefined, and negative counts produce mathematically computable but physically meaningless results unless explicit input validation rejects them.

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": {
    "mode": "pigeonhole",
    "pigeons": 23,
    "holes": 5
  },
  "expected_outputs": {
    "guaranteed_at_least_in_one_hole": 5
  },
  "working": "Compute the average occupancy: 23 / 5 = 4.6. Round upward to the next integer: ceil(4.6) = 5. Therefore, some hole must contain at least 5 pigeons."
}

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