FAILURE MAP
← Case archive

FA-5706 / Combinatorics / Open access

Birthday distinct assignments · case 01

Colliding assignments remain in the sample count.

Verified by executionVariant 1 · 4 checks per implementationDownload source bundle ↓JSON ↗

ROOT CAUSE

Colliding assignments remain in the sample count.

THE FAILURE

Colliding assignments remain in the sample count.

Unsuccessful approach: People identities are lost by unordered day selection.

Case contract

Nonnegative integer counts. Permutation and combination counts are zero when a requested selection exceeds the available objects. Shape sizes satisfy the preconditions stated below. Birthday distinct assignments. Exact operational definition: math.perm(days,people)

Why this case matters

Small exact fixtures expose this error without platform timing, external services, or probabilistic observations. Combinatorics results depend on the stated convention.

1 / The failure

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json
import math
import calendar
import statistics
import itertools
from fractions import Fraction
from datetime import date, datetime, timedelta, timezone
from decimal import Decimal, ROUND_HALF_UP, ROUND_DOWN, ROUND_CEILING, ROUND_FLOOR

N = 1
observations = []
def solve(people, days):
    return days**people
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('fixture 1: (2, 4)', solve(*(2, 4)), 12)
check('fixture 2: (3, 3)', solve(*(3, 3)), 6)
check('fixture 3: (0, 5)', solve(*(0, 5)), 1)
check('fixture 4: (4, 3)', solve(*(4, 3)), 0)
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
Boundary fixtureActualExpectedOutcome
fixture 1: (2, 4)1612Failed
fixture 2: (3, 3)276Failed
fixture 3: (0, 5)11Passed
fixture 4: (4, 3)810Failed

SHA-256 / 2d939f356aec8210b970ed3ab81f3059267f0e2e5d6a7bc7a8d4370cbbd8bc90

2 / The unsuccessful fix

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json
import math
import calendar
import statistics
import itertools
from fractions import Fraction
from datetime import date, datetime, timedelta, timezone
from decimal import Decimal, ROUND_HALF_UP, ROUND_DOWN, ROUND_CEILING, ROUND_FLOOR

N = 1
observations = []
def solve(people, days):
    return math.comb(days,people)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('fixture 1: (2, 4)', solve(*(2, 4)), 12)
check('fixture 2: (3, 3)', solve(*(3, 3)), 6)
check('fixture 3: (0, 5)', solve(*(0, 5)), 1)
check('fixture 4: (4, 3)', solve(*(4, 3)), 0)
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
Boundary fixtureActualExpectedOutcome
fixture 1: (2, 4)612Failed
fixture 2: (3, 3)16Failed
fixture 3: (0, 5)11Passed
fixture 4: (4, 3)00Passed

SHA-256 / e8d3875bb0f07d98c2744b4e30f5964121cbc9b280207abe730b2beebeebf275

HELD IN THE MEMBER ARCHIVE

The verified repair and its recorded checks are member-only.

This mechanism has 4 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.

Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.

Member access is invitation-based. Sign in with your invited account to inspect the repair.

Sign in to the archive ↗

Verification & scope

This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.

Observations recorded using Python 3.12.14 at 2026-09-29T14:37:52.803174+00:00.

Case digest / 20f9b21fd384a96a8b5aa67487a877b389699611ae6d5b866028d0a6fd8a077f