FAILURE MAP
← Case archive

FA-7236 / Transport flow control / Open access

Serial distance is forward modular distance · case 01

Serial distance is forward modular distance.

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

ROOT CAUSE

The faulty implementation uses `end-start` for the serial-distance-is-forward-modular-distance decision.

THE FAILURE

The faulty implementation uses `end-start` for the serial-distance-is-forward-modular-distance decision.

Unsuccessful approach: The attempted repair uses `abs(end-start)` and still violates a separate fixture.

Case contract

Bounded offline decision model: serial distance is forward modular distance. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic transport flow control model isolates the serial-distance-is-forward-modular-distance policy at a network component boundary.

1 / The failure

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json
import ipaddress
import re
from urllib.parse import urlsplit, urljoin
N = 1
observations = []
def solve(start, end):
    return end-start
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
_fixtures = ["check('fixture 1', solve(250, 3), 9)", "check('fixture 2', solve(3, 250), 247)", "check('fixture 3', solve(10, 10), 0)", "check('fixture 4', solve(0, 1), 1)"]
for _line in _fixtures[N % len(_fixtures):] + _fixtures[:N % len(_fixtures)]:
    exec(_line)
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 2247247Passed
fixture 300Passed
fixture 411Passed
fixture 1-2479Failed

SHA-256 / 72b3d52ade77f96d7b67b9e44562fdf3a0aa71aa7aea4ea8d28e453c9eee8d03

2 / The unsuccessful fix

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json
import ipaddress
import re
from urllib.parse import urlsplit, urljoin
N = 1
observations = []
def solve(start, end):
    return abs(end-start)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
_fixtures = ["check('fixture 1', solve(250, 3), 9)", "check('fixture 2', solve(3, 250), 247)", "check('fixture 3', solve(10, 10), 0)", "check('fixture 4', solve(0, 1), 1)"]
for _line in _fixtures[N % len(_fixtures):] + _fixtures[:N % len(_fixtures)]:
    exec(_line)
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 2247247Passed
fixture 300Passed
fixture 411Passed
fixture 12479Failed

SHA-256 / 0c16e6bfa4daca2c303dfb3440547b3941bfdcdb2137266e017bb82b2fb218f4

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

Bounded deterministic policy model over validated inputs; not a complete protocol stack or an interoperability claim. The five variants rotate the same explicit fixture set. 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:38:09.770714+00:00.

Case digest / 571314e66ddc43b3f2791848e78d4adb2d8f51a67105e61ac1a16048a087e808