FA-7821 / Connection lifecycle / Open access

Alt service clear removes all alternatives · case 01

Alt service clear removes all alternatives.

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

ROOT CAUSE

The faulty implementation uses `alternatives` for the alt-service-clear-removes-all-alternatives decision.

THE FAILURE

The faulty implementation uses `alternatives` for the alt-service-clear-removes-all-alternatives decision.

Unsuccessful approach: The attempted repair uses `[]` and still violates a separate fixture.

Case contract

Bounded offline decision model: alt service clear removes all alternatives. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic connection lifecycle model isolates the alt-service-clear-removes-all-alternatives 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(alternatives, clear):
    return alternatives
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
_fixtures = ["check('fixture 1', solve(['a', 'b'], True), [])", "check('fixture 2', solve(['a'], False), ['a'])", "check('fixture 3', solve([], True), [])", "check('fixture 4', solve([], False), [])"]
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 fixture	Actual	Expected	Outcome
fixture 2	`['a']`	`['a']`	Passed
fixture 3	`[]`	`[]`	Passed
fixture 4	`[]`	`[]`	Passed
fixture 1	`['a', 'b']`	`[]`	Failed

SHA-256 / ae652bde8ff6e07d17f0f76f96898aa7f0d3b80a2d70bebe60c9b18dab2e0082

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(alternatives, clear):
    return []
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
_fixtures = ["check('fixture 1', solve(['a', 'b'], True), [])", "check('fixture 2', solve(['a'], False), ['a'])", "check('fixture 3', solve([], True), [])", "check('fixture 4', solve([], False), [])"]
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 fixture	Actual	Expected	Outcome
fixture 2	`[]`	`['a']`	Failed
fixture 3	`[]`	`[]`	Passed
fixture 4	`[]`	`[]`	Passed
fixture 1	`[]`	`[]`	Passed

SHA-256 / d0a205a1426ba5aad88866b85f99e236df24e033b82f385b651662ce972792e9

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.

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:15.532071+00:00.

Case digest / 642e8d8a4e3bb1200dda1b8217299c2fdfa8df286ad715de9f84c9a8f0750094